From: "Štěpán Němec" <stepnem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: /srv/bzr/emacs/trunk r103796: Add a new command `info-display-manual'.
Date: Fri, 01 Apr 2011 19:49:24 +0200 [thread overview]
Message-ID: <87liztaml7.fsf@gmail.com> (raw)
In-Reply-To: <E1Q5bQ9-0000Zy-Nk@colonialone.fsf.org> (Eli Zaretskii's message of "Fri, 01 Apr 2011 13:10:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> +(defun info-display-manual (manual)
> + "Go to Info buffer that displays MANUAL, creating it if none already exists."
> + (interactive "sManual name: ")
This would be sooo much more useful if it provided completion for manual
names...
Just saying.
Štěpán
next parent reply other threads:[~2011-04-01 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Q5bQ9-0000Zy-Nk@colonialone.fsf.org>
2011-04-01 17:49 ` Štěpán Němec [this message]
2011-04-01 19:16 ` /srv/bzr/emacs/trunk r103796: Add a new command `info-display-manual' Eli Zaretskii
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=87liztaml7.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).