--- Log opened Wed Oct 04 00:00:11 2017 00:12 -!- Horwitz [~mich1@p200300800E01B500022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:12 -!- mode/#navit [+o Horwitz] by ChanServ 00:38 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n 00:38 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed 00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 02:41 -!- noradtux [~noradtux@2a02:2028:767:801:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 246 seconds] 02:59 -!- noradtux [~noradtux@2a02:2028:50e:a401:ec4:7aff:fe33:3dc1] has joined #navit 05:06 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 06:29 -!- naggety [028e5498@gateway/web/freenode/ip.2.142.84.152] has joined #navit 07:12 #navit: <@KaZeR> hi Navit 07:12 #navit: <@KaZeR> hi naggety 07:12 #navit: < naggety> hi kazer 07:15 #navit: < naggety> I need a bit of help here. I'm trying to run navit from eclipse and I get this error: error:navit:plugins_init:Warning: No plugins found. Is Navit installed correctly? 07:16 #navit: < naggety> Then other errors are also reported, but I guess that is because plugins are not loaded 07:16 #navit: < naggety> navit.xml was not found, neither, but I have solved it from "run configurations" 07:17 #navit: < youte> hi 07:19 #navit: < naggety> hi 07:38 #navit: <@KaZeR> naggety: looks like navit is confused about your start path. this can happen if navit hasn't been installed, and you are trying to call it from outside its directory 07:38 #navit: <@KaZeR> currently to guess the path when it's not installed we rely on `pwd`. Maybe we should rely on the binary path itself 07:39 #navit: <@KaZeR> are you able to alter the startup command from eclipse? 07:39 #navit: < naggety> yes 07:39 #navit: <@KaZeR> if you are starting it like this : "~/dev/navit/bin/navit/navit" then instead try "cd ~/dev/navit/bin/navit/ && ./navit" 07:40 #navit: < naggety> ok, I try 07:41 #navit: < youte> hi KaZeR 07:41 #navit: <@KaZeR> naggety: here's one part of the puzzle : https://github.com/navit-gps/navit/blob/trunk/navit/start_real.c#L173 07:41 #navit: <@KaZeR> hey youte 07:43 #navit: <@KaZeR> naggety: here's the next part of the puzzle : https://github.com/navit-gps/navit/blob/trunk/navit/main.c#L79 07:44 #navit: <@KaZeR> naggety: and here's the last part : https://github.com/navit-gps/navit/blob/trunk/navit/main.c#L351 07:48 #navit: < naggety> I see 07:48 #navit: < naggety> However, I can't do what you said. I can't fully modify startup command 07:49 #navit: < naggety> if it start with 'cd', it converti it to /path/to/eclipse/project/cd 07:51 #navit: <@KaZeR> ok. Another way is to export NAVIT_PREFIX so that it points to the correct folder 07:51 #navit: < naggety> what is NAVIT_PREFIX env variable for 07:52 #navit: < naggety> ah 07:52 #navit: <@KaZeR> :) 07:52 #navit: < naggety> xD 07:52 #navit: < naggety> I think I can do that 07:53 #navit: <@KaZeR> perfect 07:59 #navit: < naggety> not working 07:59 #navit: < naggety> :( 08:05 #navit: <@KaZeR> complaining about navit.xml or complaining about plugin loading? 08:05 #navit: < naggety> plugin loading 08:08 #navit: < naggety> Everybody here program with vim? xD 08:12 #navit: < naggety> done 08:12 #navit: < naggety> https://stackoverflow.com/questions/21028690/how-do-i-change-the-working-directory-for-an-eclipse-run-configuration 08:13 #navit: < naggety> Now I get: (navit:10026): Gtk-WARNING **: cannot open display: 08:13 #navit: < naggety> :( 08:14 #navit: <@KaZeR> export DISPLAY=:0 08:14 #navit: <@KaZeR> :) 08:14 #navit: <@KaZeR> and vim ftw :D 08:16 #navit: < naggety> working! 08:16 #navit: < naggety> thank you kazer 08:17 #navit: <@KaZeR> :D 08:17 #navit: < naggety> what is that display var? 08:18 #navit: <@KaZeR> that's how apps know where to send the window content 08:18 #navit: <@KaZeR> if you have a dual monitor display, you can specify 0.0 or 0.1 for example 08:19 #navit: <@KaZeR> you can also have completely different displays running (different users, different window manager) at the same time. in this case you can use 0, 1, etc 08:19 #navit: <@KaZeR> the DISPLAY thing is not navit specific, it's for all Xorg applications 08:20 #navit: <@KaZeR> if you ssh to a machine and want to start a graphical app from the ssh session for example, you'll have to set it 08:20 #navit: < naggety> I don't understand why I need to set it for Eclipse and not for running from terminal. But OK. 08:21 #navit: <@KaZeR> that's probably because Eclipse did not propagate it. There's probably an option somewhere, but i haven't used eclipse in years 08:21 #navit: < naggety> I'm going to edit the wiki to indicate how to make this run in Eclipse. Maybe I add a warning about that most navit developers are vim fanatics. 08:22 #navit: <@KaZeR> also, the variable is automatically set when you start a terminal from your X environment. Try "echo $DISPLAY" and it'll be here 08:22 #navit: < naggety> That can scare new developers, but the desire to know it 08:22 #navit: < naggety> xD 08:22 #navit: <@KaZeR> lol 08:22 #navit: <@KaZeR> excellent 08:29 #navit: < jkoan> Hi Kazer and youte 08:29 #navit: <@KaZeR> hey jkoan 08:30 #navit: < jkoan> Yesterday I put navit on Android in the Hands of my uncle. The UX was terrible 08:46 #navit: < naggety> I haven't tried the android version, but gui_internal menu is not intuitive at all 08:54 #navit: < jkoan> The android app is exactly like the computer version. The terrible part was the gui_internal menu 08:55 #navit: < jkoan> And also he had the idea of double tab to zoom in 08:58 #navit: <@KaZeR> afk back in a few hours 09:23 #navit: < naggety> jkoan: many people will have that idea 09:47 -!- naggety [028e5498@gateway/web/freenode/ip.2.142.84.152] has quit [Ping timeout: 260 seconds] 09:51 -!- naggety [028e5498@gateway/web/freenode/ip.2.142.84.152] has joined #navit 10:50 #navit: < jkoan> Thanks naggety for documenting Eclipse inside the wiki 10:53 #navit: < naggety> your welcome 14:15 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 14:39 -!- naggety [028e5498@gateway/web/freenode/ip.2.142.84.152] has quit [Quit: Page closed] 15:07 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:51 #navit: < jkoan> Hacktober yust stared. I will write an article how people can help at navit ;) 15:51 #navit: < jkoan> https://hacktoberfest.digitalocean.com/ 15:58 #navit: < jkoan> Kazer we should create a list of easy tasks for the hacktober then I will include it inside my article 15:59 #navit: < jkoan> But we need to be fast 16:26 #navit: <@KaZeR> jkoan: good point 16:28 #navit: < jkoan> do you want to fill the list? :D http://trac.navit-project.org/report/11 16:30 #navit: <@KaZeR> yep will help 16:32 #navit: < jkoan> only add hacktober2017 tag ;) (and tink to reset the severity to something meaningfull) 16:33 #navit: < jkoan> *think 16:34 #navit: <@KaZeR> yeah. we also need to pick low-hanging fruit so that people can contribute without a really deep knowledge of our codebase 16:34 #navit: < jkoan> yep 16:35 #navit: < jkoan> should we also add short "todos"? 16:37 #navit: <@KaZeR> maybe. like what? 16:37 #navit: <@KaZeR> btw : i just merged the qml2 updates in trunk. Can you try to see if you still get the segfault? 16:39 #navit: < jkoan> i will check 16:39 #navit: <@KaZeR> this might be an easy one for example : http://trac.navit-project.org/ticket/489 17:22 #navit: <@KaZeR> https://github.com/search?l=&q=state:open+label:hacktoberfest&ref=advsearch&type=Issues&utf8=%E2%9C%93 : crap we should maybe use github issues :( 18:05 #navit: < youte> hi 18:08 #navit: < Number6> yeah, I'm surprised that GH Issues isn't being used since the move from SourceForge 18:08 #navit: < Number6> Trac isn't exactly nice to use 18:10 #navit: < Number6> Navit would qualify for a free jira from atlassian as well, btw. Dunno if it's on-prem or atlassian hosted, though. I'd say on-prem 18:17 #navit: <@KaZeR> hey Number6 18:17 #navit: <@KaZeR> one of the reason that we're still using trac is that when asked about the switch from SF to GH, some devs said that they wanted to keep the issues in trac 18:18 #navit: < Number6> ¯\_(ツ)_/¯ 18:18 #navit: <@KaZeR> but it's been over 2 years now, so maybe it's time to reconsider. Maybe we should test it during the hacktoberfest and decide later 18:18 #navit: <@KaZeR> how was greece? did your skin recover from the sunburns? :) 18:19 #navit: < Number6> Greece was amazing, thanks. Getting used to wearing the wedding ring! Thankfully no sunburn, which is a rarity... I was told I would be murdered if I was burnt for the pictures :-D 18:20 #navit: < Number6> How're you keeping? 18:22 #navit: <@KaZeR> haha 18:22 #navit: <@KaZeR> things have been busy on my end too. I get less sleep at night. Which *sometimes* mean more time to hang around here :) 18:23 #navit: < Number6> Baby? 18:27 #navit: <@KaZeR> yep 18:27 #navit: < Number6> Congrats! 18:30 #navit: <@KaZeR> thanks :) 18:32 #navit: < youte> my wife like greece 18:32 #navit: <@KaZeR> your life likes pretty much any place :) 18:32 #navit: <@KaZeR> *wife 18:33 #navit: <@KaZeR> jkoan: i've enabled github issues. We should probably use that to gain visibility in hacktoberfest 18:33 #navit: <@KaZeR> youte: this might be worth an announcement somewhere 18:34 #navit: < youte> ? hackoberfest? 18:34 #navit: < youte> we participe hackoberfest? 18:35 #navit: <@KaZeR> we should try to. Could be a good way to get a few contributors 18:39 #navit: < youte> it's a good idea. is there some need about it? do you want that i register us or someting like this? 18:40 #navit: <@KaZeR> from what i've seen we just need to tag tickets on github with the hacktoberfest label. but we should spread the word, so probably post on FB/twitter 18:41 #navit: < jkoan> KaZeR: not github Tickets. It's only about the PRs 18:42 #navit: < youte> ok i need the acces to twitter! 18:43 #navit: <@KaZeR> jkoan: https://github.com/search?q=label:hacktoberfest+state:open+type:issue 18:43 #navit: <@KaZeR> ha crap. Need more sleep :D 18:44 #navit: < jkoan> The rules : 18:44 #navit: < jkoan> To get a shirt, you must make four pull requests between October 1–31 in any timezone. Pull requests can be to any public repo on GitHub, not just the ones we’ve highlighted. The pull request must contain commits you made yourself. Pull requests reported by maintainers as spam or that are automated will be marked as invalid and won’t count towards the shirt. 18:44 #navit: < youte> yes, inmilk give a xanax lol 18:49 #navit: <@KaZeR> wait no. that's issues :) 18:49 #navit: <@KaZeR> issues tagged with the label so that they are easy to find. 18:52 #navit: < jkoan> KaZeR: but also without hacktober, so *you* want to migrate? 18:53 #navit: <@KaZeR> i think that there would be some benefits to migrate. but there's also the question of dealing with the existing issues. And then the question of what happens if someday we want to move out of github 19:33 #navit: < jkoan> We can import them over api, so I think it's also possible to export them 19:34 #navit: <@KaZeR> i'd double check that :) importing is important to get more business. exporting makes you loose business :) 19:38 #navit: < jkoan> Yes, but you also have all issues as rss so there will be a way 19:39 #navit: <@KaZeR> yeah 20:52 #navit: <@KaZeR> jkoan: what would you think of backporting the important and active issues to github? we could do that manually and we could tag them for the hacktoberfest 21:18 #navit: < jkoan> I think this would be to much work which we should spend on other things. Look at Trac2github and convert all. Then we can also clean up them 21:24 #navit: <@KaZeR> i'm concerned that importing all of our trac history would create a lot of noise 23:58 -!- Horwitz [~mich1@p200300800E01B500022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] --- Log closed Thu Oct 05 00:00:13 2017