Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Git git git git git

caiustheory.com

Post reply on HN
Print view View original

221–230 of 244 posts

Re: Git git git git git

#221

Post by sverige »

simias wrote: post #162
sverige wrote: post #114

Earlier quoted context omitted.

OpenBSD comes standard with vi. Vim is a package.

It ships nvi, as do the other BSDs. I think it's reasonable, BSDs have a stronger divide between the base system and third party packages, I'm not sure it would make a lot of sense to maintain vim as part of the former. Besides on my FreeBSD system /usr/bin/vi is around 400kB while on my Debian machine /usr/bin/vim.basic is 2.4MB. It's not much these days but on embedded platform it could still make a significant dif…

Yep, and "nex/nvi are intended as bug-for-bug compatible replacements for the original Fourth Berkeley Software Distribution (4BSD) ex and vi programs."

Re: Git git git git git

#222

Post by jasonm23 »

andreareina wrote: post #138
emodendroket wrote: post #111

Earlier quoted context omitted.

My favorite one of these is typing ctrl-w (cut in emacs) in a browser tab as I am editing a bunch of text in a text box.

One of the things I appreciate about macOS is that it implements some of the emacs behavior (C-a, C-e, C-k). Unfortunately not C-y, and non of the M- ones work since that's for special characters. I understand they originally come from the readline library.

Now try C-k and then C-y

Then regular old Cmd + v.

You're welcome.

Re: Git git git git git

#223

Post by jasonm23 »

emodendroket wrote: post #219
pvorb wrote: post #158

Earlier quoted context omitted.

So why is emodendroket referring to ctrl-w then?

In other words ctrl-w is "kill," which is what most people would think of as "cut," and ctrl-y is "yank," which is what most people would think of as "paste."

And Vimmers would think of yank as copy or kill save

Re: Git git git git git

#224

Post by busterarm »

I sometimes have this problem but I hate solutions like this because I figure if I make this kind of mistake, I'm not paying sufficient enough attention to what I'm doing at the moment.

I take a minute, clear out distractions and then come back to what I'm working on.

Re: Git git git git git

#225

Post by jasonm23 »

AdamGibbins wrote: post #196
z1mm32m4n wrote: post #166

Earlier quoted context omitted.

I actually aliased :q to clear: https://github.com/jez/dotfiles/blob/master/util/aliases.sh#... I also have clera, lcear, and lcera -> clear, and :tabe -> vim.

Are you aware Ctrl-l also clears? I can't recall the last time I typed clear.

I have to admit, I wince when I see someone type clear.

Re: Git git git git git

#226

Post by aws_ls »

perlgeek wrote: post #27
gulperxcx wrote: post #14

>I quite often type git then go away and come back, then type a full git status after it. Does anyone else actually do this besides OP. I've never heard of this problem until now.

I do. And I also write "vim vim thefile.txt" and stuff like that. Finally I've written a small shell function that corrects "gi tpull" to "git pull", because that happens at least once a day.

Got a weird idea reading this. How about checking for all 127 error codes returned by $? (this is the return code that the shell gets, following a failed command, due to command not found).

This process should happen behind the scenes. And then train a RNN for translating it to the following command, which returns a success code. Perhaps, we need to add a few checks that successful command has the same intent as the one which returned 127 error code to the shell.

Re: Git git git git git

#227

Post by vollmond »

dbcurtis wrote: post #135
projektfu wrote: post #60

Earlier quoted context omitted.

I always typed rebnoot, so I patched Netbsd to allow rebnoot. Then I patched it still so it would say, "Rebnooting". Fun times.

Relatable. For years, I aliased mroe to more. Now I alias mroe and more to less. My wife drafts a lot of legal documents, and has a problem with "doe snot". Which unfortunately the spelling checker is perfectly happy with.

My standard .bashrc aliases cd.. and cd- to the same thing with a space. Eliminating minor annoyances and focus-disruptors is great.

Re: Git git git git git

#228

Post by Fnoord »

Singletoned wrote: post #178
dbcurtis wrote: post #135

Earlier quoted context omitted.

Relatable. For years, I aliased mroe to more. Now I alias mroe and more to less. My wife drafts a lot of legal documents, and has a problem with "doe snot". Which unfortunately the spelling checker is perfectly happy with.

There's defintitely room for an advanced spell checker that can say "This is valid, but probably wrong".

command-not-found [1] could implement that, if it isn't implemented already. I remember a Linux distribution with an application which would let a train pass in a few seconds after typing typical commands wrong. Trust me, you'll learn to type correct when that happens because it is very annoying.

EDIT: as mentioned below, it is called 'sl'

[1] https://wiki.ubuntu.com/CommandNotFoundMagic

Re: Git git git git git

#229

Post by sli »

perlgeek wrote: post #27
gulperxcx wrote: post #14

>I quite often type git then go away and come back, then type a full git status after it. Does anyone else actually do this besides OP. I've never heard of this problem until now.

I do. And I also write "vim vim thefile.txt" and stuff like that. Finally I've written a small shell function that corrects "gi tpull" to "git pull", because that happens at least once a day.

I put my most common git commands on keyboard macros mostly for this reason.

Re: Git git git git git

#230

Post by Fnoord »

tosstossy wrote: post #117
popcorncolonel wrote: post #92

Earlier quoted context omitted.

Knowing software developers, probably entirely serious.

The seasoned sysadmins are a little more careful before smacking the enter key...

rm -i and rm -f (as well as mv and cp) allow to specify certainty not merely for everyone above UID 0.

Keyword: Backups.

Post reply on HN