emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Colin Baxter <m43cap@yandex.com>
Cc: emacs-orgmode@gnu.org, Robert Klein <roklein@roklein.de>
Subject: Re: Documentation fix
Date: Mon, 15 May 2017 18:00:02 +0200	[thread overview]
Message-ID: <87mvaexg8t.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r2zq1bd3.fsf@yandex.com> (Colin Baxter's message of "Mon, 15 May 2017 14:46:32 +0100")

Hello,

Colin Baxter <m43cap@yandex.com> writes:

>>>>>> "Nicolas" == Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>     Nicolas> Hello, Robert Klein <roklein@roklein.de> writes:
>
>     >> Ahh, well, on second look it only was a warning:
>     >> 
>     >> org.texi:11371: warning: `.' or `,' must follow @xref, not `f'.
>
>     Nicolas> Oddly, I don't get this warning when using "make
>     Nicolas> info". Anyway, I added the missing comma. Thank you.
>
>     Nicolas> Regards,
>
>     Nicolas> -- Nicolas Goaziou
>
>
> It's depends on your version of makeinfo. For example with makeinfo (GNU
> texinfo) 4.13, there are no warnings; however, with texi2any (GNU
> texinfo) 6.0, as well as the above `.' or `,' warning, there are
> multiple `@table has text but no @item' warnings. The docs still make
> ok, though.

I see, thanks. Could you send the warnings, or better, a patch, so as to
fix them?

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-05-15 16:00 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 [this message]
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

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=87mvaexg8t.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=m43cap@yandex.com \
    --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).