From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: helpex.el 0.2 --- useful extensions for the C-h prefix
Date: Thu, 22 Jan 2004 12:20:37 -0700 [thread overview]
Message-ID: <40102285.20202@yahoo.com> (raw)
In-Reply-To: jwvfze911ky.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca
Stefan Monnier wrote:
>Michael Schierl writes:
>>Is there a good solution for the Info-goto-node "problem" as well?
>
> IIRC, the goto-node code in CVS does completion within the parenthesese,
> but it does not do completion of the node name afterwards (this requires
> looking inside the Info file and I didn't bother writing it up).
That's a feature I've always wanted. In fact, I think I hacked it up in a
previous lifetime, but I lost it...
--
Kevin Rodgers
next prev parent reply other threads:[~2004-01-22 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <buhb0j$hu8n8$2@ID-39741.news.uni-berlin.de>
2004-01-20 17:16 ` helpex.el 0.2 --- useful extensions for the C-h prefix Stefan Monnier
2004-01-21 19:36 ` Michael Schierl
2004-01-21 20:44 ` Stefan Monnier
2004-01-22 19:20 ` Kevin Rodgers [this message]
2004-01-26 19:43 ` Michael Schierl
2004-01-26 22:02 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40102285.20202@yahoo.com \
--to=ihs_4664@yahoo.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).