From: Jean Louis <bugs@gnu.support>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 44783@debbugs.gnu.org
Subject: bug#44783: 28.0.50; wish for eww: include gopher and gemini links
Date: Wed, 9 Dec 2020 13:20:28 +0300 [thread overview]
Message-ID: <X9Ck7In0/P5yfbS6@protected.rcdrun.com> (raw)
In-Reply-To: <87v9dn822a.fsf@tcd.ie>
* Basil L. Contovounesios <contovob@tcd.ie> [2020-11-30 15:25]:
> Jean Louis <bugs@gnu.support> writes:
>
> > * Lars Ingebrigtsen <larsi@gnus.org> [2020-11-30 14:13]:
> >> Jean Louis <bugs@gnu.support> writes:
> >>
> >> > I was thinking it is not a list, not I see it is a list, that is good.
> >>
> >> No, it's a regexp. You can say mailto:\\|gopher:\\|gemini: or whatever
> >> you want.
> >
> > I just wonder why is regexp in one line. That makes it harder for
> > users. My expectation is to have it as a list
>
> I don't mind either way, but FWIW rx allows for some programmatic regexp
> composition:
>
> (with-eval-after-load 'eww
> (setq eww-use-browse-url
> (rx (| (: bos (| "gopher:" "gemini:"))
> (regexp eww-use-browse-url)))))
Thank you, there are various ways to customize stuff.
prev parent reply other threads:[~2020-12-09 10:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 19:41 bug#44783: 28.0.50; wish for eww: include gopher and gemini links Jean Louis
2020-11-21 19:52 ` Eli Zaretskii
2020-11-21 19:59 ` Jean Louis
2020-11-24 7:23 ` Lars Ingebrigtsen
2020-11-24 9:03 ` Jean Louis
2020-11-24 9:04 ` Lars Ingebrigtsen
2020-11-24 9:10 ` Jean Louis
2020-11-24 9:13 ` Lars Ingebrigtsen
[not found] ` <X8LLGThoBscm0dd3@protected.rcdrun.com>
2020-11-29 9:53 ` Lars Ingebrigtsen
[not found] ` <X8PbQsqsgKm/pe/M@protected.rcdrun.com>
2020-11-30 10:25 ` Lars Ingebrigtsen
2020-11-30 10:54 ` Jean Louis
2020-11-30 11:13 ` Lars Ingebrigtsen
2020-11-30 11:17 ` Jean Louis
2020-11-30 12:24 ` Basil L. Contovounesios
2020-12-09 10:20 ` Jean Louis [this message]
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=X9Ck7In0/P5yfbS6@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=44783@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.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.