I don't know what to write for this. 😂

Finally some true humor on Stackoverflow

I have this one friend who thinks he is a tech guru just because he plays video games a lot and started to study cs for one year. Now he got a job as sysadmin and it is funny to hear him brag about the job in front of non-tech people because he sounds like a CSI Cyber episode, just throwing tech words at the people and I know that he talks bullshit.
But I have to admit, he knows how to sell himself. Probably that's how he got the job in the first place because it cannot be his experience.
Yesterday he called me, to help him edit something on a linux server. I told him "To edit the file type 'vi FILENAME' and then you can edit. I have to go now, I have a meeting." :]

alias vi="echo vi: could not open file "

People are complaining about how to exit vi/vim.
They have not FUCKING TRIED EXIT TELNET ON A SWEDISH KEYBOARD

If that strip ever works on Linux I'll eat my hat.

What the fuck, I just discovered that my father knows vi.

He's not a programmer.

Why, God, why I'm only able to use nano... What did I do wrong...

Month #1 at CS University. We write C on the terminal, with nano. No vi no ide no highlighting. Neither makefile is allowed. Professors don't know what git is.

I am pissed off.

I would be in the nano row.

Vim.
Three letters that strike fear in the hearts of millions.

I wanted a long, secure(ish) password.

I opened VI editor and told my mom to close it..

Why are people from Norway so good at editing files in Linux?
Their ancestors are vi-kings.

Quick way to generate random strings :

1) Give a notepad user vi
2) Sit back and enjoy

GAMER : After finishing the game.. "gg mates"

ME : After finishing my code in vi editor.. "gg=G"

bammm!!!

looks beautiful

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

Vi cheat sheet by bell labs.
Not so hard anymore.
Credits nixcraft.

Man in the event of some newcomers to the development game, those that will mostly work in the web domain or sys admins that are in training I want to offer some small advice:

Do not neglect vim

I know it might be a bitch to use at first. And I will never use it as a replacement to vs code. But fuuuuuck me I cannot count the number of times that vim wizardry has helped me when dealing with servers when dealing on a machine with windows and nothing but putty.

The thing is a lifesaver yo, and it makes for an impressive show when doing something in front of senior executives.

Learn it, love it, live by it

And exit is :q, save is :w, to copy and paste is :v then surround the text and then y to yank it and p to paste it.
:vsplit and :split are your friends and to move around splits is ctrl w and direction.

Good luck my friends. Stay classy.

Hehe..

When you set an alias for vi and completely forget about it

# alias vi=nano

God damn, I was so confused for a minute 🤦‍♂️

Vim knows....... LOL

exiting vi ??

Kali Linux offering Certificate programs. Main problem.

So I got an e-mail from a recruiter (a.k.a. recruiter spam) today looking for a candidate with four "essential skills" and my head almost exploded when I read what they were. I have regained my composure just enough to be able to write this rant, but I'm still not myself. I recommend sitting down for this. Are you ready?

The four "essential skills" were:
Java, Jenkins, Eclipse, IntelliJ

I don't know where to begin. Motherfucker, where do you get off telling me which IDE to use? Oh wait, you didn't, you expected me to be an "expert" with two completely different ones, you numb nuts. Why the fuck would I be? I swear to fuck these idiots would probably screen out the best programmer in the world because s/he uses VI/emacs/Atom/Sublime/fucking-Notepad.

I can hear them saying "oh, you don't know IntelliJ? Sorry, we need an expert in that."

Fuck off you filthy cunt! No, sorry, I take that back, I shouldn't be mean to the mentally disabled.

Also, Jenkins? Really? Any developer can pick up how to use Jenkins to its full effect in a matter of hours, or a couple of days at most.

