Olivier Perret
Olivier Perret
`advance` is awkward to use because it stops when executing the current function. We could add a simple `tbreak; run` command
We could support `gdb-display-expression`, `gdb-display-clear` and every time the execution is stopped, the expressions would be shown automatically
Need to investigate which side is causing this
It's a bug on gdb's side, more information here: ``` 2017-09-25 14:41:21 occivink sometimes when I run "continue" from mi, and hit a breakpoint, the following message appears on the...
Should fix #8 For lack of a better idea, it's now implemented directly in the script. The auto-discard is removed as soon as insert mode is exited, or the selections...
Hi, It often happens to me that I carefully craft a selection with multiple cursors, ready to make changes elegantly, only to completely mess it up by pressing a wrong...
Fixes #2147 The last commit (35efc83) is not exactly related to the issue, but I think it makes sense. I can remove it, or move it to a different pull...
The one I'm particularly interested in is `scratch` but I figured the others could be useful as well. Note that `scratch` is the only one that is the negation of...
First of all thanks for the python bindings, I previously tried to get into libfive but wrapping my head around both scheme and functional representation at once was a little...
Hi, I'm a casual OpenSCAD user, and I'm looking into moving to libfive (better language, faster...). The basics seem to map easily, but I could not find an equivalent to...