On Wed, 13 Jul 2011 02:20:22 +0200 Kai-Martin Knaak <k...@familieknaak.de> wrote:
> Girvin R. Herr wrote: > > > I keep getting the following: > > > > 536:$gnetlist -g bom xx.sch > > Loading schematic > > [/home/gherr/projects/vds160/original/hardware/dac/docs/xx.sch] > > Backtrace: > > In current input: > > 1: 0* [bom "output.net"] > > In /usr/local/share/gEDA/scheme/gnet-bom.scm: > > 37: 1 (let ((port #) (attriblist #)) (bom:printlist (cons # > > attriblist) port) ...) > > 40: 2* [bom:parseconfig ... > > 40: 3* [open-input-file "attribs"] > > In unknown file: > > ?: 4 [open-file "attribs" "r"] > > > > > > <unnamed port>: In procedure open-file in expression (open-file > > str OPEN_READ): > > <unnamed port>: No such file or directory: "attribs" > > I remember to have been scratching my head on this, when I did my > first BOMs. My students tend to fall into this trap, too -- Even when > they were told they'd need an attrib file. The keyword "backtrace" > suggests a severe crash had happened. I guess, it is a scheme > one-liner to text for existance of the file and issue a newbie > friendly message. Or even better, produce a sensible default file on > the fly. Peter B? John D.? Can you whip up such a line? How about allowing the user to specify the name of the 'attribs' file on the gnetlist command line? Sometimes I would like to produce BOM listings with different sets of fields (e.g., parts list for assembly vs. BOM for other purposes). Regards, Colin _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user