From: "Thomas S. Dye" <tsd@tsdye.com>
To: William Henney <whenney@gmail.com>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] missing braces on line 5914 of doc/org.texi
Date: Fri, 25 Jun 2010 12:37:58 -1000 [thread overview]
Message-ID: <48A57924-056C-4694-84E1-BC08B5856A77@tsdye.com> (raw)
In-Reply-To: <AANLkTimUjh5dDartUZ2h1Kkd8Ck015zizeDbRI2t1XfW@mail.gmail.com>
Aloha all,
It might make sense to hold off on this patch, or not (I'm behind Will
on the git learning curve). I'm in the middle of revising the Org-
babel chapter of org.texi to bring it into line with the rest of the
documentation. I saw this error when I pulled earlier today and fixed
it along with many other changes. Holding off might save one of the
maintainers having to deal with a merge conflict when I send a patch
with my Org-babel changes.
All the best,
Tom
On Jun 25, 2010, at 12:15 PM, William Henney wrote:
> Hi list
>
> I just got the following error when updating my org installation:
>
> $ sudo make install-info
> (cd doc; makeinfo --no-split org.texi -o org)
> org.texi:5914: @kbd expected braces.
> org.texi:5914: @kbd missing close brace.
> makeinfo: Removing output file `org' due to errors; use --force to
> preserve.
> make: *** [doc/org] Error 1
>
> Attached trivial patch fixes this
>
> Cheers
>
> Will (who is finally starting to learn to use git)
>
>
> --
>
> Dr William Henney, Centro de Radioastronomía y Astrofísica,
> Universidad Nacional Autónoma de México, Campus Morelia
> <0001-Fix-missing-braces-in-
> org.texi.patch>_______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-06-25 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 22:15 [PATCH] missing braces on line 5914 of doc/org.texi William Henney
2010-06-25 22:37 ` Thomas S. Dye [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=48A57924-056C-4694-84E1-BC08B5856A77@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=whenney@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/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).