From: Juri Linkov <juri@linkov.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 60213@debbugs.gnu.org, Drew Adams <drew.adams@oracle.com>
Subject: bug#60213: [PATCH] Copy Info-goto-node-web URL as kill with prefix argument
Date: Wed, 21 Dec 2022 10:30:44 +0200 [thread overview]
Message-ID: <86zgbh87zn.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkm=nJprHq9fZqq02HE7h70caXnGh-FOehJMDnH6AJJdjXQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 20 Dec 2022 19:57:23 -0600")
>> 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).
>
> That can be customized in `browse-url', so I'd personally use the prefix
> argument for something more useful. But I won't protest if someone
> wants to do that.
It would make sense to use eww by default to browse an external Info
in the same Emacs window. And with a prefix argument open that Info
in an external browser.
> Anyways, we could consider moving the functionality I want to a positive
> prefix argument of `Info-copy-current-node-name'. Or a negative prefix
> argument of `Info-goto-node-web'. I don't really care which it is, as
> long as its somewhere.
Using a different prefix argument for `w' (`Info-copy-current-node-name')
makes sense as well like in `dired-copy-filename-as-kill' where the prefix
argument supports different values. Another variant is to add new key 'W'
for URL copying. OTOH, 'W' has a nice mnemonic to open a web browser.
next prev parent reply other threads:[~2022-12-21 8:30 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
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 [this message]
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=86zgbh87zn.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=60213@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).