From: Juri Linkov <juri@jurta.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Bastien <bzg@altern.org>, 16542@debbugs.gnu.org
Subject: bug#16542: 24.3.50; When finding a file via a bookmark, that file is not part of file-name-history
Date: Tue, 28 Jan 2014 09:28:03 +0200 [thread overview]
Message-ID: <87bnywpohw.fsf@mail.jurta.org> (raw)
In-Reply-To: <d45e48b4-53ea-4f32-92d0-d34c1cb36afc@default> (Drew Adams's message of "Mon, 27 Jan 2014 09:31:29 -0800 (PST)")
> 1. A user option such as what you describe, but with nil meaning
> "go for it generally: let the command decide", a non-nil list as
> you mention meaning "do not let these commands decide", and any
> other non-nil value meaning "do not let any command decide".
I think a cleaner solution would be to have two separate history lists:
1. history of minibuffer input
2. history of visited files
and a new option to select which history to access via M-p
in the minibuffer that reads a file name.
Actually we already have a history of recently visited files
in recentf, so we could add `bookmark-jump' to `recentf-used-hooks'.
Or maybe this is not needed because it already contains `find-file-hook'.
next prev parent reply other threads:[~2014-01-28 7:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 21:45 bug#16542: 24.3.50; When finding a file via a bookmark, that file is not part of file-name-history Bastien Guerry
2014-01-25 8:19 ` Dani Moncayo
2014-01-25 8:42 ` Drew Adams
2014-01-27 11:29 ` Bastien
2014-01-27 15:11 ` Drew Adams
2014-01-27 15:26 ` Bastien
2014-01-27 17:31 ` Drew Adams
2014-01-28 7:28 ` Juri Linkov [this message]
2014-01-28 13:28 ` Stefan Monnier
2014-01-29 9:10 ` Juri Linkov
2014-01-29 10:43 ` Bastien
2014-01-29 13:58 ` Stefan Monnier
2014-01-28 16:20 ` Drew Adams
2020-08-25 10:57 ` Lars Ingebrigtsen
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=87bnywpohw.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=16542@debbugs.gnu.org \
--cc=bzg@altern.org \
--cc=drew.adams@oracle.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).