From: roodwriter@core.com
Subject: Re: Word wrap / "soft" line breaks
Date: 07 Apr 2006 04:52:01 -0400 [thread overview]
Message-ID: <877j61vkcu.fsf@linux.site> (raw)
In-Reply-To: 44362009.3040406@cgv.tugraz.at
Sven Havemann <s.havemann@cgv.tugraz.at> writes:
> Hi!
>
> I would like to configure the behaviour of Emacs concerning the
> display of long lines of text.
>
> What it does:
> =============
> Long lines (say 800 characters with one newline at the end) fill
> several lines in the window, but emacs treats them as one long
> continuous line: Words are broken right in the middle and continued on
> the next line, which is indicated with a small bent arrow. Navigation
> is possible only to the left and right, the up and down keys may skip
> a dozen lines in the window. The alternative is using auto-fill, but
> that inserts many newlines, and I have to re-format the paragraph
> whenever I change something in it.
>
> What I would like it to do:
> ===========================
> A true word wrap mode where long lines fill the width of the window,
> but complete words are put on the next line if they do not fit. Up-
> and down-keys work as expected, going down one line on the screen, and
> not one line of the file.
>
>
> Any help is appreciated,
> thanks in advance,
> cheers,
> Sven
That's long been a problem with Emacs, but not anymore. Get the add-on
longlines.el. That'll give you exactly what you're looking for.
I'm a full-time writer and I use it every day. It's much superior to
all the other work-arounds.
--Rod
______________________
Author of "Linux for Non-Geeks--Clear-eyed Answers for Practical
Consumers" and "Boring Stories from Uncle Rod." To reply by e-mail
take the second "o" out of the e-mail address.
next prev parent reply other threads:[~2006-04-07 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 8:17 Word wrap / "soft" line breaks Sven Havemann
2006-04-07 8:52 ` roodwriter [this message]
2006-04-07 9:24 ` Mathias Dahl
2006-04-07 12:49 ` Sven Havemann
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=877j61vkcu.fsf@linux.site \
--to=roodwriter@core.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.
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).