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=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=CuqxS4f5zAU34pdBievhlDvp0f99s sZRnEuVN63PDWc=; b=Wi1BrnMAx4VNYgUYkPuq35GdJbBUG7Nfhs4mIvu6OUtmj P2zbZRXsJk16AA07Y7AQQUqNE+CoD6oJyt0n7jZhoXUQOi0v1+JQbSQ8Wj7ljA9U 8Fq9EEI3tkdcL16r1Jit8O8La9sBTWDiJuZ1Wta74SToz8ku4chlNJA/2KkNdk7V xiBDXvi6/jtwKQ1s8PwnoXGmvJNFoHmhLwIKeaAafF/+ThjnSXU9hRP3aZ/2ut+i KnDh9+OYrviKt/1AkuWoubq/n0y1fqP0jeakCps6tiK6uIKAOddB+NwmFqnmmrmq HZLtZbKDUe37VkWqn+JjxurZV7sCnJ1KE46bCJVcg== X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=CuqxS4 f5zAU34pdBievhlDvp0f99ssZRnEuVN63PDWc=; b=wH6C4TjQmirrm/FpEJxvEX /oQ4j4L2+ZOE9V/W8CXdZD3TlD6xig7wYfZAwMkJzT2LmZOXDx+ZTv4TOuuMx1Bj 3fkZdxZS7qlUU5Cj3jx44r1Ti6OLBVPpm1+hlEWAyQRpsP+HtLgoDoKyf/T4TgOK s1QuPeHC3Hzel/w70s5ZnI09op8t54Ze0jUv4mDwimBrO0tTmupLp09C2LnSmX4l zzAXlAwy4VZ9Qkdimebge6kReQAn5UXK+ClvhhKMn3DyyjMC9/qmBottHKB7Ln7A HxjS4HWK/9+mpmCueKImoxvU1rEPvBg9NB1CPIYyPsRmL6YrRgKA0Ug8ZN3NEHAA == X-ME-Proxy:

X-ME-Sender: Message-Id: <1531368952.2286296.1438062920.4E165C0D@webmail.messagingengine.com> From: "Edward Hennessy (ehennes+oss AT fastmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_153136895222862960" X-Mailer: MessagingEngine.com Webmail Interface - ajax-957169fa Subject: Re: [geda-user] adventures using arrows (for documentation), or cross my lines In-Reply-To: <20180712035816.26F69841DE80@turkos.aspodata.se> References: <20180702125528 DOT D32CF81F76FE AT turkos DOT aspodata DOT se> <20180709204944 DOT GA921 AT debian DOT lokolhoz> <1531286153 DOT 3131974 DOT 1436831304 DOT 36E05F01 AT webmail DOT messagingengine DOT com> <20180711182359 DOT 227FE81F772D AT turkos DOT aspodata DOT se> <1531363092 DOT 2191172 DOT 1437992056 DOT 3A4E875E AT webmail DOT messagingengine DOT com> <20180712035816 DOT 26F69841DE80 AT turkos DOT aspodata DOT se> Date: Wed, 11 Jul 2018 21:15:52 -0700 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 This is a multi-part message in MIME format. --_----------=_153136895222862960 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Wed, Jul 11, 2018, at 8:58 PM, karl AT aspodata DOT se wrote: > Perhaps the only place it is useful to have width = 0 is in filled > paths, and I'm guessing that paths are not much used, so one could > break compatibility just there without too much breakage. Or, maybe, create a separate object for an enhanced path? Leave the old "H" path alone. It would provide an opportunity to make a clean break and redesign the path object without the breakage. Ed --_----------=_153136895222862960 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"

On Wed, Jul 11, 2018, at 8:58 PM, karl AT aspodata DOT se wrote:

Perhaps the only place it is useful to have width = 0 is in filled

paths, and I'm guessing that paths are not much used, so one could

break compatibility just there without too much breakage.

Or, maybe, create a separate object for an enhanced path? Leave the old "H" path alone. It would provide an opportunity to make a clean break and redesign the path object without the breakage.

--_----------=_153136895222862960--