From: "Drew Adams" <drew.adams@oracle.com>
To: "'Dani Moncayo'" <dmoncayo@gmail.com>, "'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 ofvisited files
Date: Sun, 13 Jan 2013 09:13:58 -0800 [thread overview]
Message-ID: <A533F7126D684E0E9A16D202608A7299@us.oracle.com> (raw)
In-Reply-To: <CAH8Pv0hGYN6Q2L+fxgvpsXLmd9Up2J=nfUiq9oM08VFW3W8+2A@mail.gmail.com>
> FWIW, I also don't want to pollute the minibuffer history, obviously.
> That would make harder to find the entries you care about.
Yes, and different users can prefer different things. One person's pollution or
noise is another person's convenience feature or dwim.
And the same user can want different things at different times or in different
contexts.
> 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).
Yes, but users should also be able to pick and choose which kinds of
file-choosing interactions should result in adding names to `file-name-history'.
Different users...different contexts...
next prev parent reply other threads:[~2013-01-13 17:13 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
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 ` Drew Adams [this message]
2013-01-14 7:52 ` 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=A533F7126D684E0E9A16D202608A7299@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12915@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=dmoncayo@gmail.com \
--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).