From: Juri Linkov <juri@jurta.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 2588@debbugs.gnu.org
Subject: bug#2588: 23.0.90; Man buffer improperly formatted - wrong width
Date: Fri, 07 Oct 2011 03:34:51 +0300 [thread overview]
Message-ID: <87sjn5ftxs.fsf@mail.jurta.org> (raw)
In-Reply-To: <m3pqi9hj7i.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 07 Oct 2011 00:02:41 +0200")
>>> Did anything more happen here afterwards? Is this still buggy?
>>
>> Is this the same as bug#9084?
>
> And it is, I think. Is there a particular reason why we don't just use
> `frame-width' in these circumstances?
On 07 Mar 2009 in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2588#60
Stefan said:
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.
On 11 Jan 2010 I posted a patch that implements asynchronous formatting
in the immediately displayed Man buffer in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5054#76
(see subthread with the subject "Man truncated", please don't merge bug#5054
because its initial report was about a different problem).
Is it time to install this patch now?
It fixes the problem with wrong widths in a new window/frame.
Though it doesn't implement formatting on the fly from the process-filter,
but maybe this could be implemented later in 24.2?
next prev parent reply other threads:[~2011-10-07 0:34 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 [this message]
2009-03-08 4:05 ` Stefan Monnier
2009-03-08 15:45 ` Chong Yidong
2009-03-08 15:57 ` Drew Adams
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=87sjn5ftxs.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=2588@debbugs.gnu.org \
--cc=larsi@gnus.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.