Andrey Listopadov

Results 306 comments of Andrey Listopadov

Seems that first input is duplicated when selection is single char: ![image](https://user-images.githubusercontent.com/19470159/56868703-8fff6580-69fe-11e9-8225-81c243888d0a.png) Here I've pressed v once when first placeholder was selected. Snippet definition: ``` for (int ${1:i} = 0;...

It's more interesting than I've initially thought. Look at the following snippet: ${1:1} ${2:2} ${3:3} ${4:4} ${5:5} ${6:6} ${7:7} ${8:8} ${9:9} If I jumpt towards the 9th placeholder without changing...

>Thanks for testing it's like top priority feature for my workflow, so really big thanks to you for working on this.

> I think it's possible to detect in which mode we are when jumping to the placeholders but that's not super trivial. I've thought that introduction of `has_default` will mean...

I've managed to make it work with this hook: hook window -group snippets-auto-discard InsertChar .* %sh{ cursor=${kak_cursor_column} selection=${kak_selection_desc} # let's get cursor positions from selection description selection1=${selection##*,}; selection1=${selection1##*.} selection2=${selection%%,*}; selection2=${selection2##*.}...

probably we could slim it down to hook window -group snippets-auto-discard InsertChar .* %sh{ if [ $(printf "%s\n" ${kak_selection} | wc -m) -eq 2 ]; then printf "%s\n" 'remove-hooks window...

@occivink I've thought about one aspect of allowing user to visually distinguish if default text is going to be discarded or not. But this will require modifications on how you...

seems like 78852bf91b23005c57cfe6febff9c04f3acf2bc1 doesn't affect zero placeholders

I think we're asking for the same feature: https://github.com/occivink/kakoune-snippets/issues/21

this can be solved by adding this hook to the very end of `snippets-select-next-placeholders` command: ```kak hook window -once InsertChar .* %{ execute-keys -draft "di%val{hook_param}" } ```