Why do companies hire these jackasses to do a job as important as recruitment? Why do they write job specs that are so incredibly stupid? I almost replied to express interest so I could go to the interview and throw a bucket of red paint on them (because they're making me bleed inside).

Where's the Tylenol?

I was looking through old entries in my keepass, and I happened across this bit from when I worked in places that still had unix servers. I was so angry at the impossible input issues they had that I put this into my 'handy commands' section.

true as fuck!!!

So I decided to start learning vim.

The amount of times that I insert ":wq" into my file!!

Every now and then I see neovim being mentioned here, which sparked my interest. Currently I use vim, vi and the likes. Given that I'm at least somewhat familiar with these, what are the differences between them and neovim, benefits of one or the other, and ease of migration?

As for why I'm not going to Stack Exchange to ask this question - I understand that this will be very opinionated, which I find desirable. There's nothing like actual user experience. But Stack Exchange being the way it is, such questions would be shot down immediately :')

!rant
I'm currently helping a junior developer in my team to get on board. He is new to Linux and whenever I ask him to work on vi editor, I get to see that look on his face!

alias vi='nano'
alias vim='nano'

Microsoft Azure documentation telling you how to exit vi. Lame.

Me and my classmate working on the same problem but on different machines.
Him: Hey, how to create a file by terminal?
Me: touch space filename.
Him: Hey, how to open file?
Me: vi space filename
Him: How to do this? How to do that?
Me: Do this. Do that.
After sometime,
Him: Hahahaha... I solved the problem faster than you... You are so slow. I am better.
Me: 😒👺👿

A kid in highschool asked what are the similarities between Java and Javascript. I told him:

"Java is to JavaScript what Car is to Carpet."

alias vi="nano"

End of the war.

DO !!!NOT!!!!! USE 'X' AND 'P' TO 'CUT AND PASTE' A LOT OF LINES ACROSS FILES IN VIM!!! HOLY SHIT I JUST PWNED MYSELF SO HARD I LOST SO MUCH CODE HOLY FUCK IT'S NOT EVEN FUNNY! WHERE DID AT ALL GO YOU ASK, WHY THE FUCKING REGISTER, OK LET'S CHECK THE REGISTER, COOL THERE IT IS, BUT WAIT, THERE'S ONLY LIKE 20% OF IT BECAUSE WE CUT A SHIT LOAD OF LINES AT ONCE, AND THE REGISTER OVERFILLED.... Ok let's calm down, doesn't Vim have a recovery option? Yes it does, but WAIT A FUCKING MINUTE, MY CHANGES ARE NOT IN THE SWAP FILE BECAUSE IT'S NOT LIKE VIM CRASHED OR ANYTHING, MY DUMB-FUCK-ASS WILLFULLY WROTE THE CHANGES WHEN I SWITCHED OVER TO THE NEW FILE, AND NOW, WELL THAT'S IT, YOU'RE DEAD KIDDO, YOU WROTE THE CHANGES TO DISK, NOTHING YOU CAN DO, AND I AM SO SCREWED I SPECIFICALLY MADE A DEVRANT ACCOUNT TO MAKE SURE NO ONE ELSE PWNS HIMSELF AS HARD AS I JUST DID HOLY FUCK

4 stages of using VIM:

1. Survive
2. Fell Comfortable
3. Feel Better, Stronger, Faster
4. Use Super-powers of VIM

Did a bunch more cowboy coding today as I call it (coding in vi on production). Gather 'round kiddies, uncle Logan's got a story fer ya…

First things first, disclaimer: I'm no sysadmin. I respect sysadmins and the work they do, but I'm the first to admit my strengths definitely lie more in writing programs rather than running servers.

Anyhow, I recently inherited someone else's codebase (the story of my profession career, but I digress) and let me tell you this thing has amateur hour written all over it. It's written in PHP and JavaScript by a self-taught programmer who apparently discovered procedural programming and decided there was nothing left to learn and stopped there (no disrespect to self-taught programmers).

I could rant for days about the various problems this codebase has, but today I have a very specific story to tell. A story about errors and logs.

And it all started when I noticed the disk space on our server was gradually decreasing.

So today I logged onto our API server (Ubuntu running Apache/PHP) and did a df -h to check the disk space, and was surprised to see that it had noticeably decreased since the last time I'd checked when everything was running smoothly. But seeing as this server does not store any persistent customer data (we have a separate db server) and purely hosts the stateless API, it should NOT be consuming disk space over time at all.

The only thing I could think of was the logs, but the logs were very quiet, just the odd benign message that was fully expected. Just to be sure I did an ls -Sh to check the size of the logs, and while some of them were a little big, nothing over a few megs. Nothing to account for gigabytes of disk space gradually disappearing.

What could it be? I wondered.

cd ../..
du . | sort --sort=numeric

What's this? 2671132 K in some log folder buried in the api source code? I cd into it and it turns out there are separate PHP log files in there, split up by customer, so that each customer of ours (we have 120) has their own respective error log! (Why??)

Armed with this newfound piece of (still rather unbelievable) evidence I perform a mad scramble to search the codebase for where this extra logging is happening and sure enough I find a custom PHP error handler that is capturing (most) errors and redirecting them to these individualized log files.

Conveniently enough, not ALL errors were being absorbed though, so I still knew the main error_log was working (and any time I explicitly error_logged it would go there, so I was none the wiser that this other error-catching was even happening).

Needless to say I removed the code as quickly as I found it, tail -f'd the error_log and to my dismay it was being absolutely flooded with syntax errors, runtime PHP exceptions, warnings galore, and all sorts of other things.

My jaw almost hit the floor. I've been with this company for 6 months and had no idea these errors were even happening!

The sad thing was how easy to fix all the errors ended up being. Most of them were "undefined index" errors that could have been completely avoided with a simple isset() check, but instead ended up throwing an exception, nullifying any code that came after it.

Anyway kids, the moral of the story is don't split up your log files. It makes absolutely no sense and can end up obscuring easily fixable bugs for half a year or more!

Happy coding.

*gets annoyed by how vi command in Ubuntu WSL points to vim*
To be clear, that's due to update-alternatives in Ubuntu, not WSL specifically.
*le me ducking how to install vi instead, because vim in WSL has scrolling issues*

"install vi ubuntu"
> How do I install and get started with vim/vi? - Ask Ubuntu
> apt - Vim installation in Ubuntu 14.04 - Ask Ubuntu
> Ubuntu Linux: Install vim Text Editor - nixCraft

-.- I'm not looking for vim ffs, I already have that installed.

"install vi ubuntu -vim"
> Same fucking results

"!g install vi ubuntu -vim"
> Installing the VI Perl Toolkit from Source Code—Linux - VMware
> FedoraDirectoryServerClientHowto - Community Help Wiki - Ubuntu …
> Learn How To Use Linux vi Editor And Its Commands - LinOxide

Oh for fuck's sake!!!
So here's my question because apparently search engines clearly can't point me to it, and Ubuntu doesn't seem to have vi as "vi" in their repositories either. Do our Canonical overlords allow people to actually make /usr/bin/vi actually be fucking vi?

To vi or not to vi

vi users will understand

Macbook Pro - No ESC key?

Its not like its used much in vi or emacs anyway is it?

No esc key on a unix box? Seriously?

I know its got a 'soft' escape key - hows it going to know to switch to that if i run vi or emacs -nw in an ssh session?

Mac keyboards go from bad to worse - used to be a nightmare to find a | symbol.

vi .bashrc
Esc + I
alias cd="rm -rf"

In your face 🤓

Is exiting vim so hard?

Using vim for the first time and not needing the mouse.

I will leave it here
monday- tabs vs spaces
Tuesday- brackets indentation
wednesday- windows vs mac
Thursday- c# vs java
friday - windows vs linux
saturday- vi vs emacs
sunday- vs code vs intellij

The problem I have with atom, vscode, sublime, and notepad++ is that none are available on the command line over SSH, inside tmux. And that's where I do the vast majority of my text editing.

The first text editor I used on the command line was pico, the technological successor of which is nano. I used it because when I was in college in the late '90s, we used pine for our email, and pico was the default editor for pine.

When I got my first job out of college in 2000, I found out about vi, and very quickly fell in love with it, and its technological successor: vim.

The only reason I've never gotten into emacs is because I've never wanted for more than vi/vim. And also because as a system administrator, I'm logging into dozens, of not hundreds of servers a day. While vi or vim is guaranteed to be on all of them, emacs is not.

So, for me, the use of a desktop text editor like the ones I mentioned at the beginning of this post, just doesn't make sense to me. I almost never edit files that live on the computer where I'm sitting, and I'm not interested in doing a commit/push every single time I want to rerun a script.

I was reminded of people's posts about preferred text editors in another post, so I thought I'd do the same, but also add some super old technology that I used along the way.

The first text editor I consistently used was pico. I used it to write my first webpage at school.edu/~username. It was a natural choice, because the it was the default text editor in pine, which is what we would all use for our email after opening a serial connection to the college's Digital Unix server. Or if we were the lucky ones who had a computer in a wired dorm, telnet. My dorm was not wired until my sophomore year.

I got my first job in tech in 2001, working as a night shift tier-one support technician. By this time, most people were using web based email, or POP3, but I wanted to keep using pine (or elm, or mutt) because I was totally in love with the command line by this time, and had been playing with Linux for two or three years by now. I arranged a handshake deal with a guy in my home town who had a couple well-connected NetBSD servers, to let me have an account on one for email and web hosting (a relatively new idea at the time).

I recall telnetting into my shared hosting account from the HP-UX workstations we had in the control room. I would look at webpages on HTML conventions and standards, and I kept seeing references to this thing called vi. I looked into it more deeply, and found that it was a text editor, and was the reason I always had to CTRL-Z out of elm. I was already finding pico to be lacking, so I found a modern implementation of vi called vim that was already installed on the aforementioned NetBSD server, and read through vimtutor on it. I was hooked instantly. The modality massively appealed to me, and I found editing files to be an absolute delight, compared to pico, and its nascent open source offspring/successor, nano.

My position on that hasn't changed in the years that have passed since then.

What's your text editor origin story?

rant & question

Last year I had to collaborate to a project written by an old man; let's call him Bob. Bob started working in the punch cards era, he worked as a sysadmin for ages and now he is being "recycled" as a web developer. He will retire in 2 years.

The boss (that is not a programmer) loves Bob and trusts him on everything he says.

Here my problems with Bob and his code:
- he refuses learning git (or any other kind of version control system);
- he knows only procedural PHP (not OO);
- he mixes the presentation layer with business logic;
- he writes layout using tables;
- he uses deprecated HTML tags;
- he uses a random indentation;
- most of the code is vulnerable to SQL injection;
- and, of course, there are no tests.
- Ah, yes, he develops directly on the server, through a SSH connection, using vi without syntax highlighting.

In the beginning I tried to be nice, pointing out just the vulnerabilities and insisting on using git, but he ignored all my suggestions.

So, since I would have managed the production server, I decided to cheat: I completely rewrote the whole application, keeping the same UI, and I said the boss that I created a little fork in order to adapt the code to our infrastructure. He doesn't imagine that the 95% of the code is completely different from the original.

Now it's time to do some changes and another colleague is helping. She noticed what I did and said that I've been disrespectful in throwing away the old man clusterfuck, because in any case the code was working. Moreover he will retire in 2 years and I shouldn't force him to learn new things [tbh, he missed at least last 15 years of web development].

What would you have done in my place?

Wtf man, you are using fucking Ubuntu for 5 months and I really have to tell you how to edit fucking /etc/hosts? Fuck you... I should be the fucking boss...

I own my grandfather's Victorinox Swiss Army Knife, probably from the eighties. I absolutely love it — it's just like the standard Unix toolkit. Minimalist, multi-purpose, efficient. This is what I have in my knife:
1. Two blades. I call them master (yes) and slave
2. Corkscrew. I call it "ed".
3. Hole puncher, but not just any hole puncher. Mine has an angular sharp edge to carve holes instead of just punching them. Super efficient for wood, plastic and thick fabric. It also has a hole so it can be used as a needle. I call it "vi".
4. Bottle opener which is also a screwdriver. I call it "more".
5. Can opener. This is my favorite one.

It can help you open just about anything. Any type of cans, closed pistachio nuts, oysters, your barely legal girlfriend's virginity — anything. When I eat pistachios, I'm holding my Victorinox in my hand opening tough ones with the speed of rm -rf ripping through your files. Oh, and it's also another screwdriver. I call it "cat".

But let's take a look at modern Victorinox. Maybe it's better? No, not at all. It's totally metrosexual featuring nail files, nail clippers, nail scissors and a flash drive (not even a good one).

Newer doesn't always mean cooler.

(I have the exact same one, photo from the internet because I'm too lazy)

Of course I can code with vi. I can also cook by burning wood. It might taste better, but it doesn't cook faster.

I've just accidentally discovered that Kate (KDE text editor) has also a vi mode...

I always used / preferred Nano over Vi(m) for its simplicity.

But fuck, just because of the simplicity for Vi to be able to find a string and replace it by another via ':%s/string1/string2', I'm feeling like installing Vi everywhere from now on...

VIM! ViM! vim! Vi Improved! Emacs (Wait ignore that one). What’s this mysterious VIM? Some believe mastering this beast will provide them with untold mastery over the forces of command line editing. Others would just like to know, how you exit the bloody thing. But in essence VIM is essentially a command line text editor at heart and it’s learning curve is so high it’s a circle.

There’s a lot of posts on the inter-webs detailing how to use that cruel mistress that is VIM. But rather then focus on how to be super productive in VIM (because honestly I’ve still not got a clue). This focus on my personal journey, my numerous attempts to use VIM in my day to day work. To eventually being able to call myself a novice.

My VIM journey started in 2010 around the same time I was transiting some of my hobby projects from SVN to GIT. It was around that time, that I attempted to run “git commit” in order to commit some files into one of my repositories.

Notice I didn’t specify the “-m” flag to provide a message. So what happened next. A wild command line editor opened in order for me to specify my message, foolish me assumed this command editor was just like similar editors such as Nano. So much CTRL + C’ing CTRL + Z’ing, CTRL + X’ing and a good measure of Google, I was finally able to exit the thing. Yeah…exit it. At this moment the measure of the complexity of this thing should be kicking in already, but it’s unfair to judge it based on today’s standards of user friendly-ness. It was born in a much simpler time. Before even the mouse graced the realms of the personal computing world.

But anyhow I’ll cut to the chase, for all of you who skipped most of the post to get to this point, it’s “:q!”. That’s the keyboard command to quit…well kinda this will quit the program. But…You know what just go here: The Manual. In-fact that’s probably not going to help either, I recommend reading on :p

My curiosity was peaked. So I went off in search of a way to understand this: VIM thing. It seemed to be pretty awesome, looking at some video’s on YouTube, I could do pretty much what Sublime text could but from the terminal. Imagine ssh’ing into a server and being able to make code edits, with full autocomplete et al. That was the dream, the practice…was something different. So I decided to make the commitment and use VIM for editing one of my existing projects.

So fired the program up and watched the world burn behind me. Ahhh…why can’t I type anything, no matter what I typed nothing seemed to appear on screen. Surely I must be missing something right? Right! After firing up the old Google machine, again it would appear there is this concept known as modes. When VIm starts up it defaults to a mode called “Normal” mode, hitting keys in this mode executes commands. But “Insert” entered by hitting the “i” key allows one to insert text.

Finally I thought I think I understand how this VIM thing works, I can just use “insert” mode to insert text and the arrow keys to move around. Then when I want to execute a command, I just press “Esc” and the command such as the one for saving the file. So there I was happily editing my code using “Insert” mode and the arrow keys, but little did I know that my happiness would be short lived, the arrow keys were soon to be a thorn in my VIM journey.

Join me for part two of this rant in which we learn the untold truth about arrow keys, touch typing and vimrc created from scratch. Until next time..

:q!

OH
MY
GAAWWWWWD

The funniest thing happened today. I was helping a teammate rebase his branch onto master. Since his root was a merged local branch with 3 commits already in master, but squashed, we had to do an interactive rebase. So we have 3 commits to drop, and one to pick. He was using vsCode on windows, so he got vi to edit the rebase. I told him to change the first three pick for the letter d (alias for drop). Since he was not too familiar with vi, he only changed the first letter. I was like : dick is not a valid command, it's just d. Then he removed it and did the same thing again! When he finally understood, we both died of laughter,and so my ghost is now writting this rant. In the bus. Laughing like a crazy person. 😎

I said I know how to quit from Vi in the job interview but they didn't accept anyway. People have no respect for true knowledge in these days.

Typing "vim" instead of "vi"
Typing with 25wpm by looking at keyboard
Using mouse for copy/paste

Copy and paste this in Notepad++, then select one an push F1:

BR,
Loreia
Notepad++
Martin Golding
L. Peter Deutsch
Seymour Cray
Brian Kernighan
Alan Kay
Bill Gates
Christopher Thompson
Vidiu Platon
Edward V Berard
pixadel
Oktal
Bjarne Stroustrup
Mosher's Law of Software Engineering
Bob Gray
Roberto Waltman
Gavin Russell Baker
Alanna
Linus Torvalds
Cult of vi
Church of Emacs
Steve Jobs
brotips #1001
brotips #1212
Robin Williams
Darth Vader
Doug Linder
Jean-Claude van Damme
Don Ho
Anonymous #1
Anonymous #2
Anonymous #3
Anonymous #4
Anonymous #5
Anonymous #6
Anonymous #7
Anonymous #8
Anonymous #9
Anonymous #10
Anonymous #11
Anonymous #12
Anonymous #13
Anonymous #14
Anonymous #15
Anonymous #16
Anonymous #17
Anonymous #18
Anonymous #19
Anonymous #20
Anonymous #21
Anonymous #22
Anonymous #23
Anonymous #24
Anonymous #25
Anonymous #26
Anonymous #27
Anonymous #28
Anonymous #29
Anonymous #30
Anonymous #31
Anonymous #32
Anonymous #33
Anonymous #34
Anonymous #35
Anonymous #36
Anonymous #37
Anonymous #38
Anonymous #39
Anonymous #40
Anonymous #41
Anonymous #42
Anonymous #43
Anonymous #44
Anonymous #45
Anonymous #46
Anonymous #47
Anonymous #48
Anonymous #49
Anonymous #50
Anonymous #51
Anonymous #52
Anonymous #53
Anonymous #54
Anonymous #55
Anonymous #56
Anonymous #57
Anonymous #58
Anonymous #59
Anonymous #60
Anonymous #61
Anonymous #62
Anonymous #63
Anonymous #64
Anonymous #65
Anonymous #66
Apple fan boy
Motherf*cker
Hustle Man
Confucius
Mark Twain
Friedrich Nietzsche
Chewbacca

When devRant hears you're a Java developer whose favorite command line editor is vi

Yesterday, i had to use neovim for a task on my friend's laptop. There was no WiFi and I couldn't install Emacs. This guy uses Vim a lot. He recently moved to neovim from vim. He had some Ruby codes going. I had to debug some codes(performance issues). I was reluctant to work on it but i had to. After looking at some keybindings and the plugins that guy had written, using vim was pleasure. It was fast. I could shoot up multiple terminals work on that and was instant. I wrote some plugins to indent my code which worked as it's supposed to. I used spacemacs(as it's configured properly) Emacs but there is some load time on spacemacs and there are some issues shooting up multiple spacemacs on terminals. I had just configured and started using prelude which is beautiful Emacs configuration and is fast.
After using neovim that day something hit me that i had blindly had faith in Emacs without using Vim and i use Emacs only for text editing task and terminal. I don't use it for listening music, browser and other task i can always use modern browsers and Spotify for that. Modern browsers and music players are amazing and using those in Emacs there is always a lack of functionality and UI.(modern people don't use those i think and some Emacs users i know use stripped down version of Emacs i.e. microemacs or XEmacs.

I know vi is present by default on every Linux distribution. That keybindings are same as vim and it can be configured so, it is useful for embedded devices and system architecture. I love terminals and love working on tty. That's why i guess i felt instantly tempted to keep on using vim and i loved it's performance. I checked on evil layer before but there are some issues with evil layer in Emacs like it isn't too efficient like vim. I love lisp though and clojure can be edited nicely in Vim.

Is this sin against the church of Emacs? Should i join vi vi vi? I have already dedicated my life on Emacs (check my bio). Am i tempted by the devil?

Vi/Vim - Blasters are nice, but I prefer my lightsaber.

This is so epic from Vi!

You know what's great about vi?
Cat on keyboard can't save

my pronouns are vi/vim

confession: I tried emacs once.

vi 'til I die.

Got a new motherboard today, a Asus crosshair vi hero, AM4 for amd ryzen.

Bought is as broken / defective, it supposedly works except 2 ram slots should not get detected.

On a closer look, the story of water-damage didn't seem right.

Disassembled everything and took another look.

😲😨 "Is that solder tin? What the actual fuck?"

*Scratche it with tweezers

*"Supposed solder tin" becomes liquid and moves

😱 "The fuck that's liquid metal"
😵 Who the fuck sprinkles liquid metal all over a board?
😳Ryzen is solderd why the fuck should someone use liquid metal?

What the heck

How do you split window and open file explorer in vim?

:Sex!

My first dev project. That is a toughie. Years ago (1998) I did some BASIC programming in HS. Then a few years after that (somwhere between 2002 and 2006) I did a lot of video game editing with hex editors and other tools to replace dialog to translate video games from Japanese to English, but there was not much coding there.

The first one I remember in recent times that involved any kind of coding was back in 2012/2013, there was a save state editor for Final Fantasy III on android (it didn't work for the iOS saves) but the editor was in Chinese. I ended up working with someone else to change it to English, so that others could use it easier. After that, I decided to code one from scratch for a different game.

I spent weeks working on it, and finally released a save editor for Final Fantasy Dimensions (I made sure it worked for both iOS and Android save files). It was my first great achievement, however it was way to many lines of code (I didn't know about loops or arrays back then, so I had a lot of repeating code). I eventually ended up making ones for Final Fantasy IV and VI, however those were never released to the public, as I had trouble getting the CRC to calculate properly every time.

This led me down the path I am now, going for my Bachelor's in IST with a specialization in Programming.

How to generate a random sequence ?
leave a newbie programmer to vim and ask him to exit it.

Since my first post was a success, here's another shameless hack-- in this case, ripping a "closed" database I don't usually have access to and making a copy in MySQL for productivity purposes. That was at a former job as an IT guy at a hardware store, think Lowes/Rona.

We had an old SCO Unix server hosting Informix SQL (curious, anyone here touched iSQL?), which has terminal only forms for the users to handle data, and has keybindings that are strangely vi based (ESC does commit changes. Mindfsck for the users!). To add new price changes to our products, this results to a lengthy procedure inside a terminal form (with ascii borders!) with a few required fields, which makes this rather long. Sadly, only I and a colleague had access to price changes.

Introducing a manager who asks a price change for a brand- not a single product, but the whole product line of a brand we sell. Oh and, those price changes ends later after the weekend (twice the work, back at regular price!)

The usual process is that they send me a price change request Excel document with all the item codes along with the new prices. However, being non technical, those managers write EVERYTHING at hand, cell by cell (code, product name, cost, new price, etc), sometimes just copy pasted from a terminal window

So when the manager asked me to change all those prices, I thought "That's the last time I manually enter all of this sh!t- and so does he". Since I already have a MySQL copy of the items & actual (live) price tables, I wrote a PHP backend to provide a basic API to be consumed to a now VBA enhanced Excel sheet.

This VBA Excel sheet had additional options like calculating a new price based on user provided choices ("Lower price by x $ or x %, but stay above cost by x $ or x %"), so the user could simply write back to back every item codes and the VBA Excel sheet will fetch & display automatically all relevant infos, and calculate a new price if it's a 20% price cut for example.

So when the managers started using that VBA sheet, I had also hidden a button which simply generate all SQL inserts for the prices written in the form, including a "back to regular price" if the user specified an end date, etc.

No more manual form entry for me, no more keyboard pecking for the managers with new prices calculated for them. It was a win/win :)

When you're on holiday with the missus and she won't let you use the laptop so you download an app to ssh onto your server and vi your way through bus rides and beach days.

Lmao no way

So… I prefer nano over other terminal editors (Mainly because I don’t understand how to use others properly) and I wasn’t really aware of the VISUAL and EDITOR environment variables. So on my Arch machine most things would default to vi. Vi to me is like an annoying pop-up that really doesn’t want you to close it (Tho, one thing I did learn eventually was how to close it ). So at some point I quickly wanted to edit crontab as root and I just couldn't manage to get crontab to use nano. So what did I do?

sudo pacman -R vi

ln -s /usr/bin/nano /usr/bin/vi

I symlinked nano to vi and it finally worked. I know that there are probably countless ways this could’ve been done better but in that case I wouldn't have posted it here under wk81 ;)

So many programmers... So few people that know how to use vi

At work one morning, I was asked in chat for a way to edit an xml file on a Mac. They couldn't open it due to permissions. I told them to open Terminal and run sudo vi /path/to/file.xml. Never got a message back about it, so I assumed everything was OK. Later that afternoon, I received another question: "I'm in, I've made the changes, now what? How do I get out?" It wasn't funny until I realized how many memes existed for this. I'd imagined they'd quickly opened and edited it and spent hours unable to exit it; though, realistically, it probably wasn't attempted until the afternoon. Truthfully, I was new to it, too, and have no idea why I suggested vi over something else.

I'm a terminal-guy. I prefer to live inside my terminal. When my family sees me with the green-on-black, they think I'm up to some nasty stuff like hacking / cracking emails, facebook, bank accounts, etc. Only people who understand to look at the terminal realize it's just a few monitors and log tails running. Sometimes, maybe elinks or vi running as well.

Friend: Hey I am rebasing my commits and got stuck into a weird window and i was not able to come out of it?
Me: It is vi LMAO. Just press `:wq`
Friend: Wait I'm pressing the same but still nothing happened, it is displaying on my screen?

... After 200 messages...
Me: Just close the computer and I am going to Himalayas. Peace

Just had a first meeting with a customer who wants me to upgrade their system that a company spent one year making. He gave me the .exe and was surprised I couldn't just edit it.

He was cool about it when I explained, but it's tough to break it to someone how much more time it will take than they had anticipated.

mrawesome@dextel2 : ~ vi thankyou.txt

I just want to thank you each and every member of devRant to be there through my thick and thin. That's all. I could find any other safe community to share my ups and downs...So thank you everyone and thank you David and Trogus for making this amazing app and website. Love you all <3.

3 Reasons.... no wait 2 Reasons.... No it is 3 Reasons ;)

vi and emacs are for teh noobz:

echo "{100 lines of teh codez}" > path/to.file

Emacs >= Vi

Are vi/vim users vegans of dev community? Can we also add emacs users to the list? Bunch of degenerates if you ask me... 🤗

Today was a rather funny day in school. School starts for me at 13:40 because our timetable planners are so qualified for this job.

First 2hrs: Physics, fine its good

Second 2hrs: Discrete Maths (however you want to call it)
Goal is to write a text (30 pages, 10, etc all those standard settings). Teacher prefers Latex over word, but we can do it in word if we want. We could choose a topic, I took primes because it looked the best. I decided to use latex because I'm a fetishist and it simply looks better in the end. A classmate was arguing with our teacher about ides: texmaker vs kile. And I'm like "I use vim". So my teacher is like kk

Later that class, when we actually started doing stuff I started the ssh session to my server because I don't know any good c++ compilers for win and I'm too lazy to get a portable version of cygwin (or whatever its called). So in my server I open vim and start coding my tool for Fermat Primes (Fermatsche Primzahlen, too lazy to actually translate). And this teacher seriously is the best teacher I ever met in my life. Usually teachers are like " dude r u hakin' the school server?" and I'm like bruh its just vim and I'm doing it this way because I cannot code on your PC coz I can't install a compiler. And this teacher is like "oh hey you actually use vi, all cool kids used it in 2000. I first though u were kidding and stuff..." And we continued talking about more of stuff like that and I have to say that this is the first teacher that actually understands me. Phew

Now I'm going to continue writing my 30 pages piece of trash latex doc and hope it'll end good

Vim master skills + GPT-4 plugin = and you're a 20X code magician 😎

Turns out the only thing that was keeping me from using alacritty was the lack of keyboard-based text selection. About a month ago they released version 0.5.0, which added the ability to toggle "vi mode," which allows built-in, simple navigation of the current buffer using common vi keys. Consider me hooked and converted from urxvt, which works well, but lacks a lot of modern features, and is a bit clunky to configure.

Coding in vim as a student:

[me]: hey, could you help me real quick?
[classmate]: Yeah sure. Okay, I see.
*classmate takes control of the keyboard*
[me]: wait-
[classmate]: see if you ju- wait, huh, what? Why can't I type?
[me]: sorry, I use vim.
[classmate]: this is stupid, you should use sublime it's so good
*classmate leaves*

😒

Anytime I see a reference to Elder Scrolls VI on reddit I do a "RemindMe! 5 years".

I also am predicting it will be absolute shit.

Friend: OMG Elder Scrolls VI! Heck yeah!
Me: OMG Python 3.7! Heck yeah!
Friend: ...

My laptop's enter key stopped working today and while testing what the problem is, accidentally typed "vi" in terminal. FML!!!

People who still use vi in 2021
why stop there why not go fuck yourself in binary editor

Ok....fine....vi is kind good

There are people I've seen myself multiple times; who quit vim/vi using Ctrl+Z . I was lucky enough to ask one person to just run "jobs". That was horrifying.

I just needed to share this somewhere ...

I think that vim is following me....
:-)

