Turn on the color support unconditionally, and use color commands
specified by the ANSI escape sequences for the 8 standard colors.
@item @var{num}
-Use color mode for @var{num} colors. If @var{num} is -1, turn off
+Use color mode for @var{num} colors. If @var{num} is @minus{}1, turn off
color support (equivalent to @samp{never}); if it is 0, use the
default color support for this terminal (equivalent to @samp{auto});
otherwise use an appropriate standard mode for @var{num} colors.
list enables Eldoc mode (@pxref{Lisp Doc}) by calling
@code{eldoc-mode} with no argument (calling it with an argument of 1
would do the same), and disables Font Lock mode (@pxref{Font Lock}) by
-calling @code{font-lock-mode} with an argument of -1.
+calling @code{font-lock-mode} with an argument of @minus{}1.
@example
;; Local Variables:
@samp{\begin@{pmatrix@} a & b \\ c & d \end@{pmatrix@}} format in
@LaTeX{} mode; you may need to edit this afterwards to change to your
preferred matrix form. If you invoke @kbd{d T} or @kbd{d L} with an
-argument of 2 or -2, then matrices will be displayed in two-dimensional
+argument of 2 or @minus{}2, then matrices will be displayed in two-dimensional
form, such as
@example
@item
When it's @code{nil}, the command indents the line by an extra
@code{c-basic-offset} columns. A prefix argument acts as a
-multiplier. A bare prefix (@kbd{C-u @key{TAB}}) is equivalent to -1,
+multiplier. A bare prefix (@kbd{C-u @key{TAB}}) is equivalent to @minus{}1,
removing @code{c-basic-offset} columns from the indentation.
@end itemize
which assign each message an integer value. Depending on
the value the message is highlighted in summary buffer (if
it's high, say +2000) or automatically marked read (if the
-value is low, say -800) or some other action happens.
+value is low, say @minus{}800) or some other action happens.
There are basically three ways of setting up rules which assign
the scoring-value to messages. The first and easiest way is to set
To take @code{gnus-del-mark} as an example---this alist says that all
articles that have that mark (i.e., are marked with @samp{e}) will have a
-score entry added to lower based on the @code{From} header by -4, and
-lowered by @code{Subject} by -1. Change this to fit your prejudices.
+score entry added to lower based on the @code{From} header by @minus{}4, and
+lowered by @code{Subject} by @minus{}1. Change this to fit your prejudices.
If you have marked 10 articles with the same subject with
@code{gnus-del-mark}, the rule for that mark will be applied ten times.
-That means that that subject will get a score of ten times -1, which
-should be, unless I'm much mistaken, -10.
+That means that that subject will get a score of ten times @minus{}1, which
+should be, unless I'm much mistaken, @minus{}10.
If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
the read articles will be marked with the @samp{E} mark. This'll
current article, thereby matching the following thread.
If you use this scheme, you should set the score file atom @code{mark}
-to something small---like -300, perhaps, to avoid having small random
+to something small---like @minus{}300, perhaps, to avoid having small random
changes result in articles getting marked as read.
After using adaptive scoring for a week or so, Gnus should start to
@enumerate
@item
-Scores between -3 and 3 will be set to 0 when this function is called.
+Scores between @minus{}3 and 3 will be set to 0 when this function is called.
@item
Scores with magnitudes between 3 and 60 will be shrunk by 3.
projects / emacs.git / commitdiff