From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefankangas@gmail.com>,
"60213@debbugs.gnu.org" <60213@debbugs.gnu.org>
Subject: bug#60213: [PATCH] Copy Info-goto-node-web URL as kill with prefix argument
Date: Tue, 20 Dec 2022 17:24:50 +0000 [thread overview]
Message-ID: <SJ0PR10MB548865338F3DBBA3BFFED0B7F3EA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkm=6tPc-TFZGMLkQcEFMWwMhw2j1UtDmwG8gt9VP4052bw@mail.gmail.com>
> The attached patch make `Info-goto-node-web' copy the URL as kill with a
> prefix argument, instead of opening it with `browse-url'. I've seen
> this feature requested a couple of times now by various people.
Couple of times, various people? Any besides
the one time and one person (Marcin)? Based
on what, a month of experience with the new
command? What's the inconvenience that the
enhancement request would overcome - just
killing/copying the URL in the minibuffer?
What about using the prefix arg to open the
URL in a separate browser window? After all,
that's the behavior of `Info-goto-node-web'
(the original).
[If not then `info+.el' will keep needing to
define the command (now REdefine), even after
Emacs 29. OK, I'm used to it...]
That's the behavior users have enjoyed for
almost a decade. During those years, I never
once received a request to add copying the
URL to the kill-ring. Not that that's a
horrible idea - but how useful is it compared
to the longstanding prefix-arg behavior?
Consider also: how hard is it to get the URL
to the kill-ring? Just copy (or kill & yank)
it in the minibuffer to begin with. If you
forget to do that, then when you use the same
minibuffer history again, `M-p C-k' retrieves
the URL and adds it to the kill ring. Not a
big deal.
And compare, e.g., `find-file'. There we
have a separate command for `other-window'.
(Not a browser window, but ~same idea.) We
don't have anything special for saving the
file location (abs-name) to the kill-ring.
We haven't needed that for 40 years... Has
anyone even requested it?
For `find-file' and such, it's apparently
enough that you can get to the file name
with `M-p' - we've felt no need to add it
to the kill-ring.
Or perhaps combine both optional behaviors,
as I suggested in my msg in thread #60190?
If you insist on doing what you're doing
then I'd suggest you at least add another
command for opening the URL in a separate
browser window. And perhaps yet another
to open it in a separate browser tab.
next prev parent reply other threads:[~2022-12-20 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 4:44 bug#60213: [PATCH] Copy Info-goto-node-web URL as kill with prefix argument Stefan Kangas
2022-12-20 14:04 ` Eli Zaretskii
2022-12-20 17:24 ` Drew Adams [this message]
2022-12-21 1:57 ` Stefan Kangas
2022-12-21 6:01 ` Drew Adams
2022-12-21 8:36 ` Stefan Kangas
2022-12-21 16:07 ` Drew Adams
2022-12-21 8:30 ` Juri Linkov
2022-12-21 16:05 ` Drew Adams
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=SJ0PR10MB548865338F3DBBA3BFFED0B7F3EA9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=60213@debbugs.gnu.org \
--cc=stefankangas@gmail.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).