Live data from Hacker News

The Fuck – Correct your previous console command

github.com

31–40 of 173 posts

Re: The Fuck – Correct your previous console command

#32
post #5

Earlier quoted context omitted.

While I agree with what I take to be your overall point, what would have been lost had you replaced your comment with the following, which does not assume anything about the poster's motivation? The utility is actually called "The Fuck", with no asterisk. Please respect creators by not bowdlerizing the names they have chosen.

True. As the title has been updated and your version is better, I'm deleting my original comment.

I'm not sure if this is too much of a de-rail, and I will delete it if it is inappropriate, but I am constantly surprised by and grateful for the civility of HN, where, despite strong opinions, constructive criticism is often accepted and acted upon. Thank you for being part of that!

Re: The Fuck – Correct your previous console command

#33
An issue that popped up for a user, kind of funny:

https://github.com/nvbn/thefuck/issues/1

  who@where:~$ fuck
  No fuck given
  who@where:~$ fuck
  fsck from util-linux 2.20.1
  e2fsck 1.42.9 (4-Feb-2014)
  /dev/sda6 is mounted.

  WARNING!!!  The filesystem is mounted. If you continue 
  you ***WILL*** cause ***SEVERE*** filesystem damage.

  Do you really want to continue? no 
  check aborted.

Re: The Fuck – Correct your previous console command

#34

An issue that popped up for a user, kind of funny: https://github.com/nvbn/thefuck/issues/1 who@where:~$ fuck No fuck given who@where:~$ fuck fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) /dev/sda6 is mounted. WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you really want to continue ? no check aborted.

Yup, is it possible to simulate the "up arrow" but fix it first before injecting it back into the input field of the terminal?

Re: The Fuck – Correct your previous console command

#36
post #6
post #4

Not being 100% sure which command this will correct to is dangerous. Also the need for this is largely negated by a shell with autosuggestions.

> Not being 100% sure which command this will correct to is dangerous. And yet the concept of the invocation `fuck --dry-run` is surely unappealing. :-)

What if you could fuck with a small D? `fuck -d`

Re: The Fuck – Correct your previous console command

#37

I'm going to go out on a limb here and suggest that you rename it "The Fix." Then you could type "fixit" or just "fix".

I rather enjoy the abrasive edge of many parts of programming culture and prefer it not be dulled, even when it ends up cutting me.

Re: The Fuck – Correct your previous console command

#39

Earlier quoted context omitted.

Yes, using the word "fuck" for this just strikes me as a bit immature.

If it was called the fix it never would have made it to page 1

Would make me more likely to recommend it as a serious tool to a colleague though. But then again I'm a curmudgeon.

Re: The Fuck – Correct your previous console command

#40

I just keep getting "No host name on command line, aborting." Also was asked to install "suck." Not sure why / what that is.

One of the issues on the Github reveals that at least one user ended up running "fsck" after typing "fuck" twice. :)
Post reply on HN