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: Fri, 01 Apr 2016 20:40:40 +0300 [thread overview]
Message-ID: <8337r5teg7.fsf@gnu.org> (raw)
In-Reply-To: <87oa9t8iq4.fsf@fimbulvetr.bsc.es> (message from Lluís on Fri, 01 Apr 2016 17:13:55 +0200)
> From: Lluís <xscript@gmx.net>
> Cc: 23169@debbugs.gnu.org
> Date: Fri, 01 Apr 2016 17:13:55 +0200
>
> > 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?
>
> Thing is I don't know the width of the window that will be used, since in some
> cases it does not exist yet:
>
> +-----+ +--+--+
> | | | | |
> | | -> M-x man man -> | | |
> | | | | |
> +-----+ +--+--+
Isn't the window that man will use half of the window before the
command? Then you know the width in advance, because you are familiar
with your window and frame configurations
> The ideal without breaking the asynchronicity would be to somehow display the
> new buffer on a window before populating it (display-buffer might or might not
> reuse a window here), calculate its window's width, set COLUMNS, asynchronously
> call man to populate the buffer, and then really show the buffer on the previous
> window.
>
> The only problem is that creating a temporary window just to calculate its width
> could annoy people because the contents won't be shown yet.
Yes, that's the problem.
next prev parent reply other threads:[~2016-04-01 17:40 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
2016-04-01 15:13 ` Lluís
2016-04-01 16:20 ` martin rudalics
2016-04-01 17:40 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8337r5teg7.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 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.