From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Wordprocessor behaviour
Date: Tue, 24 Jun 2003 09:05:10 +0200 [thread overview]
Message-ID: <84he6ggdll.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: vfeqb2m41kkq0a@corp.supernews.com
"Roodwriter@core.com" <Roodwriter@core.com> writes:
> That being said it appears using refill mode and paragraph-indent-text-mode
> together may be a winner for writing text documents--except for the
> drawback that you'll still get short lines, which not everyone will
> consider a drawback. (You can macro that problem away, though, or use
> longlines.)
Maybe longlines.el could be used to ameliorate that. If it works,
that is.
--
This line is not blank.
prev parent reply other threads:[~2003-06-24 7:05 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
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 [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=84he6ggdll.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).