Menu
▾
▴
bashdb-zshdb
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rocky B. <ro...@cp...> - 2015-01-01 02:32:13
|
Just realized that I hadn't posted news of the release from mid December. The major changes to this release are adding command completion and interactive history. My thanks to Bart Schaefer, Mikael Magnusson, and Peter Stephenson for showing me how to get this done. |
|
From: Rocky B. <ro...@gn...> - 2011-03-16 00:09:34
|
A new release is out. The first three items from the NEWS file I think are cool. Some wiki entries for the he first three features. See https://github.com/rocky/zshdb/wiki/Terminal-Colors https://github.com/rocky/zshdb/wiki/Evaluating-the-current-source-line-before-it-runs https://github.com/rocky/zshdb/wiki/Nested-Shell - syntax coloring if the Python pygments package installed (and --highlight option used) - easy way to evaluate the current source line or expression inside the source line (debugger commands "eval" and "eval?") - ability to go into a nested shell but keeping existing variables and functions set. (debugger command "shell") With this, one needs... - ability to save variables to an outer shell ("set_vars" function inside the interactive shell) - ability to save values from inside a subshell to the outer shell (debugger command "export") - add debugger "display" and "undisplay" commands - add --init-file (akin to same option in bash) to have bash code sourced |
|
From: Rocky B. <ro...@gn...> - 2011-03-05 15:30:10
|
I am currently planning a release around March 15, the ides of March.
Changes include:
- Updates for bash 4.2
- syntax coloring if the Python pygments package installed (and
--highlight option used)
- easy way to evaluate the current source line or expression inside the
source line (debugger commands "eval" and "eval?")
- ability to go into a nested shell but keeping existing variables and
functions set. (debugger command "shell") With this, one needs...
- ability to save variables to an outer shell ("set_vars" function inside
the interactive shell)
- ability to save values from inside a subshell to the outer shell
(debugger command "export")
Haven't done this yet, but nested debugging of expressions. Previously I
allowed only file names and
I wasn't setting variables properly there.
|
