#vim — Public Fediverse posts

@paniash @jtr @ericsfraga

Interesting perspective. I never thought of #Vim as ergonomic. I guess if its key bindings contribute less to RSI, that counts.

I've been using vi for about 35 years. I first learned about it when my computer science professor assigned a project to write a simple version of it in 8086 assembler language. Later, in my with with Unix and Linux machines, I put an effort into learning more about it because it was the ubiquitous editor.

@paniash @jtr @ericsfraga

Interesting perspective. I never thought of #Vim as ergonomic. I guess if its key bindings contribute less to RSI, that counts.

I've been using vi for about 35 years. I first learned about it when my computer science professor assigned a project to write a simple version of it in 8086 assembler language. Later, in my with with Unix and Linux machines, I put an effort into learning more about it because it was the ubiquitous editor.

@paniash @jtr @ericsfraga

Interesting perspective. I never thought of #Vim as ergonomic. I guess if its key bindings contribute less to RSI, that counts.

I've been using vi for about 35 years. I first learned about it when my computer science professor assigned a project to write a simple version of it in 8086 assembler language. Later, in my with with Unix and Linux machines, I put an effort into learning more about it because it was the ubiquitous editor.

@paniash @jtr @ericsfraga

Interesting perspective. I never thought of #Vim as ergonomic. I guess if its key bindings contribute less to RSI, that counts.

I've been using vi for about 35 years. I first learned about it when my computer science professor assigned a project to write a simple version of it in 8086 assembler language. Later, in my with with Unix and Linux machines, I put an effort into learning more about it because it was the ubiquitous editor.

For the #HelixEditor I added a couple of `gq` keybindings that work like #Vim to reflow selected text:

[keys.normal.g]
q = ":reflow"

[keys.select.g]
q = ":reflow"

For the #HelixEditor I added a couple of `gq` keybindings that work like #Vim to reflow selected text:

[keys.normal.g]
q = ":reflow"

[keys.select.g]
q = ":reflow"

For the #HelixEditor I added a couple of `gq` keybindings that work like #Vim to reflow selected text:

[keys.normal.g]
q = ":reflow"

[keys.select.g]
q = ":reflow"

For the #HelixEditor I added a couple of `gq` keybindings that work like #Vim to reflow selected text:

[keys.normal.g]
q = ":reflow"

[keys.select.g]
q = ":reflow"

For the #HelixEditor I added a couple of `gq` keybindings that work like #Vim to reflow selected text:

[keys.normal.g]
q = ":reflow"

[keys.select.g]
q = ":reflow"

I'm finally taking the time to move from my old school vim setup to neovim. I'm already liking this so much more. I used the kickstart.nvim setup and its been pretty great so far.

#vim #neovim

I'm finally taking the time to move from my old school vim setup to neovim. I'm already liking this so much more. I used the kickstart.nvim setup and its been pretty great so far.

#vim #neovim

I'm finally taking the time to move from my old school vim setup to neovim. I'm already liking this so much more. I used the kickstart.nvim setup and its been pretty great so far.

#vim #neovim

I'm finally taking the time to move from my old school vim setup to neovim. I'm already liking this so much more. I used the kickstart.nvim setup and its been pretty great so far.

#vim #neovim

I'm finally taking the time to move from my old school vim setup to neovim. I'm already liking this so much more. I used the kickstart.nvim setup and its been pretty great so far.

#vim #neovim

Découverte Neovim : le folding natif. `zM` et tout un fichier Rust se replie — il ne reste que les signatures. `zR` et tout revient.

Naviguer dans des centaines de lignes devient enfin lisible.

Bonus : un pli fermé compte comme une seule ligne, donc `dd` sur une fonction repliée la déplace en entier.

#Neovim #Vim

Découverte Neovim : le folding natif. `zM` et tout un fichier Rust se replie — il ne reste que les signatures. `zR` et tout revient.

Naviguer dans des centaines de lignes devient enfin lisible.

Bonus : un pli fermé compte comme une seule ligne, donc `dd` sur une fonction repliée la déplace en entier.

#Neovim #Vim

