unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: David Reitter <david.reitter@gmail.com>
Cc: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Display-based word wrapping
Date: Sun, 22 Jun 2008 18:24:42 -0400	[thread overview]
Message-ID: <873an52jmd.fsf@stupidchicken.com> (raw)
In-Reply-To: <E7285F8F-1E25-4D35-8CA9-621364F7D82B@gmail.com> (David Reitter's message of "Sun, 22 Jun 2008 23:08:07 +0100")

David Reitter <david.reitter@gmail.com> writes:

> On 22 Jun 2008, at 21:33, Chong Yidong wrote:
>>>
>>> Yes, I would find this quite impractical to not have a
>>> wrap-column'. I do not want to resize windows just to edit text in a
>>> comfortable way.
>>
>> Introducing a wrap-column variable is almost exactly the same as
>> changing the window width, or equivalently the right fringe width.  I
>> don't see the advantage in further complicating this part of the code
>> to introduce a new way to do the same thing.
>
> How does the specification of a wrap column work with variable-width
> fonts?

In the current patch that I'm working with, the wrap occurs at the
window edge, calculated using pixel positions.  So it DTRT with respect
to variable-width fonts.

If a wrap-column is introduced, it will probably specify a number of
pixels equal to N standard-width columns.




  reply	other threads:[~2008-06-22 22:24 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 [this message]
2008-06-22 23:45         ` David Reitter
2008-06-23  0:32     ` Miles Bader
2008-06-22 20:12 ` David Kastrup
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

  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=873an52jmd.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    /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).