GNU bug report logs - #14172
[gmane.emacs.devel] Re: read-from-minibuffer vs completing-read -- Cueing Users:

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 14172 in the body.
You can then email your comments to 14172 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jambunathan K <kjambunathan <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: [gmane.emacs.devel] Re: read-from-minibuffer vs completing-read --
	Cueing Users:
Date: Wed, 10 Apr 2013 10:08:57 +0530

Copy of http://thread.gmane.org/gmane.emacs.devel/157498

        
Jambunathan K <kjambunathan <at> gmail.com> writes:

> "T. V. Raman" <tv.raman.tv <at> gmail.com> writes:
>
>> As a long-time emacs user, I always see if there are completions
>> available in the minibuffer -- so the worst that happens is that
>> I get disappointed if I am answering a read-from-minibuffer
>> prompt  -- thinking of this, I realized   that there is a good
>> chance  that new-comers to Emacs do a lot worse in the other
>> direction, i.e. never realize that completions are available.
>> Should we be cueing this somehow in the prompt -- (are  we
>> already cueing the user visually?)
>> vs a completing-read prompt
>
> I have been using icomplete-mode for a while.  Bzr trunk has an enhanced
> version.
>
> My only complain is that the icomplete-mode starts showing completions
> only after you enter the first character.  If the first character is
> wrong, then you get a more useless "No match" or some such thing.
>
> There is a buglet in the queue, only that it is not filed.

I am essentially saying this:

Enhance icomplete-mode so that it shows completion even without any user
input.  The visual cue is right there hiding behind the curtains.  

Try installing this quick change, do M-x and wait for the visual cue to
reveal itself to you. 

=== modified file 'lisp/icomplete.el'
--- lisp/icomplete.el	2013-02-15 19:19:29 +0000
+++ lisp/icomplete.el	2013-03-03 20:18:15 +0000
@@ -267,11 +267,11 @@ and `minibuffer-setup-hook'."
     (save-excursion
       (goto-char (point-max))
                                         ; Insert the match-status information:
-      (if (and (> (point-max) (minibuffer-prompt-end))
-               buffer-undo-list         ; Wait for some user input.
+      (if (and ;; (> (point-max) (minibuffer-prompt-end))
+               ;; buffer-undo-list         ; Wait for some user input.
                (or
                 ;; Don't bother with delay after certain number of chars:
-                (> (- (point) (field-beginning)) icomplete-max-delay-chars)
+                ;; (> (- (point) (field-beginning)) icomplete-max-delay-chars)
                 ;; Don't delay if the completions are known.
                 completion-all-sorted-completions
                 ;; Don't delay if alternatives number is small enough:

-- 

Message #10 received at 14172-done <at> debbugs.gnu.org (full text, mbox):

From: Jambunathan K <kjambunathan <at> gmail.com>
To: 14172-done <at> debbugs.gnu.org
Subject: Re: bug#14172: [gmane.emacs.devel] Re: read-from-minibuffer vs
 completing-read -- Cueing Users:
Date: Fri, 15 Nov 2013 10:11:24 +0530

OP here.  Closing it.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.