all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-pretest-bug@gnu.org, ihs_4664@yahoo.com
Subject: Re: Directory name completion blocks when it shouldn't
Date: Sun, 17 Dec 2006 00:37:41 -0500	[thread overview]
Message-ID: <E1GvoiT-0006Io-MF@fencepost.gnu.org> (raw)
In-Reply-To: <m2vekme8vg.fsf@chrislap.local> (message from Chris Moore on Fri, 08 Dec 2006 15:54:11 +0100)

[I sent this message a week ago but did not get a response.]

    read-file-name-internal ignores the value of PREDICATE if ACTION is
    nil (ACTION is t if we are listing possible completions, and nil if
    are actually doing the completion)

I wonder if that is a bug.  Unfortunately there is no comment which
explains why the code does this.

I looked for calls to read-file-name that pass a predicate.  Aside
from this one, I found one other, in compile.el.  The comment there
suggests that in this case too it is a problem that read-file-name
ignores the predicate.

Is it feasible to fix read-file-name to obey the predicate
in the completion case?  It could be that the reason it doesn't
do so was the difficulty of implementing that case efficiently.

Would someone please try?

       reply	other threads:[~2006-12-17  5:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871wng3yyw.fsf@leeloo.anubex.internal>
     [not found] ` <m3wt57vkvv.fsf@kfs-l.imdomain.dk>
     [not found]   ` <el1l03$j4p$1@sea.gmane.org>
     [not found]     ` <E1GrSYo-0004AE-I3@fencepost.gnu.org>
     [not found]       ` <m2vekme8vg.fsf@chrislap.local>
2006-12-17  5:37         ` Richard Stallman [this message]
2006-12-18  1:12           ` Directory name completion blocks when it shouldn't Richard Stallman
2006-12-19 20:16             ` Chris Moore
2006-12-20  6:14               ` Michael Albinus
2006-12-20 10:28                 ` Sascha Wilde
2006-12-20 13:24                   ` Michael Albinus
2006-12-20 14:08                     ` Sascha Wilde

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1GvoiT-0006Io-MF@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=ihs_4664@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.