From: "Richard M. Stallman" <rms@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Line wrapping during redisplay
Date: Fri, 22 Jul 2005 18:51:57 -0400 [thread overview]
Message-ID: <E1Dw6N3-000346-Tt@fencepost.gnu.org> (raw)
In-Reply-To: <m3irz3dx0s.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
It is no different from how continued lines are handled in the
current code. The only real difference is that continued lines
break at spaces rather than at some arbitrary column which happens
to be the width of the window.
That is true. And this mode of continuation could be better in some
cases than the current one.
What I am saying is that this new mode of continuation doesn't do the
job that longlines is trying to do, and doesn't make the use of
one-line-per-paragaph a desirable mode of operation.
I don't claim that the wrap-column functionality would replace any
of the existing packages -- but it may be useful for some things...
It could be so.
> Here's a peculiar idea. Make it possible for an overlay to make a
> space "appear" as a newline or vice versa. The result is a change in
> the apparent contents of the buffer, for display purposes and for some
> commands. But killing and yanking would not copy these overlays
> (since they don't copy any overlays).
Would it have the same problems with line movement being out of sync
with what's displayed in the window...
The ideas is that most commands that examine the buffer contents would
see the result of the overlays. So cursor motion commands would treat
the apparent newline as a real newline, and treat the apparent space
as a real space. Only things that copy text (including kill and yank,
and file I/O) would ignore them.
prev parent reply other threads:[~2005-07-22 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 23:41 longlines.el problems David Kastrup
2005-07-12 17:05 ` Chong Yidong
2005-07-21 13:59 ` Line wrapping during redisplay (was: longlines.el problems...) Kim F. Storm
2005-07-21 16:59 ` Line wrapping during redisplay David Kastrup
2005-07-22 11:43 ` Chong Yidong
2005-07-22 22:52 ` Richard M. Stallman
2005-07-22 4:55 ` Line wrapping during redisplay (was: longlines.el problems...) Richard M. Stallman
2005-07-22 9:12 ` Line wrapping during redisplay Kim F. Storm
2005-07-22 22:51 ` Richard M. Stallman [this message]
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=E1Dw6N3-000346-Tt@fencepost.gnu.org \
--to=rms@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 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).