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=20161025;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=XN9ITRkwbLK5zUk9/nTwcFT/LRAz0YuUs1+DR5ntb4M=;
        b=LnA2k74sqE56qsXTNE++u84QvLzmLByxyze/AlOCq1RGFP+6Ui0mFUoJrKjpxzIR13
         XrVHnIVsF+tkzwrgVAPsmOsFMZoeUPiJuxLaxBBWtN/Xzvfu08lDkXevjPLqBjbzNMqS
         AFbUwJNPHd+ti3dyDrBT39Eq56nNggg8wbP8T7uu3cKiMXoq8KhXPXXYtBU9K+6FzPKs
         /5EEIdkQOH0r10aRuYLOTQP+HBXe1qzeUfxzAvKto97evWtKK6WYiILzmJLLmlqmsTHf
         iwx1/Cub8jQkBqx9SWlBLsC4rBF7mhjsKiGQyr25AzbLP2V7517GzHxw2RvZQGRF8CpK
         dXjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=XN9ITRkwbLK5zUk9/nTwcFT/LRAz0YuUs1+DR5ntb4M=;
        b=gcjfxmxxyx1LukTykaTb9vpIYuyhYlCkeIGagPZCFFOqcntKYfPLNNVxP1hk+W79GY
         s/QGwin7d1PxW5TRDzZtUegpqQZPhaNe5yZBfUC39fOc5UmtwfghM8vwcHZemnxY1QOP
         qsAQXP0u/6m/spWe2M5pEDTCjD5l3EGZpBZgoZ/qzLQvw3FIOzeOpuHVtFQclJCJ7Bbv
         vGtwHOCBcK7srtYdAdwfxo7rKwZV4fxET139V1AFvCBbRbHxXhKQflGOcyeB4817RqmE
         P3g4P63jDT5jEV6NQPss5uTUz54mi5ZgBHzkgP7bLS6V2HX53HirjqBCxGdze8DrUGS+
         U3Yg==
X-Gm-Message-State: AKGB3mJIJUXTKBmldtVxugWr5S1XZ2DJ9SCGtrV9wGkpf6Yxq45Ne15Q
	T3hbi5c2tqwm8CBJqVyqs4r7ww==
X-Google-Smtp-Source: ACJfBovHpQlQMv83ZPtXTd/cRqx+pzvQrxBvbTcwbbi5mfIs4zPRYZfr5b8yPfeQyqS/Hsb60OEtCQ==
X-Received: by 10.46.29.11 with SMTP id d11mr27859951ljd.24.1514930994046;
        Tue, 02 Jan 2018 14:09:54 -0800 (PST)
Date: Tue, 2 Jan 2018 23:09:50 +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] why pinnumber in sym pins?
Message-Id: <20180102230950.cbefc3e2b79ca9655c9957bb@gmail.com>
In-Reply-To: <alpine.DEB.2.20.1801022222590.16512@nimbus>
References: <20171226122009 DOT 366BF804CEDE AT turkos DOT aspodata DOT se>
	<alpine DOT DEB DOT 2 DOT 20 DOT 1801022021340 DOT 14184 AT nimbus>
	<20180102213205 DOT 4565128f84cb6f27ef88033d AT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 20 DOT 1801022222590 DOT 16512 AT nimbus>
X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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 Tue, 2 Jan 2018 22:31:01 +0100 (CET)
Roland Lutz <rlutz AT hedmen DOT org> wrote:

> On Tue, 2 Jan 2018, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via 
> geda-user AT delorie DOT com] wrote:
> > The default then not pinnumber identifier is available could be pinlabel 
> > or default could be to used pinnumber but no pinlabel in symbols.
> >
> > Schematics are read by human so it make sense to use pinlabel as 
> > identifier.
> 
> Erm...
> 
> The pinnumber *is* the identifier.  If you don't like the term 
> "pinnumber", call it something else, like "pin identifier".

Yes I thought about it a while and come to the conclusion instead of leaving out pinnumber and use pinlabel as identifier pinlabel could be left out and pinnumber made visible with the information usually written in pinlabel. I did not think about it first.

Like this:
  1. No pinlabel.
  2. Pinnumber with the information usually written in pinnumber.