Hi!

Your site is fantastic and I look forward to seeing it grow. Are ye sticking to bash commands/scripts exclusively? I haven't noticed any Windows commands, but at the same time, I didn't see any bash-specific language in the documentation. Have ye any desire to support windows-only commands, and if so , how should they be differentiated from the bash?

Here is a place to brainstorm ideas for Windows commands to include on the resource. Thanks to @kieranjol for the suggestion!

Maybe a good thing to add to this is the template HTML for adding a new command...

for i in *.wav; do mv “$i” “$(echo $i | sed ’s/MAC/MN/g’)”; done

This is a supplement to the command to append file extensions. This works within the full filename string, instead of only at the beginning or end. It uses “sed” to do this substitution work. The ‘s’ tells sed that we want it to perform a substitution. The "/" characters serve as separators between the old and new values we want to find/replace. First we define the old value we want to replace. In this case “MAC”. Then we define the new value we want to substitute for the old value. In this case “MN”. The ‘g’ tells sed that we want it to do this globally in the string, i.e., every time it sees MAC it replaces with MN. It is essentially a find and replace action.

• Bert

It would be nice to add contribution guidelines. I think Github now supports a contributing.md, but I'm not that well-versed in writing contribution guidelines.

One thing I'd like to see highlighted is ways to find frequently used commands to turn into contributions. I'm starting with history | less but working towards a cut command.

The command we're building in #18 can be more useful with more commands stored in the history. The problem is, is that this gets kind of shell-specific. I'll make a PR for bash since that should cover the base case, but it will probably need more shells over time.

ls -alR /set/your/path/here > /set/your/output/path/inventory.txt

This is great way to extract a list of files/directories (as well as filesystem data about the files/directories) to a "space" separated text file that you can parse separately from the CLI interface.

• Bert

In the Handling White Space tip, I think it would be safe to make the note that a script should capture the user's original IFS and then reset the IFS once the script completes:

For example:
oIFS=$IFS
IFS=$'\n'
[script text]
IFS=oIFS

A lot of the commands here are fairly long and have sections that need to be edited like source and destination directories.

I think it would be useful to have directions about using the mouse to move cursor. I know on Terminal and ZSH on Macs you can do this by pressing alt/option and clicking where you want the cursor to go. Is this universal enough on other consoles that we can add instructions for it?

Another option could be some of the basic cursor movement commands like ctrl+a and ctrl+e
https://www.gnu.org/software/bash/manual/html_node/Commands-For-Moving.html

I think a lot of us use OS X. In 10.13, APFS will be default, which means filenames are going to become more complicated. https://eclecticlight.co/2017/04/06/apfs-is-currently-unusable-with-most-non-english-languages/

This issue is for an audit of current commands to see if they'll be affected by APFS filenaming.

Adding in more examples from presentations at AMIA

I feel it would be a nice value-add to link the commands to explainshell.com.
It shows the switch details in a visual manner.