From: Colin Baxter <m43cap@yandex.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, Robert Klein <roklein@roklein.de>
Subject: Re: Documentation fix
Date: Thu, 25 May 2017 12:07:31 +0100 [thread overview]
Message-ID: <87r2zdqjnw.fsf@yandex.com> (raw)
In-Reply-To: <87o9uiclb9.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 24 May 2017 17:43:22 +0200")
Dear Nicolas,
>>>>> "NG" == Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
NG> Hello, Colin Baxter <m43cap@yandex.com> writes:
>> I've appended (inline) the warnings associated with the
>> documentation output of 'make all', removing extraneous output.
>>
>> ---- Begin -------- org-version: 9.0.7
>> (release_9.0.7-478-g30ceb5) makeinfo --no-split org.texi -o org
>> makeinfo --html --number-sections --no-split -o org.html org.texi
>> texi2pdf --batch --clean --expand org.texi -:1267: warning:
>> @itemx should not begin @table -:1345: warning: @table has text
>> but no @item
NG> [...]
>>
>> The 'make all' process continues satisfactorily to its
>> conclusion.
NG> These are innocuous warnings.
>> Deleting the 'x' from 'itemx' in org.texi at the lines
>> corresponding to the warnings '@itemx should not begin @table',
>> that is, at lines 1267, 7819, 10342, removes those
>> warnings. That's all the patch did.
NG> This would be wrong. The @orgcmd macro above already introduces
NG> @item, so the second one really needs to be @itemx.
Yes, I see that.
NG> One solution would be to replace the @itemx ... with @xorgkey,
NG> @xorgcmd, or @xorgcmdnki depending on the needs. But then, it
NG> would fall-back to the other warning, i.e., a @table without any
NG> @item (all are @orgsomething macros).
NG> I'm no Texinfo expert, so I'm not sure what is the best way to
NG> handle this. Maybe also create a special macro that would create
NG> a table. It sounds convoluted, though.
I'll look at this more carefully and see what I can do - if anything. It
will have to wait until I have the time, though.
Best wishes,
Colin.
--
--
Colin Baxter
m43cap@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8
prev parent reply other threads:[~2017-05-25 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 6:34 Documentation fix Robert Klein
2017-05-15 6:42 ` Nicolas Goaziou
2017-05-15 7:13 ` Robert Klein
2017-05-15 12:06 ` Nicolas Goaziou
2017-05-15 13:46 ` Colin Baxter
2017-05-15 16:00 ` Nicolas Goaziou
2017-05-15 19:30 ` Colin Baxter
2017-05-23 19:22 ` Nicolas Goaziou
2017-05-24 13:14 ` Colin Baxter
2017-05-24 15:43 ` Nicolas Goaziou
2017-05-25 11:07 ` Colin Baxter [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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2zdqjnw.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=roklein@roklein.de \
/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/org-mode.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).