2023-11-14T05:56:28 *** teepee_ is now known as teepee 2023-11-14T10:57:11 download.o.o moving now 2023-11-14T11:01:30 ^-^ 2023-11-14T13:20:56 download.opensuse.org should be back. please report any issues, you see, here. 2023-11-14T13:35:53 acidsys and darix users have reported verification emails arriving... 2023-11-14T13:46:51 neat 2023-11-14T14:59:29 *** teepee_ is now known as teepee 2023-11-14T17:07:10 went through all the vm's which had failing repositories .. lots of unmanaged urls, duplicate .repo files, pointing to non-existing directories .. ugh. now all refresh cleanly 2023-11-14T18:08:23 finally mastered color in the terminal and plain text in the file at the same time .. `unbuffer salt \* test.ping | pee tee 'ansifilter | tee /dev/shm/out >/dev/null'` 2023-11-14T19:38:44 acidsys: for SR 1126449 - wouldn't changing the parameters to goodout.sh make things much easier? 2023-11-14T19:39:02 Instead of the parameter magic, you could just save $1 and then shift 2023-11-14T19:40:16 hi cboltz_ 2023-11-14T19:40:28 I agree it would make the script much simpler 2023-11-14T19:41:12 my rationale was that I potentially want to run the same command with different file names repeatedly though, making it easier not having to modify an argument at the beginning of a long line 2023-11-14T19:41:50 is that harder than modifying the end of the line? ;-) 2023-11-14T19:41:57 QQ: does the shift thing work in sh ? 2023-11-14T19:42:19 yes it is because you need to jump around with arrow keys 2023-11-14T19:43:02 arrow up -> pos1 -> ctrl + right arrow -> vs arrow up -> 2023-11-14T19:43:37 hehe, probably depends on your bash config - with set -o vi I type esc k w and have the cursor at the beginning of the first parameter 2023-11-14T19:44:08 o_o 2023-11-14T19:44:16 https://tldp.org/LDP/Bash-Beginners-Guide/html/sect_09_07.html says The shift command is one of the Bourne shell built-ins that comes with Bash. so I'd say it should be sh-compatible 2023-11-14T19:44:51 cool because that would be an argument I can live with :] the pound foo would run in sh but return empty 2023-11-14T19:51:57 tbh sh compat only matters if your shebang line is /bin/sh 2023-11-14T19:52:04 if you do /bin/bash ... go wild 2023-11-14T19:52:18 or even better ... use ruby or python instead of /bin/*sh 2023-11-14T19:53:18 the whole point is being able to make the shebang /bin/sh 2023-11-14T19:53:28 why? 2023-11-14T19:53:31 what do you gain from it? 2023-11-14T19:53:42 running without bash 2023-11-14T19:54:45 bash-derived sh is still a bit cheating though. i like testing against dash 2023-11-14T19:55:18 you can go busybox-sh if you want to go hardcore :p 2023-11-14T19:57:48 yes, my minimal busybox containers use it 2023-11-14T19:58:31 if something does not _need_ some bash functionality I like making it compatible with systems which do not have bash 2023-11-14T19:58:57 if on the other hand a script is very big and complex and will only ever be run on a normal openSUSE, well then I also don't have a problem going bash+ 2023-11-14T19:59:03 me too. i change the she bang line to #/usr/bin/ruby ... then i can launch the script from every shell ;) 2023-11-14T19:59:22 _runs_ 2023-11-14T19:59:32 * acidsys removes darix' ruby interpreter 2023-11-14T19:59:50 ruby ruby rubyyyy! 2023-11-14T20:00:06 i think you will have more pain from me removing /bin/sh than from you removing /usr/bin/ruby ;D 2023-11-14T20:00:44 well you are the one who just stated you just change all your shebangs to /usr/bin/ruby ^^ 2023-11-14T20:01:09 well ... sure ... but you have to see it holistically :D 2023-11-14T20:01:28 your system will break much more with /bin/sh removed compared to /usr/bin/ruby 2023-11-14T20:01:31 good luck fixing that! 2023-11-14T20:01:57 had do to that once ... where a coadmin called rm -r * in the wrong dir ...