Show HN: I published my first website – ShellMagic.xyz
71–79 of 79 posts
Re: Show HN: I published my first website – ShellMagic.xyz
#72My 2 cents: top menu goes away when you reduce window width; on mobile no menu at all (but content goes one column correctly, so halfway responsive). If you move or click on something, it highlights the cell (not everywhere) but there is no operation/command bound with that (no copy to clipboard or any kind of interaction). Usually, something highlightening represents an action that user can do.
Re: Show HN: I published my first website – ShellMagic.xyz
#73I think there's a mistake in "Access Codes & Permissions", AFAIK (which is not much) the o stands for "others" and now "owner".
Re: Show HN: I published my first website – ShellMagic.xyz
#74Some feedback you probably won't hear from the HN crowd: Give more context to the site for initial visitors. Its going to be more obvious to those who visited from HN but not to those who stumbled upon it somehow. A little blurb at the top saying this is a reference site for bash scripting syntax and maybe why you saw the need for such a thing would do ease people into the site a bit. I hate the popup at the bottom,…
It would definitely be helpful to have more context. I know some bash, but I'm far from an expert. The first thing I see on the page is a list of flags, but no clue what commands these flags are used with. A few usage examples would help a lot. For example "-e checks if files exists" How? -e filename ? This doesn't work?
test -e file
or: if [ -e file ]; then
echo "File exists!"
else
echo "File does not exist!"
fi
Edit: Untested, I'm currently not at my desk to verify it :)Re: Show HN: I published my first website – ShellMagic.xyz
#75If I might suggest something: Maybe you'd like to investigate different layouts for different use cases? The alphabetical ordering of builtins e.g. will mainly help you if you encounter it, but don't know what it does.
For more exploratory/educational lookup attempts, perhaps it could be useful to group them together by their use? I'm fairly certain, for example, that grouping `cd` together with `pushd` and `popd` might help someone avoid some rather nasty bugs in their script. Maybe, even a "see also" in the direction of subshells could help (as `cd` only affects the commands in the subshell).
And, on a sidenote: Interestingly, one can find similar "lookup problems" all over the place. For instance, any good guide to morse code will show you an alphabetical list of codes (text -> morse code) as well as a morse tree (morse code -> text) :)
Re: Show HN: I published my first website – ShellMagic.xyz
#76I don’t believe this is true. These aren’t expansions, but rather actual objects you can reference that point to cwd and cwd's parent.
You can tell because `echo .` doesn’t expand while `echo ~` does
Re: Show HN: I published my first website – ShellMagic.xyz
#77> . expands to the current directory. > .. expands to parent directory. I don’t believe this is true. These aren’t expansions, but rather actual objects you can reference that point to cwd and cwd's parent. You can tell because `echo .` doesn’t expand while `echo ~` does
Re: Show HN: I published my first website – ShellMagic.xyz
#78really nice, I'm going to use it. I think there's a mistake in "Access Codes & Permissions", AFAIK (which is not much) the o stands for "others" and now "owner".