From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 17831@debbugs.gnu.org, sdl.web@gmail.com
Subject: bug#17831: 24.4.50; bad default value for `Man-width'
Date: Tue, 24 Jun 2014 18:46:37 +0300 [thread overview]
Message-ID: <83zjh2qpia.fsf@gnu.org> (raw)
In-Reply-To: <53A92532.9040901@gmx.at>
> Date: Tue, 24 Jun 2014 09:13:54 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: 17831@debbugs.gnu.org, Leo Liu <sdl.web@gmail.com>
>
> To fix this we could either use some sort of maximimum width (for me
> more than 80 columns are not very readable anyway) and propose an
> adequate display buffer action or implement simple heuristics to detect
> how large the window used by `display-buffer' would be and fill the
> buffer in some adequate manner.
None of this will ever work 100% reliably in the "M-x man" case,
because while the command runs in the background, the user could
change the window and frame configuration at will.
> Alternatively, we could display the buffer first, look at what size we
> get, fill the buffer, and possibly resize the window afterwards. For
> `with-temp-buffer-window' this means that we would have to fill the
> buffer either via `temp-buffer-window-show-hook' or in QUIT-FUNCTION.
But this will momentarily flash incorrect (e.g., empty) display,
right? Not nice, IMO.
next prev parent reply other threads:[~2014-06-24 15:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 13:30 bug#17831: 24.4.50; bad default value for `Man-width' Leo Liu
2014-06-23 12:53 ` Stefan Monnier
2014-06-23 23:17 ` Juri Linkov
2014-06-24 1:26 ` Stefan Monnier
2014-06-24 7:13 ` martin rudalics
2014-06-24 12:53 ` Stefan Monnier
2014-06-24 15:55 ` Eli Zaretskii
2014-06-24 17:33 ` Stefan Monnier
2014-06-24 17:59 ` Eli Zaretskii
2014-06-25 6:54 ` martin rudalics
2014-06-24 15:46 ` Eli Zaretskii [this message]
2014-06-24 17:31 ` Stefan Monnier
2014-06-24 17:56 ` Eli Zaretskii
2014-06-24 19:35 ` Stefan Monnier
2014-06-24 20:06 ` Eli Zaretskii
2014-06-24 20:29 ` Stefan Monnier
2014-06-24 23:48 ` Juri Linkov
2014-06-25 3:11 ` Stefan Monnier
2014-06-26 23:49 ` Juri Linkov
2014-06-27 2:16 ` Stefan Monnier
2014-06-27 23:45 ` Juri Linkov
2014-06-28 1:30 ` Stefan Monnier
2014-06-29 23:42 ` Juri Linkov
2014-06-30 3:29 ` Stefan Monnier
2014-06-24 23:42 ` Juri Linkov
2014-06-25 6:54 ` martin rudalics
2014-06-24 23:44 ` bug#17809: 24.4.50; Completions display Juri Linkov
2014-06-25 6:54 ` martin rudalics
2014-06-26 23:41 ` Juri Linkov
2014-06-27 2:07 ` Stefan Monnier
2014-06-27 6:43 ` martin rudalics
2014-06-27 23:54 ` Juri Linkov
2014-06-28 8:18 ` martin rudalics
2014-06-29 23:47 ` Juri Linkov
2014-07-01 23:30 ` Juri Linkov
2014-07-04 23:40 ` Juri Linkov
2014-07-06 4:32 ` Stefan Monnier
2014-07-06 23:32 ` Juri Linkov
2014-07-07 1:21 ` Stefan Monnier
2014-07-07 1:24 ` Stefan Monnier
2014-07-07 6:49 ` Juri Linkov
2014-07-08 3:43 ` Stefan Monnier
2014-07-08 8:03 ` Juri Linkov
2014-06-27 6:43 ` martin rudalics
2014-06-27 23:53 ` Juri Linkov
2014-06-28 8:17 ` martin rudalics
2014-06-23 23:21 ` bug#17831: 24.4.50; bad default value for `Man-width' Leo Liu
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=83zjh2qpia.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17831@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=sdl.web@gmail.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 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).