310 reputation
315
bio website
location
age
visits member for 2 years
seen 1 hour ago

Shyy erny anzr - Naqernf Rvonpu


Sep
1
comment wget: Retrieving a list of URLs when modifying input data file on the fly
@garethTheRed You're a marvel. Doing them in this order works. Thank you very much. But thanks as well to Mark for the alternate solution, which works if you use wget -nc -i <(cut -f1 -d' ' inp). No dollars here. :)
Sep
1
revised wget: Retrieving a list of URLs when modifying input data file on the fly
corrected title. It's URLs that's in that ascii data file, which wget reads.
Sep
1
asked wget: Retrieving a list of URLs when modifying input data file on the fly
Sep
1
awarded  Quorum
Aug
31
revised find: Why is the -a operator not commutative in combination with -print?
Oops, asterisks (\*) need to be quoted when they're not meant to be used as markup, but literally.
Aug
30
revised find: Why is the -a operator not commutative in combination with -print?
cleaned up headline/title
Aug
30
comment Use find to find certain directory and delete all files in it except one directory
Yes I agree it IS better than the great part of the other Bash PF articles. (I never link you to any pointless crap, mind you :)) And thanks for the link.
Aug
30
comment Use find to find certain directory and delete all files in it except one directory
Well, you're the first to complain about me linking it. Seriously. Though not all "tips" might be the creme de la creme, there are lots of neat tricks in there that have helped me many times. Still, I'm no "gregwoo fanboi" - but I wouldn't go as far as daring accuse him of "ignorance" either.
Aug
30
comment Use find to find certain directory and delete all files in it except one directory
Well it was supposed to mean that the first subshell doesn't know anything of the second, if there are two. And so things might give different results as you would expect because both subshells are independent of each other. But you might expect parameters to be "known" to both. (Heck, you even used export, so why doesn't that work?) However, you debug variables and get zero length and other nonsense. YMMV...but since I've avoided cd in scripts and specified paths directly instead, my scripts are less prone to errors. mywiki.wooledge.org/BashPitfalls#cd_.2Ffoo.3B_bar
Aug
30
comment find: Why is the -a operator not commutative in combination with -print?
Looks excellent now in my opinion. Thanks for your agreement on improvement. As you have seen, this stuff is way trickier than it looks at first.-- Lastly, this has now turned a great solution for alias as well. Remember, alias needs the argument at the EOL, and the -print was in the way all the time. Thanks to your marvellous "dummy option" -a -name ., this is now feasible. Fantastic! Thank you.
Aug
30
comment find: Why is the -a operator not commutative in combination with -print?
Well, that's not quite the same. Try it out. "./exclude_me" does get listed once you omit the -print at the end of the line. But I want it both excluded and not even listed at all. Not until you add the explicit -print, however, "exclude_me" will actually be left out of the listing. Trust me, I can try here "live" and I know what I'm talking about :)
Aug
30
comment Use find to find certain directory and delete all files in it except one directory
Well, I think the downvote is fully justified in this case. It always makes my toenails roll up whenever I see cd in a shell script. This will cause nothing but trouble. Think of shell sessions, subshells, subshell A not knowing anything of subshell B and their parameters and vice versa---and so on. Avoid.
Aug
30
revised find: Why is the -a operator not commutative in combination with -print?
fixed typo
Aug
30
asked find: Why is the -a operator not commutative in combination with -print?
Aug
29
comment Why do we use double hyphen in “tar --anchored” and single hyphen in “tar -b”?
@Zeke Ugh! Don't you remind me of that.
Aug
29
comment Why do we use double hyphen in “tar --anchored” and single hyphen in “tar -b”?
I guess it's pretty simple. tar (= "tape archiver", think of QIC-80 and friends) is a VERY old command from the beginnings of UNIX, and in the old days, there were only those said -X options. I've scoured the man page, and I can't remember any tar option being available from the old days that took 2 dashes. Hence, there is a rule of thumb that all of the latter ones are commands which were added much later during recent years.
Aug
25
comment How to set conkys window width?
Yes, but it will only work every second time when .conkyrc is edited with gedit, as I've found out. So you edit it, save the file - nothing happens. You edit it again (a pseudo-edit might do)...and all of a sudden, conky will detect the config file change and restart automatically.
Aug
25
comment conky: proper column alignment
conky -D might come in handy as well perhaps (will put conky into debug mode, letting you peek way more deeply into its inner workings, and maybe giving you a clue what your build of conky is "allergic" against)
Aug
24
comment diskio/diskiograph in Conky only understands physical device names?
And again you're right!! Once I omit the parameters, I get ugly colors and wrong height, but yes it works! However, I can't accept this. I ought to file a bug report that the parameters will actually "kill" the graph when no physical device name is given.
Aug
24
comment diskio/diskiograph in Conky only understands physical device names?
Well, my whole line is ${diskiograph /dev/disk/by-uuid/1234567890ABCDEF 15, 130 828282 7f8ed3 0.1 -l}. Since there are a decent lot of parameters following the UUID, it's only natural that there is a space after it. :) diskio is not diskiograph; the former does not take any parameters.