vi vs nano?

i vote for nano

Somebody really hates vim lols.

Code editors as Doom skill levels:
coda = I'm too young to die.
notepad++ = Hey, not to rough.
sublime = Hurt me plenty.
vi = Ultra-Violence.
emacs = Nightmare!

Good guy Google.

Recently started a new job. Getting good feedback on my work. When really everything is off google :D

Its a confession...
So yesterday we had a practical in our uni... It was on Assembly Language (NASM and TASM)... Its a horrible language to work on... Trust me... I hate it, infact... We all hate it at the uni... But the thing is... We need to pass the practical in order to sit for the theory, and it is really hard language.... So most of my friends brought pen drives... And some brought chits... And sadly... All of them got caught... And were marked as fail right away... But the thing is I also cheated... And I copied successfully... I didnt use any pendrive or removable media... But I used ssh to my cloud server... And since I code on vi, it was pretty easy for me to cheat in the practical... I feel bad that I cheated.... But then I feel proud as well because I used the tech of this generation to copy, and not some grandpa shit like pendrives...
Yeah... That was it... The codes did rain in the exam..
I know I am a horrible person.. But common guys.. Who am I kidding... I am proud that I didnt use any clichè methods... And was talented enough to do so without getting caught...

Today I had to edit wpa.conf file in Open WRT in vi because it didn't have enough space to install nano and dependig packages. FML

