ale5000

It is because the screen of your phone is bigger. Try on a phone with a screen of 122.40 x 64.20 mm and stock Android Lollipop.


These works perfectly for me in BusyBox: ``` printf '%s\n' "abc123" | tr '0-9' '0' | tr 'a-z' 'x' | tr 'A-Z' 'X' printf '%s\n' "abc123" | tr '[:digit:]' '0'...

It is normal, by default it doesn't alert about undefined uppercase variables (that are usually global), unless you enable the check. You can also choose to enable all checks by...

@abitrolly It is simply how the shell is, by using unquoted vars you will always get problems. The shell doesn't behave like a programming language where parameters are strictly defined....

This is a "static analysis tool", it isn't a shell nor a shell manual; it just give general hints to help do better programming. How already said you can use...

Using Windows line ending in a shell file is just a bad habit. Git doesn't force anything, you just have to configure it with `*.bash text eol=lf` inside `.gitattributes` in...

Using getopt would be really good if the support was fine but there may be cases where getopt isn't supported (most Android), but also case where it is supported but...

@ArrayBolt3 Note that shellcheck will use the line `# shellcheck source=sourced_file1` by looking of the current folder where you are running the shellcheck command. So if you have the files...

@moonfruit My opinion: shellcheck already detect the shell by itself in multiple ways so there isn't any need for the server to suggest it (even more so if the suggestions...