meta user
network profile
| bio | website | kanvuanza.tk |
|---|---|---|
| location | Salvador, Brazil | |
| age | 21 | |
| visits | member for | 8 months |
| seen | May 12 at 22:42 | |
| stats | profile views | 11 |
An usual guy, interested in human beings and computer things. I do molecular modeling.
|
Apr 1 |
comment |
Regular expression problem(s) in Bash: [^negate] doesn't seem to work @vonbrand, now I understand it. Thanks you too. |
|
Mar 31 |
comment |
Merge chunks from multiple files Very useful module, I'll test with real data tomorrow, but seems pretty fast. When the mapped file is freed up from memory? I'm worried about filling up the RAM because 4 or 6 files can easily reach 100Mb. |
|
Mar 31 |
comment |
Merge chunks from multiple files I'm looking for a small and elegant solution instead of writing a new program. Anyway this is a nice answer! |
|
Mar 31 |
comment |
Regular expression problem(s) in Bash: [^negate] doesn't seem to work I guess you're right, that is the common notation for class negation (ie. [^abc]. But I'm pretty sure that grep don't support class negations, except a few standard ones (eg. [[:^digits:]]). Grep support for negation is horrible! |
|
Mar 31 |
revised |
Regular expression problem(s) in Bash: [^negate] doesn't seem to work deleted 148 characters in body |
|
Mar 31 |
awarded | Custodian |
|
Mar 31 |
revised |
Merge chunks from multiple files added new information |
|
Mar 31 |
reviewed | Approve suggested edit on Merge chunks from multiple files |
|
Mar 31 |
comment |
Merge chunks from multiple files I mean "file foo/a from byte 11970 to 12010". Thanks, I'll update the question. |
|
Mar 31 |
answered | Regular expression problem(s) in Bash: [^negate] doesn't seem to work |
|
Mar 31 |
comment |
Merge chunks from multiple files Please feel free to fix grammar and semantic errors, so I can improve my English. |
|
Mar 31 |
asked | Merge chunks from multiple files |
|
Mar 31 |
awarded | Critic |
|
Oct 18 |
comment |
Tmux eclipsed colorized output of ls Funny, sometimes we're looking far away but the answer is in front of us :) |
|
Oct 18 |
comment |
Tmux eclipsed colorized output of ls Sorry, I misread your answer. :-1 |
|
Oct 18 |
comment |
Tmux eclipsed colorized output of ls Did you mean --color=always? My ls didn't recognizes -2. |
|
Oct 18 |
answered | Tmux eclipsed colorized output of ls |
|
Oct 12 |
revised |
Function caller positional parameters added 162 characters in body |
|
Oct 12 |
comment |
Function caller positional parameters Read and write the parent $@. I'm writing a wrapper around getopt for aesthetic purposes. |
|
Oct 12 |
comment |
Function caller positional parameters And if I need to rewrite it? |
