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

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

[debbugs-tracker] bug#19987: closed (Broken sexp movement in Python mode


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#19987: closed (Broken sexp movement in Python mode)
Date: Thu, 09 Apr 2015 04:56:01 +0000

Your message dated Thu, 09 Apr 2015 01:55:54 -0300
with message-id <address@hidden>
and subject line Broken sexp movement in Python mode
has caused the debbugs.gnu.org bug report #19987,
regarding Broken sexp movement in Python mode
to be marked as done.

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


-- 
19987: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19987
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Broken sexp movement in Python mode Date: Tue, 3 Mar 2015 11:33:24 +0100
$ emacs - q

Visit a new Python buffer and type:

a = b (0)

C-M-f at the beginning of the buffer moves the point immediately to the end of line. Expected is point after 'a', as in other modes. As another visible and annoying effect, C-M-k kills more than expected, thus breaking editing habits.

Note that C-M-b from the end of line moves point to '(', then to 'b', then to 'a', just as expected.

Paul

--- End Message ---
--- Begin Message --- Subject: Broken sexp movement in Python mode Date: Thu, 09 Apr 2015 01:55:54 -0300 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Adding the following to your .emacs will disable python.el's default
forward-sexp behavior (which works in a ~lispy way):

(add-hook 'python-mode-hook
          (lambda () (setq forward-sexp-function nil)))

The parentheses behavior is a special case I'll document better as a
follow up of #19954.


Cheers,
Fabián.


--- End Message ---

reply via email to

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