Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: Files ~/Mail/IncomingXXXX, and need some general explanations ...
Date: Sat, 15 Oct 2005 17:41:53 +0200	[thread overview]
Message-ID: <v9zmpaiy7y.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87hdbjm1jh.fsf@fleuret.homeunix.org>

On Sat, Oct 15 2005, François Fleuret wrote:

> Looked for 1h, did not find the answer, posted my question, and found
> the answer 2min later in mail-source.el.

Next time, try `Info-index'[1] and `Info-index-next'[2] in Gnus
manual:

`i Incoming RET ,' and also the next `,' are the relevant matches:

(info "(gnus)Gnus Development")
(info "(gnus)Mail Source Customization")

If there is no index entry for your keyword, please suggest to add it.

Bye, Reiner.

[1]
,----[ `C-h k i' ]
| i runs the command Info-index
|    which is an interactive compiled Lisp function in `info'.
| It is bound to i, <menu-bar> <Info> <Index> <Lookup a String...>.
| (Info-index topic)
| 
| Look up a string topic in the index for this file.
| If there are no exact matches to the specified topic, this chooses
| the first match which is a case-insensitive substring of a topic.
| Use the , command to see the other matches.
| Give a blank topic name to go to the Index node itself.
`----

[2]
,----[ `C-h k ,' ]
| , runs the command Info-index-next
|    which is an interactive compiled Lisp function in `info'.
| It is bound to ,, <menu-bar> <Info> <Index> <Next Matching Item>.
| (Info-index-next num)
| 
| Go to the next matching index item from the last i command.
`----
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/


      reply	other threads:[~2005-10-15 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 11:59 François Fleuret
2005-10-15 12:01 ` François Fleuret
2005-10-15 15:41   ` Reiner Steib [this message]

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=v9zmpaiy7y.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --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).