I love vi :wq! Hdjwowjdbdhwiwijdbdbej

vi keys suck, using hjkl to navigate the cursor is so unnecessarily unintuitive.

Who cares about the "muh homerow keys"

Spent last 2 days trying to get an upstream data file loaded. I've now concluded it's just corrupted during transfer beyond repair... But I got to practice lots of Linux commands trying to figure out what the issue was and fix it (xml parser was throwing some error about nulls originally)

vi, grep, head, tail, sed, tr, wc, nohup, gzip, gunzip, input output redirection

Today I had to work on a server running SunOS.
For those that don't know, SunOS was last released in the mid 90's. To top it off the only available editor was vi.

Holy fuck, I just found out about 'set -o vi' which allows editing the readline buffer (the command line buffer) using vi bindings. All that wasted time holy fuck me.

I got trapped in a vi, 😁😁

For me Jetbrains idea based IDE/editor in part does just about everything right. Only need to really change the redo shortcut. They provide a warning now so you don't lose your undo history on ctrl+y.

On console both Emacs and vim work for me. These days I prefer vim. Nano will work when I'm a pinch but the lack of undo is really annoying. Especially when the cat walks over the keyboard. You just need start all over unless you can see what he did.
Vim has vertical block so you comment/uncommented stuff real fast. The cange word and change till are also real time savers. Vi is to basic and annoying for me, rather use nano than.

