+2002-12-10 R. Bernstein <rocky@panix.com>
+
+ * gud.el (bashdb): Prompt now included parenthesis for subshell
+ levels. Fix erroneous print expression command, and fix typos.
+ (perldb): Undo previous change in prompt regexp.
+
2002-12-10 Steven Tamm <steventamm@mac.com>
* generic-x.el (javascript-generic-mode): Added C style block
; (gud-def gud-down "down %p" ">" "Down N stack frames (numeric arg).")
(gud-def gud-print "%e" "\C-p" "Evaluate perl expression at point.")
- (setq comint-prompt-regexp "^ DB<+(*[0-9])*+>+ ")
+ (setq comint-prompt-regexp "^ DB<+[0-9]+>+ ")
(setq paragraph-start comint-prompt-regexp)
(run-hooks 'perldb-mode-hook))
\f
(gud-def gud-finish "finish" "\C-f" "Finish executing current function.")
(gud-def gud-up "up %p" "<" "Up N stack frames (numeric arg).")
(gud-def gud-down "down %p" ">" "Down N stack frames (numeric arg).")
- (gud-def gud-print "pe %e" "\C-p" "Evaluate bash expression at point.")
+ (gud-def gud-print "x %e" "\C-p" "Evaluate BASH expression at point.")
;; Is this right?
- (gud-def gud-statement "eval %e" "\C-e" "Execute Python statement at point.")
+ (gud-def gud-statement "eval %e" "\C-e" "Execute BASH statement at point.")
- (setq comint-prompt-regexp "^bashdb<+[0-9]*>+ ")
+ (setq comint-prompt-regexp "^bashdb<+(*[0-9]+)*>+ ")
(setq paragraph-start comint-prompt-regexp)
(run-hooks 'bashdb-mode-hook)
)