CHANGELOG.md in byebug-3.2.0 vs CHANGELOG.md in byebug-3.3.0

@@ -1,278 +1,304 @@
+# 3.3.0
+
+- Bugfixes
+ * Fix "verbose" setting ("set verbose" works now).
+ * Fix unsetting post_mortem mode ("set post_mortem false" works now).
+ * Fix some cases where the debugger would stop in byebug internal frames.
+ * Fix some crashes when displaying backtraces (with "nofullpath" setting and
+when calculated stack size was smaller than the real one).
+
+- Removals
+ * "info locals" has been removed, use "var local" instead.
+ * "info instance_variables" has been removed, use "var instance" instead.
+ * "info global_variables" has been removed, use "var global" instead.
+ * "info variables" has been removed, use "var all" instead.
+ * "irb" command stepping capabilities were removed, see
+[8e226d0](https://github.com/deivid-rodriguez/byebug/commit/8e226d0).
+ * --script and --restart-script options from byebug's executable were removed.
+Also, '-t' option now turns tracing on whereas '-x' options tells byebug to run
+the initialization file (.byebugrc) on startup. This is the default behaviour
+though.
+
+- Improvements
+ * byebug's script has been libified and tests have been added.
+
+
 # 3.2.0
 
 - Bugfixes
  * Fix bug in remote debugging (#71), thanks @shuky19.
  * Fix source command (#68), thanks @Olgagr.
  * Fix bug #71 preventing the test suite from running against ruby-head.
  * Remove warning reported in #77.
 
 - Removals
- * `post_mortem` activation through `Byebug.post_mortem` is no longer allowed.
-Use `set post_mortem` instead.
- * `info stack` command has been removed. Use `where`|`backtrace` instead.
- * `method iv` command has been removed. Use `var instance` instead.
+ * "post_mortem" activation through "Byebug.post_mortem" is no longer allowed.
+Use "set post_mortem" instead.
+ * "info stack" command has been removed. Use "where"|"backtrace" instead.
+ * "method iv" command has been removed. Use "var instance" instead.
 
 
 # 3.1.2
 
-* Really fix starting `post_mortem` mode in bin/byebug
-* Fix starting line tracing in bin/byebug
+* Really fix starting "post_mortem" mode in bin/byebug.
+* Fix starting line tracing in bin/byebug.
 
 
 # 3.1.1
 
-* Fix starting `post_mortem` mode in bin/byebug
+* Fix starting "post_mortem" mode in bin/byebug.
 
 
 # 3.1.0
 
-* `show commands` moved to a separate `history` command.
+* "show commands" moved to a separate "history" command.
 * Byebug.start can't recieve options any more. Any program settings you
 want applied from the start should be set in .byebugrc.
-* `trace` command has been removed. Line tracing functionality should be
-enabled through the `linetrace` setting whereas the global variable
-tracing functionality is now provided through the `tracevar` command.
-* `version` setting has been removed. It was not really a setting because it
-couldn't be set. Use `byebug --version` to check byebug's version.
-* `arg` setting removed. Program restart arguments should be set through
-`restart` command from now on.
-* `linetrace_plus` setting has been renamed to `tracing_plus`.
+* "trace" command has been removed. Line tracing functionality should be
+enabled through the "linetrace" setting whereas the global variable
+tracing functionality is now provided through the "tracevar" command.
+* "version" setting has been removed. It was not really a setting because it
+couldn't be set. Use "byebug --version" to check byebug's version.
+* "arg" setting removed. Program restart arguments should be set through
+"restart" command from now on.
+* "linetrace\_plus" setting has been renamed to "tracing\_plus".
 
 
 # 3.0.0
 
 - Bugfixes
- * Fix post_mortem mode
+ * Fix post_mortem mode.
  * Command history is also saved after regular program termination, not only
-after quitting with the `q` command.
+after quitting with the "q" command.
  * Fix failure when calling Byebug.start with Timeout::timeout (see #54), thanks
 @zmoazeni!
 
 - Changes
- * `show commands` command for listing history of previous byebug commands now
-behaves like shell's `history` command.
- * Changes in `history` commands: see
-[50e6ad8](https://github.com/deivid-rodriguez/byebug/commit/50e6ad8)
- * Changes in `finish` semantics and in the C extension API: see
-[61f9b4d](https://github.com/deivid-rodriguez/byebug/commit/61f9b4d)
- * The `init` option for Byebug.start has been removed. Information to make the
-`restart` command work is always saved now.
+ * "show commands" command for listing history of previous byebug commands now
+behaves like shell's "history" command.
+ * Changes in "history" commands: see
+[50e6ad8](https://github.com/deivid-rodriguez/byebug/commit/50e6ad8).
+ * Changes in "finish" semantics and in the C extension API: see
+[61f9b4d](https://github.com/deivid-rodriguez/byebug/commit/61f9b4d).
+ * The "init" option for Byebug.start has been removed. Information to make the
+"restart" command work is always saved now.
 
 - Features
- * Allow disabling post_mortem mode
+ * Allow disabling post_mortem mode.
 
 
 # 2.7.0
-* Bugfix release (#52, #53 and #54)
+* Bugfix release (#52, #53 and #54).
 
 
 # 2.6.0
 
-* Fix circular dependency that was affecting `pry-byebug`, thanks @andreychernih
+* Fix circular dependency that was affecting "pry-byebug" (thanks
+@andreychernih).
 
 
 # 2.5.0
 
-* Support for `sublime-debugger`
+* Support for "sublime-debugger".
 
 
 # 2.4.1
 
-* Fix installation error in Mac OSX (#40), thanks @luislavena
+* Fix installation error in Mac OSX (#40), thanks @luislavena.
 
 
 # 2.4.0
 
-* Use `require` instead of `require_relative` for loading byebug's extension
-library (thanks @nobu)
-* Adds back `debugger` as an alias to `byebug` (thanks @wallace)
+* Use "require" instead of "require_relative" for loading byebug's extension
+library (thanks @nobu).
+* Adds back "debugger" as an alias to "byebug" (thanks @wallace).
 * Adds -R option to byebug's binary to specify server's hostname:port for remote
-debugging (thanks @mrkn)
-* Fixes `thread list` showing too many threads
-* Change in tracing global variables. Use `trace variable foo` instead of `trace
-variable $foo`
-* Fix setting post mortem mode with `set post_mortem`. Now this is the only
-post mortem functionality available as specifying `Byebug.post_mortem` with a
+debugging (thanks @mrkn).
+* Fixes "thread list" showing too many threads.
+* Change in tracing global variables. Use "trace variable foo" instead of "trace
+variable $foo".
+* Fix setting post mortem mode with "set post_mortem". Now this is the only
+post mortem functionality available as specifying "Byebug.post_mortem" with a
 block has been removed in this version.
 
 
 # 2.3.1
 
-* Fixes bug preventing users from deleting breakpoints
-* Fix broken test suite
+* Fixes bug preventing users from deleting breakpoints.
+* Fix broken test suite.
 
 
 # 2.3.0
 
-* Compatibility with Phusion Passenger Enterprise (thanks @FooBarWidget)
-* More minimalist help system
+* Compatibility with Phusion Passenger Enterprise (thanks @FooBarWidget).
+* More minimalist help system.
 
 
 # 2.2.2
 
-* Fix another compilation issue in 64 bit systems
+* Fix another compilation issue in 64 bit systems.
 
 
 # 2.2.1
 
-* Fix compilation issue introduced by 2.2.0 (#26)
-* "show" and "set" option `stack_trace_on_error` is now called `stack_on_error`
+* Fix compilation issue introduced by 2.2.0 (#26).
+* "show" and "set" option "stack_trace_on_error" is now called "stack_on_error".
 
 
 # 2.2.0
 
-* Small fixes in stack_size calculations
-* Warning free byebug
-* Add `verbose` setting for TracePoint API event inspection
-* Fix setting `post_mortem` mode
-* Allow `edit <filename>` without a line number
+* Small fixes in stack_size calculations.
+* Warning free byebug.
+* Add "verbose" setting for TracePoint API event inspection.
+* Fix setting "post_mortem" mode.
+* Allow "edit <filename>" without a line number.
 
 
 # 2.1.1
 
-* Fix bug when debugging code inside '-e' flag
+* Fix bug when debugging code inside '-e' flag.
 
 
 # 2.1.0
 
-* Fix bug in remote debugging display
+* Fix bug in remote debugging display.
 * Fix bug where eval would crash when inspect raised an exception (reported by
-@iblue)
-* `enable breakpoints` now enables every breakpoint
-* `disable breakpoints` now disables every breakpoint
+@iblue).
+* "enable breakpoints" now enables every breakpoint.
+* "disable breakpoints" now disables every breakpoint.
 
 
 # 2.0.0
 
-* Various bug fixes
-* "Official" definition of a command API
-* Thread support
+* Various bug fixes.
+* "Official" definition of a command API.
+* Thread support.
 
 
 ## 1.8.2
 
-* More user friendly regexps for commands
-* Better help for some commands
-* `save` command now saves the list of "displays"
-* Fixes bug in calculating stacksize
+* More user friendly regexps for commands.
+* Better help for some commands.
+* "save" command now saves the list of "displays".
+* Fixes bug in calculating stacksize.
 
 
 ## 1.8.1
 
-* Bugfix release
+* Bugfix release.
 
 
 ## 1.8.0
 
-* Remote debugging support
+* Remote debugging support.
 
 
 ## 1.7.0
 
-* Callstack display: specifically mark c-frames
-* Callstack navigation: skip c-frames
-* Callstack navigation: autolist after navigation commands
+* Callstack display: specifically mark c-frames.
+* Callstack navigation: skip c-frames.
+* Callstack navigation: autolist after navigation commands.
 
 
 ## 1.6.1
 
-* Windows compatibiliy: compilation and terminal width issues
+* Windows compatibiliy: compilation and terminal width issues.
 
 
 ## 1.6.0
 
-* `byebug` placed at the end of a block or method call now works as expected
-* Don't autolist when ruby '-e' option is used
+* "byebug" placed at the end of a block or method call now works as expected.
+* Don't autolist when ruby '-e' option is used.
 * Fixes callstyles. From now on, use 'long' for detailed frames in callstack and
-'short' for more concise frames
+'short' for more concise frames.
 
 
 ## 1.5.0
 
-* No more Byebug.start to get correct callstack information! Dropping `byebug`
+* No more Byebug.start to get correct callstack information! Dropping "byebug"
 anywhere and inmediately printing the stack just works now. :)
 
- 
+
 ## 1.4.2
 
-* Fixes crash when using "help command subcommand"
-* Byebug now works with Rails Console debugging flag
-* Fix post-mortem mode when running byebug from the outset
-* Fix --no-quit flag when running byebug from the outset
+* Fixes crash when using "help command subcommand".
+* Byebug now works with Rails Console debugging flag.
+* Fix post-mortem mode when running byebug from the outset.
+* Fix --no-quit flag when running byebug from the outset.
 
 
 ## 1.4.1
 
-* Fixes crash when printing some filenames in backtraces
+* Fixes crash when printing some filenames in backtraces.
 * Allows byebug developers to easily use compilers different from gcc (thanks
-@GarthSnyder!)
+@GarthSnyder!).
 
 
 ## 1.4.0
 
 * Byebug now uses the Debug Inspector API: faster and nicer!
-* Fixes bug that prevents some random crashes
+* Fixes bug that prevents some random crashes.
 
 
 ## 1.3.1
 
-* Byebug now works with Rails debugging flag
+* Byebug now works with Rails debugging flag.
 * Fix bug which would make byebug crash when trying to print lines of code
-containing the character '%'
-* Fix bug which prevented basename and linetrace options from working together
+containing the character '%'.
+* Fix bug which prevented basename and linetrace options from working together.
 
 
 ## 1.3.0
 
-* Support colon-delimited include paths in command-line front-end (@ender672)
+* Support colon-delimited include paths in command-line front-end (@ender672).
 
 
 ## 1.2.0
 
 * Added 'pry' command.
-* Ctrl+C during command line editing is handled and works like pry/irb
+* Ctrl+C during command line editing is handled and works like pry/irb.
 
 
 ## 1.1.1
 
-* Better help system
-* Code cleanup
-* First version compatible with pry-byebug
+* Better help system.
+* Code cleanup.
+* First version compatible with pry-byebug.
 
 
 ## 1.1.0
 
-* Post-mortem support
+* Post-mortem support.
 
 
 ## 1.0.3
 
-* "autoreload" is set by default now
+* "autoreload" is set by default now.
 * "list" command: no negative line numbers shown, and line range behaves as
-expected at the begining/end of file
+expected at the begining/end of file.
 * In some weird cases, "backtrace" command segfaults when trying to show info on
 some frame args. Don't know the reason yet, but the exception is handled now and
 and the command doesn't segfault anymore.
-* Try some thread support (not even close to usable)
+* Try some thread support (not even close to usable).
 
 
 ## 1.0.2
 
-* "autolist" and "autoeval" are default settings now
+* "autolist" and "autoeval" are default settings now.
 * Fixes bug which messed up the call-stack when manipulating backtrace
-information and when nexting/stepping
+information and when nexting/stepping.
 
 
 ## 1.0.1
 
-* Corrected small bug preventing byebug from loading
+* Corrected small bug preventing byebug from loading.
 
 
 ## 1.0.0
 
-* Green test suite
+* Green test suite.
 
 
 ## 0.0.1
 
-* Initial release
+* Initial release.