GNU bug report logs -
#14457
24.3; buggy forward-sexp in octave mode?
Previous Next
Reported by: Leo Liu <sdl.web <at> gmail.com>
Date: Fri, 24 May 2013 03:09:02 UTC
Severity: normal
Found in version 24.3
Done: Leo Liu <sdl.web <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
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
This bug report was last modified 12 years and 36 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.