I love vim, but it wasn’t always like this. When I was a Linux newbie one of the things that irritated me most is that tutorials aimed at beginners told readers to use vim, without explaining how to maneuver it. People, if you write tutorials aimed at beginners please use nano, even if it’s not your preferred text editor.
i agree with your request. vim used to scare me first.
as a side note: one of the reasons I believe as to why vscode grew in popularity was due to it lowering the barrier to just open up the editor and use it right away(with plugin system and a nice GUI). it is something vim by default doesn’t do.
The first time I opened vim (it was probably just vi at the time) I couldn’t exit it and had to shut down the computer by holding down the power button (!) to regain control of the machine. It took a while before I tried it again. Ultimately nano felt like it was for kids and emacs felt like an even worse option than vi so I memorized a few sequences, eg :q!, :wq, how to enter the insert mode and how to exit it and simple edit commands like dd and x and this gave me enough proficiency to get by.
Most all the terminal commands require prior study before they become easy to use. Its because Unix was created by engineers rather than by ui/ux design professionals.
In Linux terminals, you probably could have pressed Alt+F2 or Ctrl+Alt+F2 (F2 could be other F-keys) and log in on a second terminal to recover (by reading the manual or killing it). Also, if bash already had job control back then Ctrl+Z would have suspended vi/vim to the background.
I’m writing this, so people try it and maybe remember it, if they get stuck in some program. Doesn’t have to be vi. Maybe you just launched a long dd command and don’t want to end it, but want to look something up. These hints may help then.
ci" means change inside “” ca" means change around “”
the " can be replaced with any of: ({[wspbt
For changing inside or around parentheses, curky brackets, square brackets, words, sentences, paragraphs, code blocks and HTML tags respectively.
So for example if you want to replace all parameters in a function call you just do ci(
But that’s not all, the c is one of the possible operators, but not the only one.
di{ deletes the content of a block ya[ copies the content of something inside square brackets g~iw swaps the case of a word guis makes a sentence lower case gUip makes a paragraph upper case
And the most useless one: g?at replaces the content of an HTML tag with its rot13
I managed to plug the 4pin CPU_POWER cable into two corresponding ports. As in 2 pins from one port and two from the other, since they make up an 8pin port.
Surprisingly it was working but crashing randomly every half an hour.
These ports are shaped so that this is impossible, but I managed to do it anyway.
Those connectors are keyed, but only to prevent you from installing them backwards or rotated 90 degrees, and not from doing what you did. The “tombstone” shaped pins will fit in the square holes, but not vise versa.
Offsetting it by 1 pin side to side won’t result in the loss of any smoke, because you will observe the wire colors and that all of the pins on the top edge are 12v positive and all the pins on the bottom edge are ground. You got away with what you got away with because you merely delivered insufficient current to the board, but not the wrong voltage or wrong polarity to the wrong place.
Something I’ve realised is that a lot of people when starting a task they’ve never done, don’t realise that fact and attempt to start and finish it all in one go anyways, rather than before starting realising you have no expertise and searching the web for “How to do: X” for more complex tasks this can be unsuccessful, but for simple tasks like installing computer parts people just wing it first time for some reason. 🤷♂️
Listen, I figured out how to do this at age 10 in 1994 before Google existed. It’s not fucking hard, OP’s guy must have been hammering those square pegs into round holes too. Some people just don’t have any common sense or problem solving capability.
discuss.tchncs.de
Newest