all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 2588@emacsbugs.donarmstrong.com
Subject: bug#2588: 23.0.90; Man buffer improperly formatted - wrong width
Date: Sun, 08 Mar 2009 21:04:55 +0200	[thread overview]
Message-ID: <uy6vfltt4.fsf@gnu.org> (raw)
In-Reply-To: <87wsb0m1ym.fsf@cyd.mit.edu>

> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: drew.adams@oracle.com,  2588@emacsbugs.donarmstrong.com
> Date: Sun, 08 Mar 2009 12:08:49 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > AFAICS, we started setting COLUMNS in the environment because on some
> > GNU/Linux system, under X, not setting it would result in over-long
> > lines.  To avoid that with pop-up-frames, we could set COLUMNS to the
> > value 80.  For a frame that is not yet created, 80 sounds like a
> > better default than the width of some other frame/window.
> 
> Right, and this handles the case where the selected frame is abnormally
> wide.  But suppose the selected frame is the normal width, and has a
> width of 200.  The default-to-80-columns would do the wrong thing.

Again, I was talking _only_ about the use-case where pop-up-frames is
non-nil.  In that case, how do you know that default-to-80-columns is
the wrong thing?  The fact that the frame selected when "M-x man" is
invoked is 200 columns wide says nothing about the frame that will be
used to display the formatted manual.

Or maybe you meant that the frame to be popped up will be 200 columns
wide.  But that is a marginal case, IMO, and it didn't work in Emacs
20, either.  So we could leave that for fixing after the release, if
ever.

When pop-up-frames is nil, the current code works well, and we don't
need to change it, IMO, certainly not before 23.1 is released.






  parent reply	other threads:[~2009-03-08 19:04 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07  4:22 bug#2588: 23.0.90; Man buffer improperly formatted - wrong width Chong Yidong
2009-03-07  4:50 ` Drew Adams
2009-03-07 14:15   ` Eli Zaretskii
2009-03-07 16:20     ` Drew Adams
2009-03-07 19:27       ` Eli Zaretskii
2009-03-07 19:43         ` Chong Yidong
2009-03-07 19:45           ` Drew Adams
2009-03-07 20:07           ` Eli Zaretskii
2009-03-08 16:08             ` Chong Yidong
2009-03-08 16:23               ` Drew Adams
2009-03-08 19:06                 ` Chong Yidong
2009-03-08 19:23                   ` Eli Zaretskii
2009-03-08 19:40                     ` Chong Yidong
2009-03-08 20:01                       ` Eli Zaretskii
2009-03-08 20:17                       ` Drew Adams
2009-03-09  4:05                         ` Eli Zaretskii
2009-03-09  5:33                           ` Drew Adams
2009-03-09  3:27                       ` Stefan Monnier
2009-03-09  3:38                         ` Chong Yidong
2009-03-09 13:28                           ` Stefan Monnier
2009-03-08 20:16                   ` Drew Adams
2009-03-09  4:03                     ` Eli Zaretskii
2009-03-09  5:33                       ` Drew Adams
2012-01-10 18:38                   ` Glenn Morris
2012-01-10 18:39                     ` Glenn Morris
2009-03-08 19:04               ` Eli Zaretskii [this message]
2009-03-08 19:45               ` Stefan Monnier
2009-03-08 20:04                 ` Eli Zaretskii
2011-09-11 21:51                 ` Lars Magne Ingebrigtsen
2011-09-15 18:45                   ` Juri Linkov
2011-09-17  5:22                     ` Lars Magne Ingebrigtsen
2011-10-06 22:02                   ` Lars Magne Ingebrigtsen
2011-10-07  0:34                     ` Juri Linkov
2009-03-08  4:05     ` Stefan Monnier
2009-03-08 15:45       ` Chong Yidong
2009-03-08 15:57         ` Drew Adams
2009-03-08 19:43         ` Stefan Monnier
2009-03-08 20:03           ` Eli Zaretskii
2009-03-08 20:17             ` Drew Adams
2014-07-01 23:57       ` Juri Linkov
  -- strict thread matches above, loose matches on Subject: below --
2009-03-06 20:51 Drew Adams
2009-03-07 13:58 ` Eli Zaretskii
2009-03-07 16:20   ` 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=uy6vfltt4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=2588@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /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.