Conversation
Notices
-
man the new finder is fucking ugly
-
@pagat @caskd @cirno @orekix @pernia nah, vim for individual files and vs code for projects
-
@nik @caskd @cirno @orekix @pernia I'm sure you use ed as your text editor too, right?
-
@caskd @pernia @cirno @orekix i just, dont use a file managershell is all i need baby
-
@pernia @cirno @nik @orekix based nnn user
-
@cirno @orekix @nik psh cringe all of you
-
@orekix @nik For me, it's Nautilus
-
@nik looks worse than dolphin
-
@nik @caskd @cirno @orekix @pagat @pernia limitations?
-
@caskd @cirno @orekix @pagat @pernia i tried but i didnt like debugging within vim, just limitations of text-based ui
-
@nik @pagat @cirno @orekix @pernia why not use vim for projects? lsp integration makes vim pretty much a full replacement for vs code/IDE
-
@shmibs @caskd @cirno @orekix @pagat @pernia not really limitations, more that the all the state exploration ui stuff would be more cumbersome if stuck in a terminal. it's just preference.
-
@nik @caskd @cirno @orekix @pagat @pernia what language are you debugging? writing here can't remember the last time actually needed a debugger, with C usually quicker to figure things out just having debug asserts in functions and funclangs spit out where the problem is etc
-
@nik @caskd @cirno @orekix @pagat @pernia (not trying to be some "i'm so cool"; more honestly wondering what debuggers are for / how-why they're used, why that would be stuck inside the editor instead of a separate program like gdb, etc
-
@caskd @cirno @nik @orekix @pagat @pernia gdb can be prettified nicely, like this: https://gef.readthedocs.io/en/master/was kind of useful for crafting shellcode / rop stuff for a class back when, but not used since ????
-
@shmibs @cirno @nik @orekix @pagat @pernia i also use debuggers even with C (undefined behaviour reliance, wrong pointer aritmethics etc..) so i can understand. gdb/lldb is still pretty much unknown for me like git, i only know what i used
-
@shmibs @nik @cirno @orekix @pagat @pernia when you have a big codebase debuggers are needed, especially if you work with code that's not yours or have a really uncommon bug
-
@caskd @shmibs @cirno @orekix @pagat @pernia yeah this, i just need to click to the left of the line number in any open file and it adds a breakpoint, then when it breaks it shows the current variable state right in the code
-
@nik @caskd @cirno @orekix @pagat @pernia ah yeh, gdb does that, break-line and showing varsno idea about javascript though; foreign land XX
-
@shmibs @cirno @nik @orekix @pagat @pernia they usually have quick integration into the editor for breakpoints and following the code while it's running. yes, one can argue debuggers offer that too but some like it that way
-
@nik @caskd @cirno @orekix @pagat @pernia ahmaybe don't understand that, yeh, putting things in the editor that can be separate programs, feels for me less convenient rather than more, complicating interfaces, sharing output space, slowing startup etc
-
@shmibs @caskd @cirno @orekix @pagat @pernia i know gdb does that but this is easier cause it's right in the editor (note, vs code doesnt do the actual debugging of course, it's just a different frontend for things like gdb)
nikki
PGT
pernia
orekix
バツ子（痛いの痛いの飛んでけ;;
All senooken JP Social content and data are available under the