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>
Cc: bug-gnu-emacs@gnu.org, bojohan+news@dd.chalmers.se
Subject: RE: completion problem with read-file-name
Date: Thu, 12 Jul 2007 08:47:22 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEPMDNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <uk5t69uhc.fsf@gnu.org>

> > >     ** The completion commands TAB, SPC and ? in the minibuffer apply
> > >     only to the text before point.  If there is text in the buffer
> > >     after point, it remains unchanged.
> >
> > Thanks for the info. Still seems like retrogression to me.
>
> You never explained why you thought it was a retrogression.

Sure I did:

> In previous versions of Emacs, completion used the entire minibuffer
> input, not just the part before the cursor.  I don't know if this
> change is considered a feature, but it seems like a bug to me.  To me,
> the old behavior makes sense: all of your input is tested by
> completion, not just the part before point.

This is just my opinion, of course, but I think the behavior in all previous
Emacs releases is preferable. Just as hitting `RET' takes the entire
minibuffer input into account, no matter the cursor position, so has this
always been true for `TAB' as well. To me, that makes sense. I don't find it
helpful for Emacs to complete qqq.el to qq-xxx-q.elq.el if the cursor is on
the third q. Such a completion is useless, and requires me to hit C-k.

I'm not claiming that everyone (or even anyone) else will agree with me, but
I find the previous behavior better.

I'm not that concerned by this change, personally, as I always use Icicles,
whose prefix completion is like the previous Emacs behavior, and which also
allows regexp/substring completion. I nevertheless consider this change to
be in the wrong direction for Emacs.

Here, again, is the part of the bug report to reproduce what I consider to
be bad behavior:

> emacs -Q
>
> Create files qqq.el and qq-xxx-q.el in the same directory. Visit Dired
> there.
>
> C-x C-f qqq.el TAB, then C-b C-b C-b C-b, then type -xxx TAB.
>
> The minibuffer input is completed to qq-xxx-q.elq.el (with the cursor
> on the last `q').

  reply	other threads:[~2007-07-12 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 20:32 completion problem with read-file-name Drew Adams
2007-07-11 23:03 ` Johan Bockgård
2007-07-12  1:05   ` Drew Adams
2007-07-12  3:22     ` Eli Zaretskii
2007-07-12 15:47       ` Drew Adams [this message]
2007-07-12 17:39         ` 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=DNEMKBNJBGPAOPIJOOICGEPMDNAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bojohan+news@dd.chalmers.se \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@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).