The spec says:

If a client has access to environment variables, several standard ones exist to specify the language in which a client should operate. If not, then clients MUST make reasonable assumptions based on the information provided by the environment in which they operate (e.g. consulting navigator.languages in a browser, etc.).

Windows systems do have environment variables, but the

I think it would be a good idea to mention the tee command, probably somewhere in the "Cat, Less, Tail and Head" chapter

Description

Uncommenting info "Disk" disk results in a partially correct output: Disk (81%): 495G / Fles/Git (97G%). What is Fles/Git (97G%)? I'm guessing this might be my external SSD.

Also uncommenting info "Font" font info "Users" users info "Song" song [[ "$player" ]] && prin "Music Player" "$player" results in no display of this info.

• Does this issue still occ

it might be a good idea to keep the standard git-log bahavior and just pass arguments to git log instead of limiting the functionality and setting non-standard default values like it's done for -d and -a.
I can see the need for --abbrev-commit and --pretty=format:'${GIT_FORMAT}' but otherwise it would be nice to make it behave like git-log does with its
`git log [] [<revision ra

This is pretty self-explanatory - it'd be nice if I had something like spotify status player which returns either PLAYING, PAUSED or STOPPED. Think of it as mirroring the play button's status on a music player.

The motivation behind this is that I'm using shpotify to display the player status on my terminal prompt. I'm okay with taking a stab at implementing this if the maintainers ar

Should the 2nd if check for $commandargs instead?

elif [[ $command == "user-stats" ]]; then
    if [[ $command != "" ]]; then

Let's say I have a directory A with hundreds of thousands of files. I would like to move these files to new subdirectories, containing for instance 100 files each.

Source: http://unix.stackexchange.com/questions/63265/distributing-thousands-of-files-over-subfolders

Each file should sport their build and execution instructions, ideally in the header as comments, maybe even required versions (for example the Java version requires Java 8).

That would allow every one to build and run every file, no matter if they are familiar with the toolchain or not. For some files, like the shell, it's as simple as executing the file, others, like the Java version, require