GNU bug report logs -
#31363
26.1; Fix gud-statement for pdb
Previous Next
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
[Message part 1 (text/plain, inline)]
Your bug report
#31363: 26.1; Fix gud-statement for pdb
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 31363 <at> debbugs.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>
> 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.
[Message part 3 (message/rfc822, inline)]
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) *")
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.