X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=VQ2sQs7qy4OseuBHRs1Dkoz3Fm703ux3+inb9C95vxA=;
        b=KYnq5QpHPsTSbSz88mRR5c2UZBj6docv4CSyduLeoKM5DFlH0fRZQQQI17ufs6poBz
         2D0IB/i/PlcA/nYHlbWh79WN8ztnT7RkdZjx9jnSRah4sBQgFkSlqh0RyJQNr6PxVxly
         BcOIZ5U7HBf+Fd+5xFm6F+GtNPpazbmZ8E0ZqhLliCYFJ6ZjnzxrGZY1xvlzWuUI+4gB
         Ay1NrOrwyvJqZMrYgjDBVkO90scE43JyxtNoU/XCFbXGYqVMFqPL1jP16p/eurFAXIO7
         8uSSuVntmaX/V8RpUSw4ITUlQsvVi5c/2vCTWGqNmG6jfnxyWqFf62ChAB9Z2hEVxRhS
         EzOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type;
        bh=VQ2sQs7qy4OseuBHRs1Dkoz3Fm703ux3+inb9C95vxA=;
        b=OkUDvSQcdoCnIh/oLVSxi/4SXTq8VPD7wLEqRLsDwlaPEkpAh/f7XXqFuzZlGAo9Pn
         XXSeSE758KHJWCSYD2Wa0IcDnO3RmPeqGQrLowQ/VzunNigYpv63AneatXQ+GlOu6Lfm
         DyH/SAEaEViG1RUhE1cEuR1O3SeT2MYlIAJB02COjuS9zv2XBEWiji8LRpt9HYxTWw5i
         GdCEt8RqHzsfnXQBYqhXM110U7OK8OJGx0l9U6kAiBQdOgJmsxyjiKajWrZEFoSV61iT
         5WetWxoZWy93/c3ZsROTuN9c7bv17cMCI9CKbGj0600XNxeyMR/jy0Vsj8RsGrKH27wQ
         PRlQ==
X-Gm-Message-State: AG10YOQuHGXex2tAYA8cbPnxv7SHMq3N4Zezxkx3gS1z2EFk9QYmQSG9D9yGMbdRzvyH9uKHfsFCmGmHHDHGHQ==
MIME-Version: 1.0
X-Received: by 10.107.137.26 with SMTP id l26mr6252120iod.141.1453514266948;
 Fri, 22 Jan 2016 17:57:46 -0800 (PST)
In-Reply-To: <20160122223314.954B681053E4@turkos.aspodata.se>
References: <20160102091556 DOT BBC6D809D79B AT turkos DOT aspodata DOT se>
	<CAJXU7q_Zwyfpcb4g00QCFNTjQ9Le2Tm8WjKz3CKMnNXb7gMceg AT mail DOT gmail DOT com>
	<20160102131252 DOT F383A809D79A AT turkos DOT aspodata DOT se>
	<CAMvDHVCi5wR78jybhOEG0EmKyqWVpeaoYFuyWkWSrtkxF7kXQw AT mail DOT gmail DOT com>
	<20160121144142 DOT 2703D81053E4 AT turkos DOT aspodata DOT se>
	<20160121161958 DOT GB4788 AT localhost DOT localdomain>
	<20160121174016 DOT E995881053E3 AT turkos DOT aspodata DOT se>
	<20160121184048 DOT GD4788 AT localhost DOT localdomain>
	<20160121193929 DOT 11E5881053E4 AT turkos DOT aspodata DOT se>
	<CAMvDHVB1jRzDJ_sJnpBwT-YEDSphiLLVVsDYW+jKW0NNKTq2dA AT mail DOT gmail DOT com>
	<20160122110632 DOT D67C281053E3 AT turkos DOT aspodata DOT se>
	<BFF6073F-1240-4BE6-A0BB-92350870F3C4 AT noqsi DOT com>
	<20160122223314 DOT 954B681053E4 AT turkos DOT aspodata DOT se>
Date: Fri, 22 Jan 2016 17:57:46 -0800
Message-ID: <CAOP4iL2-rnPiLjFN=_nsiQSx=D6ZbDhr-RK7hyYtvLpzDaV_oA@mail.gmail.com>
Subject: Re: [geda-user] sym precedence ordering (was: should we broaden scope
 of libgeda)
From: "Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=001a113fc4048ebcb20529f6a932
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

--001a113fc4048ebcb20529f6a932
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 22, 2016 at 2:33 PM, <karl AT aspodata DOT se> wrote:

>
>
> Though, in the lib.browser, you can choose any one, even the ones
> deep down the list. Then when you late open the sch, you'll get the
> wrong syms. And that is not how it should be, precedence order or not.
>
> I propose that the C (component) syntax be augmented whith some
> optional selector, so can get  the right one.
>
>  In
> $ grep ^C regulator.sch | grep -i diode | head -1
> C 16600 76400 1 0 0 diode.sym
>
> why not append e.g. author="Karl Hammar", to select the diode.sym
> which has the attribute given.
>
> Regards,
> /Karl Hammar
>
> -
>

Thats how IP-Xact does it. It has fields for component name, library name
and vendor name for that reason.
Search paths should only be used to initially find a component and never
used to load a schematic. Two designers
with the same schematic and different rc files will have two different
designs


John Eaton

--001a113fc4048ebcb20529f6a932
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Jan 22, 2016 at 2:33 PM,  <span dir=3D"ltr">&lt;<a href=3D"mail=
to:karl AT aspodata DOT se" target=3D"_blank">karl AT aspodata DOT se</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><br>
<br>
Though, in the lib.browser, you can choose any one, even the ones<br>
deep down the list. Then when you late open the sch, you&#39;ll get the<br>
wrong syms. And that is not how it should be, precedence order or not.<br>
<br>
I propose that the C (component) syntax be augmented whith some<br>
optional selector, so can get=C2=A0 the right one.<br>
<br>
=C2=A0In<br>
$ grep ^C regulator.sch | grep -i diode | head -1<br>
C 16600 76400 1 0 0 diode.sym<br>
<br>
why not append e.g. author=3D&quot;Karl Hammar&quot;, to select the diode.s=
ym<br>
which has the attribute given.<br>
<br>
Regards,<br>
/Karl Hammar<br>
<br>
-<br></blockquote><div><br></div><div>Thats how IP-Xact does it. It has fie=
lds for component name, library name and vendor name for that reason.<br></=
div><div>Search paths should only be used to initially find a component and=
 never used to load a schematic. Two designers<br></div><div>with the same =
schematic and different rc files will have two different designs<br></div><=
div><br><br></div><div>John Eaton<br><br><br></div></div></div></div>

--001a113fc4048ebcb20529f6a932--