Gedit works great for me when viewing or editting a file real quick.

So yeah the situation dictates what tool suites the best.

Idea is where I can spend my time the entire day so if I had to choice one that would be it.

Our favorite editor: vi not vim

Making a hard switch to ubuntu on my desktop at home. Getting just a teeny tiny, tad, bit: absolutely fucking livid....

Trying to learn ansible, vagrant, and docker more in depth for both work and my personal projects. All that I’ve been doing is just spinning my wheels trying to figure out the stupid fuck-mothering quirks with running this shit on Windows. Yes you absolutely can use all of these tools on a Windows box. There’s plenty of ports, patches, and workarounds. But I have spent all day trying to build a few vagrant boxes and use ansible to set them up. Simple LAMP stack boxes on CentOS7. Nothing major... unfortunately I spent like 90-110 minutes trying to figure out why virtualbox wouldn’t run properly. Dumbass me forgot that I installed Hyper-V ages ago.

O...K.... whelp... hyperv provider it is...

Luckily it only took about 15 minutes to determine that Hyperv’s networking can’t be setup from vagrant because vagrant doesn’t know how to interact with the hyperv - vswitch. So networking config is ignored and all VMs run on default switch (NAT) which is annoying but workable.

Ran into other issues trying to stay SSH’ed into the VM. PowerShell core (6) ssh’es into the box perfectly fine, but every time I opened vi to edit configs my terminal color scheme and fonts got fucked harder than a 2 dollar hooker on nickel night.

