From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: A build problem with flymake.info
Date: Sat, 28 Jul 2018 14:27:37 +0100 [thread overview]
Message-ID: <87tvoj8p86.fsf@gmail.com> (raw)
In-Reply-To: <83fu03r8ln.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Jul 2018 12:51:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: João Távora <joaotavora@gmail.com>
>> Date: Sat, 28 Jul 2018 09:39:42 +0100
>> Cc: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
>>
>> I tried, looked around, but iirc it wasn't easy, or I was afraid of
>> breaking something. Or maybe it was that not all texinfo processors
>> support that feature. Maybe i was looking in the wrong place, I don't
>> remember.
>>
>> Anyway, if you know an easier way, I'm all ears.
>
> Maybe there's a misunderstanding on my part: where (in what commands)
> did you need this, and in which use cases?
C-c C-c, which is bound to TeX-command-master when using the non-core
AucTex package. But the problem also happens with Emacs's built-in
C-c RET C-b (makeinfo-buffer)
TeX-command-master is where I tried fixing it, so it may be easier in
Emacs's built-in makeinfo.el, which is where makeinfo-buffer hails from.
(For those curious, TeX-command-master is a command multiplexer designed
to understand what the next logical command for a certain file is (e.g
first compiling, then viewing, etc...) It works fine with latex files
and doc/misc/flymake.texi, except for the load-path issue)
> IOW, can you describe in more detail what are the situations where you
> need to modify the @include lines, and why?
<from emacs checkout dir>
src/emacs -Q
C-x C-f RET doc/misc/flymake.texi RET ; find the file
C-c RET C-b RET ; makeinfo-buffer
If I don't modify the include line, this errors. If I modify it, it
succeeds and presents the updated info buffer.
João
next prev parent reply other threads:[~2018-07-28 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 7:23 A build problem with flymake.info martin rudalics
2018-07-28 7:47 ` João Távora
2018-07-28 8:05 ` Eli Zaretskii
2018-07-28 8:39 ` João Távora
2018-07-28 9:51 ` Eli Zaretskii
2018-07-28 13:27 ` João Távora [this message]
2018-07-28 13:48 ` Eli Zaretskii
2018-08-01 8:03 ` João Távora
2018-08-01 9:00 ` Eli Zaretskii
2018-07-28 8:30 ` martin rudalics
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=87tvoj8p86.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).