From: Leo Liu <sdl.web@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14457@debbugs.gnu.org
Subject: bug#14457: 24.3; buggy forward-sexp in octave mode?
Date: Sat, 25 May 2013 12:17:28 +0800 [thread overview]
Message-ID: <m14ndrsnfr.fsf@gmail.com> (raw)
In-Reply-To: <jwvmwrldnyc.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 24 May 2013 00:07:38 -0400")
On 2013-05-24 12:07 +0800, Stefan Monnier wrote:
> Please in your bug reports, do mention the behavior that you see rather
> than assume that I will see the same one. Also, try to explain the
> behavior you would have liked to see instead.
Sorry, Stefan, that was an oversight.
>
> What I see is that it jumps to "right after the previous matching
>case". Is that what you see?
It jumps to the previous 'case' with point on the opening '{'.
>
>> Is this correct behaviour?
>
> It's the expected behavior, at least (IOW if it changes, you'll have to
> adjust the indentation rules accordingly).
>
> Since "after otherwise" is not a position that corresponds to the end of
> a "sexp", the meaning of (forward-sexp -1) is unclear. SMIE defines
> such things in a way I found useful, but admittedly, it might take some
> time to get used to it.
>
> What behavior did you expect?
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?
Leo
next prev parent reply other threads:[~2013-05-25 4:17 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 [this message]
2013-05-25 6:59 ` Stefan Monnier
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=m14ndrsnfr.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=14457@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.