From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 74781@debbugs.gnu.org
Subject: bug#74781: [PATCH] Add `browse-url-qutebrowser'
Date: Wed, 11 Dec 2024 16:40:07 +0200 [thread overview]
Message-ID: <865xnq4720.fsf@gnu.org> (raw)
In-Reply-To: <87msh21z0i.fsf@daniel-mendler.de> (bug-gnu-emacs@gnu.org)
> Date: Wed, 11 Dec 2024 08:04:29 +0100
> From: Daniel Mendler via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> The browser launcher supports the NEW-WINDOW argument and
> `browse-url-qutebrowser-new-window-is-tab' to open tabs. Furthermore
> opening new URLs is speed up via Unix socket IPC if available.
Thanks.
> Furthermore opening new URLs is speed up via Unix socket IPC if
> available. ^^^^^^^^
Typo: "sped up"
> (browse-url-qutebrowser-program, browse-url-qutebrowser-arguments,
> browse-url-qutebrowser-new-window-is-tab): New customizables.
Our conventions are to format these kinds of identifier lists
differently:
(browse-url-qutebrowser-program, browse-url-qutebrowser-arguments)
(browse-url-qutebrowser-new-window-is-tab): New customizables.
IOW, the list should be closed at EOL, and then reopened on the next
line. This makes searching for changes of a function/variable easier.
> +(defcustom browse-url-qutebrowser-program "qutebrowser"
> + "The name by which to invoke Qutebrowser."
> + :type 'string)
Please add a :version tag.
> +(defcustom browse-url-qutebrowser-arguments nil
> + "A list of strings to pass to Qutebrowser when it starts up."
> + :type '(repeat (string :tag "Argument")))
Same here.
> +(defcustom browse-url-qutebrowser-new-window-is-tab nil
> + "Whether to open up new windows in a tab or a new window.
The first line of this doc string should mention Qutebrowser, so that
the various apropos commands could find this variable when the user
wants to look up something Qutebrowser-related.
> +If non-nil, then open the URL in a new tab rather than a new window if
> +`browse-url-qutebrowser' is asked to open it in a new window."
The "is asked to open it in a new window" part confused me: asked by
whom? Is this something that Emacs does, or something else?
> + :type 'boolean)
The :version tag is missing.
> +(defun browse-url-qutebrowser-send (cmd)
> + "Send CMD to Qutebrowser via IPC."
> + (let* ((dir (getenv "XDG_RUNTIME_DIR"))
^^^^^^^^^^^^^^^^^^^^^^^^^^
Why not use xdg-runtime-dir instead?
> + (sock (and dir (expand-file-name
> + (format "qutebrowser/ipc-%s" (md5 (user-login-name)))
> + dir))))
I think Qutebrowser is available on Windows, where we don't (yet)
support local sockets. So I think there should be some kind of test
for running on Windows, and falling back to alternatives.
Last, but not least: I think the fact that Emacs will now support
Qutebrowser warrants a NEWS entry.
next prev parent reply other threads:[~2024-12-11 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 7:04 bug#74781: [PATCH] Add `browse-url-qutebrowser' Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 8:27 ` Robert Pluim
2024-12-11 9:07 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 9:58 ` Robert Pluim
2024-12-11 10:45 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 14:14 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 14:38 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 16:16 ` Eli Zaretskii
2024-12-11 15:32 ` Eli Zaretskii
2024-12-11 15:36 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 14:40 ` Eli Zaretskii [this message]
2024-12-11 15:12 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 15:44 ` Robert Pluim
2024-12-11 15:54 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 16:54 ` Eli Zaretskii
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=865xnq4720.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74781@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
/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).