all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@jurta.org>
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 08:28:04 -0500	[thread overview]
Message-ID: <jwviot4ck60.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87bnywpohw.fsf@mail.jurta.org> (Juri Linkov's message of "Tue, 28 Jan 2014 09:28:03 +0200")

>> 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.

Better would be to somehow give access to those two lists without going
through an option.


        Stefan





  reply	other threads:[~2014-01-28 13: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
2014-01-28 13:28               ` Stefan Monnier [this message]
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

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

  git send-email \
    --in-reply-to=jwviot4ck60.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=16542@debbugs.gnu.org \
    --cc=bzg@altern.org \
    --cc=juri@jurta.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 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.