News for hackers. Stuff that matters.
Re:The Front-End Developer's Guide to the Terminal by tokumei on Thursday April 21, 2022 @11:00AM (#31110319)
One thing with $ in a shell prompt - $ is meant to indicate the command should be ran as a normal user, while # indicates the command should be ran as a super user.
Re:The Front-End Developer's Guide to the Terminal by 0xdeadb00f on Saturday April 23, 2022 @12:45AM (#31131492)
Generally, yes. But some guides or tutorials don't respect this convention and use any number of chars including the author's own personal prompt. (I see `>` used often too).
Re:The Front-End Developer's Guide to the Terminal by tokumei on Thursday May 05, 2022 @06:16PM (#31278977)
I would always use '>' in README files to indicate the command was to be ran in a command prompt window for Windows users, usually followed with context.
Re:The Front-End Developer's Guide to the Terminal by spondyl on Saturday April 23, 2022 @01:26AM (#31131638)
I'm guilty of this, as I have my prompt set to a single > character. I'd be interested to know where the $ as a representation for user input suggestion originated from. I didn't know about # indicating that a command should be run as a superuser
Re:The Front-End Developer's Guide to the Terminal by jjav on Saturday April 23, 2022 @02:10AM (#31131865)
> I'd be interested to know where the $ as a representation for user input suggestion originated from.

In the absence of any configuration, the default prompt for most shells is (or was) simply $. When you su to root, it becomes #

Re:The Front-End Developer's Guide to the Terminal by 0xdeadb00f on Saturday April 23, 2022 @04:16AM (#31132402)
Indeed.