2317 lines
106 KiB
HTML
2317 lines
106 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||
|
|
<head>
|
||
|
|
<!-- 2020-01-11 sam. 21:59 -->
|
||
|
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||
|
|
<title>Dunst (Notification Manager)</title>
|
||
|
|
<meta name="generator" content="Org mode" />
|
||
|
|
<meta name="author" content="Dehaeze Thomas" />
|
||
|
|
<style type="text/css">
|
||
|
|
<!--/*--><![CDATA[/*><!--*/
|
||
|
|
.title { text-align: center;
|
||
|
|
margin-bottom: .2em; }
|
||
|
|
.subtitle { text-align: center;
|
||
|
|
font-size: medium;
|
||
|
|
font-weight: bold;
|
||
|
|
margin-top:0; }
|
||
|
|
.todo { font-family: monospace; color: red; }
|
||
|
|
.done { font-family: monospace; color: green; }
|
||
|
|
.priority { font-family: monospace; color: orange; }
|
||
|
|
.tag { background-color: #eee; font-family: monospace;
|
||
|
|
padding: 2px; font-size: 80%; font-weight: normal; }
|
||
|
|
.timestamp { color: #bebebe; }
|
||
|
|
.timestamp-kwd { color: #5f9ea0; }
|
||
|
|
.org-right { margin-left: auto; margin-right: 0px; text-align: right; }
|
||
|
|
.org-left { margin-left: 0px; margin-right: auto; text-align: left; }
|
||
|
|
.org-center { margin-left: auto; margin-right: auto; text-align: center; }
|
||
|
|
.underline { text-decoration: underline; }
|
||
|
|
#postamble p, #preamble p { font-size: 90%; margin: .2em; }
|
||
|
|
p.verse { margin-left: 3%; }
|
||
|
|
pre {
|
||
|
|
border: 1px solid #ccc;
|
||
|
|
box-shadow: 3px 3px 3px #eee;
|
||
|
|
padding: 8pt;
|
||
|
|
font-family: monospace;
|
||
|
|
overflow: auto;
|
||
|
|
margin: 1.2em;
|
||
|
|
}
|
||
|
|
pre.src {
|
||
|
|
position: relative;
|
||
|
|
overflow: visible;
|
||
|
|
padding-top: 1.2em;
|
||
|
|
}
|
||
|
|
pre.src:before {
|
||
|
|
display: none;
|
||
|
|
position: absolute;
|
||
|
|
background-color: white;
|
||
|
|
top: -10px;
|
||
|
|
right: 10px;
|
||
|
|
padding: 3px;
|
||
|
|
border: 1px solid black;
|
||
|
|
}
|
||
|
|
pre.src:hover:before { display: inline;}
|
||
|
|
/* Languages per Org manual */
|
||
|
|
pre.src-asymptote:before { content: 'Asymptote'; }
|
||
|
|
pre.src-awk:before { content: 'Awk'; }
|
||
|
|
pre.src-C:before { content: 'C'; }
|
||
|
|
/* pre.src-C++ doesn't work in CSS */
|
||
|
|
pre.src-clojure:before { content: 'Clojure'; }
|
||
|
|
pre.src-css:before { content: 'CSS'; }
|
||
|
|
pre.src-D:before { content: 'D'; }
|
||
|
|
pre.src-ditaa:before { content: 'ditaa'; }
|
||
|
|
pre.src-dot:before { content: 'Graphviz'; }
|
||
|
|
pre.src-calc:before { content: 'Emacs Calc'; }
|
||
|
|
pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
|
||
|
|
pre.src-fortran:before { content: 'Fortran'; }
|
||
|
|
pre.src-gnuplot:before { content: 'gnuplot'; }
|
||
|
|
pre.src-haskell:before { content: 'Haskell'; }
|
||
|
|
pre.src-hledger:before { content: 'hledger'; }
|
||
|
|
pre.src-java:before { content: 'Java'; }
|
||
|
|
pre.src-js:before { content: 'Javascript'; }
|
||
|
|
pre.src-latex:before { content: 'LaTeX'; }
|
||
|
|
pre.src-ledger:before { content: 'Ledger'; }
|
||
|
|
pre.src-lisp:before { content: 'Lisp'; }
|
||
|
|
pre.src-lilypond:before { content: 'Lilypond'; }
|
||
|
|
pre.src-lua:before { content: 'Lua'; }
|
||
|
|
pre.src-matlab:before { content: 'MATLAB'; }
|
||
|
|
pre.src-mscgen:before { content: 'Mscgen'; }
|
||
|
|
pre.src-ocaml:before { content: 'Objective Caml'; }
|
||
|
|
pre.src-octave:before { content: 'Octave'; }
|
||
|
|
pre.src-org:before { content: 'Org mode'; }
|
||
|
|
pre.src-oz:before { content: 'OZ'; }
|
||
|
|
pre.src-plantuml:before { content: 'Plantuml'; }
|
||
|
|
pre.src-processing:before { content: 'Processing.js'; }
|
||
|
|
pre.src-python:before { content: 'Python'; }
|
||
|
|
pre.src-R:before { content: 'R'; }
|
||
|
|
pre.src-ruby:before { content: 'Ruby'; }
|
||
|
|
pre.src-sass:before { content: 'Sass'; }
|
||
|
|
pre.src-scheme:before { content: 'Scheme'; }
|
||
|
|
pre.src-screen:before { content: 'Gnu Screen'; }
|
||
|
|
pre.src-sed:before { content: 'Sed'; }
|
||
|
|
pre.src-sh:before { content: 'shell'; }
|
||
|
|
pre.src-sql:before { content: 'SQL'; }
|
||
|
|
pre.src-sqlite:before { content: 'SQLite'; }
|
||
|
|
/* additional languages in org.el's org-babel-load-languages alist */
|
||
|
|
pre.src-forth:before { content: 'Forth'; }
|
||
|
|
pre.src-io:before { content: 'IO'; }
|
||
|
|
pre.src-J:before { content: 'J'; }
|
||
|
|
pre.src-makefile:before { content: 'Makefile'; }
|
||
|
|
pre.src-maxima:before { content: 'Maxima'; }
|
||
|
|
pre.src-perl:before { content: 'Perl'; }
|
||
|
|
pre.src-picolisp:before { content: 'Pico Lisp'; }
|
||
|
|
pre.src-scala:before { content: 'Scala'; }
|
||
|
|
pre.src-shell:before { content: 'Shell Script'; }
|
||
|
|
pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
|
||
|
|
/* additional language identifiers per "defun org-babel-execute"
|
||
|
|
in ob-*.el */
|
||
|
|
pre.src-cpp:before { content: 'C++'; }
|
||
|
|
pre.src-abc:before { content: 'ABC'; }
|
||
|
|
pre.src-coq:before { content: 'Coq'; }
|
||
|
|
pre.src-groovy:before { content: 'Groovy'; }
|
||
|
|
/* additional language identifiers from org-babel-shell-names in
|
||
|
|
ob-shell.el: ob-shell is the only babel language using a lambda to put
|
||
|
|
the execution function name together. */
|
||
|
|
pre.src-bash:before { content: 'bash'; }
|
||
|
|
pre.src-csh:before { content: 'csh'; }
|
||
|
|
pre.src-ash:before { content: 'ash'; }
|
||
|
|
pre.src-dash:before { content: 'dash'; }
|
||
|
|
pre.src-ksh:before { content: 'ksh'; }
|
||
|
|
pre.src-mksh:before { content: 'mksh'; }
|
||
|
|
pre.src-posh:before { content: 'posh'; }
|
||
|
|
/* Additional Emacs modes also supported by the LaTeX listings package */
|
||
|
|
pre.src-ada:before { content: 'Ada'; }
|
||
|
|
pre.src-asm:before { content: 'Assembler'; }
|
||
|
|
pre.src-caml:before { content: 'Caml'; }
|
||
|
|
pre.src-delphi:before { content: 'Delphi'; }
|
||
|
|
pre.src-html:before { content: 'HTML'; }
|
||
|
|
pre.src-idl:before { content: 'IDL'; }
|
||
|
|
pre.src-mercury:before { content: 'Mercury'; }
|
||
|
|
pre.src-metapost:before { content: 'MetaPost'; }
|
||
|
|
pre.src-modula-2:before { content: 'Modula-2'; }
|
||
|
|
pre.src-pascal:before { content: 'Pascal'; }
|
||
|
|
pre.src-ps:before { content: 'PostScript'; }
|
||
|
|
pre.src-prolog:before { content: 'Prolog'; }
|
||
|
|
pre.src-simula:before { content: 'Simula'; }
|
||
|
|
pre.src-tcl:before { content: 'tcl'; }
|
||
|
|
pre.src-tex:before { content: 'TeX'; }
|
||
|
|
pre.src-plain-tex:before { content: 'Plain TeX'; }
|
||
|
|
pre.src-verilog:before { content: 'Verilog'; }
|
||
|
|
pre.src-vhdl:before { content: 'VHDL'; }
|
||
|
|
pre.src-xml:before { content: 'XML'; }
|
||
|
|
pre.src-nxml:before { content: 'XML'; }
|
||
|
|
/* add a generic configuration mode; LaTeX export needs an additional
|
||
|
|
(add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
|
||
|
|
pre.src-conf:before { content: 'Configuration File'; }
|
||
|
|
|
||
|
|
table { border-collapse:collapse; }
|
||
|
|
caption.t-above { caption-side: top; }
|
||
|
|
caption.t-bottom { caption-side: bottom; }
|
||
|
|
td, th { vertical-align:top; }
|
||
|
|
th.org-right { text-align: center; }
|
||
|
|
th.org-left { text-align: center; }
|
||
|
|
th.org-center { text-align: center; }
|
||
|
|
td.org-right { text-align: right; }
|
||
|
|
td.org-left { text-align: left; }
|
||
|
|
td.org-center { text-align: center; }
|
||
|
|
dt { font-weight: bold; }
|
||
|
|
.footpara { display: inline; }
|
||
|
|
.footdef { margin-bottom: 1em; }
|
||
|
|
.figure { padding: 1em; }
|
||
|
|
.figure p { text-align: center; }
|
||
|
|
.equation-container {
|
||
|
|
display: table;
|
||
|
|
text-align: center;
|
||
|
|
width: 100%;
|
||
|
|
}
|
||
|
|
.equation {
|
||
|
|
vertical-align: middle;
|
||
|
|
}
|
||
|
|
.equation-label {
|
||
|
|
display: table-cell;
|
||
|
|
text-align: right;
|
||
|
|
vertical-align: middle;
|
||
|
|
}
|
||
|
|
.inlinetask {
|
||
|
|
padding: 10px;
|
||
|
|
border: 2px solid gray;
|
||
|
|
margin: 10px;
|
||
|
|
background: #ffffcc;
|
||
|
|
}
|
||
|
|
#org-div-home-and-up
|
||
|
|
{ text-align: right; font-size: 70%; white-space: nowrap; }
|
||
|
|
textarea { overflow-x: auto; }
|
||
|
|
.linenr { font-size: smaller }
|
||
|
|
.code-highlighted { background-color: #ffff00; }
|
||
|
|
.org-info-js_info-navigation { border-style: none; }
|
||
|
|
#org-info-js_console-label
|
||
|
|
{ font-size: 10px; font-weight: bold; white-space: nowrap; }
|
||
|
|
.org-info-js_search-highlight
|
||
|
|
{ background-color: #ffff00; color: #000000; font-weight: bold; }
|
||
|
|
.org-svg { width: 90%; }
|
||
|
|
/*]]>*/-->
|
||
|
|
</style>
|
||
|
|
<link rel="stylesheet" type="text/css" href="../css/htmlize.css"/>
|
||
|
|
<link rel="stylesheet" type="text/css" href="../css/readtheorg.css"/>
|
||
|
|
<script type="text/javascript" src="../js/jquery.min.js"></script>
|
||
|
|
<script type="text/javascript" src="../js/bootstrap.min.js"></script>
|
||
|
|
<script type="text/javascript" src="../js/jquery.stickytableheaders.min.js"></script>
|
||
|
|
<script type="text/javascript" src="../js/readtheorg.js"></script>
|
||
|
|
<script type="text/javascript">
|
||
|
|
/*
|
||
|
|
@licstart The following is the entire license notice for the
|
||
|
|
JavaScript code in this tag.
|
||
|
|
|
||
|
|
Copyright (C) 2012-2020 Free Software Foundation, Inc.
|
||
|
|
|
||
|
|
The JavaScript code in this tag is free software: you can
|
||
|
|
redistribute it and/or modify it under the terms of the GNU
|
||
|
|
General Public License (GNU GPL) as published by the Free Software
|
||
|
|
Foundation, either version 3 of the License, or (at your option)
|
||
|
|
any later version. The code is distributed WITHOUT ANY WARRANTY;
|
||
|
|
without even the implied warranty of MERCHANTABILITY or FITNESS
|
||
|
|
FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
|
||
|
|
|
||
|
|
As additional permission under GNU GPL version 3 section 7, you
|
||
|
|
may distribute non-source (e.g., minimized or compacted) forms of
|
||
|
|
that code without the copy of the GNU GPL normally required by
|
||
|
|
section 4, provided you include this license notice and a URL
|
||
|
|
through which recipients can access the Corresponding Source.
|
||
|
|
|
||
|
|
|
||
|
|
@licend The above is the entire license notice
|
||
|
|
for the JavaScript code in this tag.
|
||
|
|
*/
|
||
|
|
<!--/*--><![CDATA[/*><!--*/
|
||
|
|
function CodeHighlightOn(elem, id)
|
||
|
|
{
|
||
|
|
var target = document.getElementById(id);
|
||
|
|
if(null != target) {
|
||
|
|
elem.cacheClassElem = elem.className;
|
||
|
|
elem.cacheClassTarget = target.className;
|
||
|
|
target.className = "code-highlighted";
|
||
|
|
elem.className = "code-highlighted";
|
||
|
|
}
|
||
|
|
}
|
||
|
|
function CodeHighlightOff(elem, id)
|
||
|
|
{
|
||
|
|
var target = document.getElementById(id);
|
||
|
|
if(elem.cacheClassElem)
|
||
|
|
elem.className = elem.cacheClassElem;
|
||
|
|
if(elem.cacheClassTarget)
|
||
|
|
target.className = elem.cacheClassTarget;
|
||
|
|
}
|
||
|
|
/*]]>*///-->
|
||
|
|
</script>
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<div id="org-div-home-and-up">
|
||
|
|
<a accesskey="h" href="./index.html"> UP </a>
|
||
|
|
|
|
||
|
|
<a accesskey="H" href="./index.html"> HOME </a>
|
||
|
|
</div><div id="content">
|
||
|
|
<h1 class="title">Dunst (Notification Manager)</h1>
|
||
|
|
<div id="table-of-contents">
|
||
|
|
<h2>Table of Contents</h2>
|
||
|
|
<div id="text-table-of-contents">
|
||
|
|
<ul>
|
||
|
|
<li><a href="#org8a20fe1">Global</a>
|
||
|
|
<ul>
|
||
|
|
<li><a href="#org1538ca5">Display</a></li>
|
||
|
|
<li><a href="#org3209801">Text</a></li>
|
||
|
|
<li><a href="#org0b3fe43">Icons</a></li>
|
||
|
|
<li><a href="#orgfccb12b">History</a></li>
|
||
|
|
<li><a href="#org4cdd8ed">Misc/Advanced</a></li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li><a href="#orga574d4b">Shortcuts</a></li>
|
||
|
|
<li><a href="#org2443a5f">Urgency</a></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div id="outline-container-org8a20fe1" class="outline-2">
|
||
|
|
<h2 id="org8a20fe1">Global</h2>
|
||
|
|
<div class="outline-text-2" id="text-org8a20fe1">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf">[<span class="org-type">global</span>]
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div id="outline-container-org1538ca5" class="outline-3">
|
||
|
|
<h3 id="org1538ca5">Display</h3>
|
||
|
|
<div class="outline-text-3" id="text-org1538ca5">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf"><span class="org-comment-delimiter"># </span><span class="org-comment">Which monitor should the notifications be displayed on.</span>
|
||
|
|
<span class="org-variable-name">monitor</span> = <span class="org-highlight-numbers-number">0</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Display notification on focused monitor. Possible modes are:</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">mouse: follow mouse pointer</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">keyboard: follow window with keyboard focus</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">none: don't follow anything</span>
|
||
|
|
<span class="org-comment-delimiter">#</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">"keyboard" needs a windowmanager that exports the</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">_NET_ACTIVE_WINDOW property.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">This should be the case for almost all modern windowmanagers.</span>
|
||
|
|
<span class="org-comment-delimiter">#</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">If this option is set to mouse or keyboard, the monitor option</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">will be ignored.</span>
|
||
|
|
<span class="org-variable-name">follow</span> = keyboard
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The geometry of the window:</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">[{width}]x{height}[+/-{x}+/-{y}]</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The geometry of the message window.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The height is measured in number of notifications everything else</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">in pixels. If the width is omitted but the height is given</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">("-geometry x2"), the message window expands over the whole screen</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">(dmenu-like). If width is 0, the window expands to the longest</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">message displayed. A positive x is measured from the left, a</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">negative from the right side of the screen. Y is measured from</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">the top and down respectevly.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The width can be negative. In this case the actual width is the</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">screen width minus the width defined in within the geometry option.</span>
|
||
|
|
<span class="org-variable-name">geometry</span> = <span class="org-string">"250x50-10+37"</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Show how many messages are currently hidden (because of geometry).</span>
|
||
|
|
<span class="org-variable-name">indicate_hidden</span> = yes
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Shrink window if it's smaller than the width. Will be ignored if</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">width is 0.</span>
|
||
|
|
<span class="org-variable-name">shrink</span> = no
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The transparency of the window. Range: [0; 100].</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">This option will only work if a compositing windowmanager is</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">present (e.g. xcompmgr, compiz, etc.).</span>
|
||
|
|
<span class="org-variable-name">transparency</span> = <span class="org-highlight-numbers-number">0</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The height of the entire notification. If the height is smaller</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">than the font height and padding combined, it will be raised</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">to the font height and padding.</span>
|
||
|
|
<span class="org-variable-name">notification_height</span> = <span class="org-highlight-numbers-number">0</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Draw a line of "separator_height" pixel height between two</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">notifications.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Set to 0 to disable.</span>
|
||
|
|
<span class="org-variable-name">separator_height</span> = <span class="org-highlight-numbers-number">4</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Padding between text and separator.</span>
|
||
|
|
<span class="org-variable-name">padding</span> = <span class="org-highlight-numbers-number">16</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Horizontal padding.</span>
|
||
|
|
<span class="org-variable-name">horizontal_padding</span> = <span class="org-highlight-numbers-number">16</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Defines width in pixels of frame around the notification window.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Set to 0 to disable.</span>
|
||
|
|
<span class="org-variable-name">frame_width</span> = <span class="org-highlight-numbers-number">2</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Defines color of the frame around the notification window.</span>
|
||
|
|
<span class="org-variable-name">frame_color</span> = <span class="org-string">"#32302f"</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Define a color for the separator.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">possible values are:</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">* auto: dunst tries to find a color fitting to the background;</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">* foreground: use the same color as the foreground;</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">* frame: use the same color as the frame;</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">* anything else will be interpreted as a X color.</span>
|
||
|
|
<span class="org-variable-name">separator_color</span> = frame
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Don't remove messages, if the user is idle (no mouse or keyboard input)</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">for longer than idle_threshold seconds.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Set to 0 to disable.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">default 120</span>
|
||
|
|
<span class="org-variable-name">idle_threshold</span> = <span class="org-highlight-numbers-number">120</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Sort messages by urgency.</span>
|
||
|
|
<span class="org-variable-name">sort</span> = yes
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div id="outline-container-org3209801" class="outline-3">
|
||
|
|
<h3 id="org3209801">Text</h3>
|
||
|
|
<div class="outline-text-3" id="text-org3209801">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf"><span class="org-variable-name">font</span> = Hack Nerd Font <span class="org-highlight-numbers-number">10</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">The height of a single line. If the height is smaller than the</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">font height, it will get raised to the font height.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">This adds empty space above and under the text.</span>
|
||
|
|
<span class="org-variable-name">line_height</span> = <span class="org-highlight-numbers-number">4</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Possible values are:</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">full: Allow a small subset of html markup in notifications:</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment"><b>bold</b></span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment"><i>italic</i></span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment"><s>strikethrough</s></span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment"><u>underline</u></span>
|
||
|
|
<span class="org-comment-delimiter">#</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">For a complete reference see</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"><http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">#</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">strip: This setting is provided for compatibility with some broken</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">clients that send markup even though it's not enabled on the</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">server. Dunst will try to strip the markup but the parsing is</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">simplistic so using this option outside of matching rules for</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">specific applications *IS GREATLY DISCOURAGED*.</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">#</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">no: Disable markup parsing, incoming notifications will be treated as</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">plain text. Dunst will not advertise that it has the body-markup</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">capability if this is set as a global setting.</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">#</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">It's important to note that markup inside the format option will be parsed</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">regardless of what this is set to.</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-variable-name"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">markup</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"> = full
|
||
|
|
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">The format of the message. Possible variables are:</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%a appname</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%s summary</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%b body</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%i iconname (including its path)</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%I iconname (without its path)</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%p progress value if set ([ 0%] to [100%]) or nothing</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">%n progress value if set without any extra characters</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-comment-delimiter"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"># </a></span><span class="org-comment"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">Markup is allowed</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">
|
||
|
|
</a><span class="org-variable-name"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">format</a></span><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b"> = </a><span class="org-string"><a href="http://developer.gnome.org/pango/stable/PangoMarkupFormat.html>.
|
||
|
|
#
|
||
|
|
# strip: This setting is provided for compatibility with some broken
|
||
|
|
# clients that send markup even though it's not enabled on the
|
||
|
|
# server. Dunst will try to strip the markup but the parsing is
|
||
|
|
# simplistic so using this option outside of matching rules for
|
||
|
|
# specific applications *IS GREATLY DISCOURAGED*.
|
||
|
|
#
|
||
|
|
# no: Disable markup parsing, incoming notifications will be treated as
|
||
|
|
# plain text. Dunst will not advertise that it has the body-markup
|
||
|
|
# capability if this is set as a global setting.
|
||
|
|
#
|
||
|
|
# It's important to note that markup inside the format option will be parsed
|
||
|
|
# regardless of what this is set to.
|
||
|
|
markup = full
|
||
|
|
|
||
|
|
# The format of the message. Possible variables are:
|
||
|
|
# %a appname
|
||
|
|
# %s summary
|
||
|
|
# %b body
|
||
|
|
# %i iconname (including its path)
|
||
|
|
# %I iconname (without its path)
|
||
|
|
# %p progress value if set ([ 0%] to [100%]) or nothing
|
||
|
|
# %n progress value if set without any extra characters
|
||
|
|
# Markup is allowed
|
||
|
|
format = "<b>%s</b">"<b>%s</b></a>\n%b"</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Alignment of message text.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Possible values are "left", "center" and "right".</span>
|
||
|
|
<span class="org-variable-name">alignment</span> = left
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Show age of message if message is older than show_age_threshold</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">seconds.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Set to -1 to disable.</span>
|
||
|
|
<span class="org-variable-name">show_age_threshold</span> = <span class="org-highlight-numbers-number">300</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Split notifications into multiple lines if they don't fit into</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">geometry.</span>
|
||
|
|
<span class="org-variable-name">word_wrap</span> = yes
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Ignore newlines '\n' in notifications.</span>
|
||
|
|
<span class="org-variable-name">ignore_newline</span> = no
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Merge multiple notifications with the same content</span>
|
||
|
|
<span class="org-variable-name">stack_duplicates</span> = false
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Hide the count of merged notifications with the same content</span>
|
||
|
|
<span class="org-variable-name">hide_duplicate_count</span> = false
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Display indicators for URLs (U) and actions (A).</span>
|
||
|
|
<span class="org-variable-name">show_indicators</span> = yes
|
||
|
|
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div id="outline-container-org0b3fe43" class="outline-3">
|
||
|
|
<h3 id="org0b3fe43">Icons</h3>
|
||
|
|
<div class="outline-text-3" id="text-org0b3fe43">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf"><span class="org-comment-delimiter"># </span><span class="org-comment">Align icons left/right/off</span>
|
||
|
|
<span class="org-variable-name">icon_position</span> = off
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Limit icons size.</span>
|
||
|
|
<span class="org-variable-name">max_icon_size</span>=<span class="org-highlight-numbers-number">32</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Paths to default icons.</span>
|
||
|
|
<span class="org-variable-name">icon_path</span> = /usr/share/icons/Arc/16x16/status/:/usr/share/icons/Arc/16x16/devices/
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div id="outline-container-orgfccb12b" class="outline-3">
|
||
|
|
<h3 id="orgfccb12b">History</h3>
|
||
|
|
<div class="outline-text-3" id="text-orgfccb12b">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf"><span class="org-comment-delimiter"># </span><span class="org-comment">Should a notification popped up from history be sticky or timeout</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">as if it would normally do.</span>
|
||
|
|
<span class="org-variable-name">sticky_history</span> = yes
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Maximum amount of notifications kept in history</span>
|
||
|
|
<span class="org-variable-name">history_length</span> = <span class="org-highlight-numbers-number">20</span>
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div id="outline-container-org4cdd8ed" class="outline-3">
|
||
|
|
<h3 id="org4cdd8ed">Misc/Advanced</h3>
|
||
|
|
<div class="outline-text-3" id="text-org4cdd8ed">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf"><span class="org-comment-delimiter"># </span><span class="org-comment">dmenu path.</span>
|
||
|
|
<span class="org-variable-name">dmenu</span> = /usr/bin/dmenu -p dunst:
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Browser for opening urls in context menu.</span>
|
||
|
|
<span class="org-variable-name">browser</span> = qutebrowser
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Always run rule-defined scripts, even if the notification is suppressed</span>
|
||
|
|
<span class="org-variable-name">always_run_script</span> = true
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Define the title of the windows spawned by dunst</span>
|
||
|
|
<span class="org-variable-name">title</span> = Dunst
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Define the class of the windows spawned by dunst</span>
|
||
|
|
<span class="org-variable-name">class</span> = Dunst
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Print a notification on startup.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">This is mainly for error detection, since dbus (re-)starts dunst</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">automatically after a crash.</span>
|
||
|
|
<span class="org-variable-name">startup_notification</span> = false
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div id="outline-container-orga574d4b" class="outline-2">
|
||
|
|
<h2 id="orga574d4b">Shortcuts</h2>
|
||
|
|
<div class="outline-text-2" id="text-orga574d4b">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf">[<span class="org-type">shortcuts</span>]
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Shortcuts are specified as [modifier+][modifier+]...key</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Available modifiers are "ctrl", "mod1" (the alt-key), "mod2",</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">"mod3" and "mod4" (windows-key).</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Close notification.</span>
|
||
|
|
<span class="org-variable-name">close</span> = mod1+space
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Close all notifications.</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">close_all = mod1+shift+space</span>
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Redisplay last message(s).</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">On the US keyboard layout "grave" is normally above TAB and left</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">of "1". Make sure this key actually exists on your keyboard layout,</span>
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">e.g. check output of 'xmodmap -pke'</span>
|
||
|
|
<span class="org-variable-name">history</span> = mod1+grave
|
||
|
|
|
||
|
|
<span class="org-comment-delimiter"># </span><span class="org-comment">Context menu.</span>
|
||
|
|
<span class="org-variable-name">context</span> = mod1+shift+period
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div id="outline-container-org2443a5f" class="outline-2">
|
||
|
|
<h2 id="org2443a5f">Urgency</h2>
|
||
|
|
<div class="outline-text-2" id="text-org2443a5f">
|
||
|
|
<div class="org-src-container">
|
||
|
|
<pre class="src src-conf">[<span class="org-type">urgency_low</span>]
|
||
|
|
<span class="org-variable-name">background</span> = <span class="org-string">"#32302f"</span>
|
||
|
|
<span class="org-variable-name">foreground</span> = <span class="org-string">"#ebdbb2"</span>
|
||
|
|
<span class="org-variable-name">timeout</span> = <span class="org-highlight-numbers-number">4</span>
|
||
|
|
|
||
|
|
[<span class="org-type">urgency_normal</span>]
|
||
|
|
<span class="org-variable-name">background</span> = <span class="org-string">"#32302f"</span>
|
||
|
|
<span class="org-variable-name">foreground</span> = <span class="org-string">"#ebdbb2"</span>
|
||
|
|
<span class="org-variable-name">timeout</span> = <span class="org-highlight-numbers-number">6</span>
|
||
|
|
|
||
|
|
[<span class="org-type">urgency_critical</span>]
|
||
|
|
<span class="org-variable-name">background</span> = <span class="org-string">"#32302f"</span>
|
||
|
|
<span class="org-variable-name">foreground</span> = <span class="org-string">"#cc241d"</span>
|
||
|
|
<span class="org-variable-name">timeout</span> = <span class="org-highlight-numbers-number">0</span>
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div id="postamble" class="status">
|
||
|
|
<p class="author">Author: Dehaeze Thomas</p>
|
||
|
|
<p class="date">Created: 2020-01-11 sam. 21:59</p>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|