all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>,
	"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 2588@emacsbugs.donarmstrong.com
Subject: bug#2588: 23.0.90; Man buffer improperly formatted - wrong width
Date: Sun, 8 Mar 2009 08:57:10 -0700	[thread overview]
Message-ID: <000001c9a006$8ac230c0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <871vt86ms0.fsf@cyd.mit.edu>

> > We could try to fix this: I think it would actually be 
> > desirable to pop up the frame immediately and then
> > asynchronously fill it as man's output comes in.
> >
> > This said, we could also just remove the COLUMNS business.
> > Who introduced this COLUMNS thingy and what was the 
> > motivation for it?
> 
> This is explained in the code comments: it's required to 
> ensure that the output of the manpage formatter has the
> same number of columns as the Emacs window/frame.

(1) The code does not do that correctly in the case cited: The new frame is 80
columns wide, but the text is formatted to 30 columns wide. (2) The code cannot
always know the number of columns of the to-be-created frame. (3) That number of
columns, even when the code can know it accurately, is *not pertinent* to how
the buffer should be formatted.

The code should not assume fixed window or frame sizes, or that those sizes
should govern formatting of the buffer text. That is not what is done generally
in Emacs when text is formatted (e.g. *Help*, *Apropos*,...).

The code here is nonstandard - Emacs generally does not behave like this. Some
particular group of users might (*might* - not sure) find this code helpful, but
for other users it is downright harmful. 

Please revert this unhelpful cleverness.








  reply	other threads:[~2009-03-08 15:57 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
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 [this message]
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='000001c9a006$8ac230c0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=2588@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=monnier@iro.umontreal.ca \
    /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.