vim 2021-12-02 | Slack Archive

timo11:12:09

Anyone using a step debugger with nvim/conjure? Any recommendations?

👀 1

dharrigan11:12:01

I don't think there is one, but this issue points to a wish for it to be done:

👍 1

jkrasnay12:12:10

I like using this thing: https://github.com/jpmonettas/flow-storm-debugger

👀 2

jkrasnay12:12:39

It’s a little work to set up, but it’s pretty cool being able to move forward and backward through the trace.

dominicm17:12:24

This isn't the same, but I've found it to be good enough: https://github.com/gfredericks/debug-repl/

sheluchin19:12:17

I recently added the this mapping and I'm not sure how I ever lived without it:

nmap <Leader>if :IcedEval ( *1)<Left><Left><Left><Left>

Is there perhaps a cleaner way of accomplishing the same thing with vim-iced, and does anyone have other similar mappings they find useful?

walterl01:12:14

It might be "cleaner" to convert that macro to a function, like @U0AHJUHJN did https://github.com/daveyarwood/dotfiles/blob/c0a8316978872f45c5eebfe7218cd99708846a40/vim/custom/300-filetypes.vim#L57-L70

walterl01:12:29

Obviously I don't really mind the macros 😉

Noah Bogart22:12:39

What does it do?

tomd22:12:08

It starts command-line mode, types :IcedEval ( *1) and then puts the cursor just after the opening paren. Presumably ready to type a function which takes *1 (last result) as an arg.

👍 1

sheluchin01:12:55

Yes, exactly as @UE1N3HAJH said. I find I often eval forms that I need to subsequently transform and this is a convenient way of doing it. Often it's because the original eval returned something that's too large for the screen, and I end up just doing something like (take 5 *1), or threading few a few values to transform a large collection in some other way. I know I can yank an eval result or print it out and include the literal in a transformation, but using *1, *2, etc. is often more convenient when I don't really care about the intermediate values.

2021-12-02

Channels