[05:49] <flocculant> :)
[05:57] <flocculant> bluesabre: I'll check it out this evening - much too morningish right now 
[11:37] <knome> flocculant, will we be pushing this out after the fixed ISOs?
[11:38] <knome> flocculant, poked the article a bit
[12:08] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 17.10 - i386 - i386 built.
[12:11] <Unit193> ↑ Lies.
[12:30] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 17.10 - i386 - i386 built.
[12:35] <Unit193> Accurate.
[12:45] <Unit193> ↑ Lies ↓
[12:51] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 17.10 - amd64 - amd64 built.
[13:16] <bluesabre> flocculant: http://bazaar.launchpad.net/~menulibre-dev/menulibre/master/revision/457 :}
[17:53] <flocculant> knome: was my intention to do so - don't want to push people to 17.10 if the page still has the warning on it
[17:53] <flocculant> bluesabre: :)
[18:19] <flocculant> knome: also I guess if EOL slips a bit - then it's just us affected anyway
[18:54] <knome> flocculant, yes, i guessed that and changed the wording to be more assuring for people
[18:55] <knome> and i agree on the EOL slipping... it's not a huge thing
[19:12] <flocculant> knome: read the poking - thanks
[19:13] <flocculant> if I see artful is released before work in the morning - I'll publish, if not - either someone else can check and publish, or I'll look later
[19:15] <knome> sure, thanks
[19:36] <bluesabre> flocculant: hopefully there are no more bugs for you to find, the completed list is getting long https://launchpad.net/menulibre/+milestone/2.1.4 :)
[19:36] <Unit193> So I looked and the new isos actually enable -updates globally, not just to pull in kernels.
[19:37] <bluesabre> Unit193: Seems that is an unwanted thing?
[19:39] <Unit193> No?  I did the mistake of presuming minimal change, so did that with Core. :P
[19:47] <flocculant> bluesabre: will look in a bit at 'it' in the meantime does "  preventing subdirectories from leaving parent directories" mean that you can't make a sub-dir in an existing and then move it out? Given you said you have to  make a new dir in an existing one?
[19:51] <flocculant> ok - I'm completely confused by how this is supposed to work :(
[19:52] <flocculant> sigh
[19:54] <flocculant> made a dir - made a launcher in an exsting dir cos it wouldn't create in the new one, moved the launcher into the new dir, deleted the new dir, the launcher went to end of the list - and I can't stop it telling me https://i.imgur.com/MxHai4L.png without killing menulibre
[19:55] <flocculant> bluesabre: don't mean to be nitpicky here - but is there a simple way to make a new dir and launchers and then show it in the menu?
[19:57] <flocculant> bluesabre: you might want to look here https://bluesabre.org/doku/doku.php?id=menulibre-docs
[19:58] <flocculant> our docs link to smdavis - I assume you've a redirect
[19:58] <knome> i think our website links to smdavis too
[20:02] <flocculant> are not they they same thing?
[20:03] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 17.10 - i386 - i386 built.
[20:03] <knome> https://xubuntu.org/press/
[20:03] <knome> is that docs?
[20:04] <knome> :)
[20:04] <knome> bbl
[20:05] <flocculant> oh right - that redirects ok
[20:23] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 17.10 - amd64 - amd64 built.
[21:34] <bluesabre> flocculant: flocculant ah, that link should be https://wiki.bluesabre.org/doku.php?id=menulibre-docs
[21:35] <bluesabre> flocculant: normally you create the new dir, click save, then add launcher, and it goes into the folder... and now I see that it just goes away
[21:36] <bluesabre> man, everything is breaking
[21:37] <bluesabre> flocculant: seems it's broken when doing that at the toplevel, if you create a subdir in a dir and add a launcher, things work
[21:40] <Unit193> Ala http://paste.openstack.org/show/OrAsu9NwXdyIzR8JrpOx then.
[22:32] <ochosi> bluesabre, knome: so regarding gtk-theme-config: there are a few rough edges to take off but what i can already say is that we'll need some ifs to support greybird *and* adwaita
[22:32] <ochosi> and i'm not sure how well this will work for all other themes
[22:33] <ochosi> the "problem" is that gtk3 theming has opened so many doors, made things so flexible, it's very hard to properly override the selected_bg_color correctly
[22:34] <ochosi> so here's what i think is feasible:
[22:34] <ochosi> a limited gtk-theme-config that works for greybird and adwaita, with limited functionality, so mostly changing the selected_bg_color and selected_fg_color (although the latter can be problematic, but we can try)
[22:35] <ochosi> changing the panel color is also possible, but i'm not sure it's very meaningful as you can already change that through the panel anyway
[22:35] <ochosi> and the menus, well, that's possible too, but tbh that part is fairly useless imho
[22:36] <ochosi> if you all feel that it's terribly important we can try to get it done, but from my pov it would be the last step
[22:37] <ochosi> i still need to clean up the code quite a bit more
[22:39] <ochosi> but if anyone wants to test this i can push the crude prototype somewhere
[22:40] <ochosi> oh, and as i mentioned before, we gain a dependency to sassc
[22:40] <ochosi> but i may be able to get rid of that, not sure yet
[22:41] <ochosi> it's not my top priority atm
[23:23] <Unit193> I pressed buttons and stuff on the docs.
[23:35] <bluesabre> thanks Unit193 
[23:35] <bluesabre> flocculant: fixed that bug
[23:35] <bluesabre> ochosi: soooo, do you want to do this or drop gtk-theme-config?
[23:36] <Unit193> Unfortunatly, as much as the idea of it is nice, I think option 2 makes more sense.
[23:57] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [bionic] r644 Update Sean's website location for menulibre and mugshot. (by Unit 193)