From: Leo <sdl.web@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: visual-line-mode and line wrapping
Date: Tue, 25 May 2010 17:33:53 +0100 [thread overview]
Message-ID: <xbai4ohwkkjy.fsf@cam.ac.uk> (raw)
In-Reply-To: <jwvfx1gnkp0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 25 May 2010 10:04:29 -0400")
On 2010-05-25 15:04 +0100, Stefan Monnier wrote:
>> Also, it would be nice if one could bound the width used for wrapping
>> so that when a window becomes wider than a certain size, the wrapping
>> width would stick at some maximum -- this is because extremely wide
>> paragraphs can be hard to read. Similarly, when windows become narrow
>> than some width, it would be nice if wrapping actually respected some
>> _minimum_ width, so that you don't end up with the text in a single
>> narrow vertical line (the text is probably unreadable either way, but
>> at least with the bounded-width version, you can get a more sensible
>> idea of the document structure).
>
> I'd be fine with a "wrap-width" if it's a buffer-local variable that
> completely overrides the window-width wrapping, so that the wrapping
> is purely determined by the buffer and not by the window. This would
> mean that in narrow windows, long lines would be wrapped *and*
> truncated.
That will do for me too.
Yidong has said something like this in 2009:
http://article.gmane.org/gmane.emacs.devel/114706/match=visual+line+mode
I wonder if he has a patch in his local branch.
Thanks.
Leo
next prev parent reply other threads:[~2010-05-25 16:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 14:09 visual-line-mode and line wrapping Leo
2010-05-24 14:12 ` Lennart Borgman
2010-05-24 15:08 ` Leo
2010-05-24 15:29 ` Lennart Borgman
2010-05-24 16:42 ` Leo
2010-05-24 17:41 ` Lennart Borgman
2010-05-24 17:34 ` Stefan Monnier
2010-05-24 19:18 ` Leo
2010-05-24 19:31 ` Chong Yidong
2010-05-24 19:53 ` Leo
2010-05-24 20:33 ` Lennart Borgman
2010-05-24 19:58 ` Lennart Borgman
2010-05-24 20:27 ` Leo
2010-05-24 20:36 ` Lennart Borgman
2010-05-25 1:05 ` Johan Bockgård
2010-05-24 20:26 ` Stefan Monnier
2010-05-24 21:26 ` Lennart Borgman
2010-05-25 12:59 ` Sean Sieger
2010-05-25 5:10 ` Leo
2010-05-25 7:37 ` Miles Bader
2010-05-25 10:05 ` João Távora
2010-05-25 11:11 ` Lennart Borgman
2010-05-25 13:27 ` João Távora
2010-05-25 11:09 ` Lennart Borgman
2010-05-25 14:04 ` Stefan Monnier
2010-05-25 14:18 ` Lennart Borgman
2010-05-25 15:06 ` Drew Adams
2010-05-25 14:49 ` Drew Adams
2010-05-25 16:33 ` Leo [this message]
2010-05-25 8:36 ` Uday S Reddy
2010-05-25 11:48 ` Stephen J. Turnbull
2010-05-25 13:16 ` Uday S Reddy
2010-05-25 14:40 ` Drew Adams
2010-06-05 9:21 ` Uday S Reddy
2010-06-07 20:34 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2010-05-25 2:52 MON KEY
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=xbai4ohwkkjy.fsf@cam.ac.uk \
--to=sdl.web@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).