I just pushed out a point release of Xastir 2.1.6.
Users of the master branch code will see no difference --- it's just that
we need a numbered release available so that pacakge maintainer can get
the benefit of all the changes that have happened since 2.1.4 back in July
of 2019.
If you're a
On Fri, Apr 17, 2020 at 03:22:02PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> I updated scripts/get-NWSdata.in in my Github/Xastir repo.
>
> Don't recall whether I need to go update my repo first before I do a
> pull request. Might be easier / faster if you snag
I updated scripts/get-NWSdata.in in my Github/Xastir repo.
Don't recall whether I need to go update my repo first before I do a
pull request. Might be easier / faster if you snag that one-line
change out of that repo and apply it directly. I tested the resulting
script and it works fine.
On Fri,
FWIW, I went to "fix" the script today so that the fixed version would be
in the 2.1.6 point release, only to find that the URL we have been using
all along is working again. So no fix needed. Problem was on their end.
On Sun, Mar 29, 2020 at 11:32:27AM -0400, we recorded a bogon-computron
Yes please.
On Fri, Apr 17, 2020 at 9:16 AM km5vy Tom Russo wrote:
>
> On Fri, Apr 17, 2020 at 08:54:30AM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > Sure.
>
> I can do that tonight if we're all in accord. It's a fairly lightweight
> process anymore to push
On Fri, Apr 17, 2020 at 08:54:30AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> Sure.
I can do that tonight if we're all in accord. It's a fairly lightweight
process anymore to push out a release on github.
> On Fri, Apr 17, 2020 at 8:33 AM Tom Russo wrote:
> >
On Fri, Apr 17, 2020 at 08:31:34AM -0700, we recorded a bogon-computron
collision of the flavor, containing:
>
> Ah.. ok. Seems like a good first step would be to tag a new Xastir release
> and tell the Debian maintainer to start with that.
Yes, a point release seems in order.
> On
Ah.. ok. Seems like a good first step would be to tag a new Xastir
release and tell the Debian maintainer to start with that.
--David
KI6ZHD
On 04/17/2020 08:27 AM, Tom Russo wrote:
On Fri, Apr 17, 2020 at 07:14:19AM -0700, we recorded a bogon-computron collision of
the flavor,
Zoom levels are to some extent already tied to function keys. Most other
things don't have F ket or ALT key sequences.
you may be able to create some macros (xdotool) that you invoke with the
keyboard, but that could be dependent on the specific location of windows,
number of entries in a list,
Is it possible (for a non-programmer) to use a streamdeck with Xastir to do
things like start/stop/re-start interfaces, change zoom levels, etc? In a
mobile application I can’t mess around with mouses and menus, but can click a
button on a keyboard. Specifically a streamdeck connected to a Pi
GCC: Forcing coders to write better code since 1987.
On Fri, Apr 17, 2020 at 7:14 AM David Ranch wrote:
>
>
> Just saw this notification on the Xastir list. Seems like GCC-10 is
> going to require a lot of different Linux programs to do some clean ups.
>
> --David
> KI6ZHD
>
>
>
Just saw this notification on the Xastir list. Seems like GCC-10 is
going to require a lot of different Linux programs to do some clean ups.
--David
KI6ZHD
Forwarded Message
Subject:Bug#957970: xastir: ftbfs with GCC-10
Resent-Date:Fri, 17 Apr 2020 11:38:07
12 matches
Mail list logo
