unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Glenn Morris'" <rgm@gnu.org>
Cc: 10770@debbugs.gnu.org
Subject: bug#10770: info-display-manual replaces existing *info* buffer
Date: Thu, 9 Feb 2012 11:16:34 -0800	[thread overview]
Message-ID: <72A72E53E0D9483C9CA95A995F84D033@us.oracle.com> (raw)
In-Reply-To: <83hayzaktp.fsf@gnu.org>

> Also because typing "emacs" or "make" is shorter than "*info*<emacs>"
> etc., and completion doesn't help much when all the candidates begin
> with the same substring.

Huh?  Prefix completion for things that share a common prefix just abstracts
away that prefix (by completing to it), so you do not have to type it.  The
difference would be that completion would help with the *non*-prefix part.

(I do not have a particular opinion about the rest of what was discussed.  Just
pointing out that it is not the case that completion doesn't help much when all
candidates share a common prefix.)






  reply	other threads:[~2012-02-09 19:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  6:33 bug#10770: info-display-manual replaces existing *info* buffer Glenn Morris
2012-02-09  9:28 ` Juri Linkov
2012-02-09 18:43   ` Eli Zaretskii
2012-02-09 18:36 ` Eli Zaretskii
2012-02-09 18:46   ` Glenn Morris
2012-02-09 18:53     ` Glenn Morris
2012-02-09 19:05       ` Eli Zaretskii
2012-02-09 19:16         ` Drew Adams [this message]
2012-02-09 19:19         ` Glenn Morris
2012-02-09 22:04           ` Eli Zaretskii
2012-02-09 19:23       ` Glenn Morris
2012-02-10 10:14         ` Juri Linkov
2012-02-10 15:13         ` Stefan Monnier
2012-02-09 19:04     ` Eli Zaretskii
2012-12-02  6:24       ` Chong Yidong
2012-02-10 15:15     ` 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=72A72E53E0D9483C9CA95A995F84D033@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10770@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rgm@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).