From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: require-hard-newlines to use newline
Date: Fri, 04 Mar 2005 18:45:49 -0500 [thread overview]
Message-ID: <E1D7MUP-0002Oi-FA@fencepost.gnu.org> (raw)
In-Reply-To: <1404.220.255.169.59.1109889146.squirrel@www.stupidchicken.com> (cyd@stupidchicken.com)
First, recall that soft newlines
are equivalent to spaces, so fill-paragraph can delete a soft newline or
replace it with one or more spaces.
Now if you have a paragraph
foo foo\n
bar bar\n
\N
foo bar\n
...
where \n denotes a soft newline and \N a hard newline, then it is refilled to
foo foo\n
bar bar\N
That seems to be replacing \n with zero spaces, not with one space.
Is it correct?
Anyway, if it is a fact that both of these newlines are normally
hard, then it seems to me that there is no way of telling
whether the user wants a hard newline or a soft one
when require-final-newline adds a newline.
A user might save the file with an unfinished paragraph,
then go back to writing more of it.
Perhaps use-hard-newlines should inhibit the effect of
require-final-newline.
next prev parent reply other threads:[~2005-03-04 23:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 2:26 (no subject) Chong Yidong
2005-03-02 3:02 ` Luc Teirlinck
2005-03-02 3:26 ` require-hard-newlines to use newline Chong Yidong
2005-03-02 3:55 ` Luc Teirlinck
2005-03-03 2:29 ` Richard Stallman
2005-03-03 2:49 ` Chong Yidong
2005-03-03 20:57 ` Richard Stallman
2005-03-03 22:32 ` Chong Yidong
2005-03-04 0:33 ` Luc Teirlinck
2005-03-04 0:56 ` Chong Yidong
2005-03-04 1:40 ` Miles Bader
2005-03-04 6:02 ` Chong Yidong
2005-03-04 9:55 ` David Kastrup
2005-03-04 23:46 ` Richard Stallman
2005-03-08 0:05 ` Luc Teirlinck
2005-03-08 2:10 ` Chong Yidong
2005-03-08 3:09 ` Luc Teirlinck
2005-03-08 4:28 ` Luc Teirlinck
2005-03-08 15:45 ` Luc Teirlinck
2005-03-08 16:42 ` Chong Yidong
2005-03-08 18:04 ` Stefan Monnier
2005-03-08 18:12 ` Luc Teirlinck
2005-03-08 19:02 ` Stefan Monnier
2005-03-08 18:26 ` Luc Teirlinck
2005-03-08 16:03 ` Richard Stallman
2005-03-08 16:39 ` Chong Yidong
2005-03-09 9:45 ` Chong Yidong
2005-03-11 1:46 ` Richard Stallman
2005-03-11 9:10 ` Chong Yidong
2005-03-11 10:25 ` Kim F. Storm
2005-03-11 13:03 ` Chong Yidong
2005-03-11 14:32 ` Stefan Monnier
2005-03-11 14:57 ` Kim F. Storm
2005-03-11 15:08 ` Chong Yidong
2005-03-11 15:28 ` Stefan Monnier
2005-03-11 15:13 ` Chong Yidong
2005-03-11 15:30 ` Stefan Monnier
2005-03-11 16:11 ` Chong Yidong
2005-03-11 17:32 ` Stefan Monnier
2005-03-12 2:40 ` Chong Yidong
2005-03-11 22:29 ` Kim F. Storm
2005-03-12 2:23 ` Chong Yidong
2005-03-12 22:16 ` Richard Stallman
2005-03-12 23:53 ` Stefan Monnier
2005-03-14 3:00 ` Richard Stallman
2005-03-13 6:14 ` Chong Yidong
2005-03-14 3:00 ` Richard Stallman
2005-03-14 3:42 ` Chong Yidong
2005-03-15 18:39 ` Richard Stallman
2005-03-12 22:16 ` Richard Stallman
2005-03-04 23:45 ` Richard Stallman [this message]
2005-03-05 2:03 ` Chong Yidong
2005-03-06 0:41 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 2:18 Chong Yidong
2005-03-07 5:02 ` Richard Stallman
2005-03-07 10:45 ` Oliver Scholz
2005-03-08 0:50 ` Luc Teirlinck
2005-03-08 1:43 ` Luc Teirlinck
2005-03-08 2:52 ` Richard Stallman
2005-03-08 1:31 ` Luc Teirlinck
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=E1D7MUP-0002Oi-FA@fencepost.gnu.org \
--to=rms@gnu.org \
--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).