emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#14457: closed (24.3; buggy forward-sexp in octave


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#14457: closed (24.3; buggy forward-sexp in octave mode?)
Date: Sat, 08 Jun 2013 03:38:02 +0000

Your message dated Sat, 08 Jun 2013 11:36:47 +0800
with message-id <address@hidden>
and subject line Re: bug#14457: 24.3; buggy forward-sexp in octave mode?
has caused the debbugs.gnu.org bug report #14457,
regarding 24.3; buggy forward-sexp in octave mode?
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
14457: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14457
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3; buggy forward-sexp in octave mode? Date: Fri, 24 May 2013 11:07:02 +0800
1. Open the attached file
2. Move point to end of the word 'otherwise'
3. M-: (forward-sexp -1)

Is this correct behaviour? I noticed this via
smie-highlight-matching-block-mode.

Leo

Attachment: unimplemented.m
Description: unimplemented.m


--- End Message ---
--- Begin Message --- Subject: Re: bug#14457: 24.3; buggy forward-sexp in octave mode? Date: Sat, 08 Jun 2013 11:36:47 +0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (OS X 10.8.3)
On 2013-05-25 14:59 +0800, Stefan Monnier wrote:
> 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").

I have noticed with your last change to smie, 'case' 'elseif' are now
nicely highlighted. So I agree with your points and consider this done ;)

Leo


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]