From: Richard Stallman <rms@gnu.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: emacs-devel@gnu.org
Subject: Re: Don't move to eol in end-of-defun?
Date: Thu, 04 Aug 2022 00:04:16 -0400 [thread overview]
Message-ID: <E1oJS5o-0006Dj-HF@fencepost.gnu.org> (raw)
In-Reply-To: <m2fsidzenv.fsf@fastmail.fm> (message from Filipp Gunbin on Wed, 03 Aug 2022 15:37:24 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Yes, that will be the behavior. This post and example were about moving
> over the braces vs. moving into them, and <4> will really be on blank
> line between defuns.
We may be partly miscommunicating. With other languages, such as
Lisp, C-M-e moves to the blank line after the defun from _anywhere_
inside the defun. (Except in weird cases, such as this,
(defun foo (a b)
x y z))
where the extra closeparen after the defun means the only valid place
to stop is before the extra closeparen.)
You're planning to break that rule, right?
I think that this rule behavior will be useful in other languages too;
maybe breaking it is not a good idea.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-08-04 4:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 12:40 Don't move to eol in end-of-defun? Filipp Gunbin
2022-07-30 23:40 ` Daniel Martín
2022-07-31 22:31 ` Filipp Gunbin
2022-08-01 17:50 ` Alan Mackenzie
2022-08-01 20:49 ` Filipp Gunbin
2022-08-01 22:01 ` Filipp Gunbin
2022-08-03 3:46 ` Richard Stallman
2022-08-03 12:37 ` Filipp Gunbin
2022-08-04 4:04 ` Richard Stallman [this message]
2022-08-04 14:58 ` Filipp Gunbin
2022-08-06 3:41 ` Richard Stallman
2022-08-06 9:33 ` Alan Mackenzie
2022-08-07 4:24 ` Richard Stallman
2022-08-08 14:29 ` Filipp Gunbin
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=E1oJS5o-0006Dj-HF@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
/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).