let g:gutentags_cache_dir = expand('~/.cache/tags')

Should I store tags per project basis or in single location?

That will allow to re-run installing that file if needed.

Once dense-analysis/ale#2592 is merged and the plugin updated, antew/vim-elm-language-server can be replaced. The linter name is elm_ls. See https://github.com/elm-tooling/elm-language-server/pull/80/files for changes.

Something like kdot seems like a nice idea.
You get it? kornicameister + dotfiles ;D

• install
• upgrade
• logging into files available inside of /tmp for reference if something goes wrong
• printing bad things at the end (or perhaps 2 column layout?)
• --verbose
• --quiet
• improved handling of parts that have been already done (i.e. do not reconfigure neovim but allow to re execute pkg.install.conf.yaml if there's newer version)

This would be nice to have a setup that I consider common enough and load machine specific configuration. oooooooo yeah ;-)

The idea is to have lazy load for all envs that is keyword aware. It means that if someone decides to use go a lazy load plugin must load goenv.

Plugin name changed

An idea is to check out how deep can I affect settings for deoplete or Ale when it comes all languages I am working with.

https://github.com/dustinkirkland/byobu/blob/0a44bf215883cedac2f555ad7c6cc6feb43b4063/usr/bin/purge-old-kernels#L21-L27

See: https://github.com/pechorin/any-jump.vim
Ref: akrawchyk/awesome-vim#55

  4 - papercolor-theme: OK                                                                                                                                                                                                                
  5 - vim-jsx: OK
  6 - elm-vim: OK (not loaded)
  7 - neco-vim: OK
  8 - fzf.vim: OK
  9 - vimproc.vim: OK
 10 - vim-markdown: OK
 11 - .fzf: OK
 12 - vim-json: OK
 13 - committia.vim: OK
 14 - vim-pyenv: OK (not loaded)
 15 - Dockerfile.vim: OK
 16 - yats.vim: OK
 17 - deoplete.nvim: OK
 18 - SimpylFold: OK (not loaded)
 19 - deoplete-jedi: OK
 20 - ale: OK
 21 - vim-fugitive: OK
 22 - vim-markdown-toc: OK
 23 - rainbow: OK
 24 - vim-wakatime: OK
 25 - vim-airline-themes: OK
 26 - vim-surround: OK
 27 - indentpython.vim: OK
 28 - vim-javascript: OK
 29 - deoplete-elm: OK
 30 - vim-gitgutter: OK
 31 - nerdcommenter: OK
 32 - vim-airline: OK
 33 - vimtex: OK                                                                                                     
 34 - vim-bracketed-paste: OK                                                                                        
 35 - vim-flake8: OK                                                                                                 
 36 - rootignore: OK   

There are some plugins which shouldn't be loaded, like deoplete or vimtex when for instance running nvim with vim file.

Right now, I have just ctags running over template dir, but it could be so much more!. That would however require to implement some sort of manager to wrap several different hooks in linear manner.

See: #386

It seems like nicer alternative compared to managing all those submodule dependencies.
Not to mention that it might be easier to install stuff not available in prezto by default.
I am not particularly interested in maintaining forks like that.

I decided that glo is better way to work with git history in interactive manner. It also matches rest of my setup in nicer way.

Fresh installation must not be executed with root privileges. However running a package installation requires those. In quick summary:

• execution of pkg.install.conf.yaml requires root
• execution of install.conf.yaml does not

Root cause: Most likely CI setup introduced in #80

How to approach that? Would be nice to solve that before crashing into different OS and experiencing this once again.

I am not using VIM and seems akward to have a setup for one and the other while I completely ignore normal VIM.

hello this look good customazation for zsh

but i try to run :

rohanex@kali:~/dotfiles-master$ sudo bash ./install
[  ] Kali GNU/Linux Rolling : kornicameister/dotfiles - first run :
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
./install: line 7: /home/rohanex/dotfiles-master/dotbot/bin/dotbot: No such file or directory
/home/rohanex/dotfiles-master
./install: line 73: /home/rohanex/dotfiles-master/dotbot/bin/dotbot: No such file or directory
/home/rohanex/dotfiles-master
No WAKATIME_API_KEY provided, skipping...

An idea is to use modern replacement for ls. Resolving this issue ought to be coupled with:

• maintaining current aliases (ll for instance) but having them pointing at exa
• removing ( preferably ) all aliases that are for ls

--
Follow-Up: #340

Detected-In: #407

Dependabot couldn't find the submodule dependencies/powerline-fonts. Perhaps it isn't committed, or isn't a submodule?

You can mention @dependabot in the comments below to contact the Dependabot team.

" Get off my lawn
nnoremap <Left> :echoe "Use h"<CR>
nnoremap <Right> :echoe "Use l"<CR>
nnoremap <Up> :echoe "Use k"<CR>
nnoremap <Down> :echoe "Use j"<CR>

Implement that to finally learn VIM movement.
Taken from here.
All credit goes to @thoughtbot

There are some global NPM packages installed in my setup. Would be great to store them inside of a package.json. Also that makes it possible to leverage dependentabot

This was meant to be TODOs plugin.
But I am not using it at all.

TBH, it would be nice to have a little bit of cleanup tasks, maybe even move docker pruning elsewhere.

Reason for it is that I want to have newest code that does it and I want jq to be available all the time instead of having it available after loading the shell which was introduced in #345 .

This should implement the same mechanism as ctags.

URL: https://stedolan.github.io/jq/download/

An example of an error is => Cannot find color scheme 'dracula':e

Currently if there's newer version out there in the web, builds fail because that fail to locate it.

Detected-in: #710

Aforementioned plugin is hardly required on global level all the time.
Would make sense to have it installed only if project is Elm based (i.e. contains elm.json)
Another point would be to make sure that we initialize things correctly.

FZF_DEFAULT_COMMAND='git ls-tree -r --name-only HEAD || ag --follow -g ""'

Generally, the point is to make fzf respect the fact that I do search stuff inside of git directory somehow. There are lot of stuff customly addded to ag command there that for some reason make ag ignore .gitignore file.

Follow-Up: #251 #369