From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Leo Liu <sdl.web@gmail.com>
Cc: 14457@debbugs.gnu.org
Subject: bug#14457: 24.3; buggy forward-sexp in octave mode?
Date: Sat, 25 May 2013 02:59:08 -0400 [thread overview]
Message-ID: <jwvhahreeqs.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m14ndrsnfr.fsf@gmail.com> (Leo Liu's message of "Sat, 25 May 2013 12:17:28 +0800")
> Since 'case', 'otherwise' are closers to 'switch' as in
> smie-closer-alist, I was expecting (forward-sexp -1) to jump back to
> 'switch', much like from 'elseif' to 'if'. Does this make sense?
Both behaviors make sense. Note that elseif/else behaves just like
case/otherwise: if will stop at the previous matching elseif.
For indentation purpose it's better if it doesn't jump
too far, which is why octave-mode currently behaves this way.
The reason why it's better is:
- faster indentation since we parse less of the buffer.
- more local decision means that the behavior is easier to understand
for the user.
- also means that it better takes into account choices of the user: if
the user decides to place his "case" at some other indentation, only
the first "case" after "switch" will disagree with the user, all the
other ones will simply align under the first.
Ideally, this behavior would also allow to use C-M-t to transpose two
cases, just like you can do with the usual infix operators/separators,
but currently this doesn't work (and it can't be done with "otherwise").
Stefan
next prev parent reply other threads:[~2013-05-25 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 3:07 bug#14457: 24.3; buggy forward-sexp in octave mode? Leo Liu
2013-05-24 4:07 ` Stefan Monnier
2013-05-25 4:17 ` Leo Liu
2013-05-25 6:59 ` Stefan Monnier [this message]
2013-06-08 3:36 ` Leo Liu
2013-05-24 5:30 ` Andreas Röhler
2013-05-25 4:20 ` Leo Liu
2013-05-25 17:45 ` Andreas Röhler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvhahreeqs.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14457@debbugs.gnu.org \
--cc=sdl.web@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.