GNU bug report logs - #31363
26.1; Fix gud-statement for pdb

Previous Next

Package: emacs;

Reported by: Xu Chunyang <mail <at> xuchunyang.me>

Date: Fri, 4 May 2018 11:48:02 UTC

Severity: normal

Found in version 26.1

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#31363: closed (26.1; Fix gud-statement for pdb)
Date: Sun, 06 May 2018 19:49:03 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sun, 06 May 2018 22:47:59 +0300
with message-id <83po28r2fk.fsf <at> gnu.org>
and subject line Re: bug#31363: 26.1; Fix gud-statement for pdb
has caused the debbugs.gnu.org bug report #31363,
regarding 26.1; Fix gud-statement for pdb
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
31363: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31363
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Xu Chunyang <mail <at> xuchunyang.me>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.1; Fix gud-statement for pdb
Date: Fri, 04 May 2018 19:47:15 +0800
I'm using Python 3.6.5. When I have selected a simple expression (such
as 42) then run M-x gud-statement, it fails by saying


*** IndentationError: unexpected indent


The following changes fix the issue from here.


diff --git a/lisp/progmodes/gud.el b/lisp/progmodes/gud.el
index 15b428bb68..9cf818e99e 100644
--- a/lisp/progmodes/gud.el
+++ b/lisp/progmodes/gud.el
@@ -1694,8 +1694,7 @@ pdb
   (gud-def gud-up     "up"           "<" "Up one stack frame.")
   (gud-def gud-down   "down"         ">" "Down one stack frame.")
   (gud-def gud-print  "p %e"         "\C-p" "Evaluate Python expression at point.")
-  ;; Is this right?
-  (gud-def gud-statement "! %e"      "\C-e" "Execute Python statement at point.")
+  (gud-def gud-statement "!%e"      "\C-e" "Execute Python statement at point.")
 
   ;; (setq comint-prompt-regexp "^(.*pdb[+]?) *")
   (setq comint-prompt-regexp "^(Pdb) *")


[Message part 3 (message/rfc822, inline)]
From: Eli Zaretskii <eliz <at> gnu.org>
To: Xu Chunyang <mail <at> xuchunyang.me>
Cc: 31363-done <at> debbugs.gnu.org
Subject: Re: bug#31363: 26.1; Fix gud-statement for pdb
Date: Sun, 06 May 2018 22:47:59 +0300
> From: Xu Chunyang <mail <at> xuchunyang.me>
> Cc: 31363 <at> debbugs.gnu.org
> Date: Sun, 06 May 2018 19:57:21 +0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Xu Chunyang <mail <at> xuchunyang.me>
> >> Date: Fri, 04 May 2018 19:47:15 +0800
> >> 
> >> I'm using Python 3.6.5. When I have selected a simple expression (such
> >> as 42) then run M-x gud-statement, it fails by saying
> >> 
> >> *** IndentationError: unexpected indent
> >> 
> >> The following changes fix the issue from here.
> >
> > Thanks.  Is the problem and the solution the same for Python 2.x?
> 
> Yes, I've checked both of them against Python 2.7.14.

Thanks, pushed to the release branch.


This bug report was last modified 7 years and 20 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.