320 reputation
316
bio website
location
age
visits member for 2 years, 1 month
seen 11 hours ago

Shyy erny anzr - Naqernf Rvonpu


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.
Aug
24
comment diskio/diskiograph in Conky only understands physical device names?
Proposal dismissed! This isn't chit-chat. I was even rather frowning upon getting this "chit chat warning" by SE. It's IMHO uncalled-for, and I felt treated like an immature teen.---Back to conky: Unfortunately this only works for diskio+label symlinks, but not with diskiograph. That is, when used with the latter, it will not complain about path not found, but it won't display anything either in the graph. Doing the same with the physical path did work instantly, though.
Aug
24
comment diskio/diskiograph in Conky only understands physical device names?
You're a marvel, thank you so much! So I will need to replace conky by conky-ng (a fork, see github.com/Tucos/conky-ng). I just don't understand why this hasn't been implemented yet in the "standard" conky. It's such an essential feature to have in udev times.
Aug
24
revised diskio/diskiograph in Conky only understands physical device names?
formatting fixed + improved
Aug
24
comment diskio/diskiograph in Conky only understands physical device names?
Thanks for bearing with me...I think the problem is that in my case, /dev/sdc6 is in fact a NTFS formatted partition, let's call it /dev/disk/by-label/videos for example, which on ls -l points to --> ../../sdc6. This is assigned to /media/videos, which, of course, isn't accepted either by conky. My (shortened) version line is Conky 1.9.0 compiled 2014-02-19 for Linux 3.2.0-54-generic (i686). I can't seem to believe that I really need to upgrade to 1.9.1 to get this working.
Aug
23
asked diskio/diskiograph in Conky only understands physical device names?
Aug
20
awarded  Nice Question
Aug
15
awarded  Notable Question
Aug
10
revised Xresources color settings
added 60 characters in body
Aug
10
answered Xresources color settings