From: Eli Zaretskii <eliz@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 19697@debbugs.gnu.org
Subject: bug#19697: 25.0.50; Emacs manual line is 239 chars wide!
Date: Thu, 29 Jan 2015 18:53:42 +0200 [thread overview]
Message-ID: <83oaphmstl.fsf@gnu.org> (raw)
In-Reply-To: <83bnlkozxe.fsf@gnu.org>
> Date: Tue, 27 Jan 2015 20:12:45 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: eggert@cs.ucla.edu, 19697@debbugs.gnu.org
>
> > Date: Tue, 27 Jan 2015 09:58:42 -0800 (PST)
> > From: Drew Adams <drew.adams@oracle.com>
> > Cc: drew.adams@oracle.com, 19697@debbugs.gnu.org
> >
> > I see. I thought that Emacs was responsible for, or able to take
> > care of, line lengths.
>
> The line length in the Texinfo sources is just fine. It's just that
> makeinfo renders this particular place incorrectly.
>
> > Anyway, OK by me if you close this as not an Emacs bug.
>
> If there's a rainy day soon, I might try something to work around the
> makeinfo bug.
I found a way to kludge around the bug in Texinfo, and committed the
result to the emacs-24 branch.
next prev parent reply other threads:[~2015-01-29 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<4b6ae1aa-f912-4ee1-9cf5-c2586ff0ea86@default>
[not found] ` <<54C7B12F.2070904@cs.ucla.edu>
[not found] ` <<83r3ugp1s2.fsf@gnu.org>
2015-01-27 17:58 ` bug#19697: 25.0.50; Emacs manual line is 239 chars wide! Drew Adams
2015-01-27 18:12 ` Eli Zaretskii
2015-01-27 21:09 ` Andreas Schwab
2015-01-29 16:53 ` Eli Zaretskii [this message]
2015-01-27 21:42 ` Paul Eggert
[not found] ` <<6524c25b-8914-423c-b597-bb9a709af324@default>
[not found] ` <<83bnlkozxe.fsf@gnu.org>
[not found] ` <<83oaphmstl.fsf@gnu.org>
2015-01-29 16:59 ` Drew Adams
2015-01-26 23:50 Drew Adams
2015-01-27 15:39 ` Paul Eggert
2015-01-27 15:57 ` Drew Adams
2015-01-27 16:14 ` Drew Adams
2015-01-27 17:55 ` Eli Zaretskii
2015-01-27 17:32 ` 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=83oaphmstl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19697@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).