From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: nljlistbox2@gmail.com, 31927@debbugs.gnu.org
Subject: bug#31927: 26.1; Fragment/bookmark part of URL omitted in default offered by `eww'
Date: Sun, 22 Jul 2018 17:38:54 +0300 [thread overview]
Message-ID: <83wotnwd1d.fsf@gnu.org> (raw)
In-Reply-To: <m37elnquul.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 22 Jul 2018 15:10:42 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: nljlistbox2@gmail.com (N. Jackson), 31927@debbugs.gnu.org
> Date: Sun, 22 Jul 2018 15:10:42 +0200
>
> >> 3. M-: (thing-at-point-url-at-point) RET
> >> => https://en.wikipedia.org/wiki/Midsummer#History
> >>
> >> 4. M-: (url-get-url-at-point) RET
> >> => https://en.wikipedia.org/wiki/Midsummer
> >>
> >> Is it expected for these two functions to behave differently here?
> >
> > Yes, that's the question. I hope Lars (CC'ed) could comment on that.
>
> I think the behaviour of `url-get-url-at-point' is suboptimal here.
> Perhaps we should just make eww use `thing-at-point-url-at-point'
> instead? And mark `url-get-url-at-point' as obsolete, as it doesn't
> seem very actively maintained and duplicates thingatpt functionality.
Probably. Unless some functionality really needs to ignore the parts
after the hash, for some reason.
next prev parent reply other threads:[~2018-07-22 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 15:05 bug#31927: 26.1; Fragment/bookmark part of URL omitted in default offered by `eww' N. Jackson
2018-06-21 15:47 ` Eli Zaretskii
2018-06-21 23:11 ` N. Jackson
2018-06-22 6:29 ` Eli Zaretskii
2018-07-22 13:10 ` Lars Ingebrigtsen
2018-07-22 14:38 ` Eli Zaretskii [this message]
2018-07-29 15:57 ` Noam Postavsky
2018-07-29 17:16 ` N. Jackson
2018-07-29 20:44 ` N. Jackson
2019-05-13 19:17 ` Lars Ingebrigtsen
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=83wotnwd1d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31927@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=nljlistbox2@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 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.