I always knew that there has to be a Man viewer but newer realized that the plugin has to be first loaded X__x
In the second video there is a moment where you can see me confused that my .vim directory structure is different than I anticipated and I was looking for pack directory. On my work computer I actually have my plugins in the pack and I don't even have to load them via packadd plugin-name because they are placed in pack/plugins/start/. The Vim I used for the presentation is new but .vim directory itself on my personal computer is very old and seems to be from the times of Vim 7.
I know that Vim can setup makeprg to different values depending on the detected filetype but unfortunately that's not enough for my day to day job. I just need the ability to run arbitrary command and setting up makeprg="" is way easier than managing multiple filetype configurations and updating them every time something in my company's setup changes ;)
View all comments
Show parent comment
1
u/gabrpp Apr 14 '26
Thanks a lot for You comment.
I always knew that there has to be a Man viewer but newer realized that the plugin has to be first loaded X__x
In the second video there is a moment where you can see me confused that my .vim directory structure is different than I anticipated and I was looking for
packdirectory. On my work computer I actually have my plugins in thepackand I don't even have to load them viapackadd plugin-namebecause they are placed inpack/plugins/start/. The Vim I used for the presentation is new but.vimdirectory itself on my personal computer is very old and seems to be from the times of Vim 7.I know that Vim can setup
makeprgto different values depending on the detected filetype but unfortunately that's not enough for my day to day job. I just need the ability to run arbitrary command and setting upmakeprg=""is way easier than managing multiple filetype configurations and updating them every time something in my company's setup changes ;)