[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emacs-diffs] master fc759eb: Fix with-coding-priority markup in Eli
From: |
Basil L. Contovounesios |
Subject: |
Re: [Emacs-diffs] master fc759eb: Fix with-coding-priority markup in Elisp manual |
Date: |
Sat, 13 Jun 2020 18:03:25 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Cc: emacs-devel@gnu.org
>> Date: Sat, 13 Jun 2020 17:35:58 +0100
>>
>> > What problem are you trying to avoid here?
>>
>> >> ...like ‘progn’ does (see progn.), with...
>> ^^^
>> This
>>
>> There shouldn't be a full stop there, right?
>
> Maybe not, but it's info.el which does that, not Texinfo.
Ah, I didn't realise this was an info.el artefact.
I've now reverted the change:
Revert markup change in with-coding-priority docs
6cdecc2659 2020-06-13 17:54:51 +0100
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=6cdecc2659a290f4a9eddb498978e3b07d5cbc58
> From the Texinfo POV the result is perfectly correct, and provides a
> better location to an Info reader (although ISTR the Emacs reader
> disregards that).
Are you referring to the fact that following the xref doesn't take you
to the definition of progn? Because I would have guessed that's because
there's no @anchor{progn}. Or is Texinfo smarter about it?
> IOW, the way info.el displays this is not a reason to avoid the 2nd
> argument of a cross-reference. If we think the display is wrong, we
> should fix info.el to yield a better one.
I agree, thanks,
--
Basil