From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: Chong Yidong <cyd@gnu.org>, 12915@debbugs.gnu.org
Subject: bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files
Date: Sun, 13 Jan 2013 11:15:45 +0100 [thread overview]
Message-ID: <CAH8Pv0hGYN6Q2L+fxgvpsXLmd9Up2J=nfUiq9oM08VFW3W8+2A@mail.gmail.com> (raw)
In-Reply-To: <87mwwd76ll.fsf@mail.jurta.org>
> When this feature was discussed last time at
> http://thread.gmane.org/gmane.emacs.pretest.bugs/9253/focus=43774
> I found it too irritating that it clutters the minibuffer history
> with too many unnecessary elements that were not entered manually.
>
>> I think it is best done by adding an optional argument `add-history' to
>> `find-file' (and similar functions like `find-file-other-frame'), so
>> that Lisp callers can specify to update `file-name-history' even if the
>> file name was not read interactively. Any objections?
>
> Since this is a matter of personal preference, I think not Lisp callers
> but Emacs users should be able to specify what to add to the history.
FWIW, I also don't want to pollute the minibuffer history, obviously.
That would make harder to find the entries you care about.
Perhaps I wasn't clear enough, but what I had in mind was adding to
the history every file visited _under direct user request_ (with
either `C-x C-f', drag-n-drop, click on dired buffer, jump to
bookmark, menu item, command line argument, etc).
--
Dani Moncayo
next prev parent reply other threads:[~2013-01-13 10:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 13:07 bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files Dani Moncayo
2012-11-17 19:07 ` Glenn Morris
2012-11-17 21:37 ` Dani Moncayo
2013-01-02 9:16 ` Dani Moncayo
2013-01-12 8:25 ` Chong Yidong
2013-01-12 13:18 ` Stefan Monnier
2013-01-12 14:30 ` martin rudalics
2013-01-12 16:54 ` Stefan Monnier
2013-01-12 18:01 ` martin rudalics
2013-01-12 18:02 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the historyof " Drew Adams
2013-01-12 18:01 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history ofvisited files Drew Adams
2013-01-12 18:32 ` Eli Zaretskii
2013-01-12 22:43 ` Drew Adams
2013-01-13 17:31 ` Eli Zaretskii
2013-01-13 18:55 ` Drew Adams
2013-01-12 17:59 ` Drew Adams
2013-01-13 9:56 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files Juri Linkov
2013-01-13 10:15 ` Dani Moncayo [this message]
2013-01-13 14:25 ` Stefan Monnier
2013-01-13 17:13 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history ofvisited files Drew Adams
2013-01-13 20:24 ` Dani Moncayo
2013-01-13 22:45 ` Stefan Monnier
2013-01-13 19:52 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files Dani Moncayo
2013-01-13 22:34 ` Stefan Monnier
2013-01-13 17:13 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history ofvisited files Drew Adams
2013-01-14 7:52 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files Juri Linkov
2013-01-14 8:18 ` Dani Moncayo
2013-01-14 15:18 ` Stefan Monnier
2013-01-14 15:50 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history ofvisited files Drew Adams
2013-01-14 15:45 ` Drew Adams
2013-01-15 9:57 ` Juri Linkov
2013-01-15 15:07 ` Drew Adams
2013-01-13 16:35 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files Eli Zaretskii
2013-01-13 17:14 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the historyof " Drew Adams
2021-07-18 19:21 ` bug#3909: 23.1.50; Drag drop events in command history? Lars Ingebrigtsen
2021-07-18 21:08 ` bug#12915: [External] : bug#12915: " Drew Adams
2021-07-18 22:32 ` bug#3909: " Juri Linkov
2021-07-18 22:50 ` Lars Ingebrigtsen
2021-07-19 15:24 ` Juri Linkov
2021-07-19 15:51 ` bug#3909: " Lars Ingebrigtsen
2021-07-19 21:57 ` Juri Linkov
2021-07-20 11:48 ` 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='CAH8Pv0hGYN6Q2L+fxgvpsXLmd9Up2J=nfUiq9oM08VFW3W8+2A@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=12915@debbugs.gnu.org \
--cc=cyd@gnu.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 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).