On 09/23/2012 05:24 AM, fred wrote:
...Or am I still missing something?
>
Yes - I think so.
As I think I mentioned originally - if you "use *" you can ineed do the
search as you describe.
But that messes up the current in use list. I dont want to keep losing
that list just to search for something I might not even find.
(I have already developed my own libraries and am slowly populating them
by the way - it seems pretty easy in eagle)
>
You might write a small parser that for example, works like this:
cd ~/eagle-6.4.0/lbr; ls | lbr_parse would match *80??FIO, just
an arbitrary choice, match whatever regx is appropriate for your search.
Obviously, all the other xml sections relating to the symbol name match
would be extracted as well. Then my_sub_lbr would have your matched
search item appended to the file.
This assumes, of course, that you are using an os that doesn't cripple
your access to the filesystem in some perverse way...Linux or Unix in
this example. Cygwin if you "must" run Windows.
-bill
On 09/23/2012 05:24 AM, fred wrote:
...Or am I still missing something?
>
Yes - I think so.
As I think I mentioned originally - if you "use *" you can ineed do the
search as you describe.
But that messes up the current in use list. I dont want to keep losing
that list just to search for something I might not even find.
(I have already developed my own libraries and am slowly populating them
by the way - it seems pretty easy in eagle)
>
You might write a small parser that for example, works like this:
cd ~/eagle-6.4.0/lbr; ls | lbr_parse would match *80??FIO, just
an arbitrary choice, match whatever regx is appropriate for your search.
Obviously, all the other xml sections relating to the symbol name match
would be extracted as well. Then my_sub_lbr would have your matched
search item appended to the file.
This assumes, of course, that you are using an os that doesn't cripple
your access to the filesystem in some perverse way...Linux or Unix in
this example. Cygwin if you "must" run Windows.
-bill