Show HN: I published my first website – ShellMagic.xyz

Thank you - that is an amazing resource you linked!

I find the scrolling interface strangely satisfying -> useful too, as you can do a full page search via the browser.

Good job!

I always find the context switch to get to a website jarring, and really really love tools that give me documentation on the command line. For example, I can type "go doc foo.Bar" and instantly read the docs for foo.Bar (where foo is usually resolved to example.com/some/go/package/foo, based on what is in go.mod and installed on the system). So for this, I would really like bash's built-in help to show me all this stuff.

They did a 10% implementation of what would be good:

    $ help [
     [: [ arg... ]
         Evaluate conditional expression.
     
         This is a synonym for the "test" builtin, but the last argument must
         be a literal `]', to match the opening `['.

But it doesn't know how to dive into [ and show docs for the operators, i.e., "help [ -e" doesn't work. The [ documentation also doesn't tell you what options are available, and of course [ doesn't implement --help (but, of course, /bin/[ does. And people say computers are hard to use! Psh!).

So anyway, if this could all be fixed with a command-line utility, that would be wonderful. It is likely that if I ever need to remember what [ -e does, I'll "man [" or failing that "info bash" or failing that, give up and write the program in go so at least I can work from some documentation.

I bookmarked this as it will be very helpful to me, so thank you!

My constructive or no so constructive criticism is that I really really don't like the theme. I find it really hard to look at and a bit difficult to read.

> Access Codes & Permissions

This section is missing stuff like setuid, sticky bit, extended attributes, etc. (SELinux stuff and setgid? I'm not sure if there's more.) For example, `ls -ld /tmp` shows `drwxrwxrwt`, `ls -l /bin/sudo` shows `-rwsr-xr-x`.

> History Expansion

To this section, it might be good to add `!$`. Also maybe a quick overview on word designators, to cover syntax like `!:^`, `!:2`, `!:`, etc. There's also modifiers, like `!$:h` to return the (h)ead of a path that's the last argument of the previous command, etc.

> Bash Globbing

> @ Matches exactly one of a given pattern

It might be better to put these extended glob ones as @(pattern-list) for example, just like it is on the manpage. Putting it just like @ next to ? or , implies that it just goes like that alone.

> Overview of Bash Symbols

> $(( )) is used for saving the output of arithmetic.

I guess you could save it, but you can also pass it directly to where you need it. I wouldn't call `echo $(( 1 + 2 ))` saving it.

> $[] deprecated integer expansion construct which is replaced by (( ))

No, it's replaced by `$(())`.

EDIT: Removed the part about the file types. You have that covered. However, you wrote

> c Special file

> b Block device

They're both special files. `c` is for character devices.