From: Eli Zaretskii <eliz@gnu.org>
To: Lluís <xscript@gmx.net>
Cc: 23169@debbugs.gnu.org
Subject: bug#23169: 24.5; Inconsistent text reflow in man pages depending on window configuration
Date: Thu, 31 Mar 2016 19:48:47 +0300 [thread overview]
Message-ID: <83egaqvbio.fsf@gnu.org> (raw)
In-Reply-To: <87bn5ug55o.fsf@fimbulvetr.bsc.es> (message from Lluís on Thu, 31 Mar 2016 15:15:15 +0200)
> From: Lluís <xscript@gmx.net>
> Date: Thu, 31 Mar 2016 15:15:15 +0200
>
> Before the man process is started, "Man-start-calling" calculates the "COLUMNS"
> envvar using "window-width" before splitting windows. The window split happens
> later once the process finishes, and the buffer is shown through
> "Man-notify-when-ready".
>
> Assuming the buffer is going to be shown on a vertical split, the text will go
> beyond the window limits if there was no other window in the frame (or if a new
> window is used), or will be reflowed with the proper width if an existing window
> is reused.
>
> Manually calling "Man-update-manpage" fixes it, but it's annoying. Simply adding
> a call to "Man-update-manpage" in "Man-notify-when-ready" would fix it
> ("(with-current-buffer man-buffer (Man-update-manpage))" in the "friendly" case
> for me).
>
> As a bonus, this fix also reflows the text when an existing buffer is reused.
Maybe I'm missing something, but won't your suggestion effectively
replace the background rendering of man pages with fully synchronous
one?
The usual way to fix these problems is to set Man-width to a non-nil
value, as appropriate for your frame/window dimensions. Would that
solve the problem for you?
next prev parent reply other threads:[~2016-03-31 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 13:15 bug#23169: 24.5; Inconsistent text reflow in man pages depending on window configuration Lluís
2016-03-31 16:48 ` Eli Zaretskii [this message]
2016-04-01 15:13 ` Lluís
2016-04-01 16:20 ` martin rudalics
2016-04-01 17:40 ` Eli Zaretskii
2016-04-01 19:51 ` Juri Linkov
2016-04-02 11:30 ` Lluís
2016-04-02 20:23 ` Juri Linkov
2016-04-03 13:30 ` Lluís
2019-09-29 5:40 ` Stefan Kangas
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=83egaqvbio.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23169@debbugs.gnu.org \
--cc=xscript@gmx.net \
/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).