unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Wordprocessor behaviour
Date: Mon, 23 Jun 2003 15:44:49 +0200	[thread overview]
Message-ID: <84n0g8lxgu.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: bd6kvi$duh$1@news.cybercity.dk

Daniel Andersen <dani_ande@yahoo.dk> writes:

> I'm quite new to emacs and I have a question which has bothered me a
> long time. I'm writing a book and started using emacs insteed of Word,
> which I got pretty much tired of, but there is one thing which annoyes
> me; when I have written a long sentense and it is wrapped to many
> lines on the screen, then when I want to go on "screen-line" up in the
> same sentence, it jumps to the previous paragraph insteed, which means
> that I have to move the cursor along the line insteed to get upwards.

Emacs uses the traditional Unix text file layout.  This means that
there is a "hard newline" after each line, and paragraphs are
separated by empty lines.  You can use M-q to refill a paragraph if
there are too-long or too-short lines in it.  M-x auto-fill-mode RET
allows you to produce short lines when typing normally.

It would be very difficult to make Emacs work differently internally,
but there is a tool, longlines.el, which inserts newlines when
reading from disk and removes them again when writing to disk.  That
way, the files have the one-line-one-paragraph style whereas the
Emacs buffers use the many-lines-per-paragraph style that Emacs
expects.

Warning: I wrote longlines.el initially.
-- 
This line is not blank.

  parent reply	other threads:[~2003-06-23 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 10:32 Wordprocessor behaviour Daniel Andersen
2003-06-23 13:01 ` Andrew Rutherford
2003-06-23 13:44 ` Kai Großjohann [this message]
2003-06-23 16:22 ` Kevin Rodgers
2003-06-25 19:34   ` Daniel Andersen
2003-06-23 19:30 ` Roodwriter
2003-06-23 20:09   ` Kai Großjohann
2003-06-23 20:57     ` Roodwriter
2003-06-24  7:05       ` Kai Großjohann

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=84n0g8lxgu.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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).