From: "Daniel Martín" <mardani29@yahoo.es>
To: emacs-devel@gnu.org
Subject: Re: Don't move to eol in end-of-defun?
Date: Sun, 31 Jul 2022 01:40:16 +0200 [thread overview]
Message-ID: <m1mtcq41b3.fsf@yahoo.es> (raw)
In-Reply-To: <m2czdqybhi.fsf@fastmail.fm> (Filipp Gunbin's message of "Wed, 27 Jul 2022 15:40:57 +0300")
Filipp Gunbin <fgunbin@fastmail.fm> writes:
> In Java, it's a common style to have hanging parentheses:
>
> class C <1>{<2>
> void foo() {
> }<3>
> }<4>
>
> If we're at position <1> and press C-M-e, then it's logical to move to
> <4>, and that's what I implement in javaimp package, by defining my own
> beginning-of-defun-function / end-of-defun-function.
If I yank your sample program in a buffer in Java mode, with point at
<1>, C-M-e goes to <4>, as expected. So I don´t know why you need to
implement your own end-of-defun-function in your package.
>
> OTOH, end-of-defun is documented to move to "next end of defun", and one
> could say that moving from <1> to <3> is just that.
The docstring is perhaps a bit confusing, but the Emacs manual and
glossary defines what end-of-defun does in each major mode more
precisely: It moves point to the end of the current defun. When the
point is in between two defuns, the current defun is defined as the next
defun that follows the point. So the expected navigation is <1> -> <4>,
<2> -> <3>, which is how the included java-mode works.
I'm not sure about the problem your solution is trying to fix. Perhaps
I'm missing something.
next prev parent reply other threads:[~2022-07-30 23:40 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 [this message]
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
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=m1mtcq41b3.fsf@yahoo.es \
--to=mardani29@yahoo.es \
--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).