Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
whitequa1k has joined #qi-hardware
whitequark has quit [Ping timeout: 264 seconds]
cladamw has joined #qi-hardware
xiangfu has joined #qi-hardware
rejon has quit [Ping timeout: 245 seconds]
<Ayla>
do you know how can I grep the output of a program, if that program writes on a single line?
<Ayla>
it writes a progression, and everytime I gain 1%, the line is deleted an rewritten
<wpwrak>
tr \015 \012 ? (or whatever the program uses to delete the line)
<wpwrak>
note that you still may have problems with stdout buffering
<wpwrak>
(and the exact command syntax would be tr '\015' '\012' for the bourne shell)
<Ayla>
wow!
<Ayla>
thank you!
<wpwrak>
was a pleasure :)
<Ayla>
yes, I have problems with stdout buffering :(
<wpwrak>
that's hard to fix
<Ayla>
(I'm trying to add a progression bar to wodim using zenity)
<wpwrak>
you could try running it under script -f then tail -t | tr ...
<wpwrak>
whatever wodim and zenity are ;-)
<DocScrutinizer05>
zenity is great
<DocScrutinizer05>
(cmdline gfx toolkit)
<DocScrutinizer05>
the progress bar is a itsy bit tricky to handle though
<cladamw>
wpwrak, Would it be better to generate *.mod under kicad-lib\modules or localproject\modules ?
<cladamw>
wpwrak, i'm working on linking components/footprints for m1.cmp , meanwhile checking if the footprint have clear mistakes, then just found one. :(
<cladamw>
and the 'make' can auto check a fpd changed, It's good. just make.
rejon has quit [Ping timeout: 265 seconds]
phirsch has quit [Ping timeout: 252 seconds]
phirsch has joined #qi-hardware
wej has quit [Ping timeout: 272 seconds]
wej has joined #qi-hardware
cladamw has quit [Quit: Ex-Chat]
<whitequa1k>
pabs3: thanks
Ayla has joined #qi-hardware
lekernel has quit [Remote host closed the connection]
<wpwrak>
cladamw: lemme port the PDF generator for footprints, so that we can have a catalog, too
<cladamw>
wpwrak, alright, sounds good. that way can be good to search.
<cladamw>
wpwrak, when i am doing 'match' work , it's a boring work to match since my brand memory doesn't good enough to recall. So I still open Fped to see their shapes. :(:-)
<wpwrak>
yeah, we need better names
<wpwrak>
if you go beyond thing like 0603 or QFN32, it gets difficult very quickly
<wpwrak>
it would also make sense to have list of all the parts we know, with recommended footprint and recommended symbol
<wpwrak>
e.g., YAGEO R123XYZ456 R 0603
<wpwrak>
then we could feed this data in to kicad, to make things a little easier
DocScrutinizer has quit [Ping timeout: 244 seconds]
DocScrutinizer05 has quit [Ping timeout: 240 seconds]
DocScrutinizer05 has joined #qi-hardware
DocScrutinizer has joined #qi-hardware
<cladamw>
yes, btw, since I had have wiki page with package, it's okay, but it's better to edit such data filled in sch's field. :-)
<wpwrak>
the more thing you don't have to look up manually, the better :)