| aeoril | darkxst it appears to make this work I have to switch the meaning of good and bad: http://stackoverflow.com/questions/15407075/how-could-i-use-git-bisect-to-find-the-first-good-commit | 00:25 |
|---|---|---|
| sarnold | ha | 00:25 |
| aeoril | yah, I know ... | 00:26 |
| aeoril | (found another article that confirmed this article) | 00:26 |
| aeoril | http://git.661346.n2.nabble.com/Why-can-t-I-use-git-bisect-to-find-the-first-good-commit-td6214209.html | 00:27 |
| darkxst | aeoril, sure | 00:27 |
| darkxst | its makes little difference (apart form possibly confusing you) | 00:27 |
| aeoril | darkxst now I have to test how not stupid I can be and see if I can do it without screwing myself up ... :P | 00:27 |
| aeoril | but, right now I have to cook for my sick wife ... | 00:28 |
| FOSS_drivers_FTW | good night | 01:16 |
| === bluesabre is now known as trello | ||
| === trello is now known as bluesabre | ||
| derpderp | i have downloaded the latest kernel repo from ubuntu's git archive, but how can I find the code that runs the interface used when changing resolution and monitor placement? | 01:59 |
| sarnold | derpderp: poke around in drivers/video/ or drivers/gpu/, both those seem likely candidates | 02:02 |
| derpderp | thank you! | 02:03 |
| sarnold | derpderp: you might have some success to read through the xrandr source code; it may contain magic that would help you discover what the kernel routines are. | 02:05 |
| derpderp | okay. i am having major problems dragging the rectangles in the interface when positioning monitors | 02:05 |
| derpderp | itss ridiculous so I thought I could look into it | 02:06 |
| derpderp | xrandr sounds more likw what I wnat/ | 02:06 |
| sarnold | derpderp: is the problem with the dragging-rectangles bit, or what happens to the monitors after you've dragged the rectangles? | 02:07 |
| sarnold | derpderp: it might make more sense to look at the control panel source then.. or whatever tool it is that provides the little rectangles ;) | 02:07 |
| derpderp | dragging rectangles bit | 02:07 |
| derpderp | are there places to go to find where the control panel source is? | 02:07 |
| derpderp | I hate to ask so many Qs, I'm usually able to figure things out ubut im new to opens \\ source dev | 02:08 |
| sarnold | derpderp: try looking in the unity-control-center package; apt-get source unity-control-center ought to download it for you | 02:09 |
| derpderp | thanks! | 02:09 |
| aeoril | darkxst_ you there? | 04:49 |
| Noskcaj | aeoril, What's the question? He'll see it eventually | 04:50 |
| aeoril | Noskcaj hey, I have been bisecting | 04:50 |
| === darkxst_ is now known as darkxst | ||
| aeoril | hey, darkxst | 04:50 |
| darkxst | aeoril, as Noskcaj said, just ask the question ;) | 04:51 |
| aeoril | darkxst sarnold I did the bisection. Wish I had verified v7-4 did not work before starting - it worked fine from the vim git repo, so entire bisection worked fine to versions predating trusty version, or what should be in trusty | 04:52 |
| sarnold | hey aeoril :) bummer :/ | 04:53 |
| aeoril | yah, sucks | 04:53 |
| aeoril | darkxst sarnold so could something specific to the ubuntu packages be the problem | 04:53 |
| aeoril | ? | 04:53 |
| darkxst | aeoril, build the trusty version and see | 04:54 |
| darkxst | aeoril, it could well be in a different package though | 04:54 |
| aeoril | darkxst does that make sense? Building the vivid version worked fine on trusty | 04:55 |
| sarnold | it could be debian or ubuntu specific packaging.. check the patches in debian/patches/ and see if any of them look like they might be related | 04:56 |
| aeoril | sarnold ok - sounds good | 04:57 |
| darkxst | aeoril, gtg be back later | 04:57 |
| aeoril | darkxst ok, thanks | 04:57 |
| sarnold | (check both the vivid and the trusty packages, you never know.. :) | 04:57 |
| aeoril | sarnold there is not debian/patches in either version ... | 05:02 |
| aeoril | sarnold http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/vim/vivid/files/head:/debian/ http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/vim/trusty/files/head:/debian/ | 05:03 |
| sarnold | aeoril: oh? http://paste.ubuntu.com/10103567/ | 05:03 |
| sarnold | aeoril: yeah, go ahead and ignore that ~ubuntu-branches thing entirely :) | 05:04 |
| aeoril | sarnold where the heck are you clicking to find this stuff? | 05:04 |
| sarnold | aeoril: I cheated, I've got some handy tools that make it easy to download all currently supported versions of a package. | 05:04 |
| sarnold | aeoril: so I just typed "umt download -r vivid,trusty vim" and a few seconds later had the unpacked sources sitting on my machine :) | 05:05 |
| aeoril | sarnold can I get to it from the launchpad website? | 05:05 |
| sarnold | aeoril: yeah, one second.. | 05:05 |
| aeoril | sarnold am I just stupid? :( | 05:06 |
| sarnold | aeoril: nope :) I've got these handy tools because it's not an easy task, otherwise, hehe | 05:06 |
| aeoril | sarnold are those tools standard, or did you write them yourself? | 05:07 |
| sarnold | aeoril: they're not standard, they just live in a bazaar tree; it's a royal pain to set them up though... | 05:09 |
| aeoril | better one royal pain than many | 05:09 |
| sarnold | aeoril: oh! I just remembered, there's a much better way than getting them through launchpad | 05:09 |
| aeoril | source packages? | 05:10 |
| sarnold | aeoril: install the ubuntu-dev-tools package; then you can use 'pull-lp-source vim trusty' and 'pull-lp-source vim vivid' | 05:10 |
| aeoril | sarnold that is exactly what I did with vivid ... :) | 05:11 |
| sarnold | hahaha | 05:11 |
| sarnold | that's the downside to having keen tools that simplify some tasks.. they make it easy to overlook fundementals. | 05:11 |
| aeoril | darkxst had me do that for vivid ... | 05:12 |
| aeoril | but I forgot about it til you just mentioned it ... | 05:12 |
| === semiosis_ is now known as semiosis | ||
| aeoril | sarnold I am making the trusty vim and going to try it out | 05:20 |
| sarnold | woo :) | 05:22 |
| aeoril | sarnold it worked fine | 05:23 |
| aeoril | sarnold the build environment for trusty vs. what I have must have been the difference | 05:24 |
| sarnold | aeoril: but the /usr/bin/vim fails? | 05:24 |
| aeoril | sarnold yes | 05:24 |
| aeoril | sarnold /usr/bin/vi maybe that is the difference? | 05:24 |
| sarnold | aeoril: time to compare ./vim --version with /usr/bin/vim --version and try to find out what's involved.. | 05:24 |
| aeoril | (vi vs. vim) | 05:24 |
| aeoril | what about vi vs. vim? | 05:25 |
| sarnold | aeoril: could be | 05:25 |
| aeoril | not sure why it is vi in trusty instead of vim ... | 05:25 |
| sarnold | aeoril: when you call it with 'vim' it changes a lot of the 'vi-compatible' options | 05:25 |
| aeoril | typing just "vim" just does not work | 05:26 |
| sarnold | ... also, check /etc/alternatives/vi* -- turns out my vim is actually calling vim.gtk. I never knew :) | 05:26 |
| aeoril | sarnold mine is vim.tiny ... | 05:32 |
| aeoril | sarnold the compiled one is full gui, the trusty one is small without gui, according to --version | 05:34 |
| aeoril | s/full gui/normal gui/ | 05:34 |
| aeoril | sarnold vivid is also vim.tiny | 05:35 |
| sarnold | aeoril: hah, so the tiny version in trusty is broken, the tiny version in vivid is fine? | 05:35 |
| aeoril | sarnold apparently | 05:35 |
| aeoril | sarnold gcc command line is very different between versions also according to --version. I am guessing pass option to ./configure to make vim.tiny? | 05:36 |
| sarnold | aeoril: yeah, check the debian/rules file to see if it makes it easy to tell what.. | 05:38 |
| aeoril | sarnold --version shows that both vi.tiny in trusty (/usr/bin/vi links to it) and what I compiled from trusty vim source are based on 7.4 version dated 2013 aug 10 with patches 1-52, | 05:40 |
| aeoril | sarnold "vim-tiny" - that is the name of the VARIANT - not sure what to put on the ./configure command line though | 05:44 |
| sarnold | aeoril: note these bits: | 05:47 |
| sarnold | CFLAGS_vim-tiny:=$(CFLAGS) -DTINY_VIMRC | 05:47 |
| sarnold | CFGFLAGS_vim-tiny:=$(CFGFLAGS) $(TINYFLAGS) | 05:47 |
| sarnold | aeoril: read up the debian/rules from there to figure out what should go in the CFGFLAGS and CFLAGS, then look down to the line that has a ./configure in it -- and try to run much the same configure command line :) | 05:48 |
| aeoril | I asked on #vim and they said "./configure --with-features=tiny" - would that work? | 05:49 |
| sarnold | sounds like good advice :) | 05:50 |
| aeoril | sarnold I am confused about what you said about the debian/rules thing though - I looked around but could not make sense of it ... | 05:53 |
| sarnold | aeoril: it's based on make and the makefile format; if you're not accustomed to working with them, they can be a bit much | 05:54 |
| aeoril | sarnold I used to be pretty good with make, but it has been a long time ... | 05:54 |
| sarnold | hehe, for me, it takes about a month before I feel like I'm out of touch :) | 05:55 |
| aeoril | sarnold try 10 years or so ... | 05:55 |
| aeoril | on Unix ... | 05:55 |
| sarnold | oh man, it wasn't even gnu make? | 05:55 |
| aeoril | no, Sun Solaris and a real-time System V r4.3 variant ... | 05:56 |
| aeoril | well, I mean, maybe it was gnu - don't really know. Just know it was a long time ago | 05:56 |
| aeoril | everything looks pretty familiar, but I have forgotten what stuff does really | 05:57 |
| sarnold | solaris didn't feel 'right' until I'd replaced most of the tools with gnu versions.. and the old SCO unix thing I used that might have been 4.3 was all around terrible :) | 05:57 |
| aeoril | sarnold hwo old are you? | 05:58 |
| sarnold | aeoril: 36? | 05:59 |
| aeoril | sarnold just wondering because of your working on older systems | 06:00 |
| sarnold | aeoril: it was an amazing job to find while in high school, hehe | 06:01 |
| aeoril | sarnold I found the series of lines that set up the TINYFLAGS - it starts out with "TINYFLAGS:=--with-features=small" then adds on various enable/disable flags as well. Shouldn't I use debian/rules to configure the build, not what was recommended in #vim? | 06:04 |
| aeoril | sarnold I remember there was a procedure for using the debian build rules to configure the build when I did some ubuntu builds back in the day | 06:05 |
| sarnold | aeoril: well, at least with the simple rules from #vim, you've got something _small_ to work with; the full set of debian/ubuntu configure options might be harder to work with | 06:06 |
| aeoril | sarnold I can look that up though on the ubuntu wiki I guess | 06:06 |
| sarnold | aeoril: time for dinner :) have a good night, happy hunting :) | 06:07 |
| aeoril | sarnold yah, I am gone too now | 06:07 |
| aeoril | sarnold thanks :) | 06:08 |
| sarnold | nice, have a good weekend then | 06:08 |
| aeoril | ok, thanks | 06:08 |
| slangasek | xnox: could you really not find a better way to handle keyboard name translations for console-setup than by build-depending on all of the language packs? | 11:37 |
| === udevbot_ is now known as udevbot | ||
| === Neo31 is now known as pynorcio | ||
| === pynorcio is now known as Neo31 | ||
| === _salem is now known as salem_ | ||
| === salem_ is now known as _salem | ||
| === Neo31` is now known as Neo31 | ||
| === Neo31 is now known as Neo31` | ||
| === Neo31` is now known as Neo31 | ||
| === Tribaal is now known as Tribaal_ | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!