[00:14] hi all [00:23] Hey, is there any reason the Sphinx template doesn't look like the wiki? Should I update it? [00:23] hi jbowtie, the one for docs? [00:24] no good reason; we'd like to make the themes for the main site, the wiki and the docs more consistent [00:24] poolie: Yes; I was just thinking it would be nice to make things consistent. [00:24] the www site is the most recent and arguably the best [00:24] though improvement there is still possible [00:25] poolie: OK, I'll have a look at rolling a Sphinx template this week along with fixing as many doc bugs as possible. [00:25] that would be brilliant [00:25] it doesn't need to slavishly follow the main site [00:25] for example i think the left-side table of contents is useful and should stay [00:26] but if we could at least get consistent tabs across the top that would be good [00:26] it may help if you post screenshots as you go [00:26] poolie: I'm looking at the tabs across the top and the footer at the bottom. [00:26] poolie: As well as coordinating fonts and colors. [00:27] poolie: Good point, I'll attach some screenshots to the bug when I make my merge proposal. [00:30] Looking at #405452 - what's a "ghost" revision? [00:32] jbowtie: it's a revision that Bazaar knows about but that is not present in the repository [00:33] jbowtie: so for example a parent revision of some revision that is present in the repository could be missing [00:33] jbowtie: ghosts are usually created when importing revisions from baz or subversion [00:33] jbowtie: but they could also be created using a (hypothetical) command in bzr [00:33] jelmer: since we rolled out the bzr-git update, it seems a few imports now fail with: [00:33] bzrlib.plugins.git.errors.NoSuchRef: The ref master was not found. [00:33] jelmer: any instant ideas? [00:34] mwhudson: my guess would be that these repositories do not have a master branch :-) [00:34] jelmer: the imports worked before the rollout though [00:34] jelmer: see https://code.edge.launchpad.net/~cjwatson/packages-arch-specific/trunk [00:35] has bzr-git become more careful about this? [00:35] mwhudson: yeah, we've become a bit stricter [00:35] jelmer: ok [00:42] If I create a project on launchpad.net, can I remove it later or is it like SF.net, once it exists, it lives forever? [00:44] jeremy_c: you have to ask an admin to have it removed, but it's not a big deal [00:45] I wanted to give it a try for a while but be able to backout if it doesn't seem like it's working out after a few weeks. [00:45] Hi I've got some problems with my bzr branch, I get "bzr Error: Revision {...} not present in CHKInventoryRepository(...) is there a way to repair this [00:45] parkesy: when do you get these errors exactly? [00:45] jelmer: when i do bzr log [00:46] parkesy: immediately or after a few revisions? [00:46] jelmer: the first time it was a few seconds after now it is immediately [00:47] jelmer: it also happens with bzr version-info [00:47] parkesy: but after a few revisions? [00:48] jelmer: sorry, it just started happening over night, it was fine on friday, then when i came into work today its failing. [00:49] jelmer: I tried to fix it myself and had to get the Sysadmins to restore my working branch from a backup taken over the weekend. [00:51] igc or mwhudson: Are you guys going to merge https://code.edge.launchpad.net/~mkanat/loggerhead/synchronize-lru_cache/+merge/23977 ? [00:52] mkanat: i guess i will unless Peng_ beats me to it [00:52] mwhudson: Okay. [00:59] Go ahead. I'm busy watching TV. :P [00:59] mwhudson: ^ [00:59] Is mkanat a member of loggerhead-team? [00:59] done [00:59] Peng: I'm not. [01:00] mkanat: want to be? [01:00] mwhudson: Oh, um, sure. :-) You'll have to educate me on checkin procedures and so on. [01:01] Nah, there's not much to educate on. [01:02] well, merge into trunk, then push [01:02] rather than merging trunk into your branch then pushing that to trunk [01:02] Good morning. [01:02] You should also commit! [01:02] but i'm sure you wouldn't be that tasteless anyway [01:06] Peng_: Okay. :-) [01:06] I mean, mwhudson. [01:06] Peng: Hahah, yes, committing would help. [01:06] spm: You might want to update to trunk loggerhead again to get that fix we just pushed. It's one of the crashers. [01:07] mkanat: okis, ta [01:17] spm: BTW, has loggerhead stayed up since the pygments fix? [01:17] hrm. not sure. looking... [01:18] spm: I think I'm more or less going to become the contact for loggerhead stability, so any time there's crashes or hangs, I'd love to know. [01:19] mkanat: nod; I'll pass that on. [01:19] it's been up for about 9 hours atm :-) [01:19] not sure what the cause was there [01:19] spm: Heh. Okay. [01:19] unresponsive restart; two of 'em. [01:19] spm: Would you send me the log from before the restart? [01:20] 2010-04-26 15:30 & 2010-04-26 08:28 <== bot hUTC [01:20] sure [01:54] mkanat: sorry. not forgotten, just had to progress a high priority task. just fetching logs now. [01:54] spm: Okay, no problem. :-) [01:54] hi I think I found a bug on bzr, it is actually and old hack for osx that I think it is not necessary anymore [01:54] and it makes bzr break on top of pypy [01:55] santagada: oh good. :) Please file it at https://bugs.launchpad.net/bzr [01:56] santagada: how close is bzr to running on pypy? [01:57] spiv: run it is running, now I would love to run a test suite to see if there isn't any bugs in it [01:58] spiv: how do I run bzr unittests? [02:00] santagada: bzr selftest [02:00] hi spiv [02:01] i need testtools... just a sec I will first finish filling the bug report [02:01] santagada: to be pedantic, that runs the full automated test suite. Many of those can be accurately called unit tests, but many are integration tests. [02:01] Morning poolie. [02:01] spiv: so I will be happier if it works [02:04] mkanat: mwhudson: ew! this looks .. bad: ERR [20100423-23:59:43.593] [1101093200] root: RuntimeError: maximum recursion depth exceeded [02:04] spm: i _think_ Peng_ fixed that [02:05] urg even. there's a few in teh debug log [02:05] bzr has a mbp and hg team has one mpm, I wonder how many times people confused the two nicks/people [02:07] santagada: probably about as often as spm and spiv :-) [02:07] spm: I think that's a python bug? [02:07] spm: Does it say it's being ignored? [02:10] mkanat: not that I can see; but it is in the older log = the access and debug aren't rotating at the same time. only just noticed that was from Fri; not today. [02:10] spm: Okay. [02:11] spiv: https://bugs.launchpad.net/bzr/+bug/570495 if there is any more needed info just ask :) [02:11] Ubuntu bug 570495 in bzr "bzr should not change sys.platform or should limit it to the affected python versions" [Undecided,New] [02:16] spiv: bzr: ERROR: No module named paramiko can't I just skip those testes? [02:17] fixed in r5165 so pull bzr.dev [02:17] santagada: hmm, they should be automatically skipped if the module isn't found. I think you might be encountering a recently fixed bug. [02:17] spiv: I'm using a tarball for 2.1.0 [02:17] the bzr repo is huge [02:20] mwhudson: ew. ERR [20100426-09:20:07.255] [1120741712] root: ConnectionError: Connection error: Couldn't resolve host 'bazaar.launchpad.net' (-2, 'Name or service not known') <== that so can't be good. [02:22] spm: i'd agree with that [02:22] spm: i'd also apply the SEP field from my POV [02:22] if DNS isn't working in the data centre.... [02:22] there's a heap of them in the debug log [02:23] ha [02:23] mwhudson: what's a strong I can search for "Oh Hai. loggerhead is now starting up"?? [02:23] err string, strong string even [02:23] santagada: hmm, that fix hasn't been backported to the 2.1 branch, it's just on trunk [02:23] spm: "Starting up..." i think [02:24] too bloody obvious. can't possibly be that. [02:24] spiv: also not on 2.2b1 :( cloning the whole repo now [02:24] mwhudson: 'loggerhead: Starting up...' haha [02:24] don't think I daggied it either as the previous attempt blew up the push [02:25] trivial diff to cherrypick though [02:25] santagada: http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev/revision/5165 [02:26] santagada: you can view/download just that diff from there if you like... but probably having a copy of trunk will turn out to be worth it if you find more issues to fix [02:26] yep... how big is it? it is more than 50mb [02:27] was going to suggest a lightweigth checkout, but my test run is... still running [02:27] B:\TEMP>bzr co --lightweight lp:bzr bzr.dev [02:27] [########\ ] 21179KB 107KB/s | Build phase:Adding file contents 1163/1296 [02:27] so, not much of a transfer saving. [02:28] a212901390231901: thanks for the help but now I will just let it finish [02:28] santagada: shouldn't be much more than 50 [02:28] a212901390231901: yeah, we haven't really spent much time optimising creating lightweight checkouts via the smart protocol yet [02:29] seems the tree is really that big, too. [02:29] (or updating them, for that matter) [02:31] Yeah, "bzr export bzr-trunk.tar" gives me a 21M tarball. It compresses down to 6.4M with gzip though. [02:32] mkanat: ow. http://paste.ubuntu.com/423106/ [02:33] spm: Lame. [02:33] heh, does explain why I was having trouble find the '2nd' start. was 2 mins later. [02:37] the full repo is 60mb or a little more [02:38] I didn't see the ending [02:40] the tests are running [02:41] lots of failures [02:43] it had big problems with unicode filesystem access when I looked at it, but that might be less of an issue on nix [02:43] uhm... it completely froze [1017/23179 in 40s, 1766 failed] blackbox.test_serve.TestCmdServeChrooting.test [02:43] a212901390231901: yep, most of the errors are unicode related [02:44] ...that one's probably not its fault, all the server tests are flakey [02:44] rely on refcounting and spit to hold them together [02:44] I will report some to pypy and someday maybe there can be a buildbot running bzr tests [02:45] a212901390231901: ok, so it will probably not happen [02:45] santagada: we're aware that our server tests have some flakiness, we'd like to fix that. [02:46] I'm getting a ton of NotBranchError: Not a branch: "/private/tmp/testbzr-fP73Gq.tmp/" [02:47] It's biting us in regular use too, we often seem to be leaking threads from tests that spawn servers, and that can lead to spurious failures due running out of fds and similar. [02:47] (And probably makes 'bzr selftest' consume more memory than necessary, etc) [02:48] no I think the real failure is this: [02:48] File "/Users/santagada/projects/bzr/bzrlib/config.py", line 940, in _auto_user_id [02:48] gecos = w.pw_gecos.decode('utf-8') [02:48] AttributeError: 'NoneType' object has no attribute 'decode' [02:49] that's fixable. [02:50] Interesting that we haven't encountered that one before, but yes should be easy to fix. [02:50] there's another bug asking to just remove auto_user_id [02:50] that would be better imo [02:51] Yeah. [02:51] Certainly there's no need for the test suite to be triggering it for every test as I suspect it does. [02:51] erk [02:52] I was going to file a bug complaining about it, and parse_username, which combine to do some very silly things [02:52] heres the full traceback if someone whants to have a go at it http://paste.pocoo.org/show/206563/ [02:52] After all it resets $BZR_EMAIL etc :) [03:01] it appears to be run on all tests, and when it fails I get that notbrancherror probably in another thread if I understood correctly [03:06] santagada: what about this patch: http://bzr.pastebin.com/3EtrtFUu ? [03:08] invalid syntax for some reason [03:08] Oh, missing trailing comma [03:09] My bad for not testing. [03:09] yep, let me fix that [03:10] a TON less failures [03:10] 2 failed thus far [03:10] Hmm, a quick run of the test suite finds a little bit of collateral damage (e.g. blackbox.test_annotate.TestSimpleAnnotate.test_annotate_edited_fileedited_file) [03:11] But that's a good sign. It's probably a touch faster, too ;) [03:13] unsuported locale setting... uhm maybe pypy _locale is not working as expected [03:14] spiv: is those tests results being saved anywhere? [03:17] santagada: my test results? No, but I can if you like. I only ran the blackbox tests, as they seemed most likely to fail, and in the end got 3 failures. [03:18] nope the ones I'm running [03:18] Oh right. Not by default. [03:18] as there is this status line I don't know what whill happen if I redirect stderr to a file... but I should be doing that.. [03:19] If you use --subunit you'll get the test run emitted in a machine-readable format. [03:19] (You can use the subunit2pyunit filter in the subunit package to see the output in a familiar format) [03:21] It'll be a pretty large file (it includes details of the passing tests, too), but it should gzip pretty well. [03:21] well 22 failures out of 1545 tests run, not too bad [03:22] spiv, do you think user_url and control_url etc are reasonable names? [03:22] Yes. [03:23] Especially user_url! [03:23] mm, a big clue that if you're showing it to the user you should use that one :) [03:27] Ack! I just remembered that I meant to reply to an email like a month ago. [03:28] It said "let me know this week". :( [03:28] (My answer was no anyway, so it doesn't matter, but sorry for forgetting to decline the Brussels sprint, poolie.) [03:41] had to kill the selftest process it stopped responding completely [03:42] in test "per_bzrdir.test_bzrdir.TestBzrDir.test_sprout_bzrdir_tree_branch_reference(RemoteBzrDirFor"... [03:53] Peng, ok, thanks anyhow, maybe next time === lifeless_ is now known as lifeless [05:38] spiv, could i get a quick eyeball over https://code.edge.launchpad.net/~mbp/bzr/testsubjects/+merge/24188 [05:48] Sure. [06:13] poolie: I'd like to do a pre-imp call with you on test subjects :- I'd like to clarify what you want to achieve and see if I can help you with that. [06:14] poolie: if that wouldn't help you, say no thanks :) [06:15] uh, ok [06:15] call me? [06:16] I'll just see if I've got skype on this machine yet [06:16] one minute [06:16] do you have a pots line? === jamesh_ is now known as jamesh [07:32] hi all [07:40] Morning [07:41] hi vila, gary [07:42] hey GaryvdM [07:42] hi poolie [07:53] Did anybody (else than me) testing bzr on lucid have a failure for bzrlib.tests.test_transport.TestSSHConnections.test_bzr_connect_to_bzr_ssh ? [08:05] oh lifeless, where did we eventually get to with pqm? [08:05] vila, not me, yet [08:06] poolie: hmm, too bad, you were my best hope :) [08:06] i'll try it [08:07] poolie: running just this test alone is enough here, I'm wondering if my setup is somehow screwed or if it's something deeper [08:13] no actually i do get that too [08:13] i suspect either a change in ufw [08:13] which i think i'm running here [08:13] or an icky order dependency [08:13] poolie: spm says no exceptions in pqm since the 24th [08:21] vila: FWIW, PyCrypto doesn't like fork()ing the random number generator because both processes will wind up with the same state, which is not very random. IIRC it also has thread-safety issues. [08:23] Peng: yup, but nothing we care about for tests, thanks for the info though [08:23] hi all [08:23] lifeless: no execptions doesn't mean no pending bugs, there are still no feedback on failures [08:24] (among other things) [08:26] Hi bialix [08:26] bialix: _o/ [08:26] Heya GaryvdM !!! [08:26] bonjour vila! [08:27] GaryvdM: I have strnge problem with qpush [08:27] lifeless: ok, but what's the state now? still running with lp integration, or pulled down? [08:27] GaryvdM: push to lp (when no ssh key is loaded to pageant) blows with traceback [08:28] Traceback [08:28] GaryvdM: http://pastebin.com/EDdekYpm [08:28] * GaryvdM looks [08:28] the most strange thing is when I set BZR_PDB=1 then qpush simply hangs [08:29] it's in qpush === radoe_ is now known as radoe [08:29] my problem is BZR_PDB related [08:29] poolie: running with integration [08:29] vila: I will look at that tomorrow [08:29] lifeless: be blessed :D [08:29] you didn't pull it out on thursday? [08:30] it was behaving much better [08:30] k [08:30] emailed submissions get mailed failures I think now [08:30] GaryvdM: do you (we) change something in qbzr that broke BZR_PDB you made long ago? [08:30] bialix: hmm - you need BZR_PDB on for the qbzr process, but not for the subprocess [08:30] or maybe it's a newer bzr issue [08:30] not sure how to do that. [08:31] GaryvdM: so you think it's a subprocess starting pdb session? [08:31] hmmmmmmmmmmmmmmmm [08:31] yes - before the main process errors [08:32] I don't understand what's going on [08:32] the plain push never raise error? [08:32] or there is some hidden bug in our subprocessUI class? [08:32] bialix: what about running bzr qsubprocess push [08:33] oh, I think I understand [08:33] \n issue [08:33] I do that often to debug qsubprocess [08:33] again :-( [08:33] bzr produce multiline error message [08:33] bzr: ERROR: Connection error: Unable to authenticate to SSH host as [08:33] bialix@bazaar.launchpad.net [08:33] supported auth types: ['publickey'] [08:34] Oh - my new error passing code :-( [08:34] but we're trying to send it as one string [08:34] ok, I understand the problem now [08:34] our bencode stream is very fragile re \n [08:35] we have to encode them somehow, or manually split the string into multiple strings [08:35] * bialix filing a bug [08:36] GaryvdM: any ideas re BZR_PDB in subprocess? maybe we should manually delete this variable from subprocess environment? [08:36] That would be a good idea. [08:37] And if one needs to debug the subprocess, then one can just run the subprocess. [08:39] spiv, still here? [08:39] GaryvdM: agree [08:41] poolie: yeah [08:42] lifeless: I don't think I got test failures even for my mail submissions (at least I can't find the relevant mail for https://code.edge.launchpad.net/~parthm/bzr/no-chown-if-bzrlog-exists/+merge/22197 and I'm pretty sure I submitted by mail) [08:42] spiv i split out the cleanup change into https://code.edge.launchpad.net/~mbp/bzr/cleanup/+merge/24200 [08:42] lifeless: I only got failure mails for the NEWS conflicts and the 'nothing to merge' cases [08:42] i have mixed feelings about whether this patch is worthwhile [08:44] poolie: hi :-) [08:45] spiv: istm that some other objects, like a test case, can make use of the concept of having a list of cleanups [08:45] and that it's not part of their public interface to expose a single run() [08:45] but perhaps the answer is that they should just us an OperationWithCleanups internally [08:50] poolie: Command as well as TestCase [08:50] poolie: although I think we now delegate the cleanup management in TestCase to testtools? [08:50] probably [08:50] though there, ideally, if not practicalyl, this same class would be used by all of them [08:51] Oh, and commit.Commit, slightly weirdly perhaps, psuedo-does. [08:53] (it doesn't have an add_cleanup method, instead it passes the operation var around, but in general seems a bit confused about if it's an object with state or a bunch of related functions with intimate knowledge of each other's workings) [08:53] Hi all [08:53] Can anyone tell me how to change the default editor for editing project files? [08:53] Setting the editor in prefs seems to work only for config files [08:53] sorry [08:54] in bazaar explorer [08:54] WimYedema: is this in explorer? [08:54] :/ [08:57] poolie: Btw, you may like https://code.edge.launchpad.net/~spiv/bzr/hpss-compat-528041/+merge/24202 — it removes the raise AssertionError in _remember_remote_is_before [08:57] vila: I will experiment in detail tomorrow when spm is around [08:57] lifeless: pls being ware we have zomg priorities atm.... [08:58] spm: and at a time of your choosing [08:58] WimYedema: I don't know off hand [08:58] spm: the LTS can wait, surely? :P [08:58] spm: primarily though I'll be throwing known bad stuff at it and just asking for backtraces to be pastebinned [08:58] I think I can edit editors.conf but it seems I need to add an extension there, and I don't much feel like adding all the possible extensions (never mind things without extension) [08:58] spiv: .... [08:58] lifeless: we should so get you access to the logs... [08:59] spm: +1e6 [08:59] spm: that would be nice; I mean I used to be able to log in to diagnose directly ;) [08:59] WimYedema: I _think_ it's configured at the os level [08:59] and explorer has no opinion [09:01] poolie: Hmm... okay, unfortunately Gnome doesn't seem to have a prefered text editor application. I'll try setting EDITOR then... [09:01] WimYedema: please, file a bug [09:02] bialix: okay [09:02] yeah it's definitely by extension [09:02] which was a bit strange [09:03] GaryvdM: btw, I have working code for commit-history, now I need to figure out how to fill the combobox with pending merges messages. Any hints? [09:03] bialix: The autocomplete combobox? [09:03] $EDITOR should control it [09:04] GaryvdM: I feel simple combobox will be much easier and faster to use than qdiff + message. Just because I don't need to launch qdiff window, select, copy, close window and paste [09:04] GaryvdM: but your qdiff+message is very good, I think we can do it every time for qdiff -cN [09:05] GaryvdM: it's not autocomplete [09:05] user select message in combobox and it appended to the comment [09:06] WimYedema: setting editor= in your bazaar.conf should do it [09:06] setting either EDITOR or BZR_EDITOR does not seem to have any effect [09:06] bialix: I'm not to sure about adding extra widgets to qcommit.... [09:06] poolie: nope, that's what the preferences menu sets, but it doesn't help [09:07] what does happen then? [09:07] it starts gedit [09:07] GaryvdM: it's only one-line combobox [09:07] GaryvdM: what's problem? [09:07] could it be Mime configuration or something? [09:08] bialix: qcommit is allready busy. [09:08] GaryvdM: I know. but what is alternative here? [09:09] bialix: we could put it in the autocomplete list. [09:09] GaryvdM: no [09:09] GaryvdM: this is wrong [09:09] the idea is you can put there some past entire commit message [09:09] it could be very long [09:11] WimYedema: it might be mime or it might be /etc/alternatives, controlled by update-alternatives [09:11] bialix: Maybe a button that pops up list or menu, but does not a extra text box like a combo box. [09:12] GaryvdM: and where to put such button? [09:12] can you run my branch to see it in action? [09:13] bialix: ok [09:13] bialix: sorry - what is the url agian? [09:13] you need to make some commits to seed the history, plain bzr ci catched too ;-) [09:14] GaryvdM: lp:~bialix/qbzr/post-commit [09:14] * GaryvdM branches... [09:15] the hooks are cool things! I will add similar hooks for post_push/post_pull to store push/pull history in similar manner to commit-history [09:15] MRU [09:15] bialix: https://bugs.launchpad.net/bzr/+bug/570573 [09:15] Ubuntu bug 570573 in bzr "setting default editor in explorer fails in Gnome" [Undecided,New] [09:16] WimYedema: thanks! [09:18] WimYedema: GNOME might be using mailcap to figure out how to open the files [09:18] in which case probably /etc/mimetab [09:18] mimecap? [09:18] spiv, so what do you think overall about cleanups? [09:18] poolie: that name would make sense, but no! [09:18] should i withdraw that patch? [09:19] /etc/mailcap, see 'man mailcap' and 'man run-mailcap' [09:19] bialix: I'm going to experiment with putting the messages in the autocomplete list. [09:19] poolie: I just sent a review, did you see it? [09:19] GaryvdM: I'm still think it's a wrong idea [09:20] combobox shows the commit messages in descending order [09:20] auto-complete will lose this ability [09:20] Ooh, and actual PQM failure in a merge proposal. [09:20] s/and/an/ [09:20] repr(lines) isn't my preferred format for reading failure output, but it's a lot better than nothing :) [09:21] GaryvdM: does auto-complete handle multiple words? [09:22] bialix: I think so. I want to check. [09:22] spiv: url ? [09:22] ok, I will test your auto-complete then [09:22] lifeless: https://code.edge.launchpad.net/~mbp/bzr/components/+merge/23827 [09:22] oh thanks for the review [09:23] s [09:23] s [09:23] spiv: that seems to be working okish [09:23] it does feel a bit half done to me [09:24] spiv: but actually I think its a bug, will leave this open and look tomorrow [09:24] lifeless: which one? [09:26] [] around the lines in the merge review feedback [09:26] poolie: yeah. I'm not necessarily against landing half-done things, as I hope I made clear. Just that it seems something to be aware of. [09:27] poolie: (especially not against it when the next step isn't immediately crystal clear, and the half-done point isn't likely to paint us into a corner.) [09:28] Also, rather than risk mixing metaphors any further I might go have dinner :) [09:29] agree :) [09:29] also about dinner :) [09:29] "No metaphors were harmed in the making of this patch." [09:30] GaryvdM: I'm thinking about adding main menu to qci and qdi to allow user hide the elements he is not interested to see [09:31] bialix: I had such plans for qdiff. [09:31] *have [09:31] but you feel qci is also busy, so we need to allow customization here as well [09:32] bialix: Similar to lp:~garyvdm/qbzr/annotate_find [09:32] also I want to work on redesign of bugs/author area, as Craig suggested in ML [09:32] * bialix looks [09:32] poolie: is it possible to work on tags v2 on the sprint? [09:33] poolie: maybe it's better if I send the mail with some my thoughts how I think we could improve current tags [09:33] and operations on tags [09:34] amanica said me he's willing to work on nested trees. I have many feedback on this topic based on scmproj workflow. And I have many questions on the intended nested trees behavior [09:47] GaryvdM: annotate_find: cool! why you don't merge it? [09:48] Ugh! you've got to be kidding! I did some googling, and the solution is: Change the Applications>Text Editor entry to the editor you want to use. [09:51] GaryvdM: I want to do similar ui changes to diff, cat, log and browse, an I want to do it at the same time, so that qbzr dialog have consistent feel. (maybe I'm being silly...) [09:51] Anyway, thanks for the support guys. [09:51] See you later [09:51] Lol - I'm talking to myself... [09:51] bialix ^ [09:52]