unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: M-g in dired
Date: Tue, 23 May 2006 08:16:14 +0300	[thread overview]
Message-ID: <87bqtpibul.fsf@jurta.org> (raw)
In-Reply-To: <E1FiH9k-0001NJ-VQ@fencepost.gnu.org> (Richard Stallman's message of "Mon, 22 May 2006 16:37:36 -0400")

>     Oops, this default was inserted by ffap.  When ffap-read-file-or-url
>     reads a directory/file name it uses the current buffer's file name as
>     default.  dired could do the same.
>
> The visited file name should not be the default for C-x d.  But it
> would be nice if the visited file name were easily accessible
> when you want it.  That's why I suggest putting it in the "future
> history" list.

For reading a directory/file name, ffap uses the function
`completing-read' with the value of the `initial-input' arg set
to the directory name, and the `default' arg set to the current buffer's
file name.  This has the effect that typing RET returns the directory name,
not the file name from the default value.  And only after typing `M-n RET'
it returns the default file name.

Is it possible to achieve the same effect by `read-file-name'
(which is used by dired)?

Essentially, what is used by ffap is:

    (completing-read "Dired file: "
     nil "~/" nil '("~/" . 2) 'file-name-history "~/.emacs")

    Typing `C-x C-e RET' returns "~/"
    Typing `C-x C-e M-n RET' returns "~/.emacs"

But trying to do the same for `read-file-name':

    (read-file-name "Dired file: " "~/" "~/.emacs" nil nil nil)

    Typing `C-x C-e RET' returns "~/.emacs", not "~/"
    Typing `C-x C-e M-n RET' returns "~/.emacs"

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2006-05-23  5:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <446C7B73.60907@earthlink.net>
2006-05-19  2:04 ` M-g in dired Richard Stallman
2006-05-19  3:04   ` Juri Linkov
2006-05-19  8:16     ` Kim F. Storm
2006-05-19  8:43       ` Miles Bader
2006-05-19 12:37         ` Kim F. Storm
2006-05-20 13:45         ` Juri Linkov
2006-05-20  5:03       ` Richard Stallman
     [not found]     ` <E1FhJd4-000822-Fe@fencepost.gnu.org>
2006-05-20 13:45       ` Juri Linkov
2006-05-20 15:46         ` Johan Bockgård
2006-05-20 20:03           ` Juri Linkov
2006-05-20 20:41             ` Romain Francoise
2006-05-21  0:56         ` Richard Stallman
2006-05-21  4:28           ` Juri Linkov
2006-05-22  2:38             ` Richard Stallman
2006-05-22 13:46               ` Juri Linkov
2006-05-22 20:37                 ` Richard Stallman
2006-05-23  5:16                   ` Juri Linkov [this message]
2006-05-19 18:53   ` David Hansen
2006-05-19 19:57     ` Reiner Steib
2006-05-19 20:07     ` Miles Bader
2005-10-15 11:27 Juri Linkov
2005-10-15 19:33 ` Kim F. Storm
2005-10-16 14:40 ` Richard M. Stallman
2005-10-16 14:40 ` Richard M. Stallman
2005-10-31  1:14 ` Richard Stallman
2005-10-31  7:47   ` Juri Linkov
2005-11-01  2:13     ` Richard M. Stallman
2005-11-01  9:16       ` Juri Linkov
2005-11-01 14:09         ` Andreas Schwab
2005-11-01 19:55           ` Juri Linkov
2005-11-02 10:28             ` Richard M. Stallman
2005-11-02 10:27         ` Richard M. Stallman
2005-11-03  7:48           ` Juri Linkov
2005-11-03 15:03             ` Stefan Monnier
2005-11-04 12:06               ` Juri Linkov
2005-11-05  1:37                 ` Richard M. Stallman
2005-11-05  7:55                   ` Juri Linkov
2005-11-05 23:43                     ` Richard M. Stallman
2005-11-07 14:27                       ` Juri Linkov
2005-11-07 16:03                         ` Stefan Monnier
2005-11-08 12:43                           ` Juri Linkov
2005-11-09  2:57                             ` Richard M. Stallman
2005-11-07 21:56                         ` Richard M. Stallman
2005-11-03 21:41             ` Richard M. Stallman

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=87bqtpibul.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@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).