unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: texinfo-master-menu and emacs.texi
Date: Wed, 7 Dec 2011 13:26:48 -0600	[thread overview]
Message-ID: <20191.48632.665251.448872@gargle.gargle.HOWL> (raw)
In-Reply-To: <h87h28tgcg.fsf@fencepost.gnu.org>

On Wed Dec 7 2011 Glenn Morris wrote:
> > Unless your manual is on a single large file, in which case I expect
> > texinfo-master-menu to just work.
> 
> There's an old unanswered bug report about it not working:
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2975

Thanks...Now I am yet more confused. I thought I look into
emacs.texi because I assumed that this info manual has been updated
continuously in recent years and this updating has been done with
the editor of my choice which is emacs. So what have people done who
contributed to the emacs info manual to work around these
difficulties? Which parts of emacs' texinfo support do what they are
supposed to do and which parts seem to be malfunctioning?

Roland

PS: I would find it rather ironical if emacs' texinfo support gave
me a hard time if I want to include files gpl.texi and
doclicense.texi in an info manual.



  reply	other threads:[~2011-12-07 19:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  9:20 texinfo-master-menu and emacs.texi Roland Winkler
2011-12-07  9:57 ` Leo
2011-12-07 14:30   ` Roland Winkler
2011-12-07 13:19 ` Eli Zaretskii
2011-12-07 14:08   ` Roland Winkler
2011-12-08  6:46     ` Eli Zaretskii
2011-12-08 19:04       ` Roland Winkler
2011-12-10 11:01     ` Eli Zaretskii
2011-12-07 17:57   ` Glenn Morris
2011-12-07 19:26     ` Roland Winkler [this message]
2011-12-07 22:08     ` Roland Winkler
2011-12-07 22:13       ` Karl Berry
2011-12-10 12:42     ` 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=20191.48632.665251.448872@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).