Reputation
320
Top tag
Next privilege 500 Rep.
Access review queues
Badges
3 10
Impact
~3k people reached

Apr
7
awarded  Notable Question
Sep
24
awarded  Popular Question
Jun
12
comment How do I delete the first n lines and last line of a file using shell commands?
You're probably best off fixing this inside SQL*Plus; rather than generating a file and then trying to trim the stuff you don't want, you can just tell SQL*Plus not to generate that stuff to begin with. One approach is described in the "Creating a Flat File" section at docs.oracle.com/cd/A84870_01/doc/sqlplus.816/a75664/ch44.htm; another approach is described at stackoverflow.com/q/2299375/978917.
Mar
28
comment `command .*` acts on the parent directory
@NateEldredge: Yup, I'm aware. (Hence extglob, globstar, etc.) But the specs don't seem to use that term; they just say "filename expansion", so that's what I stuck with in my comment. (By the end of #5, I was really nearing the character limit -- no room for any unnecessary facts. :-P )
Mar
28
comment `command .*` acts on the parent directory
@Izkata: Not exactly. It's complicated. See my comment. (Or alternatively, see pubs.opengroup.org/onlinepubs/009695399/utilities/…: "the exclamation mark character ('!') shall replace the circumflex character ('^') in its role in a 'non-matching list'".)
Mar
28
comment `command .*` acts on the parent directory
@trlkly: 1. POSIX regexes are different from (say) Perl-style ones. 2. But [^.] does have the appropriate meaning in a POSIX regex. 3. But POSIX filename-expansion doesn't use the same rules as POSIX regex. (If it did, then .* would mean "zero or more characters" rather than "a dot, plus zero or more characters".) 4. And in POSIX filename-expansion, you have to write [! rather than [^ -- the meaning of the latter is unspecified. 5. But the question specifically calls out Bash, not a generic POSIX shell, and Bash filename-expansion does support [^ as equivalent to [!.
Feb
21
awarded  Autobiographer
Feb
1
revised Pipes, how do data flow in a pipeline?
the right way to share the best answer is to accept it (as you have done), not to incorporate it into the question as a postscript.
Feb
1
suggested approved edit on Pipes, how do data flow in a pipeline?
Jan
4
comment Why is using && 75 times faster than if…fi and how to make code clearer
Good to know; thank you!
Jan
4
comment Why is using && 75 times faster than if…fi and how to make code clearer
Sorry, but your reply seems to assume that I already have a detailed knowledge of shell support for (( ... )). I'm flattered, but I do not have that detailed knowledge. (Remember, I'm the one who just asked if (( ... )) is less portable.) So I really can't make sense of your reply. :-/ Could you be a bit more explicit?
Jan
4
comment Why is using && 75 times faster than if…fi and how to make code clearer
What's the advantage of [ "$((...))" -eq "$((...))" ] over (( (...) == (...) ))? Is the latter less portable?
Dec
18
awarded  Scholar
Dec
18
accepted How do I use null bytes in Bash?
Dec
18
revised How do I use null bytes in Bash?
rephrased a bit more honestly
Dec
13
awarded  Self-Learner
Dec
13
comment Is space not allowed in a filename?
@terdon: Since you never posted the question, I've taken the liberty of posting a self-answered one: unix.stackexchange.com/q/174016/12378. Please let me know if you have any feedback on it.
Dec
13
awarded  Student
Dec
13
asked How do I use null bytes in Bash?
Dec
13
answered How do I use null bytes in Bash?