From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Dani Moncayo <dmoncayo@gmail.com>
Cc: Glenn Morris <rgm@gnu.org>,
"3909@debbugs.gnu.org" <3909@debbugs.gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
"12915@debbugs.gnu.org" <12915@debbugs.gnu.org>
Subject: bug#12915: [External] : bug#12915: bug#3909: 23.1.50; Drag drop events in command history?
Date: Sun, 18 Jul 2021 21:08:40 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488A41983ACAB02F66085F0F3E09@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87v957mnqw.fsf_-_@gnus.org>
> The two practical suggestions were:
>
> 1) To add an optional parameter to `find-file' to make it push the
> filename onto `file-name-history'. Then we could adjust callers
> according to taste: I think drag and drop and command line arguments
> should land on the history.
>
> 2) To add a `display-buffer-hook' to do the same if the file actually
> ends up being displayed, so this pushing would happen deep in
> `find-file-noselect'.
>
> I think 1) is attractive in that it's very straightforward and simple to
> understand. 2) is attractive in that we don't put file names into the
> history unless we actually read the file, and we don't have to adjust
> function parameters for the other `find-file-*' commands, too.
>
> I think I prefer 1), because it's easier to reason about.
>
> Anybody got an opinion?
In the #12915 thread both Juri and I argued for having
(multiple) means of _user_ control. And several such means
were suggested.
I said, for example:
Give users the _possibility_ of including, as part of
`file-name-history', file names not actually typed in the
minibuffer. But give them also the ability to _choose_
which such names get added, as defined by how the files
were chosen for access.
Juri said, specifically to argue against your #1::
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.
There are lots of good suggestions in the thread - many
specific and some based on actual implementation and use.
Asking "Anybody got an opinion?" is an invitation to
ignore lots of opinions already carefully expressed.
next prev parent reply other threads:[~2021-07-18 21:08 UTC|newest]
Thread overview: 44+ 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:21 ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files Andreas Röhler
2013-01-13 16:28 ` Eli Zaretskii
2013-01-13 9:56 ` 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 ` 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 ` Drew Adams [this message]
2021-07-18 22:32 ` bug#3909: bug#12915: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB5488A41983ACAB02F66085F0F3E09@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=12915@debbugs.gnu.org \
--cc=3909@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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 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.