network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 8 months |
| seen | 16 hours ago | |
| stats | profile views | 10 |
|
May 2 |
comment |
/usr/bin/env: zsh -: No such file or directory @Gilles: I've added a link to my post; that link refers to attacks exploiting shebang lines that use #!/bin/sh, but the same attacks, it seems to me, would be possible with #!/bin/zsh. |
|
Apr 19 |
comment |
How can a zsh script test whether it is being sourced? More specifically, this answer sounds to me like guesswork, which is not what I'm after (I can supply the guesswork myself). |
|
Apr 19 |
comment |
How can a zsh script test whether it is being sourced? The line "These truly abysmal results give me little confidence in this approach" was an attempt to discourage precisely this answer. I guess I should have been blunter about it... |
|
Apr 4 |
comment |
Why is `kill -s INT <zsh PID>` behaving differently from `Ctrl-C`? Thanks, that definitely sheds light on the situation, but there must be more to the issue, because I don't observe the same behavior under all types of Unix. Please see the latest EDIT to my question. |
|
Apr 4 |
comment |
Why is `kill -s INT <zsh PID>` behaving differently from `Ctrl-C`? @Gilles: I've updated my post in response to your comment. |
|
Mar 21 |
comment |
How does having /dev/fd make running shell scripts under sudo safe? That was an education! I think I got almost everything, but you lost me here: some *evil "-i" file that contains for instance just "sh"*. In the last "for instance", did you mean a file that contains the two-character string "sh", or the executable for sh (i.e. a copy of /bin/sh)? |
|
Mar 19 |
comment |
script failing with “chmod: … Operation not permitted” @D_Bye: that's great advice. Please add it to your answer. |
|
Mar 19 |
comment |
script failing with “chmod: … Operation not permitted” @depquid: basically the script always runs something like mkdir -p blah && chmod 775 blah, to ensure that directory blah exists and has the right permissions... |
|
Mar 7 |
comment |
How to make a path world-readable? Useful advice. Thanks. |
|
Mar 7 |
comment |
How to make a path world-readable? That's a really neat idiom for iterating over subpaths, thanks! Just out of curiosity, what's its advantage over dir=$(dirname "$dir") (other than the need to special-case / with the latter method)? |
|
Mar 7 |
comment |
[ vs [[ : which one to use in bash scripts? Dang, usually the stackexchange interface saves me from posting duplicates, but this time it didn't: it showed exactly 0 suggestions for similar questions, which is pretty unusual, and maybe for this reason made me a bit over-confident... Sorry about that. |
|
Mar 7 |
comment |
How to make a path world-readable? When would slashes be non-empty? |
|
Mar 6 |
comment |
How to make a path world-readable? @Celada: thanks, I've fixed the error. |
|
Apr 25 |
comment |
printing a string's “canonical print-escaped form” No, what I was missing was the -r flag to print, without which your original answer is not useful. Thanks. |
|
Apr 24 |
comment |
printing a string's “canonical print-escaped form” Sorry, there's a bug in the stackexchange software that causes a space to be lost in the first appearance of the substring "$' \t\n\000'" in my previous comment. |
|
Apr 24 |
comment |
printing a string's “canonical print-escaped form” Thanks, but, sorry, I fail to see the relevance of your answer to my question. As I explicitly stated, I want the output of escape FOO $IFS (with $IFS set as in my original post) to be the string "FOO=$' \t\n\000'", verbatim, and not the string "FOO=${(qqqq)IFS}", nor the string "FOO=" followed by the string that ${(qqqq)IFS} gets expanded to (which is not easy to reproduce in a comment but is nothing remotely like the string "$' \t\n\000'"). |
