Skip to main content


I keep telling myself that I will never break down and add the following to my .bash_aliases file

alias mdkir=mkdir

But it's so, so tempting.

#linux

Unknown parent

Curtis "Ovid" Poe (he/him)
@isotopp Nope. Just fat fingers. I haven't touched MS-DOS in decades.
Unknown parent

Curtis "Ovid" Poe (he/him)

@dch On a related note: I can't tell you how many times I've typed the following:

pythong path/to/program

I have NO idea why I do that. It's not like I ever type "thong," but my fingers are hallucinating programming languages.

#Python

in reply to Curtis "Ovid" Poe (he/him)

I did a somewhat opposite thing — my init.vim has:
cabbr nvim visual
(actually, it has additional logic to only trigger at the start of a command)
in reply to Curtis "Ovid" Poe (he/him)

Same here, but with alias naon=nano
I write it like that probably some 70% of the times.
in reply to luap

@luap Close, but what you really want is:

alias emacs=vim

Makes pair programming so much more fun!

:wq

#emacs #vim

in reply to Curtis "Ovid" Poe (he/him)

@ovid: most emacsers are at least fluent enough to quit vim (a testament to how ubiquitous vim is rather than how "smart" emacsers are), so that would probably not have the intended effect. However, the inverse would anger quite a few co-workers at my workplace! (C-x C-c doesn't quite have the same ring to it)
@luap
in reply to Curtis "Ovid" Poe (he/him)

@dch My go-to ed/ex/vi command when my gnarly fingers get the letters out of order is "xp", to cut the next char and put it right after. Mnemonic: XP = trans-pose.
@dch
in reply to Curtis "Ovid" Poe (he/him)

i have a script called `gi` that removes the first letter from the first argument and passes args to git

gi tpush => git push

it also leaves a harassing message to myself to type better next time

in reply to Curtis "Ovid" Poe (he/him)

For (most probably unwelcomed) information, almost same form exist in (very informal) Polish (pytong, base form being pyton). It works as a augmentative, but is also recognized as “dick”.
Unknown parent

luap
@l13u7anant
alias emacs=wine notepad.exe ?
in reply to luap

@luap @l13u7anant

Reminds me of years ago when a new developer (switching from C++ to #Perl) joined a team I was on. We asked him if he preferred #emacs or #vim. He replied, "nano."

He didn't last long.

in reply to Curtis "Ovid" Poe (he/him)

If you would make me switch from C++ to Perl, I wouldn't have lasted long either :-)

(Generally, these programming languages are used for very different problems to solve. So switching from one to the other - if the problem space stays identical - really sounds weird)

Oh and yes, I got the Nano thing :-)

This entry was edited (7 months ago)
in reply to Holger Schurig

@holgerschurig @luap @l13u7anant Problem space wasn't identical. He needed a new job and our work was very interesting to him. If you read in the news that a particular movie made X millions of dollars over the weekend, it used to be that software I worked on gave that number. Not sure if it's still there, though.
in reply to Holger Schurig

@holgerschurig @luap @l13u7anant Though I recall a time at the BBC where they concluded an unmaintainable Perl monolith was too slow and spent years rewriting it in C++. They not only created a new, unmaintainable monolith, but it was also too slow. Turns out no one profiled the original software to find out the real reasons it was slow.

Andrew Hewus Fresh reshared this.

in reply to Curtis "Ovid" Poe (he/him)

@holgerschurig @luap @l13u7anant Elsewhere “we” concluded Perl was too slow, started a 5(?) year re-write in Golang, went bankrupt. Profiling showed we had lots of opportunities for Perl improvement, but the total memory footprint was quite a problem that Golang appeared to solve. And Golang run speed was stunning.