X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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=iyAZgOk4ILNSO6nUV8MNK3ELLTllI1Oe5J04oUKfswo=; b=BiocjivMVdg1nczCiC2IAqz6hMSCsnfligQbE45J+74tEm/Bdr8Btas9AZP7G4+ZqA NvEa3bim3gnUOIEvcLeGWnFUDxFlyTMHWO3Qf7QzxHzL+acHqCZW/uHKLF/2BLyzfWfc zZjoCTEOq8FqtullURgpr0tgMQaQVdGZyhqxwXW3or7guVRPt2Tyql65LiSIvnZHsa/p HZxQVz4QlFqHMqxWMdmkEbV1qI7Z1xN15dNw/pn92sGI4feL47bZi29zq012c+pIb1jy A3L7AR/KCm4k9ZicKMHuqV/zg2KWclJYxiO1uJtR/XYOyBfpOnGtDXEKcmuJgd+hpnpk NnyA== MIME-Version: 1.0 X-Received: by 10.60.132.12 with SMTP id oq12mr21605774oeb.42.1394399716993; Sun, 09 Mar 2014 14:15:16 -0700 (PDT) In-Reply-To: <20140309173951.738798020179@turkos.aspodata.se> References: <20140127234944 DOT 924148045B78 AT turkos DOT aspodata DOT se> <20140128201110 DOT DF7D78045B78 AT turkos DOT aspodata DOT se> <20140129072550 DOT GA24560 AT localhost DOT localdomain> <20140309173951 DOT 738798020179 AT turkos DOT aspodata DOT se> Date: Mon, 10 Mar 2014 01:15:16 +0400 Message-ID: Subject: Re: [geda-user] identical symbol names From: =?KOI8-R?B?4czFy9PFyiDowdLYy8/X08vJyg==?= To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=047d7b47286ece6d7604f432fbf3 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 --047d7b47286ece6d7604f432fbf3 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable > One solution is to use your patch and another is to copy the relevant > sym's to the project directory, possible renaming the files at the same > time. > Yes, but this is more difficult and lessly convenient. Many hand operations and many files in project directory and unable to send= one file scheme, and if =C9=DB=D0 Sheme consists of many files, this will be al= l very confusing. But there will be a lot of copying, where I would like it to be > refencing instead After moving files refifrences are broken. This not very relaible solve. Send this schema another users with reference does not make sense if path to library symbols differs. > if you are using symbols from the cvs (cvs.gedasymbols.org) you'll > will notice that from time to time (by using cvs -q update -dP) > the symbols will change, dissapear, or move to another directory, > That is why the characters are already in the scheme should not be changed, and therefore they need to be copied (inserted) in the schematic :) Also, most(?) geda devs seems to like scheme code instead of c, so > if you come up with some scheme code you'll probably have a greater > chance that your patch will be applied. > The code of read and save files in libgeda wrote on C, my addition to read and save too. But write menu items for example "Update symbol..." need with sheme code. I think, geda developers confirm patch if geda users will support the proposed concept --047d7b47286ece6d7604f432fbf3 Content-Type: text/html; charset=KOI8-R Content-Transfer-Encoding: quoted-printable

=
One solution is to use yo= ur patch and another is to copy the relevant
sym's to the project directory, possible renaming the files at the same=
time.
Yes, but this is more difficult and lessly conve= nient.
Many hand operations and many files in project directo= ry and unable to send = one file scheme, and if =C9=DB=D0 Sheme consists of= many files, this will be all very confusing.

But there will be a lot of copying, where I would like it to be
refencing instead
After moving files refifrences are broke= n. This not very relaible solve.
Send this schema another us= ers with reference does not make sense if path to library symbols dif= fers.
=9A
if you are using symbols from the cvs (cvs.gedasymbols.org) you'll
will notice that from time to time (by using cvs -q update -dP)
the symbols will change, dissapear, or move to another directory,
= That is why the characters = are already in the scheme <= span class=3D"">should not be changed, and therefore they need to be copied (inserted) in the schematic :)

Also, most(?) geda devs seems to like scheme code instead of c, so
if you come up with some scheme code you'll probably have a greater
chance that your patch will be applied.
The code of re= ad and save files in libgeda wrote on C, my addition to read and save too.<= br>
But write menu items for example "Update symbol..."= need with sheme code.

I think, geda developers confirm patch if geda u= sers will support the proposed concept
--047d7b47286ece6d7604f432fbf3--