[02:52] <thomi> bschaefer: ping?
[02:52] <bschaefer> thomi, pong
[02:53] <thomi> bschaefer: remember how my ibus tests were failing? Do you think I can reset the ibus stuff by removing ~/.config/ibus?
[02:54] <bschaefer> thomi, im not actually sure. It could also be something the ibus-anthy is store else where
[02:55] <bschaefer> let me look up if there is an easy way to reset ibus-anthy
[02:55] <thomi> bschaefer: thanks. Also, I'm collecting a large number of unity branches... trying to keep them all small and ewasy to review. If you get a chance to look at them that'd be great.
[02:56] <bschaefer> cool, do you have some links?
[02:57] <bschaefer> also had a random question about memory leaks. If you have a dynamically allocated gchar* and shove it into a glib::String(), would that be a mem leak?
[02:57] <bschaefer> as the deconstructor shouldn't delete the gchar* since it's a primitive type
[03:00] <bschaefer> if you never delete the gchar* you shove into the glib::String thinking the glib::String handles it...
[03:01] <bschaefer> thumper, you might know ^ (if your not busy!)
[03:02] <thumper> hi bschaefer
[03:02] <thumper> I'm not really here
[03:02] <thumper> if you have a gchar* that you don't have ownership of, it should not be in a glib::String
[03:02] <thumper> glib::String are particularly for gchar* objects created by glib
[03:03] <thumper> not new, not malloc
[03:03] <thumper> as it does a g_str_free (or whatever it is)
[03:03] <bschaefer> ok, because the bamf_view_get_name returns a g_strdup
[03:03] <thumper> ok, that should go in glib::String
[03:03] <thumper> g_strdup returns a new string
[03:03] <thumper> which the caller needs to free
[03:03] <bschaefer> and it is put into a glib::String, and valgrind complains of a mem leak
[03:04] <thumper> that won't be it then...
[03:04] <bschaefer> shoot
[03:04] <thumper> you have to be careful
[03:05] <thumper> you need to make sure that the destructor for glib::string is called before the valgrind atexit handler kicks in
[03:05] <thumper> otherwise it is a "possibly lost"
[03:05] <bschaefer> yeah, I think it's not a real leak
[03:05] <thumper> I feel like I'm going to regret this
[03:05] <thumper> but where is it?
[03:05] <bschaefer> 0x8E433B0: unity::launcher::BamfLauncherIcon::BamfLauncherIcon(_BamfApplication*) (BamfLauncherIcon.cpp:60)
[03:06] <bschaefer> thomi, im getting ibus-anthy source code atm. It usually has a configure thing in there...let me check
[03:06] <thumper> pastebin the entire loss record?
[03:07] <bschaefer> alright
[03:10] <thumper> thomi: set a commit message and land this plz https://code.launchpad.net/~thomir/unity/autopilot-attribute-feature/+merge/101823
[03:10] <bschaefer> ugg its all in xml one sec I have to find it
[03:10] <thomi> thumper: trunk is unfrozen? or do I need UNBLOCK?
[03:11] <thumper> thomi: I think you are fine
[03:11] <thumper> thomi: I didn't realise you could use a generator expression for making a dict
[03:11] <thomi> ok, done. Let's see how it goes.
[03:11] <thumper> thomi: I would have used dict([key, value for ...])
[03:11] <thomi> thumper: huh?
[03:11] <thomi> oh
[03:11] <thumper> return {k.replace('-','_'):v for k,v in state_dict.iteritems() }
[03:11] <thomi> heh, I never thought to do it that way :)
[03:12] <thumper> does that really work?
[03:12] <thumper> yep, I guess it does
[03:14] <thomi> *sigh* - I just realised that lp-propose has helpfully put me as the reviewer on all my merge proposals :-/
[03:14] <bschaefer> thumper, http://paste.ubuntu.com/933472/
[03:16] <bschaefer> I had been looking at this other mem leak for a couple hours...that one was a definite loss dealing with a map...but ran out of ideas :(
[03:16] <thumper> thomi: https://code.launchpad.net/~thomir/unity/wait_for-to-use-testtools-exception/+merge/102198 needs fixing
[03:17] <thumper> bschaefer: ok, this loss record is around valgrind thinking that the icon itself wasn't cleaned up
[03:17] <thumper> bschaefer: as it is a std::string member variable it is complaining about
[03:18] <thomi> thumper: that's a good idea (checking for the match attribute).
[03:18]  * thumper wanders off again...
[03:18] <bschaefer> ooo ok, so it thinks it isn't cleaned up because the deconstructor for that string hasn't been called yet, but it will soon
[03:18] <bschaefer> thanks!
[03:19] <bschaefer> (I've wasted to long on those kind of false positives haha)
[03:20] <bschaefer> thomi, hmm im looking at the setup.py for ibus-anthy and Im not sure if I see a reset.
[03:20] <bschaefer> ill look some more!
[03:23] <thomi> bschaefer: ok, don't worry about it too much... I can survive without. It'd be nice to make these anthy test a bit more solid though
[03:23] <bschaefer> thomi, I just have to figure out what language you switch to when you hit space
[03:24] <bschaefer> then I can google better haha
[03:24] <bschaefer> thomi, you could trying re-installing ibus-anthy haha
=== jo-erlend_ is now known as jo-erlend
[03:34] <bschaefer> thomi, sweet figured it out!
[03:34] <thomi> cool
[03:34] <bschaefer> thomi, go to ~/.anthy
[03:34] <thomi> what's the secret sauce?
[03:35] <bschaefer> and remove last-record
[03:35] <bschaefer> last-record*
[03:35] <thomi> sweet
[03:35] <bschaefer> yup :), I knew it had to be somewhere haha
[03:35] <thomi> thanks for your help!
[03:35] <bschaefer> idk why they just don't have a reset button haha. No problem!
[03:36] <bschaefer> I guess most people who use that program understand Japaneses
[04:54] <thomi> bschaefer: still around?
[04:54] <bschaefer> thomi, yup
[04:55] <thomi> I made the ibus tests more awesomeer: https://code.launchpad.net/~thomir/unity/ibus-test-to-wait_for-feature/+merge/102236
[04:55] <bschaefer> need a review of that ibus branch?
[04:55] <bschaefer> just saw haha :)
[04:56] <thomi> :)
[04:56] <thomi> less code is always a good thing.
[04:57] <bschaefer> thomi, AWESOME! haha, let me grab the branch and make sure all the ap test pass :)
[04:59] <bschaefer> i mean ibus only test
[04:59] <bschaefer> not all haha
[05:01] <bschaefer> thomi, forgot my schoosl wireless is crap, so I had to hop on there wired connection, running the ap test now
[05:01] <bschaefer> code wise, it looks really good :)
[05:07] <bschaefer> thomi, hmm would you know why during the anthy ap test for the hud it press down a couple times?
[05:07] <thomi> bschaefer: nope, does it cause the test to fail?
[05:07] <thomi> I hadn't noticed
[05:07] <bschaefer> one of them, and it caused your problem
[05:08] <bschaefer> with anthy, it pressed 2 down during the 'system' test changing my preferences
[05:08] <bschaefer> also it seems to run the same string test multiple times in anthy only
[05:08] <bschaefer> it tries 'system' then 'system' back to back when I run it :(
[05:12] <bschaefer> thomi, nevermind about the back to back
[05:12] <bschaefer> it is because the anthy has 2 commit keys haha
[05:12] <bschaefer> ugg im starting to get tired
[05:12] <bschaefer> your branch looks good approved :)
[05:13] <thomi> thanks
[05:13] <thomi> working on fixing the launcher tests now :-/
[05:13] <bschaefer> o, there are a lot in there...
[05:14] <bschaefer> Im hoping to actually fix a memory leak sometime soon haha.
[08:51] <trijntje> Hi all, I noticed that the files-lens ignores files on separate mountpionts by default. Is there a way to whitelist certain mountpoints?
[08:51] <davidcalle> trijntje, I don't think there is. mhr3? ^
[08:53] <mhr3> trijntje, there is - /etc/updatedb.conf
[08:54] <mhr3> but i'd be careful, there are reasons those are disabled
[08:59] <trijntje> mhr3: what should I be careful about? I only want to allow some partitions I mount by default
[09:09] <apw> didrocks, i have that stacking issue again, i am starting to feel it occurs when you do an update which brings unity but you have not yet logged out to start using the new one, would that make _any_ sense ?
[09:09] <didrocks> apw: I can't say it make sense to me at least, as the old .so file is still used
[09:09] <didrocks> apw: I think it's maybe just a coincidence
[09:10] <didrocks> apw: sam is you man for that, definitively
[09:10] <apw> didrocks, no i don't think it does, but i've had it twice recently and both times when i was updating i am pretty sure
[09:10]  * apw is also reminded that -proposed is kept enabled by default ...
[09:12] <didrocks> oh, -proposed is enabled by default?
[09:19] <Cimi> didrocks, I don't think it is
[09:19] <Cimi> didrocks, I had to enable proposed to test new unity
[09:19] <Cimi> didrocks, I installed in 11.10
[09:19] <didrocks> ok
[10:14] <blueyed> Is it possible to exclude windows (e.g by app name) from being collapsed in the alt-tab switcher? (like gnome-terminal) I would rather have 4 separate entries in the first place.
[10:44] <ochosi> hi everyone, i have a question: what does a gtk-theme need to show up in unity's theme selector? (mine doesn't show up)
[11:07] <Cimi> ochosi, I guess it should be in /usr/share/themes
[11:08] <seb128> ochosi, Cimi: what do you call "unity's theme selector"?
[11:09] <Cimi> seb128, I guess he is referring to the appearance applet
[11:09] <seb128> Cimi, right, well that has an hardcoded list of supported themes, that doesn't pick any theme installed
[11:09] <seb128> i.e it's only the light themes, the a11y themes and the GNOME one when installed
[11:09] <Cimi> good then
=== MacSlow is now known as MacSlow|lunch
[11:24] <ochosi> Cimi: that's where it is. i guess i was wondering whether the theme itself needed anything special it doesn't need for other desktops
[11:24] <ochosi> seb128: hardcoded theme-list? so how can unity-users install/use new themes from the e.g. the interwebs then?
[11:25] <Cimi> ochosi, they need to use external tools
[11:26] <ochosi> Cimi: right. i wasn't aware of that. is that a design decision?
[11:26] <seb128> ochosi, dunno, gnome-tweaks, ubuntu-tweaks
[11:26] <Cimi> ochosi, gnome 3 one
[11:26] <seb128> ochosi, it's just a non supported feature, GNOME has no theme selector, we add one to allow changing between the 2 light themes variants
[11:26] <seb128> then we added the a11y themes as well and the GNOME one for gnome-shell users
[11:27] <seb128> ochosi, I guess it could be improved to pick any installed theme, it's just no a priority on the list of things to fix,work on
[11:27] <ochosi> i see
[11:27] <seb128> if you want to work on it patches are welcome I guess
[11:27] <ochosi> i've been the artwork-lead of xubuntu for a few releases now and i thought it'd be nice if our default theme supports unity as well
[11:27] <ochosi> (that's the background)
[11:28] <ochosi> sry, not too much of a coder
[11:28] <seb128> no technical reason to not do it
[11:28] <ochosi> you mean support unity? yeah, that was easy enough basing it off ambiance's unity.css
[11:29] <ochosi> the technical reason not to would be that users can't (easily) switch to the theme anyway :)
[11:29] <seb128> well they can with gnome-tweak, ubuntu-tweak, etc
[11:29] <ochosi> sure
[11:30] <ochosi> i'm just used to easily change themes in xfce and iirc in gnome2 it was also straight-forward
[11:30] <seb128> but yeah, that's something we can look at fixing next cycle, as said it started small just to be able to select which light theme variant to use
[11:30] <ochosi> mhm
[11:30] <seb128> GNOME decided that the themes is part of the desktop design and not something to tweak I think
[11:31] <seb128> i.e it's part of the shell visual identify
[11:31] <seb128> that's why they dropped the option
[11:31] <ochosi> that's a strange decision from my point of view, but anyway, it's a gnome-decision i guess
[11:31] <seb128> yes
[11:31] <zgreg> I hope they add some more configuration options
[11:31] <zgreg> for example for font size
[11:31] <seb128> it's there
[11:31] <zgreg> the accessibility settings are useless
[11:31] <ochosi> yeah, not being able to change themes feels like pre-windowsxp
[11:31] <seb128> in the accessibility panel
[11:32] <zgreg> they are the coarse...
[11:32] <zgreg> err, too coarse
[11:32] <seb128> I guess you could argue with them to get a slider with extra granularity
[11:32] <zgreg> what do you want, reasonable font size, miniscule fonts, or huge fonts? :D
[11:32] <zgreg> there's nothing inbetween
[11:35] <ochosi> seb128: anyway, thanks for the update. i guess i'll try to push the unity-support to -proposed and publish a quick howto on planet.ubuntu
[11:35] <seb128> ochosi, you're welcome
[12:02] <rye> hm, selecting Radiance makes the panel menu text glyphs looks blurred at the right edge.
[12:03] <rye> but when you invoke the menu, label redraws and becomes correct
=== greyback is now known as greyback|lunch
[12:13] <rye> could somebody from Unity team switch to Radiance - this is what I see - http://ubuntuone.com/4eMA9RedmLP8lsYHVozV1z
[12:13] <rye> It's even worse with the bold typeface of window titles
[12:14] <zgreg> ugh, looks like subpixel rendering is broken with that theme, for some reason
=== MacSlow|lunch is now known as MacSlow
[12:15] <rye> as if by default text is using a different subpixel rendering type setting
=== _salem is now known as salem_
[12:37] <rye> bug #983923  but it is weird
[12:37] <ubot5> Launchpad bug 983923 in light-themes (Ubuntu) "Subpixel rendering type of Radiance panel menus is wrong" [Undecided,New] https://launchpad.net/bugs/983923
[12:49] <rye> am I correct that unity panel is gtk3?
[12:53] <seb128> rye, yes
[13:02] <rye> eh, i guess I cannot find any way I can influence the Radiance theme atm, bug filed, back to U1 stuff
=== greyback|lunch is now known as greyback
[13:27] <malin> davidcalle: I have made some of the files needed for packing my lens
[13:28] <malin> I can push it to launchpad and I need help with some few things. What I am missing filling in in the different files and so on :)
[13:28] <davidcalle> malin, ok. I have a meeting in ten minutes, but I will give it a look later in the afternoon.
[13:30] <malin> thank you davidcalle  :)
[13:31] <malin> hm. I did something wrong. There is just one file in the project :S
[13:33] <malin> well, fixed: here is the latest revision: http://bazaar.launchpad.net/~malinkb/unity-buss/unity-buss-experimental/files
[15:46] <davidcalle> malin, ping
[15:47] <malin> davidcalle: ping ping :)
[15:47] <malin> or ping pong. here I am :)
[15:47] <davidcalle> malin, I've pushed a branch on your project
[15:48] <malin> ah :)
[15:48] <davidcalle> malin, with the packaging fixes
[15:48] <malin> thanx
[15:48] <davidcalle> malin, I've made a merge proposal, you have to review it and accept it :)
[15:49] <malin> okey :)
[15:49] <davidcalle> malin, then, you will almost be able to build it automatically in your PPA :)
[15:49] <davidcalle> There is a last tiny step to do this.
[15:51] <malin> oki :) I would like to have an explonation in detail on how to do this, so I can do it my self next time :) Maybe there is a tutorial :)
[15:52] <malin> but I am so thankfull that you are spending your time helping me with this :)
[15:54] <davidcalle> malin, I'm pretty sure there is a comprehensive packaging tutorial somewhere. I'll ping you if I find one.
[15:56] <davidcalle> malin, the last step will be to create a recipe for your package on Launchpad. It's just a form to fill when you click "create packaging recipe" on your branch page.
[15:58] <malin> thanx davidcalle :) So what does the packagin recipe need to contain?
[16:00] <davidcalle> malin, a name for your recipe (whatever you want), the PPA, the version of Ubuntu you want to build for and the recipe text (maybe I'm wrong, but it should be already filled by Launchpad, if no, it's just http://paste.ubuntu.com/934153/ )
[16:03] <malin> okey :)
[16:04] <malin> hm.. I set it to approve, but I cannot se it is merged yet
[16:07] <davidcalle> malin, you have to merge it manually, read my comment on the merge page :)
[16:08] <malin> ok
[16:09] <malin> ah, I see :)
[16:11] <malin> I did:
[16:11] <malin> bzr pull lp:unity-buss
[16:11] <malin> returned:
[16:11] <malin> No revisions or tags to pull.
[16:15] <davidcalle> malin, that's because you already are in the folder of your project. What does bzr status gives?
[16:16] <malin> davidcalle: I think I made it, just skiped the step
[16:16] <malin> and continued with merge instead
[16:17] <malin> but hm.. dosen't seemded to work. Will check br status
[16:17] <davidcalle> Ok. The step was just to be sure you were merging on a clean version of your project. Clean as in "equal to what's in your trunk on Launchpad".
[16:17] <malin> this is what I did: http://pastebin.com/J4Bt5vef
[16:17] <malin> I see
[16:18] <davidcalle> malin, from what I see on Launchpad, it worked :)
[16:19] <malin> ah it did? Cause the browser just try to load the browse code page, but it dosen't finish. I am trying to browse it once again
[16:19] <malin> dosen't load
[16:20] <malin> yeah it looks merged, but I cannot watch my code :S
[16:21] <malin> it just freeze on loading
[16:22] <davidcalle> malin, Launchpad is apparently in maintenance for a few minutes : https://plus.google.com/u/0/109129028036222996031/posts/FBixu3QNQVk
[16:22] <malin> ah
[16:22] <malin> aha, that explains all :)
[16:23] <malin> but thank you so much for helping me :) I am so happy to get it packed soon, and spread this :)
[16:27] <malin> nice. you found me at google + :)
[16:27] <davidcalle> malin, heh, I'm glad people are making their own lenses. :)
[16:27] <malin> yeah :)
[16:28] <malin> I think Jo-erlend told me I could make my own lenses, and then I just did :)
[16:29] <malin> This is the first thing I have made who is usefull and finished :) Well, there is some few improvements I will add before I will call it version 1.0
[16:31] <davidcalle> malin, yeah, version 1.0 is always a bug step :)
[16:31] <davidcalle> big*
[16:33] <malin> it is, and I think version 0.9 is very close... :)
[16:34] <bdrung> Cimi: around?
[16:34] <Cimi> bdrung, in 30 mins
[16:38] <malin> oh lord, I can browse the code again :) meaning I will get it packed
[17:08] <bdrung> Cimi: hi. do you have time to help me debugging bug #955376 and #981289?
[17:08] <ubot5> Launchpad bug 981289 in light-themes (Ubuntu) "Window list entries colored in white instead of dark (GNOME Classic / Ambiance theme)" [Undecided,New] https://launchpad.net/bugs/981289
[17:08] <ubot5> Launchpad bug 955376 in light-themes (Ubuntu) "Text color under Ambiance in top panel of GNOME Classic is dark gray instead of white" [Undecided,Confirmed] https://launchpad.net/bugs/955376
[17:09] <Cimi> bdrung, might be a :insensitive state for the first one
[17:10] <Cimi> sorry I meant the latter
[17:10] <Cimi> for the first one instead
[17:10]  * Cimi looks
[17:10] <Cimi> this is probaby a missing match
[17:10] <Cimi> I think someone did changes, but I didn't have time to approve
[17:11] <bdrung> i failed in finding a correct name to match
[17:11] <Cimi> https://code.launchpad.net/~and471/light-themes/desktop-panels-929665/+merge/92327
[17:11] <Cimi> try merging this branch into lp:light-themes
[17:11] <Cimi> and see if that fixes for you
[17:13] <bdrung> Cimi: i have to leave now. i will be back in ~2 hours. then i will test this branch and report back.
[17:13] <Cimi> bdrung, ok, I will leave too but I think I'll be online tonight
[17:14] <bdrung> but i doubt that this branch will fix the theme issue.
[17:16] <rye> Cimi: may i inquire you about this too - https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/983923/+attachment/3083260/+files/Radiance-jagged.png - bug #983923
[17:16] <ubot5> Ubuntu bug 983923 in light-themes (Ubuntu) "Subpixel rendering type of Radiance panel menus is wrong" [Undecided,New]
[17:16] <rye> the title is how i see it being at the point, but I was not able to find anything particularly different in Radiance theme (vs Ambiance)
[19:13] <shnatsel> hello!
[19:15] <shnatsel> I'm writing ulatencyd configs for Ubuntu, including Unity. Among other things it can set higher or lower priority (niceness) to specific processes. I've raised priority for UI components and unity-panel-service, but I'm not sure what priority should I set to unity-applications-daemon and lenses. Any hints?
[19:16] <davidcalle> malin, I've noticed you are building for Oneiric too. You shouldn't, as Precise lenses don't work on Oneiric. :)
[19:17] <malin> davidcalle: ah. Didn't know. Then I have to change it :)
[19:17] <malin> davidcalle: I got builds for i386 only. Belived I would get it for all
[19:18] <davidcalle> malin, it's ok : unity-lens-buss_0.9-0~22~precise1_all.deb  notice the "all" at the end.
[19:19] <malin> ah, so it is right?
[19:19] <malin> yeah, it state all, so I have to change i386 in launchpad then?
[19:20] <malin> cause the architecture tag states i386 and not all, but I see, the package is right
[19:20] <davidcalle> shnatsel, I think they should be on low priority, they are really punctual tasks. But I'm not sure. mhr3 ?
[19:22] <shnatsel> davidcalle: it depends on what they do. If they are doing something only responding to user's request, they should be higher priority to be more responsive. If they work mostly in background, they should be low priority to make way for user's real tasks.
[19:23] <davidcalle> malin, no it's fine. "All" is specified in your debian/control file and Launchpad fallbacks on the i386 tag in this case. That's normal.
[19:23] <malin> ah
[19:26] <davidcalle> shnatsel, then I was right not to be sure. They are an almost inexistent background noise and need to be super responsive on user's request.
[19:26] <davidcalle> shnatsel, my bad.
[19:28] <shnatsel> davidcalle: both lenses and applications daemon?
[19:28] <jo-erlend> is it still necessary to restart Unity in order for new lenses to become available? I thought I read about some command to reload, but that might be in another context.
[19:30] <davidcalle> jo-erlend, still necessary, yes. The command is just a request that has been made... Let's hope it's here for 12.10.
[19:30] <jo-erlend> yes, that's sort of a big deal.
[19:31] <davidcalle> shnatsel, lenses = daemons, the visible dash chrome is managed by compiz.
[19:32] <shnatsel> davidcalle: and what unity-applications-daemon do?
[19:32] <davidcalle> shnatsel, it's the lens.
[19:33] <shnatsel> davidcalle: it's not directly a lens and I couldn't find any docs about it
[19:33] <shnatsel> davidcalle: ah, sorry, my bad, indeed it is
[19:33] <shnatsel> davidcalle: thanks! I'll raise priority and propose the configs upstream once I test them a bit more.
[19:34] <davidcalle> davidcalle, thanks!
[19:34] <davidcalle> shnatsel, ok, now you see it, I'm eating and especially drinking quite a lot right now :)
[19:34] <shnatsel> :D
[19:37] <shnatsel> oh, by the way... I normally work for elementary, as the OS guy. I have conducted an extensive research about near-term performance optimization, there are 5 items and ulatecnyd is one of them (that's why I'm asking). Here are the results, in case you're interested: http://shnatsel.blogspot.com/2012/04/5-ideas-that-every-desktop-os-should.html
[19:39] <shnatsel> all those items can be used in Ubuntu, but I have no idea where to submit this.
[19:39] <malin> davidcalle: thank you again for all help
[19:39] <malin> and thanks to mhall119 too for helping
[19:40] <malin> and everyone else who have helped me :)
[19:40] <malin> I will do some few fixes on this lense, and then start on another one I think :)
[19:41] <davidcalle> shnatsel, ubuntu-devel mailing list I guess
[19:41] <shnatsel> davidcalle: thanks! will do
[19:41] <davidcalle> malin, another one? That's great :) Any ideas?
[19:41] <davidcalle> shnatsel, np
[19:52] <jo-erlend> malin, there's also a Quickly template in the works now. It should simplify and speed up the creation of single-scope lenses dramatically.
=== zyga is now known as zyga-afk
[20:33] <malin> jo-erlend: coool
[20:40] <jo-erlend> malin, yes, it doesn't seem to work, but you can see how it's supposed to work here: developer.ubuntu.com/2012/04/how-to-create-a-wikipedia-unity-lens-for-ubuntu
[20:50] <bdrung> Cimi: that branch didn't fix it, but I found a branch that fixes it: https://code.launchpad.net/~eye-zak-devel/light-themes/fixes-lp954437/+merge/97295
[20:50] <mhall119> jo-erlend: it works, at least for david and I (and a few others I've heard from)
[20:50] <mhall119> jo-erlend: what problem are you having with the quickly template?
[20:51] <mhall119> jo-erlend: it's still complaining about not having the .service file?
[20:59] <jo-erlend> mhall119, yup.
[21:00] <mhall119> jo-erlend: that's very strange, it shouldn't even *try* to do that when the lens daemon is already running...
[21:00] <mhall119> jo-erlend: the lens process is printing that error, or something else?
[21:01] <jo-erlend> mhall119, let me repeat it and see.
[21:13] <jo-erlend> mhall119, hmm. Different results now. I'm beginning to think it might've been a pebcak.
[21:17] <jo-erlend> mhall119, Why does the article recommend quickly install? It seems to me that recommending "quickly package", install the deb and restart unity would be better.
[21:20] <mhall119> jo-erlend: "quickly install" does the minimum amount necessary to allow testing via "quickly run"
[21:21] <mhall119> also, fyi, you don't need to run "quickly install" if yu add/remove categories or change your .lens file, you don't have to do it for changes to the search function to be picked up
[21:21] <mhall119> you *only* need to run quickly install in those scenarios, not "don't
[21:21] <jo-erlend> oh, ok. I see.
[21:22] <jo-erlend> in other words, it should've been called "quickly testrun" or something? :)
[21:26] <mhall119> or something, but I couldn't think of a better something
[21:27] <mhall119> I'm thinking "addlens" now, but it's too late for 12.04
[21:32] <jo-erlend> mhall119, I don't think it's a big problem. But it would be nice if the article was updated to better explain what quickly install does and what to expect.
[21:34] <davidcalle> jo-erlend, the *surprise* Unity restart?
[21:35] <jo-erlend> davidcalle, for instance, yes. And the large amount of scary text that appears in the terminal.
=== salem_ is now known as _salem
[21:38] <davidcalle> jo-erlend, you are right, but I didn't want to break the tutorial with scary things (developing lenses leads anyway to several unity --restart, with everything it involves). I'll see if I can directly update it myself tomorrow and add some kind of warning.
[21:42] <jo-erlend> you can have it in the intro, before the tutorial itself starts. Something about how lenses aren't usually added and removed all the time, and that it will be started automatically at login, etc.
[21:43] <jo-erlend> but it's really annoying that this is necessary in 12.04.
[21:43] <jo-erlend> I'm wondering if a lens-updater can be added as its own program without requiring a Unity restart?
[21:45] <davidcalle> jo-erlend, lens updater?
[21:45] <jo-erlend> yes, I mean some program to refresh the lenses in Unity without having to restart Unity itself.
[21:50] <jo-erlend> it's not a big deal in any case though.
[21:51] <malin> how do I reverse the result-list?
[21:52] <malin> I changed my lens so it display several answers again, but the newest result is placed last. I want it on top
[21:52] <malin> I tried to add reverse to this: model = search.props.results_mode by writing: model = search.props.results_mode.reverse <<--didn̈́t work
[21:53] <malin> it didn't work to write model.reverse() on a single line either
[21:53] <davidcalle> malin, create a list of results, reverse it, then append each result to the model.
[21:54] <malin> yeah, so I should actually write the results to a textfile first, and then add them to the model. Then I think I implemnt it in next version :)
[21:54] <davidcalle> malin, not to a text file, just to a variable :)
[21:54] <malin> davidcalle: ah, so it's enough to put it in a variabel?
[21:55] <malin> hm.. but I do have put it to a variabel already
[21:55] <malin> or does it need its own variabel. I need an array I guess?
[21:57] <davidcalle> malin, I don't know how you separate your results from your initial string of results. But create a list "results_list = []", then for each one, "results_list.append(result)". Then results_list.reverse (). And "for result in results_list:" model.append etc.
[21:58] <davidcalle> malin, not sure I'm clear :) Need to go to sleep ;)
[21:58] <malin> I need to sleep too :) but I can try something like that :) thank you very much
[21:58] <malin> Have a good night
[21:58] <davidcalle> malin, you too!
[22:02] <Teester> mhall119: Ping
=== yofel_ is now known as yofel
[23:14] <bdrung> Cimi: around?
[23:51] <Cimi> bdrung, no :)
[23:51] <bdrung> Cimi: in which timezone do you live?
[23:52] <Cimi> bdrung, London
[23:52] <Cimi> (Italian guy in London :))