Découverte Neovim : le folding natif. `zM` et tout un fichier Rust se replie — il ne reste que les signatures. `zR` et tout revient.

Naviguer dans des centaines de lignes devient enfin lisible.

Bonus : un pli fermé compte comme une seule ligne, donc `dd` sur une fonction repliée la déplace en entier.

#Neovim #Vim

Découverte Neovim : le folding natif. `zM` et tout un fichier Rust se replie — il ne reste que les signatures. `zR` et tout revient.

Naviguer dans des centaines de lignes devient enfin lisible.

Bonus : un pli fermé compte comme une seule ligne, donc `dd` sur une fonction repliée la déplace en entier.

#Neovim #Vim

Découverte Neovim : le folding natif. `zM` et tout un fichier Rust se replie — il ne reste que les signatures. `zR` et tout revient.

Naviguer dans des centaines de lignes devient enfin lisible.

Bonus : un pli fermé compte comme une seule ligne, donc `dd` sur une fonction repliée la déplace en entier.

#Neovim #Vim

@UmWerker

Das mit den listen sagt mir zwar nix. Gegen nervige Einrück Probleme steht vorallem das hier in meinen dotfiles. Kann das meiste zwar nicht erklären, aber vielleicht hilft ja was davon.

set autoindent
set nosmartindent
set nocindent
set indentexpr=
set indentkeys=
filetype indent plugin off
filetype indent off
autocmd BufNew,BufNewFile,BufRead *, set indentkeys= indentexpr=

#vi #vim #dotfiles #config #cmdline

@UmWerker

Das mit den listen sagt mir zwar nix. Gegen nervige Einrück Probleme steht vorallem das hier in meinen dotfiles. Kann das meiste zwar nicht erklären, aber vielleicht hilft ja was davon.

set autoindent
set nosmartindent
set nocindent
set indentexpr=
set indentkeys=
filetype indent plugin off
filetype indent off
autocmd BufNew,BufNewFile,BufRead *, set indentkeys= indentexpr=

#vi #vim #dotfiles #config #cmdline

@UmWerker

Das mit den listen sagt mir zwar nix. Gegen nervige Einrück Probleme steht vorallem das hier in meinen dotfiles. Kann das meiste zwar nicht erklären, aber vielleicht hilft ja was davon.

set autoindent
set nosmartindent
set nocindent
set indentexpr=
set indentkeys=
filetype indent plugin off
filetype indent off
autocmd BufNew,BufNewFile,BufRead *, set indentkeys= indentexpr=

#vi #vim #dotfiles #config #cmdline

@UmWerker

Das mit den listen sagt mir zwar nix. Gegen nervige Einrück Probleme steht vorallem das hier in meinen dotfiles. Kann das meiste zwar nicht erklären, aber vielleicht hilft ja was davon.

set autoindent
set nosmartindent
set nocindent
set indentexpr=
set indentkeys=
filetype indent plugin off
filetype indent off
autocmd BufNew,BufNewFile,BufRead *, set indentkeys= indentexpr=

#vi #vim #dotfiles #config #cmdline

@UmWerker

Das mit den listen sagt mir zwar nix. Gegen nervige Einrück Probleme steht vorallem das hier in meinen dotfiles. Kann das meiste zwar nicht erklären, aber vielleicht hilft ja was davon.

set autoindent
set nosmartindent
set nocindent
set indentexpr=
set indentkeys=
filetype indent plugin off
filetype indent off
autocmd BufNew,BufNewFile,BufRead *, set indentkeys= indentexpr=

#vi #vim #dotfiles #config #cmdline

Nach der kompletten Neuinstallation zickt #vim wieder herum. Drücke ich in ungeordneten Listen "Enter", startet die nächste Zeile stets mit 2 Bindestrichen, also Unterpunkten.

- Punkt 1
- - sieht dann so aus

Nervt natürlich kolossal. Ich glaube, das hat vim früher schon Mal gemacht, aber ich erinnere nicht mehr, wie ich ihm das abgewöhnen konnte. Noch bin ich nicht auf Suche gegangen. Wer aber schon eine Idee hat, darf gerne vorpreschen. Danke dafür.

