From: Krzys Majewski <krzys@cs.mcgill.ca>
Subject: Re: messages disappearing from nnimap+imap:INBOX
Date: 03 Oct 2002 08:31:25 -0700 [thread overview]
Message-ID: <87ofabo7xu.fsf@mi.krzys.ca> (raw)
In-Reply-To: <v9zntvpx2e.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4uce.02.r.steib@gmx.net> writes:
> On Thu, Oct 03 2002, Ricardo Anguiano wrote:
>
> > Chris Majewski <majewski@cs.ubc.ca> writes:
>
> >> [...] turns out to be an arcane emacs-lisp variable known only to
> >> two Gnus hackers somewhere in Germany.
>
> Hmm, _two_ Gnus hackers from Germany?
> "Kai =?iso-8859-15?q?Gro=DFjohann?=" and the other guy named
> "Kai =?iso-8859-1?q?Gro=DFjohann?="? ;-)
Hehe. Well, there used to be this guy Simon, I'm not sure if he's
still around. Anyway, kudos to those guys for showing up on the list
and helping us all out.
> Most others try (more or less successfully) to read the info manual
> and read or grep(1) the source code if necessary.
Yeah, I've taken a few stabs at the source and it was source 1, me 0.
> RET', `M-x apropos-documentation RET foo RET' (Emacs only?).
Nice, I didn't know about that one.
> ,----[ C-h k i ]
> | i runs the command Info-index
> | which is an interactive compiled Lisp function in `info'.
> | (Info-index TOPIC)
> |
> | Look up a string TOPIC in the index for this file.
> | [...]
> | Use the `,' command to see the other matches.
Or that one.
cheers
-chris
next prev parent reply other threads:[~2002-10-03 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ymh4rc4fyem.fsf@okocim.cs.ubc.ca>
2002-10-02 19:40 ` Jhair Tocancipa Triana
[not found] ` <m34rc4o58x.fsf@multivac.cwru.edu>
[not found] ` <ymh4rc475r3.fsf@okocim.cs.ubc.ca>
2002-10-03 0:32 ` Ricardo Anguiano
[not found] ` <v9zntvpx2e.fsf@marauder.physik.uni-ulm.de>
2002-10-03 15:31 ` Krzys Majewski [this message]
2002-10-04 15:32 ` Reiner Steib
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=87ofabo7xu.fsf@mi.krzys.ca \
--to=krzys@cs.mcgill.ca \
/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).