News for hackers. Stuff that matters.
Re:Thank you, GitHub by thesausageking on Wednesday November 03, 2021 @02:28PM (#29098533)
Why "cd ~ && mkdir -p nat/next" instead of just "mkdir -p ~/nat/next"?
Re:Thank you, GitHub by yibers on Wednesday November 03, 2021 @02:55PM (#29098837)
Maybe he is first going home, than moving on to the next thing?
Re:Thank you, GitHub by gscho on Wednesday November 03, 2021 @09:02PM (#29102556)
That’s how I read it
Re:Thank you, GitHub by hnov on Wednesday November 03, 2021 @02:32PM (#29098580)
Popping the stack so to speak before embarking on the next ____.
Re:Thank you, GitHub by Rokid on Wednesday November 03, 2021 @03:43PM (#29099363)
Also, in which shell does `cd $` change into a newly created directory?
Re:Thank you, GitHub by staz on Wednesday November 03, 2021 @04:40PM (#29099978)
it's `cd $_` with the underscore, it repeat the last argument.

from bash man page

> _ At shell startup, set to the pathname used to invoke the shell or shell script being executed as passed in the environment or argument list. Subse‐

> quently, expands to the last argument to the previous simple command executed in the foreground, after expansion. Also set to the full pathname used

> to invoke each command executed and placed in the environment exported to that command. When checking mail, this parameter holds the name of the

> mail file currently being checked.