Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: server parameter vs. server variable (was: mail splitting to another backend)
Date: Fri, 18 Apr 2003 23:33:05 +0200	[thread overview]
Message-ID: <v93ckfij8u.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <84n0iow25c.fsf@lucy.is.informatik.uni-duisburg.de>

On Fri, Apr 18 2003, Kai Großjohann wrote:

> Maybe it works by adding a server parameter?

Most people here use the term `server parameter' instead of `server
variable' as the manual does, see (info "(gnus)Server Variables").
The only match on `server parameter' is in the new nnmaildir node.

Any objection against the following patch?

--8<---------------cut here---------------start------------->8---
@@ -12191,6 +12191,8 @@
 
 @node Server Variables
 @subsection Server Variables
+@cindex server variables
+@cindex server parameters
 
 One sticky point when defining variables (both on back ends and in Emacs
 in general) is that some variables are typically initialized from other
@@ -12215,6 +12217,7 @@
       (nnml-newsgroups-file "~/my-mail/newsgroups"))
 @end lisp
 
+Server variables are often called ``server parameters''.
 
 @node Servers and Methods
 @subsection Servers and Methods
@@ -14811,7 +14814,7 @@
 an nnmaildir group.  The results might happen to be useful, but that
 would be by chance, not by design, and the results might be different
 in the future.  If your split rules create new groups, remember to
-supply a @code{create-directory} server parameter.
+supply a @code{create-directory} server variable.
 @end table
 
 @subsubsection Group parameters
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2003-04-18 21:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 16:59 mail splitting to another backend Ted Zlatanov
2003-04-17 18:56 ` Paul Jarc
2003-04-17 19:09   ` Ted Zlatanov
2003-04-17 19:53     ` Paul Jarc
2003-04-17 19:41 ` Simon Josefsson
2003-04-17 20:22   ` Ted Zlatanov
2003-04-17 20:31     ` Paul Jarc
2003-04-18  8:56     ` Simon Josefsson
2003-04-18 10:06       ` Kai Großjohann
2003-04-18 21:33         ` Reiner Steib [this message]
2003-04-18 23:03           ` server parameter vs. server variable Paul Jarc
2003-04-20 14:35           ` Kai Großjohann
2003-04-20 15:11             ` Jesper Harder
2003-04-21 20:23               ` texinfo markup fixes (was: server parameter vs. server variable) Reiner Steib
2003-04-21 22:05                 ` texinfo markup fixes Jesper Harder
2003-04-22  0:31                   ` François Pinard
2003-04-22  0:36                     ` Jesper Harder
2003-04-22  0:53                       ` François Pinard
2003-04-18 17:12       ` mail splitting to another backend Ted Zlatanov
2003-04-18 22:48         ` Paul Jarc
2003-04-18 23:00           ` Ted Zlatanov
2003-04-27  3:09             ` Lars Magne Ingebrigtsen
2003-04-29 18:42               ` Ted Zlatanov
2003-05-01  6:55                 ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v93ckfij8u.fsf_-_@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).