From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs-29 additional key binding suggestions
Date: Mon, 24 Apr 2023 18:57:28 +0530 [thread overview]
Message-ID: <878rehmmv3.fsf@gmail.com> (raw)
In-Reply-To: <83a5yxxz4z.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Apr 2023 15:06:52 +0300")
[திங்கள் ஏப்ரல் 24, 2023] Eli Zaretskii wrote:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: visuweshm@gmail.com, emacs-devel@gnu.org
>> Date: Mon, 24 Apr 2023 13:23:21 +0200
>>
>> >>>>> On Mon, 24 Apr 2023 14:07:29 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> >> Actually, does that mean that 'W' should invoke
>> >> `browse-url-secondary-browser-function' when called with a prefix?
That's what I planned to do in my personal configuration after noticing
C-u W does not use the secondary browser. ;-)
>> Eli> Why? Invoking any command, let alone with a prefix argument, is an
>> Eli> option, so if the user does invoke it, why should be second-guess what
>> Eli> the user had in mind?
>>
>> Iʼm showing my gnus prejudice here, but itʼs because thatʼs what 'w'
>> does in the summary buffer, and itʼs kind of neat to be able to choose
>> between two different browsers just with a prefix. It would allow
>> Visuwesh to easily keep his preferred 'show everything in EWW', but
>> allow using an external browser as well.
>
> I don't mind, but beware the over-engineering.
AFAIK, C-u to mean to use the secondary browser is a fairly common
pattern. See browse-url-button-open and browse-url-button-open-url as
well.
next prev parent reply other threads:[~2023-04-24 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:15 emacs-29 additional key binding suggestions Robert Pluim
2023-04-18 15:20 ` [External] : " Drew Adams
2023-04-20 8:21 ` Eli Zaretskii
2023-04-20 9:41 ` Robert Pluim
2023-04-20 11:34 ` Eli Zaretskii
2023-05-29 12:47 ` Robert Pluim
2023-04-20 16:06 ` Visuwesh
2023-04-20 17:55 ` Robert Pluim
2023-04-21 4:18 ` Visuwesh
2023-04-24 7:26 ` Robert Pluim
2023-04-24 11:07 ` Eli Zaretskii
2023-04-24 11:23 ` Robert Pluim
2023-04-24 12:06 ` Eli Zaretskii
2023-04-24 12:43 ` Robert Pluim
2023-04-24 13:06 ` Eli Zaretskii
2023-04-24 13:27 ` Visuwesh [this message]
2023-04-25 15:19 ` Robert Pluim
2023-04-25 15:23 ` Eli Zaretskii
2023-04-25 15:27 ` Robert Pluim
2023-05-29 12:54 ` Robert Pluim
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=878rehmmv3.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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).