From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: linux system mail - information overload
Date: Wed, 25 Oct 2006 16:22:42 +0200 [thread overview]
Message-ID: <yoijr6wwiifh.fsf@gamma02.me.chalmers.se> (raw)
In-Reply-To: <87slhccxmk.fsf@gmail.com>
Hadron Quark <hadronquark@gmail.com> writes:
> e.g do you generate this using a hot key:
>
> (info "(gnus)Mail Source Specifiers")
,----
| Info-copy-current-node-name is an interactive compiled Lisp function
| in `info.el'.
| It is bound to w, c, <menu-bar> <Info> <Copy Node Name>.
| (Info-copy-current-node-name &optional ARG)
|
| Put the name of the current Info node into the kill ring. The name
| of the Info file is prepended to the node name in parentheses.
| With a zero prefix arg, put the name inside a function call to `info'.
`----
(Emacs 22)
--
Johan Bockgård
next prev parent reply other threads:[~2006-10-25 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 15:22 Hadron Quark
2006-10-23 16:02 ` Hadron Quark
2006-10-23 17:19 ` Reiner Steib
2006-10-25 13:50 ` Hadron Quark
2006-10-25 14:22 ` Johan Bockgård [this message]
2006-10-25 15:47 ` 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=yoijr6wwiifh.fsf@gamma02.me.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
/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).