From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: 62099@debbugs.gnu.org
Subject: bug#62099: 29.0.60; Intentional change to *Help* source code links?
Date: Sat, 11 Mar 2023 14:40:01 +0200 [thread overview]
Message-ID: <83lek3wjfi.fsf@gnu.org> (raw)
In-Reply-To: <87edpvihw5.fsf@gmx.net> (message from Stephen Berman on Sat, 11 Mar 2023 13:36:58 +0100)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 62099@debbugs.gnu.org
> Date: Sat, 11 Mar 2023 13:36:58 +0100
>
> > Thank you for your detailed report. However, I'm not sure I
> > understand the bottom line: is there a bug here or isn't there? If
> > the links work, and the only issue is how they look, why is that a
> > problem?
>
> It does seem to be an aesthetic issue, not a functional one, but if it
> is an unintended consequence of the above commit, as it seems to be, and
> if it's also an undesirable change, as I think it is (the '/..' prefix
> is at least confusing), then I think it qualifies as a bug, though not a
> high-priority one. If you agree, then I would ask for it to be left
> open, in case someone wants to try fixing it. I might try myself,
> though I also have more pressing things to do.
Maybe Lars (CC'ed) can tell if this is intended or not.
next prev parent reply other threads:[~2023-03-11 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:10 bug#62099: 29.0.60; Intentional change to *Help* source code links? Stephen Berman
2023-03-11 12:11 ` Eli Zaretskii
2023-03-11 12:36 ` Stephen Berman
2023-03-11 12:40 ` Eli Zaretskii [this message]
2023-05-11 21:14 ` Stephen Berman
2023-05-12 5:51 ` Eli Zaretskii
2023-05-14 16:18 ` Stephen Berman
2023-05-14 17:41 ` Eli Zaretskii
2023-05-14 23:11 ` Stephen Berman
2023-05-15 11:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lek3wjfi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62099@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stephen.berman@gmx.net \
/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.