all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Olaf Dietsche <olaf--mail.bug-gnu-emacs@olafdietsche.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25208@debbugs.gnu.org
Subject: bug#25208: 24.5; man output uses wrong width
Date: Thu, 15 Dec 2016 18:20:39 +0100	[thread overview]
Message-ID: <87y3zhkt20.fsf@dog.fritz.box> (raw)
In-Reply-To: <831sx99lgo.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Dec 2016 19:00:07 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Olaf Dietsche <olaf--mail.bug-gnu-emacs@olafdietsche.de>
>> Date: Thu, 15 Dec 2016 14:08:13 +0100
>> 
>> I use a wide display and Emacs full-screen.
>> 
>> - emacs -Q
>> - Make the Emacs frame full-screen, so it is wider than high and shows
>>   only one window.
>> - M-x man RET ps RET -- any command works
>> 
>> Now the frame will be split into two windows side by side, one showing
>> the man page of `ps`. The man page will contain long lines, which are
>> truncated instead of wrapped around. You can see the whole lines, when
>> you scroll horizontally, of course.
>> 
>> This will not happen, if the frame is already split horizontally in two
>> equal wide windows. When you move the vertical divider to the left or
>> right and invoke another man command, you can see, that man always uses
>> the width of the starting window instead of the target (displaying)
>> window.
>
> This is the intended behavior.  What would you like to see instead?

Sorry for the incomplete bug report. I would expect to see the man
page's lines properly wrapped in the target window, so I can read it
without the need for scrolling horizontally.





  reply	other threads:[~2016-12-15 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 13:08 bug#25208: 24.5; man output uses wrong width Olaf Dietsche
2016-12-15 16:57 ` Mark Oteiza
2016-12-15 17:00 ` Eli Zaretskii
2016-12-15 17:20   ` Olaf Dietsche [this message]
2016-12-15 19:49     ` Eli Zaretskii
2016-12-15 21:31       ` Olaf Dietsche
2016-12-16  8:30         ` Eli Zaretskii
2016-12-16 10:23           ` Olaf Dietsche

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=87y3zhkt20.fsf@dog.fritz.box \
    --to=olaf--mail.bug-gnu-emacs@olafdietsche.de \
    --cc=25208@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.