From: Eli Zaretskii <eliz@gnu.org>
To: Gabriel <gabriel376@hotmail.com>
Cc: 59448@debbugs.gnu.org
Subject: bug#59448: 29.0.50; URIs in Dictionary are not properly handled
Date: Sun, 27 Nov 2022 11:45:00 +0200 [thread overview]
Message-ID: <83wn7gpw83.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR06MB8609F1F4B3DEC42F50E143C78B109@SJ0PR06MB8609.namprd06.prod.outlook.com> (message from Gabriel on Sun, 27 Nov 2022 05:27:06 -0300)
> From: Gabriel <gabriel376@hotmail.com>
> Date: Sun, 27 Nov 2022 05:27:06 -0300
>
> However, URIs (e.g.: "http://cs.pdx.edu/~trent/gnu/",
> "http://delorie.com/gnu/" etc) will also be treated as "keywords",
> creating `dictionary-link-button'. By pressing RET on these buttons, a
> `dictionary-new-search' will be executed, and no results will be found
> (because there are not results for "http://cs.pdx.edu/~trent/gnu/").
>
> If we open the dictionary result page for "fsf" in any browser (e.g.:
> Firefox, EWW etc), clicking on "keywords" (e.g.: "GNU", "free software",
> "Richard Stallman", "Emacs" etc) will display a new dictionary result
> page and clicking on URIs (e.g.: "http://cs.pdx.edu/~trent/gnu/",
> "http://delorie.com/gnu/" etc) will open the URI.
>
> The intention of this bug report is to discuss the possibility of
> enhancing the default behavior of dictionary to property identify and
> handle URIs (i.e., to not treat URIs as ordinary dictionary keywords).
> See previous threads for more details.
OK, thanks. So I think adding discovery of URLs to dictionary.el is the
better alternative. Patches are welcome.
prev parent reply other threads:[~2022-11-27 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 14:52 bug#59448: 29.0.50; URIs in Dictionary are not properly handled Gabriel
2022-11-22 7:54 ` Juri Linkov
2022-11-22 21:11 ` Gabriel
2022-11-27 7:20 ` Eli Zaretskii
2022-11-24 11:45 ` Eli Zaretskii
2022-11-27 8:27 ` Gabriel
2022-11-27 9:45 ` Eli Zaretskii [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
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=83wn7gpw83.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59448@debbugs.gnu.org \
--cc=gabriel376@hotmail.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).