.vim | My vim dotfiles for python , go and javascript development | Text Editor library

Sometimes Vim plugins suggest a load order, but Vim nowaday natively supports loading plugins with no plugin manager. You just put a submodule in a folder such as ~/.vim/pack/vendor/start and it'll automatically load. So, my question is how do you ensure a load order similar to how people would previously. Older way of doing things example below:

i use parrot security as my daily distro. its mate terminal is transparent so is vim .but i wanted to get auto complete and used some plugins.auto complete window appears to be in pink which looks really ugly in semi transparent black background.i changed the theme and it was fixed but so was gone vim transparency .

in short word (1)i have to keep the default (2)i have to keep transparent vim (3)i have to change the auto complete window from pink to semi transparent black

here is my init.vimrc

I am currently new to neovim and still adjusting to all of the keybindings but something that has me a bit stuck is being able to easily run my code. The text editor I used before trying out vim was Sublime Text 3 and in that text editor, all I had to do was press cmd + B and it would use a build system that either came with the text editor or one that I made myself. I haven't found a way to do this within vim and the closet I have gotten to doing something similar to this is by adding this to my init.vim "command PYrun :!python3 %" but I have only gotten this to work with python and it is no where near as good as the build systems in Sublime. Is there some way that neovim can read the file's extension (eg., .py, .asm, .cs) and use a preconfigured build system to run the code?

Default Python Build System:

i'm running neovim 0.5 with fzf-vim on windows 10 and can't seem to make preview to work.

my init.vim per below:

Recently updated the macOS to Bigsur and as part of the update, I also updated the packages through homebrew. My coc.nvim plugin was not working so, I reinstalled the package. And after that, I am unable to see the color of my scheme (gruvbox) which is also installed as a plugin. Now the screen is all grey with the dark background (the background was dark even previously). I am attaching the vim settings for clarification. The syntax setting is enabled and it is rightly picking erlang, the termguicolors is set as well. I am using mac terminal to invoke vim.

When using 'git ls-files -s' and 'git log' on the same file, I get different SHA hashes. Take the file lib/nerdtree/nerdtree.vim in repo https://github.com/preservim/nerdtree, tag 6.10.5, for example.

The command git log lib/nerdtree/nerdtree.vim produces,

commit 593c16add35a5461f189b8189abe219f7bbbd604 (tag: 6.10.5)

But the command git ls-files -s lib/nerdtree/nerdtree.vim produces,

100644 61a11a96ba44c7b1bf0472b598f2c967b2dce9f2 0 lib/nerdtree/nerdtree.vim

If I attempt to checkout the SHA returned by 'git log', that command succeeds. If I attempt to checkout the SHA returned by 'git ls-files -s', that produces a fatal error:

git checkout 61a11a96ba44c7b1bf0472b598f2c967b2dce9f2 lib/nerdtree/nerdtree.vim

fatal: reference is not a tree: 61a11a96ba44c7b1bf0472b598f2c967b2dce9f2

Why does 'git ls-files -s' and 'git log' produce different SHA hashes for the same file?

NOTE: I searched around for an answer and found this thread: Git - finding the SHA1 of an individual file in the index. This thread explains why there might be differences between the output of 'git hash-object' and 'git ls-files -s', but it does not explain the difference between the output of 'git ls-files -s' and 'git log'.

In vim (neovim), XML code is indenting strangely when attributes are put on their own lines, like so:

Here is my vimrc

I use fzf.vim to quickly find files in my projects in neovim.

Sometimes either because I can't find what I'm looking for or because I forgot to do something before open the new file, I need to cancel and close the pop up window without selecting any result.

Currently to do that I press to enter in normal mode and then :q but ideally it would be much faster to map it to a key combination such as

How could I map keybindings that target only the FZF window? or Is there any key combination that already close the popup window without any further action?

Thanks in advance