From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: require-hard-newlines to use newline
Date: Mon, 07 Mar 2005 00:02:34 -0500 [thread overview]
Message-ID: <E1D8AO2-00081u-44@fencepost.gnu.org> (raw)
In-Reply-To: <1605.220.255.169.59.1110075529.squirrel@www.stupidchicken.com> (cyd@stupidchicken.com)
Because, everywhere else in the buffer, the newline at the end of a
paragraph is hard.
That doesn't seem like a convincing reason.
Now suppose the user goes to another buffer to do his editing, and comes
back to this buffer a long time later. He does not remember the exact
sequence of edits he performed on that buffer -- in particular, whether he
typed RET or not. From moving point around, he observes that the buffer
contains "some text" followed by a final newline.
If he did not finish the paragraph, he will probably assume the
newline is soft. If he did finish the paragraph, he will probably
assume the newline is hard. Either way, he might be wrong.
So I think that use-hard-newlines should inhibit the effect of
require-final-newline. It is the only way to get reliable results.
next prev parent reply other threads:[~2005-03-07 5:02 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 2:18 require-hard-newlines to use newline Chong Yidong
2005-03-07 5:02 ` Richard Stallman [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2005-03-05 2:03 ` Chong Yidong
2005-03-06 0:41 ` Richard Stallman
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=E1D8AO2-00081u-44@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).