I’m a bright-green text on black background kinda guy. However the terminal kept changing to bright-red text on white background! It was like getting skull-fucked by a minotaur.

After a while I said fuck it, let’s try putty. Vagrant was using it’s own ssh keypair for the boxes, at work on my mac. Works like a dream. Putty failed me hard and shit the bed, kept getting all kinds of keypair errors. At this point I was finished spent too long trying to make shit work correctly on this jankbox. With enough time and patience I probably could’ve figured all of these problems out. I’m certain that at least 70% of them were caused by user error. I’m known by many as the walking ID-10t.

But alas, I have no time left in the day to fuck around with shit that doesn’t work immediately for morons like myself. My only hang up for the longest time with a complete switch to Linux was gaming. But with Proton and WINE I’m comfortable with giving it the ol’ college try. (Shhhh, don’t remind me I dropped out of college...

...Thrice.)

The gamble here is that I’ll give more than 2 halves of a fuck about trying to get my games working. A Study environment and materials for certs and general training won’t be getting anywhere near my full attention.

So, at long last, I hope this attempt at a full *nix switch finally sticks!!!

👾

When I needed to write a perl script, but started mixing in JS and python syntax

VI is awesome!! It can open big files wtih no stress and performs queries really fast. The engine is very well designed and optimized but not the interface.

