From: David Kastrup <dak@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Display-based word wrapping
Date: Sun, 22 Jun 2008 22:12:42 +0200 [thread overview]
Message-ID: <858wwx5iv9.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87y74x9rfl.fsf@stupidchicken.com> (Chong Yidong's message of "Sun, 22 Jun 2008 15:54:06 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> I have been studying Kim Storm's display-based word wrapping code. I
> believe it's pretty safe, and suitable for inclusion into the Emacs 23
> release (probably turned off by default).
>
> The original patch included a `wrap-column' variable, but I'd like to
> modify this to use `truncate-lines' instead, as shown below. This would
> mean that word wrap always uses the right window edge as a wrap column.
> Any objections?
>
>
>
> truncate-lines is a variable defined in `C source code'.
>
> Documentation:
> Whether lines longer than the window width are truncated.
> If the value is nil or `word-wrap', long lines are displayed using
> continuation lines. If nil, the wrapping occurs at the right window
> edge. If `word-wrap', it occurs at the rightmost space or tab
> character, if possible.
How about not using word-wrap, but rather integers? A positive integer
indicates the column before the wrap should occur, with negative
integers counting from the right margin? That makes it possible to
specify a fixed wrap position if really wanted. Also the
truncate-partial-window-width override should have the same meaning and
take precedence if non-nil.
I am not sure this flexibility is needed, though.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-06-22 20:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 19:54 Display-based word wrapping Chong Yidong
2008-06-22 20:04 ` Lennart Borgman (gmail)
2008-06-22 20:33 ` Chong Yidong
2008-06-22 20:54 ` Lennart Borgman (gmail)
2008-06-22 22:08 ` David Reitter
2008-06-22 22:24 ` Chong Yidong
2008-06-22 23:45 ` David Reitter
2008-06-23 0:32 ` Miles Bader
2008-06-22 20:12 ` David Kastrup [this message]
2008-06-22 22:02 ` Stefan Monnier
2008-06-22 23:40 ` Chong Yidong
2008-06-23 1:23 ` Stefan Monnier
2008-06-23 2:04 ` Chong Yidong
2008-06-23 16:42 ` Chong Yidong
2008-06-23 18:29 ` Stefan Monnier
2008-06-22 23:38 ` Chong Yidong
2008-06-23 0:25 ` Miles Bader
2008-06-23 0:22 ` Miles Bader
2008-06-23 1:27 ` Stefan Monnier
2008-06-23 1:51 ` Miles Bader
2008-06-23 2:03 ` Stefan Monnier
2008-06-23 2:40 ` Miles Bader
2008-06-23 18:24 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-06-24 18:06 Chong Yidong
2008-06-24 18:52 ` Stefan Monnier
2008-06-24 19:54 ` Chong Yidong
2008-06-24 20:23 ` Stefan Monnier
2008-06-24 21:52 ` Chong Yidong
2008-06-25 1:41 ` Stefan Monnier
2008-06-25 1:46 ` Miles Bader
2008-06-25 3:45 ` Stefan Monnier
2008-06-25 2:04 ` Chong Yidong
2008-06-25 3:48 ` Stefan Monnier
2008-06-25 18:14 ` Chong Yidong
2008-06-25 18:58 ` Stefan Monnier
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=858wwx5iv9.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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.