all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Drew Adams <drew.adams@oracle.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 19697@debbugs.gnu.org
Subject: bug#19697: 25.0.50; Emacs manual line is 239 chars wide!
Date: Tue, 27 Jan 2015 08:14:36 -0800 (PST)	[thread overview]
Message-ID: <331f67a3-ae7e-4e05-9114-c9e1c0af709a@default> (raw)
In-Reply-To: <436393ac-3949-427b-8982-af311d18d030@default>

> > It could be a 'makeinfo' or platform issue.  I'm using makeinfo (GNU
> > texinfo) 5.2, as shipped with Fedora.  Here's how the .info file was
> > built:
> 
> I'm using the MS Windows binary I reported the problem for.
> 
> Your reply indicates that this might be a build or platform-dependent
> bug, which is useful info.

It might also be a problem that has already been fixed.  The build
I reported about is from October 2014.





  reply	other threads:[~2015-01-27 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 23:50 bug#19697: 25.0.50; Emacs manual line is 239 chars wide! Drew Adams
2015-01-27 15:39 ` Paul Eggert
2015-01-27 15:57   ` Drew Adams
2015-01-27 16:14     ` Drew Adams [this message]
2015-01-27 17:55       ` Eli Zaretskii
2015-01-27 17:32   ` Eli Zaretskii
     [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     ` Drew Adams
2015-01-27 18:12       ` Eli Zaretskii
2015-01-27 21:09         ` Andreas Schwab
2015-01-29 16:53         ` Eli Zaretskii
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

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=331f67a3-ae7e-4e05-9114-c9e1c0af709a@default \
    --to=drew.adams@oracle.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.