X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Mon, 19 Oct 2015 15:34:21 -0400
Message-Id: <201510191934.t9JJYLlw030785@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <8EAEFD56-9005-4AF8-B298-77983D29B4C0@noqsi.com> (message from
	John Doty on Mon, 19 Oct 2015 13:30:21 -0600)
Subject: Re: [geda-user] Pin mapping (separate symbols from mappings)
References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018234424 DOT c0551dad9bef0859130239d9 AT gmail DOT com> <36B94694-F2AC-4A75-A8EB-40A1CE9A534C AT noqsi DOT com> <201510182225 DOT t9IMPkxK032763 AT envy DOT delorie DOT com> <20151019003814 DOT f62620bf0fec77e65104c105 AT gmail DOT com> <BED51F9A-F6FF-4A23-B18B-C2EC8BB9DAB6 AT noqsi DOT com> <201510190242 DOT t9J2gl7w009345 AT envy DOT delorie DOT com> <282EF9EF-E103-4101-BB56-A0A365AFFEBE AT noqsi DOT com> <201510190408 DOT t9J48ZbC015157 AT envy DOT delorie DOT com> <F9B802B2-A8F6-4A6F-9429-02161A60B6C5 AT noqsi DOT com> <201510190502 DOT t9J528LM019325 AT envy DOT delorie DOT com> <58E58C85-9493-47DD-AC5B-AD78C33A712A AT noqsi DOT com> <201510191640 DOT t9JGeWb0024375 AT envy DOT delorie DOT com> <4AC7F055-0A26-4DD8-B8F9-8D67F7E36B0A AT noqsi DOT com> <201510191722 DOT t9JHMi7G025782 AT envy DOT delorie DOT com> <EE86E5DE-3251-4B76-B3A1-7FE471FCB539 AT noqsi DOT com> <201510191858 DOT t9JIwMIB029296 AT envy DOT delorie DOT com> <8EAEFD56-9005-4AF8-B298-77983D29B4C0 AT noqsi DOT com>
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


> You forget that one way to make a variant page is "cp page1.sch
> page2.sch; gschem page2.sch".

And now it's path-to-object-in-design is different.  I mentioned that
already.

> Once you're enumerating use cases, trying to come up with a solution
> to each one, you're not thinking flexibility anymore.

Thank you for that negativity.  Please come up with an alternative
that works then.  Make sure it's flexible enough to cover all use
cases, especially the ones we're not enumerating any more.