Léa Gris

Thank you for sharing. I think language switching should be user selectable and saved preference, at least per team and or per channel while interface can keep using system locale.

Alternatively put the SC disable commands into a commands block that shares the same shellcheck disabled entries: ```sh # shellcheck disable=SCxxx { var something = that.Causes(theError); // error is not...

Or more broadly, directly as ME Chests (means directly connects to the ME network via ME cable and occupy One Channel. But at the other end of the spectrum, we...

The issue with things like ME Chests or chests connected with Storage Buses is their inventory can be altered from other sources than the ME. So the ME need to...

Why another circuit line? The post mention new names and new textures. But it does not tells why there need to be yet another circuit line or why previous circuit...

The current circuit lines are already frustrating by their claimed complexity and the actual service they fail to provide or fail to improve upper tier machines they are used with....

Why would you want to convert `$(command)` into backtick command? back-ticks are obsolete but kept for backward compatibility with very old scripts. back-ticks can not be nested unless sacrificing readability...

##### This one as well: ```Bash abc='world'; echo "Heallo $\ \ a\ b\ \ c\ "! ``` ##### Output: `Heallo world!`

@wheelerlaw although back-ticks are very outdated syntax. It is better to do this instead now: ```Bash #!/usr/bin/env bash set -x echo "$(echo "hello (world)")" exit ``` I strongly recommend you...

http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03 It became POSIX standard for command substitution nearly 20 years ago when the IEEE admitted that backticks or backquotes are overly ambiguous when nested with all the cascading \...