Fix bug: breakpoints don't work with NA constants such as NA_character_
Fix bug: Shiny breakpoints don't track editor line changes correctly
Fix bug: clicking on the line number itself shouldn't set a breakpoint
Fix bug: when debugging inside a fold, fold doesn't open automatically
Fix compilation on Mavericks
Merge remote-tracking branch 'origin/master' into bugs/breakpoints
Show full deparsed function call and frame number for the traceback.
Fix bug: debugger can get invoked at the top level in some contexts
Merge remote-tracking branch 'origin/master' into feature/cocoa-mavericks
Use libstdc++ for boost (hat tip to @shayneski)
Merge pull request #73 from rstudio/bugs/breakpoints

Fix user-reported annoyances in debugging features
linux: only set working dir from terminal if it's not the user home path
plot replay for 3.0.2
get r version string from base not grDevices
disable spell-checking in commit messages
always show .travis.yml in files pane
read default sweave template from the filesystem
Fix bug: Object sizes > 2GB show as "16 TB" in environment pane

The cause of this bug was subtle--in GWT, the "long" type is actually a (pair of
ints)[http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsCompatibility.html],
but it doesn't work quite the same way as you'd expect and consequently
doesn't play well with native ints returned from JSNI methods. Any
coercion of a JSNI int to another type of value generally results in
truncation to Int32.

The fix is to remove the use of the GWT-implemented long in most places
that deal with large object sizes and to use "int" instead, which GWT
largely leaves untreated and unbounded (except by the underlying
JavaScript's size limits, which are plenty big even for large file
sizes). The downside to this approach is that care must be taken to
avoid GWT forcefully truncating the values.
Fix execution of multi-line chunks when file uses old Mac line endings
keep Caps Lock from affecting clipboard shortcuts on Mac OS X