352 reputation
512
bio website
location
age
visits member for 2 years, 7 months
seen Aug 1 at 12:10

Apr
10
answered hunspell: add word to dictionary from command line
Apr
10
revised hunspell: add word to dictionary from command line
added 105 characters in body
Apr
10
asked hunspell: add word to dictionary from command line
Apr
1
comment Creating recursively sorted RAR archive
Thanks Eli for your answer, but unfortunately none of provided examples stores file sorted here. I'm also on Ubuntu. find * | sort lists files sorted but find * | sort | xargs rar ... stores files in unsorted order for some reason. I tried also -n@ (with additional sort command) which works fine as in your snippets, but again it does not store sorted files. I could provide screenshot from terminal if anyone requests it. So for me, snippet that works is the last update to my question: for d in */ ; do rar a -r archive.rar $d*.txt ; done which loops over folders and is acceptable to me
Mar
31
comment Creating recursively sorted RAR archive
Yeah, I started with gzipped tar and then wanted to update archive... rest is history, w/o even mentioning all handy rar options
Mar
31
revised Creating recursively sorted RAR archive
update
Mar
31
comment Creating recursively sorted RAR archive
Yes, I do, as I pipe uncompressed output to stdout with rar p. BTW unrar -v switch you mention, does not do anything here - did you test it?
Mar
30
asked Creating recursively sorted RAR archive
Mar
24
accepted diff - output line-numbers
Mar
24
comment diff - output line-numbers
Just great! Thanks :) I tried to guess from help listing, but w/o success, and thought I misread it. Then I made what I wanted with Python (difflib module with indexed files per line in list object) only that I couldn't use diff <(pipe buffer1) <(pipe buffer2) with Python, like I planed with diff. Now you saved me :)
Mar
23
asked diff - output line-numbers
Mar
3
comment make grep output without trailing newline
ah tr... interesting, works both on LF and CRLF files. I would think \010\013 for some reason, and also \f\r works correctly. About the result: I don't actually put the output in variable but as variable enclosed in $() in pattern for grep match - some pipe | grep -o " $(...) ". Thanks for comments
Mar
3
accepted make grep output without trailing newline
Mar
3
comment make grep output without trailing newline
Thanks Chris for your effort and correct answer. I still haven't got to awk, as to know the syntax, what I should, should not... but your explanation makes it simple in this case. Cheers
Mar
3
comment make grep output without trailing newline
OK, this time it does it good - output last word in a line if that line satisfies some pattern condition - don't know, maybe it's clear to me because I have this problem, and then hard to explain as non-native english speaker. Anyhow, I'll wait a bit more if someone addresses this with grep/sed solution instead awk (which I don't understand), and if not I'll use it. Thanks
Mar
3
awarded  Commentator
Mar
3
comment make grep output without trailing newline
:) Now it doesn't look elegant any more and it is still no good
Mar
3
comment make grep output without trailing newline
Thanks, it looks elegant but unfortunately CRLF is still inside X
Mar
3
asked make grep output without trailing newline
Mar
1
accepted Check if filename exist from inline command