3 ms·
You should sit this one out. You already said you aren't familiar with the systems being discussed.
by jonathankoren 3y ago
You should sit this one out. You already said you aren't familiar with the systems being discussed.
- medo-bear 3y agoLol no worries hero :) I am unfamiliar in the sense that I cant be bothered to actually try it. However everything I said applies to what is being described herein https://learn.microsoft.com/en-us/visualstudio/debugger/debugger-feature-tour?view=vs-2022 https://learn.microsoft.com/en-us/visualstudio/debugger/debu... There is no feature here that is not available for debugging Common Lisp in Emacs, which has much more powerful debugging tools, and with less overhead https://lispcookbook.github.io/cl-cookbook/debugging.html https://lispcookbook.github.io/cl-cookbook/debugging.html
- lispm 3y agoFor starters: GNU Emacs is not providing a Command Line Interface, CLI.
- medo-bear 3y agoExactly. The following demonstration on GDB in Emacs looks pretty good to me. In fact, it can do this even in tty, no GUI required. https://m.youtube.com/watch?v=aNTFDq3e2Qo https://m.youtube.com/watch?v=aNTFDq3e2Qo
- lispm 3y agoEven in terminal one can have menus, menubars, tree navigation, folding views, scrolling lists, dialogs, windows, frames, textual buttons, editor buffers with specialized functionality, etc. That means one can have backtrace frames, steppers, data inspectors, configuration menus, preference dialogs, class browser, call graphs, restart menus, read-eval-print loops, refactoring dialogs, ...