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=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=bBoGjyD+OWhYIiQtATP6w5o257Tri7GHhdIlI/IJzxc=;
        b=OFmLjVEOYk25XzYly/Mm07oLO9+gd10Fz03Guxe1tl+gaFC30s3qMWrMwJap3+eKxl
         xJvhHh+C0gEHwodTXQihTlyzP7CwpN7X3nRX2becQSualAfS8GMgfzn9oKAbslEFnOQe
         IXZRUkO9o/OTdb17ZdVG8icyAvY+QKwFFF5NCmb0laeRfyE468msyXsm7qxgGWpG0usn
         Dqz4S4o1Glbb6ULCxT+gqeNIKTTLuwpXRdmXq6j8/o2wSSp07hoPIKmZqSbmKW4Wyzww
         uwYd7tnOBIgibIX4tQr8irPpiad9+7mYXNFLg3dVL5HHAqTGr76tJ4bqapHmRY2ZpYYo
         UteA==
X-Received: by 10.28.47.8 with SMTP id v8mr40877238wmv.30.1449743179764;
        Thu, 10 Dec 2015 02:26:19 -0800 (PST)
Date: Thu, 10 Dec 2015 11:26:18 +0100
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] gsch2pcb after refdes-renum? (If implemented
 syncronization detail)
Message-Id: <20151210112618.367ae492449756cbd212e9ae@gmail.com>
In-Reply-To: <F527D101-C0BA-4BCC-A5D3-C6C69AA1DD5F@sbcglobal.net>
References: <56658683 DOT 401 AT envinsci DOT co DOT uk>
	<CALT8Ef4=tMf=WmjYmp-2B3rN0SBmoqF5RkCoWZEm=+2hTBTENA AT mail DOT gmail DOT com>
	<20151207153821 DOT c2ac19e6f24b1776a3595e4a AT gmail DOT com>
	<CD4C755E-8E00-427D-909C-3F762A038844 AT gmail DOT com>
	<20151208091411 DOT c8968b0bedb705765529176c AT gmail DOT com>
	<B2F4DA99-3254-4C97-A408-854445A09C21 AT noqsi DOT com>
	<201512081819 DOT tB8IJBrt022764 AT envy DOT delorie DOT com>
	<20151208205451 DOT bb2478f8722e1a885822689d AT gmail DOT com>
	<201512082019 DOT tB8KJOlP030874 AT envy DOT delorie DOT com>
	<72D9CDFB-BB8D-4A81-9712-2D58F802B900 AT sbcglobal DOT net>
	<86263A11-92E5-402B-95E5-5228B6FE1C65 AT noqsi DOT com>
	<76D5DA43-C966-4881-AA72-B7BEEA74E1AA AT sbcglobal DOT net>
	<91904A65-E452-4F4F-891A-56D61316E499 AT noqsi DOT com>
	<F527D101-C0BA-4BCC-A5D3-C6C69AA1DD5F AT sbcglobal DOT net>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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’re imagining copying in gschem. But a common, useful pattern is, in a shell:
> > 
> > cp page1.sch page2.sch
> > gschem page2.sch
> > 
> > Do this when page2 is similar, but not identical to, page1.
> > 
> > gschem isn’t the only tool that manipulates schematics.
> 
> There is no panacea.
> 
> But, for the case you just described:
> 
> - provide a tool to reset the surrogate keys on a page
> - provide a tool to make the file copy and automatically resets the surrogate keys
> - encode the filename and surrogate key to create the unique ID
> 
> These features won’t work in all cases, but they are much better than doing everything manually.
> 
> Ed

If it is used only for rename I still say it would be better to have some special handling for this case, even if changes should be written in separate file.

Nicklas Karlsson