unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 31464-done@debbugs.gnu.org
Subject: bug#31464: [PATCH] gnu: emacs-orgalist: Fix texinfo markup in description.
Date: Wed, 16 May 2018 11:08:55 +0200	[thread overview]
Message-ID: <87vaboge6w.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=pj6M8_TxSkmQ+tiwt9d1J1ujEe0-0c6WUgz5twkQ3QumA@mail.gmail.com> ("Gábor Boskovits"'s message of "Wed, 16 May 2018 08:18:58 +0200")

Hello!

Gábor Boskovits <boskovits@gmail.com> skribis:

> 2018-05-16 5:16 GMT+02:00 Eric Bavier <ericbavier@centurylink.net>:
>
>> On Tue, 15 May 2018 22:55:11 +0200
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>>
>> > Gábor Boskovits <boskovits@gmail.com> writes:
>> >
>> > > This markup breaks guix package -s on current master.
>> > > And guix lint also says, that there is invalid markup in the
>> description.
>> > > You might mean @dfn{LaTeX}, though.
>> >
>> > Yet, @LaTeX{} is valid Texinfo code.
>>
>> Yes, but guile's (texinfo) module does not understand the entire set of
>> texinfo commands.  I'm not sure whether the subset it does understand
>> is even clearly documented.
>>
>>
> I guess that we can contribute the @LaTeX{} macro to the guile module,
> at least a simplified version for sure, but I don't think it will make
> before
> core-updates next. In my opinion this fix is an acceptable tradeoff.
> We might add a comment to modify the markup, once support lands
> in guile, if it is deemed necessary. WDYT?

Clearly Guile’s (texinfo) modules could be improved.  In the meantime,
I’ve pushed this patch to fix the immediate issue.

Note that even when (texinfo) understands @LaTeX{}, we’ll probably
refrain from using it because Guix could be running on an older Guile.

Thanks,
Ludo’.

      reply	other threads:[~2018-05-16  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 20:03 [bug#31464] [PATCH] gnu: emacs-orgalist: Fix texinfo markup in description Gábor Boskovits
2018-05-15 20:14 ` Nicolas Goaziou
2018-05-15 20:19   ` Gábor Boskovits
2018-05-15 20:55     ` Nicolas Goaziou
2018-05-16  3:16       ` Eric Bavier
2018-05-16  6:18         ` Gábor Boskovits
2018-05-16  9:08           ` Ludovic Courtès [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vaboge6w.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31464-done@debbugs.gnu.org \
    --cc=boskovits@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).