On Sat, Mar 7, 2020 at 10:34 PM Jack corley wrote:
>
> Hey, guys I recently started a position that requires me to use a windows
> workstation but I would like to have access to vim and the plugins I normally
> would use. I feel infinitely slower doing basic tasks without it. I managed
> to
See :help vimfiles for the location of the configuration files on each
operating system.
This Vimscript code set the global variable g:vimfiles_dir to their path:
let s: vimfiles_dir = split(, ',')[0]
if isdirectory(s:vimfiles_dir)
let g:vimfiles_dir = s:vimfiles_dir
elseif if
For starters it is called _vimrc on windows, and according to :h _vimrc it
lives in $HOME/vimfiles/, which is what ~/.vim is called on Windows.
Den lör 7 mars 2020 22:35Jack corley skrev:
> Hey, guys I recently started a position that requires me to use a windows
> workstation but I would like
Hey, guys I recently started a position that requires me to use a windows
workstation but I would like to have access to vim and the plugins I
normally would use. I feel infinitely slower doing basic tasks without it.
I managed to install the windows version but I am not fully understanding
On 2020-03-07 15:36, 'J S' via vim_use wrote:
> Thanks for all the replies. It seems that:
>
> 1) There's no really clean way to do it. It seems to me that there
> should be something like "linedo" - analogous to "windo" and
> "buffdo". Of the workarounds, the %g/./normal method seems the
>
Thanks for all the replies. It seems that:
1) There's no really clean way to do it. It seems to me that there should be
something like "linedo" - analogous to "windo" and "buffdo". Of the
workarounds, the %g/./normal
method seems the best. Thanks for that.
2) It just occurred to me that, for
Hi,
I've started using pipenv instead of anacondas: and then running gvim from
within the pipenv enviroments which solves all of the issues.
cheers,
Ryan
On Friday, 6 March 2020 22:28:19 UTC, Ryan wrote:
>
> Hi,
>
> I seem to have run into a snag with vim's c-x c-o omnifunction
>
