Timeline for using EasyAlign in a function

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
Aug 2 '21 at 17:00 comment added joharr Why won't vim recognise a plugin command in the vimrc, but it will recognise it when running?
Jul 24 '21 at 6:28 history edited joharr CC BY-SA 4.0
removed false comment marker
Jul 22 '21 at 23:45 comment added B Layer @joharr "Nope"? I was just referring to the nnoremap gT mapping in your question which absolutely won't get any mapped keys within. A mapping that uses :normal (without !) is a totally different situation.
Jul 22 '21 at 7:32 comment added joharr @MaximKim, nope, I tried that, among other ideas with no luck.
Jul 22 '21 at 7:31 comment added joharr @BLayer, nope, the mapping I'm now using is nnoremap <buffer> gT :normal gAip*&<CR> successfully over-mapping default gT.
Jul 20 '21 at 14:59 comment added D. Ben Knoble You probably just have to add the full normal-sequence: normal! vip:EasyAlign *&<CR>
Jul 20 '21 at 11:18 comment added Maxim Kim The issue might be in EasyAlign and a range that is in effect when you select a paragraph. Try '<,'>EasyAlign *& in your function instead.
Jul 20 '21 at 11:16 answer Maxim Kim timeline score: 2
Jul 20 '21 at 10:58 answer joharr timeline score: 0
Jul 20 '21 at 10:51 review First posts
Jul 20 '21 at 14:07
Jul 20 '21 at 10:50 history edited joharr CC BY-SA 4.0
added where my function is located
Jul 20 '21 at 10:50 comment added B Layer The reason the mapping doesn't call EasyAlign is because you're using nnoremap which ignores existing mappings. Try nmap. This is one of those not-too-common cases where you actually don't want the "noremap" variation.
Jul 20 '21 at 10:47 history asked joharr CC BY-SA 4.0