[00:29] <guiverc> debian soft-waves :)
[00:44] <lubot> <HMollerCl> @wxl[m] [<wxl[m]> @tsimonq2 I just thought maybe you might have some insight. Adding an a …], I'm more convinced that we should drop nm-tray in favor of nm-applet
[01:12] <wxl[m]> I know why you feel that way and I'm sure you know why we'd like to not!
[01:38] <lubot> <HMollerCl> Jajajja
[04:54] -lugito:#lubuntu-devel- [rLXQTMETAPACKAGESARCHIVE8d03dc04a1f4: DSC file for 29] Diffusion committed: https://phab.lubuntu.me/rLXQTMETAPACKAGESARCHIVE8d03dc04a1f4
[04:54] -lugito:#lubuntu-devel- [rLXQTMETAPACKAGESARCHIVE5f85568b3047: Import patches-unapplied version 29 to debian/sid] agaida (Alf Gaida) committed: https://phab.lubuntu.me/rLXQTMETAPACKAGESARCHIVE5f85568b3047
[04:54] -lugito:#lubuntu-devel- [rLXQTMETAPACKAGESARCHIVEa007f7ad9426: Import patches-applied version 29 to applied/debian/sid] agaida (Alf Gaida) committed: https://phab.lubuntu.me/rLXQTMETAPACKAGESARCHIVEa007f7ad9426
[05:41] -lugito:#lubuntu-devel- [rLXQTMETAPACKAGESARCHIVE2e166303c165: DSC file for 29] Diffusion committed: https://phab.lubuntu.me/rLXQTMETAPACKAGESARCHIVE2e166303c165
[08:35] <lubot> <The_LoudSpeaker> @HMollerCl [I'm more convinced that we should drop nm-tray in favor of nm-applet], Why?
[11:22] <lubot> <HMollerCl> @The_LoudSpeaker [Why?], Mainly because nm-tray has to basic configuration options. But is full Qt and consumes less resources than cmst
[21:45] <lubot> <tsimonq2> Fwd from Lubuntu Announcements: We have reached 5,000 followers on Twitter! Thank you! ... You can follow us here: https://twitter.com/LubuntuOfficial ... https://twitter.com/LubuntuOfficial/status/1097612456522891264
[22:53] <lubot> <HMollerCl> It seems to me that bash is less resource intensive than python. Giving that, it's better to develop in bash that python? Any contrary argument?
[22:53] <lubot> <HMollerCl> (Obviously I'm talking about basic scripts)
[22:53] <wxl> i think it's a question of what you want to do
[22:54] <wxl> there certainly are limitations to what you can do with python
[22:54] <wxl> s/python/bash/
[22:54] <wxl> and python is waaaaay more readable 
[22:54] <wxl> that said, i have found bash to be generally the better solution
[22:55] <wxl> btw if you're putting something in the repos, it's really best to make sure you're portable
[22:56] <lubot> <HMollerCl> That I'm portable?
[22:56] <wxl> in other words, don't use bash, but /bin/sh
[22:56] <wxl> make it POSIX-compliant
[22:56] <wxl> unfortunately that will mean more limitations
[22:56] <wxl> a lot of "bashisms" will be missing
[22:57] <lubot> <HMollerCl> Ok
[22:57] <lubot> <HMollerCl> But is really simple what I want to do
[22:57] <wxl> ooh this is nice http://sites.harvard.edu/%7Elib113/reference/unix/portable_scripting.html
[22:58] <lubot> <HMollerCl> The interpreter of python consumes more than 5meg
[23:01] <wxl> bashisms include: [[, ((, { (including ${ and string handling), function (!), let, local, select, source, <<< (here strings), &>, string comparison with == in test
[23:02] <lubot> <HMollerCl> what I want to do is to run this script and parse teh output ... /usr/lib/update-notifier/apt-check
[23:02] <lubot> <HMollerCl> which are two number separated by ;
[23:03] <lubot> <HMollerCl> should be prety easy with bash.