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=majenko.co.uk; s=key1;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=do4AgI6uHqTYWANq0Y8qEPU4nL+m0m2hJfbvso3Yen4=;
        b=Ibjwqbz1MlwVy60LAOFRlw86aK3k9PB0YSsGhRcvjefEoSHwOlLigUC81w1lcpdQe1
         us6jidqzycRi2xHn36E1Js9PjzYLh4vnowsN4/U20UUn/oMDhP3pt0blI9pE/s+2jhDz
         O48yF8v4f50tES/yJhMbzrMrghuaLgIQDMntR84bAhl7IKWXNnzBh8z+GBh69+kFcGNa
         Bm33MJA+xuGByS3yCj/j5CBa1ZPBX9WriCC13TuGpkkgQNQ+J7B58GDc3VHHdPc9q77M
         F5tDP2ZzCvjwAQ0jb4kBvMz0pneyZBuCaG9cxuFtgB0/B0+wvzhDw7uqSsC/zqJhNOtK
         N0CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=do4AgI6uHqTYWANq0Y8qEPU4nL+m0m2hJfbvso3Yen4=;
        b=DnlGehtPFvDhb3ArUW1PBE7kf5bP8kLxQyefPvO7mEQxJ4O2hSmqiith0gMQtOlIxI
         +Svpd2zs2DAzhHvjCYRWnkZEdB8gLSiUwNKR76ZRg3OsTCrOFVXR0YeRKzfjY6BQGYTF
         G72laqcanJe84oD25XgY+mmGXjRsSWCVgb36LYGKqFjUcjg7MmOOf0+9LsHEr+atAGSD
         8pGkmwExpNWCLUIyI4QWWF26AtDXKAn/kNre5Q+YGlif8aNMSTSq7kHfTrSnqcaB7VlC
         wLgZhkl8yxw5tNA52//Yc37O8vuXjwn65Sqjf0ZdLKZg0FX5lcUijeVe2x66N6HeAc9x
         ISHg==
X-Gm-Message-State: APjAAAWseIJkvHOz8rXAiKajXkGcEa9t/ElhXNdo5KBszTWfgBhamYbD
	ErSHK0UnXcpulSWayNvw+nrI0TKx2LQ++QhGtQSqiZryedk=
X-Google-Smtp-Source: APXvYqy1gWxoFx8MxhWSmGbbU4BSXAanVvulWsMjQKmZ2Bm49YLha+51s5J8clt1wTbr/d/c+EnYwADQ1Gex90z64ZA=
X-Received: by 2002:ac2:5bde:: with SMTP id u30mr2984238lfn.59.1569358821481;
 Tue, 24 Sep 2019 14:00:21 -0700 (PDT)
MIME-Version: 1.0
References: <e9c8bd38-5517-3086-7c20-9bd92cbc331e AT wavecable DOT com>
 <CAPp8_Dpm3zuzdEv=FRNiuGHoDb=XW87DRVyS7YABc0d43Z_q3w AT mail DOT gmail DOT com>
 <CAPp8_Drs=fP1=TU8zY=JH+x4G-2iy3n4+EaZ9mzpe4EiZfOt0g AT mail DOT gmail DOT com> <87r24531yj DOT fsf AT gag DOT com>
In-Reply-To: <87r24531yj.fsf@gag.com>
From: "Majenko Technologies (matt AT majenko DOT co DOT uk) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Tue, 24 Sep 2019 22:00:10 +0100
Message-ID: <CAPp8_DrGgEm5uWWcMg4qfij6gdAeiuN8rEOkZV4NJJEdvt0-xA@mail.gmail.com>
Subject: Re: [geda-user] Is gEDA no Longer Maintained
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary="0000000000001471be059352d385"
Reply-To: geda-user AT delorie DOT com

--0000000000001471be059352d385
Content-Type: text/plain; charset="UTF-8"

Yeah, those glitches and crashes sure are a pain. If I can work out some
form of IPC for controlling saving and reverting of open files I'll
definitely switch over to it.

On Tue, 24 Sep 2019, 21:40 Bdale Garbee, <bdale AT gag DOT com> wrote:

> "Majenko Technologies (matt AT majenko DOT co DOT uk) [via geda-user AT delorie DOT com]"
> <geda-user AT delorie DOT com> writes:
>
> > So... can anyone give me a quick overview of what's improved in lepton?
> > Things I should look for and marvel at?
>
> For me, the big win is that released versions of gschem would just crash
> from time to time, and had a number of visual "artifacts" when zooming
> in/out, etc... all of which seem to be gone from the current
> lepton-schematic.  Put differently, to me lepton-schematic is just like
> gschem but with fewer annoying bugs.
>
> It may be that there are better gschem bits in git, but as a
> distribution package maintainer I *try* to use the released versions I
> package whenever possible... so I just wouldn't know.
>
> The lepton-eda folk were also happy to accept my contribution of a tEDAx
> output module for getting data to pcb-rnd sanely, and rolled it into a
> new release fairly quickly, which I really appreciated as the primary
> current maintainer of gEDA-related/derived packages in Debian.
>
> Bdale
>

--0000000000001471be059352d385
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Yeah, those glitches and crashes sure are a pain. If I ca=
n work out some form of IPC for controlling saving and reverting of open fi=
les I&#39;ll definitely switch over to it.</div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 24 Sep 2019, 21:40 Bdale =
Garbee, &lt;<a href=3D"mailto:bdale AT gag DOT com">bdale AT gag DOT com</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">&quot;Majenko Technologies (<a href=
=3D"mailto:matt AT majenko DOT co DOT uk" target=3D"_blank" rel=3D"noreferrer">matt AT ma=
jenko.co.uk</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_b=
lank" rel=3D"noreferrer">geda-user AT delorie DOT com</a>]&quot;<br>
&lt;<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank" rel=3D"noref=
errer">geda-user AT delorie DOT com</a>&gt; writes:<br>
<br>
&gt; So... can anyone give me a quick overview of what&#39;s improved in le=
pton?<br>
&gt; Things I should look for and marvel at?<br>
<br>
For me, the big win is that released versions of gschem would just crash<br=
>
from time to time, and had a number of visual &quot;artifacts&quot; when zo=
oming<br>
in/out, etc... all of which seem to be gone from the current<br>
lepton-schematic.=C2=A0 Put differently, to me lepton-schematic is just lik=
e<br>
gschem but with fewer annoying bugs.<br>
<br>
It may be that there are better gschem bits in git, but as a<br>
distribution package maintainer I *try* to use the released versions I<br>
package whenever possible... so I just wouldn&#39;t know.<br>
<br>
The lepton-eda folk were also happy to accept my contribution of a tEDAx<br=
>
output module for getting data to pcb-rnd sanely, and rolled it into a<br>
new release fairly quickly, which I really appreciated as the primary<br>
current maintainer of gEDA-related/derived packages in Debian.<br>
<br>
Bdale<br>
</blockquote></div>

--0000000000001471be059352d385--