unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master fc759eb: Fix with-coding-priority markup in Elisp manual
Date: Sat, 13 Jun 2020 18:03:25 +0100	[thread overview]
Message-ID: <87eeqi3nky.fsf@tcd.ie> (raw)
In-Reply-To: <83wo4a3oju.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Jun 2020 19:42:29 +0300")

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



  reply	other threads:[~2020-06-13 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13 15:49 [Emacs-diffs] master fc759eb: Fix with-coding-priority markup in Elisp manual Eli Zaretskii
2020-06-13 15:38 ` Basil L. Contovounesios
2020-06-13 15:49   ` Eli Zaretskii
2020-06-13 16:35     ` Basil L. Contovounesios
2020-06-13 16:42       ` Eli Zaretskii
2020-06-13 17:03         ` Basil L. Contovounesios [this message]
2020-06-13 17:16           ` 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=87eeqi3nky.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).