#Linux #Arch #ArchLinux #editor

Nach der kompletten Neuinstallation zickt #vim wieder herum. Drücke ich in ungeordneten Listen "Enter", startet die nächste Zeile stets mit 2 Bindestrichen, also Unterpunkten.

- Punkt 1
- - sieht dann so aus

Nervt natürlich kolossal. Ich glaube, das hat vim früher schon Mal gemacht, aber ich erinnere nicht mehr, wie ich ihm das abgewöhnen konnte. Noch bin ich nicht auf Suche gegangen. Wer aber schon eine Idee hat, darf gerne vorpreschen. Danke dafür.

#Linux #Arch #ArchLinux #editor

Nach der kompletten Neuinstallation zickt #vim wieder herum. Drücke ich in ungeordneten Listen "Enter", startet die nächste Zeile stets mit 2 Bindestrichen, also Unterpunkten.

- Punkt 1
- - sieht dann so aus

Nervt natürlich kolossal. Ich glaube, das hat vim früher schon Mal gemacht, aber ich erinnere nicht mehr, wie ich ihm das abgewöhnen konnte. Noch bin ich nicht auf Suche gegangen. Wer aber schon eine Idee hat, darf gerne vorpreschen. Danke dafür.

#Linux #Arch #ArchLinux #editor

Nach der kompletten Neuinstallation zickt #vim wieder herum. Drücke ich in ungeordneten Listen "Enter", startet die nächste Zeile stets mit 2 Bindestrichen, also Unterpunkten.

- Punkt 1
- - sieht dann so aus

Nervt natürlich kolossal. Ich glaube, das hat vim früher schon Mal gemacht, aber ich erinnere nicht mehr, wie ich ihm das abgewöhnen konnte. Noch bin ich nicht auf Suche gegangen. Wer aber schon eine Idee hat, darf gerne vorpreschen. Danke dafür.

#Linux #Arch #ArchLinux #editor

Nach der kompletten Neuinstallation zickt #vim wieder herum. Drücke ich in ungeordneten Listen "Enter", startet die nächste Zeile stets mit 2 Bindestrichen, also Unterpunkten.

- Punkt 1
- - sieht dann so aus

Nervt natürlich kolossal. Ich glaube, das hat vim früher schon Mal gemacht, aber ich erinnere nicht mehr, wie ich ihm das abgewöhnen konnte. Noch bin ich nicht auf Suche gegangen. Wer aber schon eine Idee hat, darf gerne vorpreschen. Danke dafür.

#Linux #Arch #ArchLinux #editor

I was wondering why completion for Ruby was so much better in Vim, compared to Emacs. Turns out ruby.vim does a lot more than propose words it finds in open buffers: https://github.com/vim-ruby/vim-ruby/blob/master/doc/ft-ruby-omni.txt
Is there anything like that for Emacs?
#vim #emacs #ruby

I was wondering why completion for Ruby was so much better in Vim, compared to Emacs. Turns out ruby.vim does a lot more than propose words it finds in open buffers: https://github.com/vim-ruby/vim-ruby/blob/master/doc/ft-ruby-omni.txt
Is there anything like that for Emacs?
#vim #emacs #ruby

I was wondering why completion for Ruby was so much better in Vim, compared to Emacs. Turns out ruby.vim does a lot more than propose words it finds in open buffers: https://github.com/vim-ruby/vim-ruby/blob/master/doc/ft-ruby-omni.txt
Is there anything like that for Emacs?
#vim #emacs #ruby

I was wondering why completion for Ruby was so much better in Vim, compared to Emacs. Turns out ruby.vim does a lot more than propose words it finds in open buffers: https://github.com/vim-ruby/vim-ruby/blob/master/doc/ft-ruby-omni.txt
Is there anything like that for Emacs?
#vim #emacs #ruby

I was wondering why completion for Ruby was so much better in Vim, compared to Emacs. Turns out ruby.vim does a lot more than propose words it finds in open buffers: https://github.com/vim-ruby/vim-ruby/blob/master/doc/ft-ruby-omni.txt
Is there anything like that for Emacs?
#vim #emacs #ruby

