Back
[01:41:58] <skunkworks> heh - I guess I didn't need to be an ass
[01:45:22] <jepler> heh
[02:04:13] <jepler> I hate desktop stuff
[02:05:06] <jepler> I just spent way too much of my life figuring out how to write scrollkeeper "omf" files, which the internet told me had something to do with getting the gnome help browser to do search and display of html docs from emc
[02:05:23] <jepler> .. but now I just read on gnome.org "Note:Scrollkeeper is dead. Rejoice"
[02:05:36] <jepler> guys, pick a technology and stick with it for a few years!
[02:06:33] <jepler> for some reason it *does* find search terms in hal_intro.html, but in the search results it insists on displaying the title of the page as "nuts"
[02:07:41] <SWPadnos> sounds more like squirrelkeeper
[02:08:34] <jepler> must be
[02:11:23] <jepler> kde help center works slightly better, but as soon as you page with the space bar beyond the bottom of a page, it goes to some erroneous url that typically doesn't exist
[02:12:22] <jmkasunich> manpages forever!
[02:13:31] <jepler> I do like hyperlinks and the promise of full-text search..
[02:13:43] <jepler> but it's just not coming true
[06:36:54] <micges1> micges1 is now known as micges_plasma
[13:42:11] <BJT-Work> jepler: is there an easy way to have the AXIS html or the pdf pop up from the AXIS help menu?
[13:44:18] <jepler> BJT-Work: no. Can't pop up html because it's not in the package. Can't pop up pdf, because there's no way that I know of to open a specific section of a pdf file from the commandline.
[13:45:57] <BJT-Work> could we take the axis.lyx and create a pdf from it as well?
[13:47:11] <jepler> that's an option I hadn't considered
[13:48:55] <SWPadnos> evince has a "--page-label=<label>" command-line option
[13:49:33] <SWPadnos> it's not quite the same as going to an exact paragraph, but it could be useful to get to e.g. the "intro to HAL" section in the integrators manual
[13:49:41] <SWPadnos> (or user manual or wherever it is now)
[13:49:51] <jepler> hmm
[13:50:12] <jepler> but we now invoke the pdf viewer through "see", a program that is standard on both ubuntu and kubuntu and should invoke the user's preferred viewer
[13:50:12] <jepler> and I dunno if our pages have labels..
[13:50:19] <BJT-Work> I see the wheels turning :)
[13:50:26] <SWPadnos> you can use numbers too
[13:50:46] <jepler> page numbers? but those vary.
[13:51:10] <SWPadnos> they should be the same for a given release
[13:51:15] <SWPadnos> err, vary when?
[13:51:32] <jepler> when bjt changes any text or image before the page in question, the page number might change
[13:51:47] <SWPadnos> it means the package build would have to stick new numbers in the .desktop files every time
[13:52:16] <SWPadnos> the point about "see" is a good one though
[13:52:32] <jepler> we could write our own wrapper that invokes evince with --page-label if evince available, otherwise invokes see
[13:52:37] <SWPadnos> I use kpdf whenever I remember to install it, since it's much more intuitive for me
[13:52:38] <jepler> but that seems a bit hostile to kubuntu users who want kpdf
[13:52:46] <SWPadnos> or me :)
[13:53:45] <SWPadnos> (of course, they both do stupid things. evince is silly because dragging should move the view by default, not select text. kpdf is stupid because there is no toolbar icon for "open file", and there isn't even one available to add to the toolbar)
[14:02:15] <BJT-Work> if we made an Axis.pdf it would only be about 16 pages long...
[14:02:42] <jepler> but if we do that, it makes sense to make a Gcode.pdf, so that you can open that directly too
[14:02:46] <jepler> and suddenly you have separate pdfs for each lyx file
[14:03:12] <SWPadnos> if our viewers support multi-file search, that's a good way to do it
[14:04:41] <jepler> it's a pity that evince's commandline doesn't support opening on an internal anchor, rather than just a page
[14:04:54] <BJT-Work> gcode is in the user manual with a quick reference all ready
[14:05:11] <jepler> (as far as I can guess from looking at the poppler api there are ways to do that, but evince doesn't have it exposed to the commandline
[14:05:14] <jepler> )
[14:06:14] <jepler> BJT-Work: the gcode quick reference uses a sickening trick to link to the linuxcnc.org website for the full gcode reference, which doesn't work for people who don't have their machines online and is frankly not a very good solution
[14:06:28] <jepler> (and I dunno if the trick even works; I haven't tried it in ages)
[14:07:11] <BJT-Work> sometimes it works for me
[14:07:14] <jepler> (well, the good news is that the trick still works for me)
[14:07:39] <BJT-Work> I use the user manual it has a page that has a list with links to each one in the manual
[14:08:15] <jepler> I rarely if ever look at the pdfs
[14:08:30] <jepler> (I think it just goes to show this is largely a matter of personal preference)
[14:08:40] <jepler> (this = pdf vs html)
[14:09:03] <BJT-Work> If your not connected to the internet you don't have anything else to look at but the pdfs
[14:09:37] <jepler> that's the question I'm kind of raising: are offline users better off with only html than they are with only pdf
[14:10:09] <BJT-Work> that's a good question :)
[14:11:39] <BJT-Work> the pdfs lack the man pages but the htmls have them ... to me that is a big difference
[14:12:33] <jepler> there are pdf copies of the manpages
http://linuxcnc.org/docs/2.3/EMC2_Manual_Pages.pdf but they're not included in the package because they duplicate what is already available through "man"
[14:12:40] <BJT-Work> if I can't remember how the man page title is spelled like hm2 or hostmot2 I just open up the html to view the list then pick one
[14:14:07] <BJT-Work> no index in the pdf makes it a bit hard to find things...
[14:15:20] <jepler> (incidentally, 'apropos hostmot2' and 'apropos hm2' at the terminal both list some appropriate manpages)
[14:15:35] <BJT-Work> apropos?
[14:15:38] <jepler> yes
[14:15:42] <BJT-Work> what is that?
[14:15:54] <jepler> apropos - search the manual page names and descriptions
[14:16:08] <BJT-Work> ok, that is a new one on me :)
[14:20:16] <BJT-Work> is there something to list the man pages for emc?
[14:20:41] <SWPadnos> apropos emc should list a lot of them
[14:20:43] <jepler> dpkg -L emc2-sim | grep /usr/share/man
[14:20:46] <SWPadnos> heh
[14:22:39] <BJT-Work> does apropos search the description of the man page
[14:22:43] <BJT-Work> ?
[14:22:50] <SWPadnos> [10:16:42]<jepler>apropos - search the manual page names and descriptions
[14:22:57] <SWPadnos> ^^ and descriptions
[14:23:07] <BJT-Work> sorry doing three things at once
[14:23:12] <SWPadnos> me three
[14:24:51] <BJT-Work> anyway to make sure "emc" is in the descriptions of all emc man pages?
[14:25:07] <jepler> only by writing it there
[14:25:09] <SWPadnos> or emc2
[14:25:16] <SWPadnos> yeah. I'd only do it if it makes sense
[14:25:27] <SWPadnos> apropos HAL would also get a lot of them already, I imagine
[14:25:45] <SWPadnos> ("...this is a HAL component ...")
[14:26:12] <jepler> no, most of them don't put that in the description line
[14:27:54] <SWPadnos> oh. I'm thinking ofthe SYNOPSIS maybe
[14:27:54] <BJT-Work> just trying to think of a way a linux newbee could find the info in the man pages...
[14:28:08] <SWPadnos> a linux newbie wouldn't be at the command line, most likely
[14:28:32] <SWPadnos> there was an X-based manpage search/display program way back when
[14:28:44] <jepler> SWPadnos: yelp, the gnome help viewer, is also a really shitty man viewer
[14:29:01] <SWPadnos> that may be the updated version of xman or whatever it is I'm thinking of
[14:29:22] <jepler> s/updated version of/rewritten in total ignorance of/
[14:29:36] <SWPadnos> sure, but equally shitty
[14:29:42] <SWPadnos> new improved shittiness
[14:29:46] <jepler> (sorry, I'm getting my gnome hate on yesterday and today after trying to do something useful with yelp)
[14:30:10] <jepler> I'm sure xman was pretty good once you forgave it for being written toXaw
[14:30:37] <SWPadnos> I think I last used it on a lesstif/motif-based system, so it fit right in
[19:30:08] <micges> seb_kuzminsky: around?
[19:31:39] <CIA-1> EMC: 03jepler 07master * r69ca1cf32c19 10/configs/5axis/5axis.ini: specifying machine geometry makes the preview look right
[19:31:50] <seb_kuzminsky> hi micges
[19:33:29] <cradek> emc2-buildmaster: how do I tell you to kick off your builds?
[19:34:05] <seb_kuzminsky> emc2-buildmaster: commands
[19:34:05] <emc2-buildmaster> buildbot commands: commands, dance, destroy, excited, force, hello, help, join, last, leave, list, notify, source, status, stop, version, watch
[19:34:08] <jepler> cradek: by /query and giving commands like force build lenny-x86-2.3-sim
[19:34:23] <jepler> but I just did that, I think for all the lsaves
[19:34:37] <cradek> ok great
[19:35:09] <micges> seb: so.. after installing 2.3.2 and new firmwares from kirk there is:
[19:35:27] <seb_kuzminsky> new firmwares from... peter?
[19:35:36] <jepler> 2.3.2 is out? somebody should have told me.
[19:35:51] <micges> no direction swapping, no loosing steps other than motor not following
[19:36:45] <seb_kuzminsky> jepler: maybe micges means 2.3.2~pre?
[19:37:00] <micges> yes that what I means
[19:37:07] <micges> and yes Peter :)
[19:37:10] <seb_kuzminsky> ok good ;-)
[19:37:50] <seb_kuzminsky> so you're good, all bugs fixed, except now your stepper motors are getting following errors?
[19:37:54] <seb_kuzminsky> mozmck_work: hi!
[19:41:05] <micges> not following error, rather loosing few steps/sec at 7080 but not loosing at 4800
[19:41:45] <mozmck_work> hi seb!
[19:41:47] <micges> but we traced that rather motor not get such high speed
[19:42:58] <seb_kuzminsky> by "loosing steps", do you mean that emc2 thinks it commanded X steps, but measuring the actual distance the machine traveled indicates that it actually took slightly fewer steps?
[19:43:29] <micges> exactly
[19:44:49] <seb_kuzminsky> i think that's normal for stepper motors, when they're driven too fast for their torque rating and load
[19:45:09] <seb_kuzminsky> it can also mean your accel is too high
[19:45:16] <seb_kuzminsky> you found that by running them slower, the problem went away?
[19:45:25] <micges> It was lowered 2 times already
[19:45:53] <micges> yes, 5000 mm/min works perfectly
[19:47:22] <micges> seb: velocity mode for stepgen also no problems
[19:47:42] <seb_kuzminsky> micges: great! :-)
[19:48:12] <micges> only not traced problem is Nan on ecoder, I hope next week I can test it more
[19:48:34] <seb_kuzminsky> yeah, i'd love to see some more info on that bug report - i couldnt reproduce it here
[19:49:22] <micges> I'll try
[19:53:41] <CIA-1> EMC: 03cmorley 07v2_3_branch * r4b6efe423367 10/debian/changelog: Update changelog about classicladder fix
[19:53:42] <CIA-1> EMC: 03cmorley 07v2_3_branch * r808c71831e15 10/src/hal/classicladder/emc_mods.c: Fix classicladder gui crash
[19:53:52] <micges> seb: one strange thing, two times I've noticed that after few starts of emc2+hm2, hm2 didn't load with no error, after swapping mesa to another PCI everything works ok
[19:54:27] <micges> that was on two different machines
[20:01:05] <seb_kuzminsky> micges: that's super odd
[20:01:59] <seb_kuzminsky> my hm2 test suite here loads and unloads emc2+hm2 22 times, and it's not unusual for me to run that suite dozens of times in a night
[20:02:02] <seb_kuzminsky> brb
[20:56:49] <alex_joni> seb_kuzminsky: something wrong with hardy-amd64-2.3-rt
[20:57:20] <alex_joni> looks like it's checking out git, but that doesn't finish in 1200s
[20:57:32] <seb_kuzminsky> yeah git fetch timed out
[20:57:54] <seb_kuzminsky> that's jepler's build slave
[20:58:15] <cradek> will it just try again?
[20:58:37] <seb_kuzminsky> next time someone commits or we tell it to retry a previous build
[20:58:39] <seb_kuzminsky> want me to do that?
[20:58:49] <cradek> if you like
[20:59:02] <cradek> nothing else is gitting right now, so maybe it'll finish in time.
[20:59:19] <seb_kuzminsky> ok it's running
[21:00:38] <cradek> bbl
[21:00:58] <seb_kuzminsky> seeya
[23:39:09] <mozmck> looks like when I cloned the git repo I only got the "master" branch. how would I add other branches?
[23:44:19] <jepler> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Git#Work_with_branches
[23:47:07] <mozmck> thanks
[23:49:11] <mozmck> hmm, maybe I did have all the branches, because it switched in a split second.
[23:49:33] <mozmck> but when I typed "git branch" it only showed *master