-
Notifications
You must be signed in to change notification settings - Fork 1
/
CHANGES
58 lines (44 loc) · 1.83 KB
/
CHANGES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
Mar 31, 2013 (0.1.6)
- Command completion includes macro names. Some completion output is now
sorted
- Small document fixes. Some trailing blanks removed from source-code
- More Windows and MinGW tolerance
Aug 08, 2012 (0.1.5)
- Incompatible change: Remove aliases 'd' and 'u' for down and up
respectively. gdb uses 'u' and 'd' to mean something different.
Oct 27, 2011 (0.1.4)
- POSIX shell -x (long form: --trace) fixed
- Go with rdoc 2.4.2 now
- Improve documentation for "macro"
- show alias => show aliases
- correct info variables
- Add ruby-debug-base dependency
- Bugs fixed, code reorganized.
June 12, 2011 (0.1.3) Fleetwood release
First attempt at backport from trepanning.
New features
- Syntax highlighting (if coderay, term-ansicolor and newer linecache)
- tab completion (more complete on MRI 1.8.7 rb-readline gem used)
- parsetree (if ParseTree installed)
New commands from trepanning:
- gdb-like "confirm" to turn on/off prompting of dangerous commands
- "eval" and "eval?" without args to run parts of the current source line
- macros
- aliases
- new help system
- unique command abbrev (or not if "set abbrev off")
- new "!" suffix on "quit" and "kill" command, e.g. "q!", to avoid prompting.
Incompatibilities:
- autoeval is on by default
- ";;" separates debugger commands so you can use ";" in eval
- some possibliy lesser-used commands have been dropped. If people notice,
they can be reinstated.
- p is now pr to avoid eval confusion with Ruby's "p" method
- dropped support for annotations and ruby-debug emacs. Use newer emacs-dbgr
- some commands have been moved to closer match gdb:
* threads -> info threads
* reload -> set reload
* trace -> set trace
This sort of works for an unpatched MRI 1.9. Better is a patched MRI
1.9.2 to use rb-threadframe and rb-trepanning.
See ruby-debug's CHANGES for older changes