X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 30 Dec 2015 09:03:41 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: gEDA and it's future with Scheme & Guile was Re: [geda-user] Project leadership In-Reply-To: <41F5814C-CBF1-4F51-8CFA-F9A2F56EC2EF@noqsi.com> Message-ID: References: <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <2297464D-0109-4CA8-98D5-AC33BD0B02C5 AT noqsi DOT com> <73273554-3E38-4F1F-9423-F731753B41D8 AT noqsi DOT com> <41F5814C-CBF1-4F51-8CFA-F9A2F56EC2EF AT noqsi DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 On Wed, 30 Dec 2015, John Doty wrote: > > On Dec 30, 2015, at 12:21 AM, gedau AT igor2 DOT repo DOT hu wrote: > >> >> >> On Tue, 29 Dec 2015, John Doty wrote: >> >>> >>> On Dec 29, 2015, at 11:28 PM, gedau AT igor2 DOT repo DOT hu wrote: >>> >>>>> >>>>> I?ve never found a serious limitation in geda-gaf abstractions. >>>> >>>> I have. See the mailing list traffic of the past few hours. >>> >>> What schematic object have you been unable to capture in the geda-gaf schematics? What circuit have you been unable to design? All I see is complaints about the work flow, not the underlying abstractions. Those are fully up to designing PCBs, ASICs, plumbing, makefiles, ... >> >> Gschem fails to handle (find, zoom onto, list, highlight, etc.) nets by name. > > That?s not a limitation on what you can design. > >> I consider this a bug. It keeps me from, guess, finding, jumping onto nets using the GUI. This, together with another shortcoming about how to handle projects with multiple schs, keeps me from fully exploiting back annotation. >> >> Simplest example: pin 1 of U5 is connected to Vcc, and it shouldn't be. Gschem can't navigate me to all occurances where this happens so that I can easily walk thrhough them and fix them. Instead, I manually have to crawl through all schs and find somtimes very hidden connections (e.g. burried in net attributes of heavy symbols) > > Grep is your friend. The textutils can do 10,000 things with .sch files. No GUI tool will ever be able to do all, or even most of them. So please show me the grep command line that does this RELIABLY. Net segment connections included. net attributes included. Even in non-embedded symbols. Multi sheet designs, hierarchic or not, included. To make sure I stay in accordance with the code of conduct, I will stop posting in these threads until I see such a grep commandline and everyone accepts that it works for all cases; or until everyone accepts it is not possible to construct such a grep command line. > >> >> I know you don't need this GUI feature. I do need it. > > You confuse wants with needs. Yes, you don't want this feature (noone forces you to use it). I do need it. (Do I have the right to know what I need?)