New answers tagged vim-windows
1
I found a solution.
For example:
I open Vivado at D:\Vivado_Projects\WorkSpace, when I click to open verilog source file in gvim, execute :cd, then I get D:\Vivado_Projects\WorkSpace, so there if include error.
If enable set autochdir, the work directory will change to file location, then include error will disappear after using :w.
Finally I write a batch ...
1
I have created a "Scratch" command
command! Scratch new | setlocal bt=nofile bh=wipe nobl noswapfile nu
3
That is a known issue: https://github.com/vim/vim/issues/6951 and https://github.com/vim/vim/issues/6365
As a temporary fix, add set t_u7= to your vimrc.
PS, the issue was introduced by windows terminal and is fixed there.
2
There are a few plugins that have started to use {name}://{whatever} to name scratch buffers (e.g. tags://patternsearched, tasks://..., ). This is kind of helpful when other plugins try to do things on buffers but wish to ignore scratch buffer. A typical example is a local-vimrc plugin that applies project configuration settings on every buffer under a ...
2
The problem with [Scratch] itself is that that's not really the name of a buffer, but just Vim telling you that this scratch buffer is actually unnamed...
It's much easier if you start with a named buffer and use bufadd() to create it. For example:
let bufnr = bufadd('MyFancyScratchBuffer')
execute 'sb' bufnr
setlocal buftype=nofile bufhidden=hide noswapfile
...
1
I'm rarely use tabs, but if I make a help window :only, (which is what I have done in the past), and then I switch to the file buffer to try what I learned, the help buffer is gone, and I have to reopen it and re-navigate to the place where I was before to continue reading the help content.
After reading all the answers here, I find that for me :tab is the ...
Top 50 recent answers are included
