ubuntu-26.04LTSにしたらやること
~/.vimrc に `set mouse=` ってだけ書いておく
ってかマウスモードってなんだよこれ、middleクリックできなくて詰んだわ
~/.vimrc に `set mouse=` ってだけ書いておく
ってかマウスモードってなんだよこれ、middleクリックできなくて詰んだわ
October 2, 2026 at 10:48 AM
ubuntu-26.04LTSにしたらやること
~/.vimrc に `set mouse=` ってだけ書いておく
ってかマウスモードってなんだよこれ、middleクリックできなくて詰んだわ
~/.vimrc に `set mouse=` ってだけ書いておく
ってかマウスモードってなんだよこれ、middleクリックできなくて詰んだわ
But… what about vi users, Eva?
Won’t someone think of the beards of the vi users with elaborate .vimrc files??
Won’t someone think of the beards of the vi users with elaborate .vimrc files??
October 1, 2026 at 12:48 PM
But… what about vi users, Eva?
Won’t someone think of the beards of the vi users with elaborate .vimrc files??
Won’t someone think of the beards of the vi users with elaborate .vimrc files??
gvimrc が読まれなくなっちゃう…。素直に ~/vimfiles に戻して、~/.config/nvim/init.vim 作って source するのが良さそう。runtimepath は vimrc で vimrc のフォルダを expand で取得して、そのフォルダを前に、after を後ろに追加かな
September 23, 2026 at 12:08 PM
gvimrc が読まれなくなっちゃう…。素直に ~/vimfiles に戻して、~/.config/nvim/init.vim 作って source するのが良さそう。runtimepath は vimrc で vimrc のフォルダを expand で取得して、そのフォルダを前に、after を後ろに追加かな
neovim 使ってみようと思って vim の設定を改造してる
素の vim も使いたいので has('nvim') 分岐をちょこちょこ入れてみて init.lua を用意して vimrc を source するようにした
XDG_CONFIG_HOME を設定 NVIM_APPNAME に vim を設定して、そこにフォルダを移動。でも vim の方は windows だと見てくれないのか…。
とりあえず ~/_vimrc を作ってこっちも source した
#vim
素の vim も使いたいので has('nvim') 分岐をちょこちょこ入れてみて init.lua を用意して vimrc を source するようにした
XDG_CONFIG_HOME を設定 NVIM_APPNAME に vim を設定して、そこにフォルダを移動。でも vim の方は windows だと見てくれないのか…。
とりあえず ~/_vimrc を作ってこっちも source した
#vim
September 23, 2026 at 2:51 AM
neovim 使ってみようと思って vim の設定を改造してる
素の vim も使いたいので has('nvim') 分岐をちょこちょこ入れてみて init.lua を用意して vimrc を source するようにした
XDG_CONFIG_HOME を設定 NVIM_APPNAME に vim を設定して、そこにフォルダを移動。でも vim の方は windows だと見てくれないのか…。
とりあえず ~/_vimrc を作ってこっちも source した
#vim
素の vim も使いたいので has('nvim') 分岐をちょこちょこ入れてみて init.lua を用意して vimrc を source するようにした
XDG_CONFIG_HOME を設定 NVIM_APPNAME に vim を設定して、そこにフォルダを移動。でも vim の方は windows だと見てくれないのか…。
とりあえず ~/_vimrc を作ってこっちも source した
#vim
明日新しいMac miniが届くので下取りの準備のためにFind my Macを解除しようとして間違えて「解除」ではなく「削除」を選んでしまったようで、中身が完全に消えてしまった。
必要なものは外付けハードディスクあるいはクラウド上にあるので困ることはないけれど、.zshrcとか.vimrcとか、そんなファイルの中身を保管していないから一つ一つ作り直しです。
必要なものは外付けハードディスクあるいはクラウド上にあるので困ることはないけれど、.zshrcとか.vimrcとか、そんなファイルの中身を保管していないから一つ一つ作り直しです。
September 21, 2026 at 10:49 AM
明日新しいMac miniが届くので下取りの準備のためにFind my Macを解除しようとして間違えて「解除」ではなく「削除」を選んでしまったようで、中身が完全に消えてしまった。
必要なものは外付けハードディスクあるいはクラウド上にあるので困ることはないけれど、.zshrcとか.vimrcとか、そんなファイルの中身を保管していないから一つ一つ作り直しです。
必要なものは外付けハードディスクあるいはクラウド上にあるので困ることはないけれど、.zshrcとか.vimrcとか、そんなファイルの中身を保管していないから一つ一つ作り直しです。
2011年の vimrc から継ぎ足しで煮詰まっている init.vim を 捨てて、新しく作り直した
September 14, 2026 at 12:17 AM
2011年の vimrc から継ぎ足しで煮詰まっている init.vim を 捨てて、新しく作り直した
i'll confess, i had a very basic vim then @neovim.io setup for most of my existence. i'd lose "the" vimrc every couple & meh whatever, back to adding a tiny bit.
but holy shit: astronvim! a light-touch framework for plugins, & community registry wrapping upstream plugins.
github.com/AstroNvim/as...
but holy shit: astronvim! a light-touch framework for plugins, & community registry wrapping upstream plugins.
github.com/AstroNvim/as...
astrocommunity/lua/astrocommunity at main · AstroNvim/astrocommunity
A community repository of common plugin specifications - AstroNvim/astrocommunity
github.com
September 9, 2026 at 4:45 PM
i'll confess, i had a very basic vim then @neovim.io setup for most of my existence. i'd lose "the" vimrc every couple & meh whatever, back to adding a tiny bit.
but holy shit: astronvim! a light-touch framework for plugins, & community registry wrapping upstream plugins.
github.com/AstroNvim/as...
but holy shit: astronvim! a light-touch framework for plugins, & community registry wrapping upstream plugins.
github.com/AstroNvim/as...
currently I have an `autocmd ColorScheme * …` in my vimrc where I set highlight groups that my colorscheme would otherwise overwrite.
I haven't looked into how much of the syntax highlighting is done via highlight groups and how much is other things, but I'll keep it in mind!
I haven't looked into how much of the syntax highlighting is done via highlight groups and how much is other things, but I'll keep it in mind!
September 7, 2026 at 9:09 PM
currently I have an `autocmd ColorScheme * …` in my vimrc where I set highlight groups that my colorscheme would otherwise overwrite.
I haven't looked into how much of the syntax highlighting is done via highlight groups and how much is other things, but I'll keep it in mind!
I haven't looked into how much of the syntax highlighting is done via highlight groups and how much is other things, but I'll keep it in mind!
neovim tutorial: first download these 20 million plugins.
vim tutorial: ok we're gonna add these 20 million lines to the .vimrc i won't explain how any of these work because they are self evident lol :)
vim tutorial: ok we're gonna add these 20 million lines to the .vimrc i won't explain how any of these work because they are self evident lol :)
trying to look for how to do shit in vim but every tutorial that floats to the top is for fucking neovim, while every actual vim tutorial is the most obtuse shit you've ever seen in your life.
September 7, 2026 at 3:02 PM
neovim tutorial: first download these 20 million plugins.
vim tutorial: ok we're gonna add these 20 million lines to the .vimrc i won't explain how any of these work because they are self evident lol :)
vim tutorial: ok we're gonna add these 20 million lines to the .vimrc i won't explain how any of these work because they are self evident lol :)
vimrcでpackadd使ってたので直した。 / runtime(doc): usr_05: packadd in a vimrc needs the ! ・ vim/vim@3e06209 https://github.com/vim/vim/commit/3e06209e5e65d3c951381c180bf85e63a0c12e8a
runtime(doc): usr_05: packadd in a vimrc needs the "!" · vim/vim@3e06209 · GitHub
Problem: Four of the package sections tell the reader to load the
plugin with "packadd", and the comment one goes on to talk
about putting that line in the vimrc file...
github.com
September 5, 2026 at 6:25 AM
vimrcでpackadd使ってたので直した。 / runtime(doc): usr_05: packadd in a vimrc needs the ! ・ vim/vim@3e06209 https://github.com/vim/vim/commit/3e06209e5e65d3c951381c180bf85e63a0c12e8a
I haven't tried yet. I ported many commands from nvim years ago in my .vimrc (github.com/sspaeti/dotf...); that's why I'm not missing too many motions.
But I will definitely try to check the difference when I get some time. Let me know if you're getting ahead of me.
But I will definitely try to check the difference when I get some time. Let me know if you're getting ahead of me.
dotfiles/obsidian/Simon/SecondBrain/.obsidian/.vimrc at master · sspaeti/dotfiles
My nvim, zsh, kitty, obsidian, tmux, omarchy and other config files and utility scripts. - sspaeti/dotfiles
github.com
August 25, 2026 at 1:19 PM
I haven't tried yet. I ported many commands from nvim years ago in my .vimrc (github.com/sspaeti/dotf...); that's why I'm not missing too many motions.
But I will definitely try to check the difference when I get some time. Let me know if you're getting ahead of me.
But I will definitely try to check the difference when I get some time. Let me know if you're getting ahead of me.
こｒｒｒｒｒｒｒｒっら！！！
自分専用の.vimrc作ってGitHubに上げていつでも引き出せるようにしとき！（オカン
自分専用の.vimrc作ってGitHubに上げていつでも引き出せるようにしとき！（オカン
August 25, 2026 at 8:16 AM
こｒｒｒｒｒｒｒｒっら！！！
自分専用の.vimrc作ってGitHubに上げていつでも引き出せるようにしとき！（オカン
自分専用の.vimrc作ってGitHubに上げていつでも引き出せるようにしとき！（オカン
My vim config is default. I messed with .vimrc for a while before deciding if I needed to copy an enormous file everywhere to use vim then it didn't have any more use to me than having to set up VSCode to do it
August 19, 2026 at 3:04 PM
My vim config is default. I messed with .vimrc for a while before deciding if I needed to copy an enormous file everywhere to use vim then it didn't have any more use to me than having to set up VSCode to do it
I spent some time learning enough about .vimrc to make it behave like an IDE before deciding I obviously don't want that because vim is good when it is bare bones and not when it is something like neovim
August 8, 2026 at 10:02 PM
I spent some time learning enough about .vimrc to make it behave like an IDE before deciding I obviously don't want that because vim is good when it is bare bones and not when it is something like neovim
Meine .vimrc
Meine .vimrc, die als Basis für weitere Konfgurationen dient
hyperblog.de
August 7, 2026 at 1:32 PM
It is kind of a bummer since the navigation keys for vi/vim are no longer all in a row. It breaks my brain a bit when I do have to use vi/vim.
I could probably make a new .vimrc to map the keys again but I don’t know if it’s worth the effort
I could probably make a new .vimrc to map the keys again but I don’t know if it’s worth the effort
August 6, 2026 at 10:13 PM
It is kind of a bummer since the navigation keys for vi/vim are no longer all in a row. It breaks my brain a bit when I do have to use vi/vim.
I could probably make a new .vimrc to map the keys again but I don’t know if it’s worth the effort
I could probably make a new .vimrc to map the keys again but I don’t know if it’s worth the effort
Me when I ssh into a server and it doesn't have my ~/.vimrc
August 4, 2026 at 11:30 AM
Me when I ssh into a server and it doesn't have my ~/.vimrc
And many user-installed programs don't create the user config files either, especially if you build from source.
A good example of this is vim. Most versions don't create a .vimrc file upon installation.
A good example of this is vim. Most versions don't create a .vimrc file upon installation.
July 31, 2026 at 8:00 PM
And many user-installed programs don't create the user config files either, especially if you build from source.
A good example of this is vim. Most versions don't create a .vimrc file upon installation.
A good example of this is vim. Most versions don't create a .vimrc file upon installation.
Just set up the offspring with a .vimrc that is more than a decade older than him (there’s an edit comment in it from 2007 but I’d been using it since maybe 1999-2000 & I inherited it from someone else).
July 21, 2026 at 9:33 AM
Just set up the offspring with a .vimrc that is more than a decade older than him (there’s an edit comment in it from 2007 but I’d been using it since maybe 1999-2000 & I inherited it from someone else).
vimrc line of the day:
tnoremap <C-q> <C-\><C-n>
^ Press ^q to enter buffer mode in :terminal, then press 'i' to come back to terminal mode
tnoremap <C-q> <C-\><C-n>
^ Press ^q to enter buffer mode in :terminal, then press 'i' to come back to terminal mode
July 19, 2026 at 5:20 PM
vimrc line of the day:
tnoremap <C-q> <C-\><C-n>
^ Press ^q to enter buffer mode in :terminal, then press 'i' to come back to terminal mode
tnoremap <C-q> <C-\><C-n>
^ Press ^q to enter buffer mode in :terminal, then press 'i' to come back to terminal mode
Claude Code 2.1.208 adds vimInsertModeRemaps: map jj to Escape in the prompt editor, just like inoremap jj in your vimrc.
https://startdebugging.net/2026/07/claude-code-2-1-208-vim-insert-mode-remaps-jj-to-escape/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
https://startdebugging.net/2026/07/claude-code-2-1-208-vim-insert-mode-remaps-jj-to-escape/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
July 14, 2026 at 3:08 AM
Claude Code 2.1.208 adds vimInsertModeRemaps: map jj to Escape in the prompt editor, just like inoremap jj in your vimrc.
https://startdebugging.net/2026/07/claude-code-2-1-208-vim-insert-mode-remaps-jj-to-escape/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
https://startdebugging.net/2026/07/claude-code-2-1-208-vim-insert-mode-remaps-jj-to-escape/?utm_source=bluesky&utm_medium=social&utm_campaign=auto
vim でマウス選択範囲がコピーできない。
以下のようにすればできるようになる😩
~/.vimrc
set mouse=
以下のようにすればできるようになる😩
~/.vimrc
set mouse=
July 10, 2026 at 5:25 AM
vim でマウス選択範囲がコピーできない。
以下のようにすればできるようになる😩
~/.vimrc
set mouse=
以下のようにすればできるようになる😩
~/.vimrc
set mouse=