@monospace I use $_ often. The other one not really because my shell is configured with: set -o vi and not emacs like many by default

#vim rulezzz

@monospace I use $_ often. The other one not really because my shell is configured with: set -o vi and not emacs like many by default

#vim rulezzz

@monospace I use $_ often. The other one not really because my shell is configured with: set -o vi and not emacs like many by default

#vim rulezzz

@monospace I use $_ often. The other one not really because my shell is configured with: set -o vi and not emacs like many by default

#vim rulezzz

@monospace I use $_ often. The other one not really because my shell is configured with: set -o vi and not emacs like many by default

#vim rulezzz

#linux #nano #vim #emacs

#linux #nano #vim #emacs

#linux #nano #vim #emacs

#linux #nano #vim #emacs

#linux #nano #vim #emacs

Sooo, I looked into how you can pass line and column numbers to different text editors. How did you spend your evening? 😅

https://www.zyzzyxdonta.net/posts/pass-line-number-to-editor/

#Blogging #IndieWeb #SmallWeb #Wikidata #TextEditor #Vim #Emacs

Sooo, I looked into how you can pass line and column numbers to different text editors. How did you spend your evening? 😅

https://www.zyzzyxdonta.net/posts/pass-line-number-to-editor/

#Blogging #IndieWeb #SmallWeb #Wikidata #TextEditor #Vim #Emacs

Sooo, I looked into how you can pass line and column numbers to different text editors. How did you spend your evening? 😅

https://www.zyzzyxdonta.net/posts/pass-line-number-to-editor/

#Blogging #IndieWeb #SmallWeb #Wikidata #TextEditor #Vim #Emacs

Sooo, I looked into how you can pass line and column numbers to different text editors. How did you spend your evening? 😅

https://www.zyzzyxdonta.net/posts/pass-line-number-to-editor/

#Blogging #IndieWeb #SmallWeb #Wikidata #TextEditor #Vim #Emacs

Sooo, I looked into how you can pass line and column numbers to different text editors. How did you spend your evening? 😅

https://www.zyzzyxdonta.net/posts/pass-line-number-to-editor/

#Blogging #IndieWeb #SmallWeb #Wikidata #TextEditor #Vim #Emacs

Found on YOUTUBE

"I just use vim when I'm writing short stories. I get more work done since I don't know how to exit the program."

#writing #VIM

Found on YOUTUBE

"I just use vim when I'm writing short stories. I get more work done since I don't know how to exit the program."

#writing #VIM

Found on YOUTUBE

"I just use vim when I'm writing short stories. I get more work done since I don't know how to exit the program."

#writing #VIM

Found on YOUTUBE

"I just use vim when I'm writing short stories. I get more work done since I don't know how to exit the program."

#writing #VIM

Found on YOUTUBE

"I just use vim when I'm writing short stories. I get more work done since I don't know how to exit the program."

#writing #VIM

gw tau pasti @kriwil akan ngeledek jika gw pakai syntax on di #vim. Gpp deh biar panas sekalian

gw tau pasti @kriwil akan ngeledek jika gw pakai syntax on di #vim. Gpp deh biar panas sekalian

gw tau pasti @kriwil akan ngeledek jika gw pakai syntax on di #vim. Gpp deh biar panas sekalian

gw tau pasti @kriwil akan ngeledek jika gw pakai syntax on di #vim. Gpp deh biar panas sekalian

gw tau pasti @kriwil akan ngeledek jika gw pakai syntax on di #vim. Gpp deh biar panas sekalian

@hottradwife #vimtutor terminal app was the one who thought me #vim

https://vimschool.netlify.app/introduction/vimtutor/

most important thing how to leave vim

ESC and then :q for quit without saving, :wq is write quit

"Just remember: if you need to move between words or lines, you need to switch back to Normal Mode by pressing the ESC key.
To save the file, type the ESC key to switch back to Normal Mode then type :w. The most important: to quit vim, type :q while in Normal Mode."

Alternatively Press Esc, then type ZZ (capital Z, twice)

That saves changes and quits.

https://docs.oracle.com/cd/E19253-01/806-7612/editorvi-9/index.html