* Re: [user42@zip.com.au: lispref paragraph break due to @anchor]
[not found] <200705020028.l420SLJ29010@f7.net>
@ 2007-05-02 15:15 ` Richard Stallman
2007-05-02 23:07 ` Karl Berry
0 siblings, 1 reply; 4+ messages in thread
From: Richard Stallman @ 2007-05-02 15:15 UTC (permalink / raw)
To: Karl Berry; +Cc: emacs-devel
P.S. Now I realize that the bug is in the Info output, not PDF output.
I will work on fixing makeinfo. Sorry for the wasted mail.
Please tell us when this is fixed, so we can make the Emacs release
with the corrected makeinfo.
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [user42@zip.com.au: lispref paragraph break due to @anchor]
2007-05-02 15:15 ` [user42@zip.com.au: lispref paragraph break due to @anchor] Richard Stallman
@ 2007-05-02 23:07 ` Karl Berry
2007-05-03 3:08 ` Eli Zaretskii
2007-05-03 13:54 ` Richard Stallman
0 siblings, 2 replies; 4+ messages in thread
From: Karl Berry @ 2007-05-02 23:07 UTC (permalink / raw)
To: rms; +Cc: emacs-devel
P.S. Now I realize that the bug is in the Info output, not PDF output.
I will work on fixing makeinfo. Sorry for the wasted mail.
Please tell us when this is fixed, so we can make the Emacs release
with the corrected makeinfo.
Shouldn't we just alter the Texinfo source to work around the bug as
Kevin suggested? It's trivial to do and does no harm. I can check in
the change on the branch (and see if there are any other instances).
Requiring usage of the development makeinfo seems
unnecessary/undesirable for this small bug?
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [user42@zip.com.au: lispref paragraph break due to @anchor]
2007-05-02 23:07 ` Karl Berry
@ 2007-05-03 3:08 ` Eli Zaretskii
2007-05-03 13:54 ` Richard Stallman
1 sibling, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2007-05-03 3:08 UTC (permalink / raw)
To: Karl Berry; +Cc: rms, emacs-devel
> Date: Wed, 2 May 2007 18:07:29 -0500
> From: karl@freefriends.org (Karl Berry)
> Cc: emacs-devel@gnu.org
>
> Please tell us when this is fixed, so we can make the Emacs release
> with the corrected makeinfo.
>
> Shouldn't we just alter the Texinfo source to work around the bug as
> Kevin suggested?
I think this is by far the best approach to the problem.
> Requiring usage of the development makeinfo seems
> unnecessary/undesirable for this small bug?
Agreed.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [user42@zip.com.au: lispref paragraph break due to @anchor]
2007-05-02 23:07 ` Karl Berry
2007-05-03 3:08 ` Eli Zaretskii
@ 2007-05-03 13:54 ` Richard Stallman
1 sibling, 0 replies; 4+ messages in thread
From: Richard Stallman @ 2007-05-03 13:54 UTC (permalink / raw)
To: Karl Berry; +Cc: emacs-devel
Shouldn't we just alter the Texinfo source to work around the bug as
Kevin suggested? It's trivial to do and does no harm. I can check in
the change on the branch (and see if there are any other instances).
I have nothing against it. If you think that is best, please do it.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-05-03 13:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200705020028.l420SLJ29010@f7.net>
2007-05-02 15:15 ` [user42@zip.com.au: lispref paragraph break due to @anchor] Richard Stallman
2007-05-02 23:07 ` Karl Berry
2007-05-03 3:08 ` Eli Zaretskii
2007-05-03 13:54 ` Richard Stallman
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).