this post was submitted on 17 Dec 2024
83 points (95.6% liked)
Linux
48668 readers
592 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Vim/neovim
I'd suggest going with LazyVIM / SpaceVIM as a starting point, though, as configuring vim from blank state is an art itself and requires quite some time and dedication.
starting off with nothing but vim/nvim really isn't bad
I still have no understanding of how to do literally anything in vim, I couldn't even close out lol.
so you literally just never tried to learn it at all? what's the point of this comment?
I'm asking now in case it comes up again, I couldn't make any sense of the documentation for the hotkeys.
I was trying to edit config files, not learn vim at the time, I just needed a text editor so I could save my changes lol
!pkill vim
Where would I even type that lol.
I got used to nano already for basic config edit needs over ssh
Apologies in advance for the WOT. I will not be offended if you don't read it, but I did try to include helpful information.
So, for reference, though this command should work it's not the correct way to exit vim (for several reasons). Also, if nano works for you, then there's nothing wrong with using it. IMHO you lose a lot of the power of vim, but some of the beauty of linux is that customization is big part of it. One of the smartest and most linux-knowledgeable people I know uses nano and can outperform me in basically every linuxy way.
Also, a caveat: I know some stuff, but I'm not an expert in anything, let alone neat stuff like this. The text below is accurate to the best of my knowledge, but may not represent the whole of the paradigm.
Now, to answer your question: vim is what's called modal. You have two primary modes: editing (amusing edit: this is also called "insert" mode) and command. Editing mode is what it sounds like: When you're editing a file. This mode is usually entered by pressing a button that starts the process of changing the file - stuff like
i
(for insert mode, which just starts adding text you type where your cursor is) oro
(which starts adding text you type on the next line) or many others. This mode is exited by pressingEsc
, which leaves you in command mode. In command mode, you can start with a:
, which generally goes to a field (not the right word, but the one I'm using) at the bottom of the window/screen. This is the command. The command can be extremely complex and even chained. People who are more into vi(m) than I am call it a sentence, I believe, but I might be misinterpreting that. (You can also type things without a:
but those will have different kind of impact.)So, to run the command I posted above, you would start by pressing
Esc
to make sure you were in command mode (if you already are it will just maintain command mode). Then you would type:
to start the command (or possibly sentence). Then you would type the!
, which tells vim that this command is to be run in the shell, rather than as a vim command. Then you would typepkill vim
which is a command that would tell the shell to identify a process calledvim
and kill it. This would exit vim but is, again, not the correct way to do so.The usual way to exit vim correctly would be to press Esc to make sure you were in command mode, then type one of the following:
:wq
(write and quit):q
(quit without saving the file)!
after it (e.g.:wq!
or:q!
) which tells it to ignore errors (:q
will complain if you have made any unsaved changed but adding!
will ignore those complaints)ZZ
(I've not used this myself, but I think it's equivalent to:wq
)One last aside: If you do decide to try to use vim, this is a useful resource: https://vimschool.netlify.app/introduction/vimtutor/
edit: Very small formatting changes.
edit 2: Just some random facts because vim is cool:
:!
with no other text to see the terminal from which you launched vim, then press enter to return to your active vim session, which can be useful if you're trying to replicate text in an environment where you can't copy and paste (and probably other circumstances)%
before any command applies it to the whole file (rather than, for example, just one line) which can be useful if you're trying to sort a file (and in other circumstances):(without the
%
it would just try to sort the current line, which likely wouldn't be too useful since I believe it only goes by the first character of the line unless you present other arguments)to apply a shell command to a single line you need
:.!command
.:!command
just runs it normally and outputs stdout to the terminal instead of inserting it into the buffer.Ah, my mistake.
Very interesting, thank you!
That does help contextualize my experience a bit, I was very much not expecting a "mode" so I started trying to just type and things were happening lmao. Much appreciated, I might have to give it another try next time, I see there's a lot of love for the vi family in general, almost cult like ;) but a good sign that it is a really powerful tool once you understand it.
Thank you for being receptive.
As I said, I'm not expert, but I am a fan. If you decide to try it out and are looking for guidance, I (and, separately, probably several communities) would be happy to help as best we're able.
Not really sure where you got this from. It's quite simple to me. The default vim config works completely fine for me if I'm eg in a VM and I don't want to copy all my vimrc and plugins over, if it's a machine I'll be using more long-term then it's quite quick to configure a few settings to be how I prefer them to be. Main changes I make to a default config is enabling line numbers (idk anyone who wouldn't want line numbers tbh) and setting them to be relative,
set scrolloff=9999
, use 4 spaces for indent, enable line and column highlighting, set a theme, and a couple odd scripts, but again the default is perfectly usable and the tweaks in my vimrc are just to my personal taste.+1 for LazyVim