From: Francis Litterio <franl_removethis@world.std.com>
Subject: Bug in Emacs 21.1 reported in February 2002 not fixed in Emacs 21.2
Date: Thu, 01 Aug 2002 12:37:16 -0400 [thread overview]
Message-ID: <uheie353m.fsf@world.std.com> (raw)
I submitted the below bug report (and the patch to fix it) in February
2002 against Emacs 21.1. It is not fixed in Emacs 21.2. Is this an
oversight or is this behavior not considered a bug?
--
Francis Litterio
franl-remove@world.omit-this.std.com
> From: franl-removethis@world.omitthis.std.com (Francis Litterio)
> Subject: Emacs 21.1: icomplete-mode prematurely inserts completion options
> Date: Fri, 22 Feb 2002 17:22:40 -0500
> Message-ID: <ud6yxnolr.fsf@world.std.com>
>
> In Emacs 21.1, when icomplete-mode is on, irrelevant incremental
> completion data appears in the minibuffer before the user types even one
> character.
>
> To reproduce:
>
> 1. Evaluate this Elisp to turn on icomplete-mode: (icomplete-mode)
>
> 2. Type "M-x".
>
> 3. icomplete-mode fills the minibuffer with an enumeration of all
> possible command names before user types anything. This is a useless
> display of command names without regard for the subset in which the
> user is truly interested.
>
> It would be better for the minibuffer to remain empty of incremental
> completion data until at least one character is typed (and an
> examination of the code reveals that this was the intention of the
> programmer).
>
> The below patch to icomplete.el fixes this problem.
> --
> Francis Litterio
> franl-remove@world.omit-this.std.com
>
>
> --- /c/apps/emacs-21.1/lisp/icomplete.el.orig Fri Feb 22 16:49:18 2002
> +++ /c/apps/emacs-21.1/lisp/icomplete.el Fri Feb 22 16:49:30 2002
> @@ -260,7 +260,7 @@
> (make-local-variable 'icomplete-eoinput))
> (setq icomplete-eoinput (point))
> ; Insert the match-status information:
> - (if (and (> (point-max) 1)
> + (if (and (> (point-max) (minibuffer-prompt-end))
> (or
> ;; Don't bother with delay after certain number of chars:
> (> (point-max) icomplete-max-delay-chars)
reply other threads:[~2002-08-01 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=uheie353m.fsf@world.std.com \
--to=franl_removethis@world.std.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.
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).