From: Juri Linkov <juri@linkov.net>
To: Gabriel <gabriel376@hotmail.com>
Cc: 59448@debbugs.gnu.org
Subject: bug#59448: 29.0.50; URIs in Dictionary are not properly handled
Date: Tue, 22 Nov 2022 09:54:35 +0200 [thread overview]
Message-ID: <86y1s3bjn8.fsf@mail.linkov.net> (raw)
In-Reply-To: <SJ0PR06MB860970E179F60D9E3FB536278B0A9@SJ0PR06MB8609.namprd06.prod.outlook.com> (Gabriel's message of "Mon, 21 Nov 2022 11:52:42 -0300")
> URIs (http, mail, news, ftp etc) in Dictionary are not properly handled.
> It means that URIs are treated like a regular search phrase, which is
> not really useful for `dictionary-search' (since most will not return
> any results) and no default mechanism is available to follow such URIs.
Thanks for the bug reports (your posts about tab-line will be addressed soon too).
> Other alternative is to handle URIs natively in `dictionary-mode'. For
> example, some proper URI handling in the action of `dictionary-link'
> button or in `dictionary-display-word-definition'.
>
> Nevertheless, I believe the default behavior of Dictionary could be
> improved, i.e., to avoid treating URIs as regular search words that will
> provide little to none value to users (since it will mostly fail to find
> results) and to provide a better integration with other Emacs features
> (e.g.: EWW to browse URLs or Gnus to compose emails).
Another alternative would be to fall back to handling URIs
only when dictionary-search fails to find a definition.
So instead of displaying the message "Word not found" it could
try to open the URI that can be found in the provided string.
next prev parent reply other threads:[~2022-11-22 7:54 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 [this message]
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
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=86y1s3bjn8.fsf@mail.linkov.net \
--to=juri@linkov.net \
--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).