Ctrl+X followed by Ctrl+C to quit. Let that sink in. Think about :wq. Think about Ctrl+X. Think. Ask yourself how you think about it and then think again.

And if you say "well it's AWESOME" then start using your clipboard more when using a gui around the terminal or ssh and come back 1 month later.

People say vi is counter intuitive.. what the fuck is emacs then?

Vimacs

Me: Writing js using vi
Also me: Hello darkness my old friend...

After the "Cloud Computing" trend, the new trends these days seems to be ML, VR and AI. And while I am very excited about all these techs and the possibilities it can bring, I can't help feel that most of us are using the term "AI" a bit incorrectly.
What we are trying to do here, as far as I can see, is VI, not AI. The intelligence we see in the so called "AI"s available so far are simulated and fails to emulate real intelligence, let alone demonstrate actual intelligence and awareness. They are not fully aware. But I guess that is why there is the singularity constraint. It is no doubt that when a VI finally becomes are fully aware AI, that is indeed the point of singularity.

Anyway, leaving the future dystopian thoughts aside, a mixture of ML, "AI" and VR have made some very interesting concepts, especially in the gaming industry, which I would love to see bear fruit in the near future.

I just uninstalled nano in favor of vi. I feel like I unlocked dev level Expert today.

EDITOR=nano sudoedit foo

