geda-gnetlist 1:1.6.2-3 / etc / gEDA / system-gnetlistrc

; 
; Init file for gnetlist
;

;  ;'s are comments
;  keywords are case sensitive (guile feature)
;  mode strings are case sensitive
;  colors are not case sensitive 
;  

; gnetlist-version string
;
; Specifies the version of this file.  This number is used to make sure 
; that the rc file is compatible with the version of gschem that is 
; being run. The end user should *not* change this value.
;
(gnetlist-version "20110115")

; Setup data path variables.  
;
; Contains all paths needed for gnetlist
(define gedadata (getenv "GEDADATA"))
(define gedadatarc (getenv "GEDADATARC"))

; net-naming-priority string
;
; Specifies which netname has priority if a net is found with two names.
; If this variable is set to "netattrib" then any netname specified with the 
; net= attribute is used as the netname.  Likewise if this variable is set to
; "netname" then any netname conflict is resolved using the netname= value.
;
(net-naming-priority "netattrib")
;(net-naming-priority "netname")

; hierarchy-traversal string
;
; Decides if the hierarchy is traversed or not.  If this is disabled then
; gnetlist will not go down searching for any underlying sources
;
(hierarchy-traversal "enabled")
;(hierarchy-traversal "disabled")

; hierarchy-uref-mangle string
;
; Controls if uref names are mangled to make them uniq when traversing 
; down into the hierarchy.  If this is disabled then urefs are not changed
; and it is the user's responsibility to make sure they are unique.
; If you disable this, you really are taking your netlist's life into your
; own hands.  You *MUST* have unique urefs throughout the entire hierarchy
; or bad things might happen.  Also you cannot reuse underlying schematics.
;
(hierarchy-uref-mangle "enabled")
;(hierarchy-uref-mangle "disabled")

; hierarchy-netname-mangle string
;
; Controls if net names are mangled to make them uniq when traversing 
; down into the hierarchy.  If this is disabled then the net names are not 
; changed and it is the user's responsibility to make sure they are unique.
; If you disable this, you really are taking your netlist's life into your
; own hands.  This basically has the effect of making all same named nets
; in the entire hierarchy be electrically connected.  Hope you know what you
; are doing.
;
(hierarchy-netname-mangle "enabled")
;(hierarchy-netname-mangle "disabled")

; hierarchy-netattrib-mangle string
;
; Controls if net created by using the net= attribute are renamed to make 
; them uniq when traversing down into the hierarchy.  If this is disabled 
; then the net= created nets are not changed.  This feature is handy to have
; global nets which spawn the entire hierarchy (like power or ground nets). 
; Please make sure you know what you are doing.
;
(hierarchy-netattrib-mangle "enabled")
;(hierarchy-netattrib-mangle "disabled")

; hierarchy-uref-separator string
;
; Specifies what the separator string between the various hierarchy tags
; for all urefs.  This string can also be "" (empty) to specify that no 
; chars should be used.  This keyword is ignored if hierarchy-uref-mangle 
; is disabled (though a default "/" is used in this case, and then all the
; internal mangling is removed so it is not seen by the user).  This keyword
; is used in conjunction with the respective hierarchy-*-order keyword.
;
(hierarchy-uref-separator "/")
;(hierarchy-uref-separator "")

; hierarchy-netname-separator string
;
; Specifies what the separator string between the various hierarchy tags
; for all nets (excluding net= nets, see below for those).  This string can 
; also be "" (empty) to specify that no chars should be used.  This keyword 
; is ignored if hierarchy-netname-mangle is disabled.  This keyword
; is used in conjunction with the respective hierarchy-*-order keyword.
;
; This keyword is also fairly coupled with hierarchy-uref-separator and
; hierarchy-netattrib-separator so you will probably have to change those
; to get the wanted hierarchy naming.
;
(hierarchy-netname-separator "/")
;(hierarchy-netname-separator "")

; hierarchy-netattrib-separator string
;
; Specifies what the separator string between the various hierarchy tags
; for net= created nets.  This string can also be "" (empty) to specify
; that no chars should be used.  This keyword is ignored if 
; hierarchy-netattrib-mangle is disabled.  This keyword is used in 
; conjunction with the respective hierarchy-*-order keyword.
;
(hierarchy-netattrib-separator "/")
;(hierarchy-netattrib-separator "")

; hierarchy-uref-order string
;
; Specifies the order in which the hierarchy tags are applied to all 
; urefs 
;
(hierarchy-uref-order "append")
;(hierarchy-uref-order "prepend")

; hierarchy-netname-order string
;
; Specifies the order in which the hierarchy tags are applied to all 
; regular nets
;
(hierarchy-netname-order "append")
;(hierarchy-netname-order "prepend")

; hierarchy-netattrib-order string
;
; Specifies the order in which the hierarchy tags are applied to nets created
; using the net= attribute
;
(hierarchy-netattrib-order "append")
;(hierarchy-netattrib-order "prepend")

; unnamed-netname string
;
; Specifies the default string which is placed in front of all nets that 
; have not been explicitly named by the user (using the netname= attribute 
; in the schematic).
;
(unnamed-netname "unnamed_net")

; unnamed-busname string
;
; Specifies the default string which is placed in front of all buses that
; have not been explicitly named by the user.
; (This is not currently useful, since gnetlist does not netlist buses).
;
(unnamed-busname "unnamed_bus")

;
; End of mode related keywords
;


;
; Start of path related keywords
;

;
; End of path related keywords
;

; world-size width height border
;
; Specifies the size of the world and a border 
; Be sure all inputs are reals (floats/doubles) and don't try to reverse
; the values: to get a portrait mode.  Code to support that needs to be added
; The code that implements this automatically transforms the dimensions into
; the proper aspect ratio.  All units are in inches.
; This is not the paper size.  That is specified elsewhere.  End users should
; not change this at all
;
(world-size 120.0 90.0 1.0)
;(world-size 60.0 45.0 1.0)