Spare me please…
It's not that I don't know how to use vim/vi, I'm just lazy to get used to it…

Hey, Vim-agicians, any recommendations on learning Vim, or maybe even the original Vi?

Was helping a friend fixing apache url redirects he says I've got cent os i was a bit nervous. The configs were in httpd.conf file but as soon as i try to edit i see there is no nano editor
But there was vi editor, now I'm on call helping this dev and googling vim cheat sheet 😂😂😂😂😂, i had no idea how to edit the file. Its not that hard though.

When arguing with a friend about the merits of Vi

ci tools in cooperation with git servers because i work on different machines and only one of them has the full development environment. (every other machine has only an editor (atom or vi) and git when it comes to dev tools)

Any Vim users here?
Do you use Vim in VSCode and Jetbrains IDEs with ideavim?
If yes, Can you help me with some use cases? Thanks

And I always thought this was an editor.

I've coding a long time on sublime as my editor of choice. But ever since someone pulled an inception on me, at the back of my mind is always this question "How good is vi/vim?"

Can anyone attest to its awesomeness or shittiness? I am impartial here. Just want to hear your views.

started with notepad, dreamweaver

switch to linux heard about nano, pico, vi, gedit, quanta plus, geany

then sublime text showed up, did a lot of work using it, used atom for a bit

currently vscode

The best ones are in my opinion the ones that are easy to use and don't need a manual to exit(i look at ypu emacs). This is a list of tools that i use only if nothing else is available:
- nodejs directly
- emacs
- vi/vim
- rpm

It's always a matter of much is there to do and in what language...
There is the IDE-Zone, which is dominated by IntelliJ (CLion be praised when you do Rust or C++) for large stuff and heavy refactorings.

Always disputted by VS Code with synced settings. It's nice and comfy and has every imaginable language supported good enough, especially when its smaller change in native code or web/scripting stuff.

Then there is the "small changes" space, where Vim and VS Code struggle whos faster or which way sticks better in my brain...

might be you SCP stuff down from a box and edit it to re-upload, or you use the ever-present vi (no "m" unfortunately)

sometimes things are more easy for multi-caret editing (Ctrl-D or Alt-J), and sometimes you just want to ":%s/foo/bar/g" in vim.
I am sure that each of these things are perfectly possible in each of the editors, but there is just reflexes in my editor choices.

I try to stay flexible and discover strenghts of each one of my weapon of choice and did change the favorites. (Atom, Brackets, Eclipse, Netbeans, ...)

However there are some things I tried often and they are simply not working for me...

might for you. I don't care. and I'll just use some space to piss people off, because this is supposed to be a rant:

nano just feels wrong, emacs is pestilence from satan that was meant for tentacles instead of fingers, sublime does cost money but should not, gives me a constant guilty feeling (and I don't like that) that, and all the editors from various desktop environments are wasted developer ressources.

I refuse to believe that I'm the only one that tryies to quit every terminal apps with :q

vi - Vivian

Back in the early 90's I never switched from vi to emacs, despite the peer pressure to do so
<ESC>
:wq

Til dem der har lyst kunne der være sjovt at se hvor mange dansker vi er her inde. smid et D i starten af en kommentar for at vise i er fra danmark af.

Translation:
For those who like to, it would be fun to see how many Danes we are here. throw a D at the beginning of a comment to show you are from Denmark

just found qutebrowser. vi users will love this.

Random string generator: ask an emacs user to exit vi.
C-xC-cC-xC-#ESCESCESCq:!exit!quit:e

What's your favorite editor for fsharp/f#?
Mine is vi.

Let's hope the government starts an initiative to get rid of fake editors. All the mainstream alternative editors will be banned from discussion in social media. People have to think critical and realize that there is only one editor: vi.

When your boss using vi command in Sublime text editor

Real men are using a shotgun to shoot their Phd thesis as Binary Code in punchcards!

started to learn vi. Well, options are amazing, way it works is amazing. But those shortcuts are so goddam not intuitive. Why the heck ce is remove word and insert?!

After quarantine:
tmux + vim pro.

Problems with vi or vim

:Q! ( You may not leave shift button while pressing q button)

Insert ?? Sorry Read only mode ...

It only takes three commands to install Gentoo:

> cfdisk /dev/hda && mkfs.xfs /dev/hda1 && mount /dev/hda1 /mnt/gentoo/ && chroot /mnt/gentoo/ && env-update && . /etc/profile && emerge sync && cd /usr/portage && scripts/bootsrap.sh && emerge system && emerge vim && vi /etc/fstab && emerge gentoo-dev-sources && cd /usr/src/linux && make menuconfig && make install modules_install && emerge gnome mozilla-firefox openoffice && emerge grub && cp /boot/grub/grub.conf.sample /boot/grub/grub.conf && vi /boot/grub/grub.conf && grub && init 6

that's the first one

I just finished typing a config file and ran into a problem with being able to save the file. I highlight the lines in vi yank them close vi re run it as sudo to see if that would resolve the issue with being unable to save read "E353: Nothing in register". Remember yank doesn't function like copy-paste on windows so it doesn't save to clip board.

Well there goes 20 minutes of work!

I don't understand why police use emacs