Re: xlog hamlib functionality with model 2
On 2/10/21 3:25 PM, Dr. Karsten Schmidt wrote: Hi Andy, it would be really cool, if You are able to find an anwser to my problem. Kind regards 73 Karsten Hi Karsten, I shall try. :-) 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: xlog hamlib functionality with model 2
Hi Andy, I finally got to the bottom of this. There were two serial port parameters that are incorrect in hamlib for my radio, such that I have always had to use the manual entry for stop_bits and handshake in most applications. Do the hamlib default settings overwrite the manual ones I wonder? I finally corrected these in the hamlib sources and rebuilt our hamlib package. Without the manual settings being needed all works correctly as you describe when using the rig selection dialogue. I have sent the corrections upstream to hamlib, so while this fixes my TS-450S issue it won't help Karsten. Thanks for your help, 73 Barry I think I sent this using the wrong account previously, if it appears in duplicate please ignore one of them. HI Barry, I'm happy to hear that the problem has been resolved. Thanks for writing to close the loop in case others see the same issue. I have reproduced the issue regarding xlog and Quisk. I will need time to look at it in more detail. I'm hopeful that I can look at it in the next few days or perhaps this coming weekend. Have fun and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: xlog hamlib functionality with model 2
On 2/7/21 7:00 PM, Barry Jackson wrote: On 07/02/2021 17:04, Dr. Karsten Schmidt wrote: Hi Barry, yes I have a similar problem. A "2" in the GUI ist stored as "1" in the config file. -K 73 de dg1vs Gentlemen, Please do not edit the config file directly. Please use the GUI or you will cause yourself problems, as you've noticed. How the data is stored in the xlog.cfg file is of no consequence as long as xlog can read/write it and behave correctly. Through the GUI, I have seen no failure. If you do things through the GUI and see a functional misbehavior, please let me know the steps to reproduce it. When I tried it, there was no problem with xlog 2.0.20 and hamlib4. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: xlog use-after-free
On 1/8/21 1:48 PM, Chris K2CR wrote: Hello, all. I've been experiencing crashes in xlog as packaged with debian. I tried the latest CVS as well, but the behavior didn't change. Some crashes have been reproducible. I ran xlog with valgrind and tracked it down to a use-after-free scenario in the gtk open dialog. Please see the attached diff, which solves the crash for me and generated a (mostly) clean valgrind output. Without this patch, lp->type was being assigned even though lp was just freed in the call to log_file_close(). Thank you and 73 -Chris K2CR Hi Chris, I think it is cool that you took the time to run valgrind on the xlog executable - thanks! The version of xlog packaged with Debian is 2.0.14 and that is ancient. Version 2.0.19 can be downloaded here: http://download.savannah.nongnu.org/releases/xlog/ Latest CVS will eventually become version 2.0.20 and I'm actively working on it now. Let me look at your patch and weave it into my latest version. BTW, is there a way that I can reliably repeat the crash scenario? Thanks(!!), and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib-4
On 11/26/20 6:36 PM, Barry Jackson wrote: On 31/10/2020 02:55, Andy Stewart wrote: HI Barry, -- Let me know if you continue to have issues. Hi Andy, OK I finally found time to have another look at this. I started by rebuilding against a recent hamlib snapshot. Hi Barry, I need very specific details in order to attempt to reproduce this problem. * if the xlog version is not 2.0.19, please try again with that version, which is the latest * Exact version of hamlib (ideally, the link from where you downloaded it) * Exact type and version of Linux * If you did any custom configuration when you compiled hamlib and/or xlog, I'll need those instructions as well * I don't have a TS-405S, so I may not be able to reproduce the problem, but I will try. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib-4
HI Barry, The following stack worked for me: * Andy's Ham Radio Linux, version 24c+ (my next dev release), which is based on Ubuntu 18.04.* * Xlog 2.0.19 * hamlib-4.0-rc2 * ICOM 7300 on /dev/ttyUSB0 * I started with a blank ~/.xlog directory. * I started Xlog and reconfigured hamlib, taking care to choose the updated rig number. * When the POWER entry is listed in the QSO entry window, it will say UNKNOWN if the rig power is set to 0, but otherwise, it reflected the rig power setting. Try ctrl-Y ctrl-K for a quick erase/update of the QSO entry window. I was able to duplicate the condition of hamlib hanging xlog, but that always happens when you turn off the rig with hamlib enabled and Xlog is still running. Xlog eventually comes out of it. This isn't ideal, but it is nothing new for Xlog, either. Turning the rig on again causes the software to be happy again. Let me know if you continue to have issues. 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib-4
On 10/30/20 10:56 AM, Barry Jackson wrote: On 30/10/2020 13:41, Andy Stewart wrote: I recommend moving your config file to a safe place and restarting xlog with no config file, as an experiment. Yes I did this effectively by using a new user and later by just re-naming the ~/.xlog dir. That allows the program to start without crashing, but would lock up when trying to enter settings in hamlib config dialog when using hamlib-4.0 HI Barry, Did you notice in the release notes for hamlib-4.0-rc2 that the model numbers for all of the rigs have changed? https://sourceforge.net/projects/hamlib/files/hamlib/4.0%7Erc2/ My question: are you using the correct value for the model of rig that you are using? Did you try using the rigctl program to isolate potential hamlib issues from potential xlog issues? I have not tested xlog with hamlib-4.0. On Ubuntu 18.04, I just compiled xlog with hamlib-4.0 and saw no issues. Note: I have not tested it with my rig (yet). That's next. I just built hamlib-4.1 and xlog against it and I can now edit the hamlib settings without a hang or crash, however rig control fails to work at all, even using a manual config string for the port. It just fails to communicate, looking at the hamlib tracker in xlog. Where are you finding hamlib-4.1? On Sourceforge, I'm finding hamlib-4.0-rc2, which is what I'm currently using for testing the latest version of xlog. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib-4
On 10/29/20 7:06 PM, Barry Jackson wrote: Hello - first visit here! I am having issues with xlog segfaulting when launched on a system that has a config file that was created in an earlier version. Hi Barry, I recommend moving your config file to a safe place and restarting xlog with no config file, as an experiment. I have narrowed this down (I think) to the fact that the new system has hamlib-4.0.0. I have not tested xlog with hamlib-4.0. I filed a bug report about this but have had no response as yet. https://savannah.nongnu.org/bugs/?59362 I'll take a look. By chance I was just looking at this list recent archive and saw some discussion about hamlib and xlog, so here I am. I maintain (or try to) xlog in Mageia. Barry I'm not familiar with Mageia. It is an Ubuntu derivative, and if so, from which version of Ubuntu are you seeing an issue? I've not tested anything past 18.04. Thanks for the report, and 73, Andy Xlog maintainer -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib ...
On 10/15/20 11:38 AM, gliderpi...@protonmail.com wrote: Folks, I compiled from the source the latest release of Xlog 2.0.19 running Ubuntu 20.04 with the latest HamLib 4.1 (http://n0nb.users.sourceforge.net/) and tested it with a Kenwood TS-890S. I found the "Band" frequencies was the only success data transferred from the radio. Xlog was unable to get the data for "Mode", "Power". I tested Hamlib 4.1 and was successful getting these parameters using rigctl on the TS-890S. Has anyone else have any issue using the latest release of Hamlib and Xlog? 73's, Oscar (N6PAZ). Sent from ProtonMail <https://protonmail.ch>, encrypted email based in Switzerland. HI Oscar, Mode should have worked. I'm not sure about power. I have not tested Xlog on Ubuntu 20.*, nor have I tested it with Hamlib 4.1. I would use the Hamlib rigctl program to verify that Hamlib is working correctly. 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
New feature: WSJT-X logs directly to Xlog
HI everybody, I was asked by Joe (K8OD) if it was possible for WSJT-X to add entries directly into Xlog. Fldigi already has this capability. As a test case, I wrote a temporary gasket program that has this functionality. It works! I am now working to incorporate that functionality entirely within Xlog. Have fun and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: 2.0.17 and deprecated GTK APIs
On 2/28/20 10:30 AM, Greg Troxel wrote: Andy Stewart writes: On 2/28/20 9:39 AM, Greg Troxel wrote: I just filed a bug about this; building 2.0.17 on NetBSD with pkgsrc results in a GTK deprecation warning which with -Werror is fatal. I wonder what the path/timeframe is from the 2.0.18 beta to the actual 2.0.18 release. (pkgsrc only packages releases, unless we conclude that an upstream is so troubled that no releases will ever come.) I'd probably update the country file information and that's all. I can't replicate a NetBSD error here, but if you have a suggested patch, I can give it a try. Does master/head still use these? GTypeDebugFlags GTimeVal I am getting warnings that they are deprecated, and so if they are in use it seems they should be adapted to what gtk wants now. Are you building against gtk2 2.24 and glib2 2.62? I wonder if this is about new glib, not new gtk. We did update to 2.62.4 and I think that was the change that caused this error. I just checked my system, and I have gtk2 2.24.32-1ubuntu1 installed. For glib2, I have version 2.56.4-0ubuntu0.18.04.4. I rebuilt the source code and saw no issues with these revs on Ubuntu 18.04.4. Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF) Founder: Chelmsford Linux Meetup Group Founder: Worcester Linux Users' Group
Re: 2.0.17 and deprecated GTK APIs
On 2/28/20 9:39 AM, Greg Troxel wrote: I just filed a bug about this; building 2.0.17 on NetBSD with pkgsrc results in a GTK deprecation warning which with -Werror is fatal. I wonder what the path/timeframe is from the 2.0.18 beta to the actual 2.0.18 release. (pkgsrc only packages releases, unless we conclude that an upstream is so troubled that no releases will ever come.) Greg, N1DAM Hi Greg, I'd probably update the country file information and that's all. I can't replicate a NetBSD error here, but if you have a suggested patch, I can give it a try. 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF) Founder: Chelmsford Linux Meetup Group Founder: Worcester Linux Users' Group
Re: [Xlog-discussion] xlog 2.0.18beta has been released
On 12/22/19 9:03 PM, Paul Bramscher wrote: Hi Andy, A big thank you for continuing to support xlog -- my ham shack has been 100% Linux (Debian) for some years now. Thanks, in part to xlog (+fldigi), I've earned entry into ARRL's DXCC. Happy Holidays, 73, KD0KZE / Paul HI Paul, Many thanks(!!) for your kind words. I'm happy that xlog has been useful to you. 73, Andy KB1OIQ -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group Vice President: PART of Westford, MA (WB1GOF)
Re: [Xlog-discussion] Searching
On 7/27/19 12:07 PM, W0OOW wrote: Is there any way to search a column for ALL that are NOT blank? For example: I am a member of SKCC. I would like to bring up ALL records that are not spaces in a column I have labeled SKCC. Thoughts: Thanks W0OOW, In xlog, I'm not aware of a way to do what you describe. However, note that the *.xlog file is a text file, and I've often processed it (carefully!) with external tools. Make a copy of it before you start, just in case. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog 2.0.18beta has been released
Hi Everybody, Please try xlog 2.0.18beta. It has been updated to support FT4 mode. If there are any problems, please let me know. http://download.savannah.nongnu.org/releases/xlog/xlog-2.0.18beta.tar.gz Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Upcoming xlog 2.0.18: Adding FT4
Hi Everybody, I am updating xlog to support ADIF version 3.1.0, which adds FT4 mode. I've also seen some intermittent Glib Critical messages in the terminal when xlog is invoked from the command line. I'd like to fix those if I can determine precisely how to make them occur. If you have a log file and a precise set of steps which makes these messages occur reliably on version 2.0.17, please contact me directly. Lastly, I'll be updating the country file (cty.dat). 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Version 2.0.17 is available
Hi Everybody, It was reported to me that newer versions of GCC (> 8.1) are able to detect a new type of problem in the code called "stringop-truncation". There was one case of this in the Xlog source code (editest.c). It isn't a problem, so I disabled this particular compiler warning. Version 2.0.17 has this modification. One other difference: * 2.0.16's country file is dated 12/2018 * 2.0.17's country file is dated 01/2019 Thank you for using Xlog! 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] getting started in xlog
On 1/19/19 9:29 PM, Andy Stewart wrote: On 1/15/19 5:36 PM, Ed wrote: I think you need Javascript installed to view all of this. file:///usr/share/doc/xlog/manual/output/html/index.html Ed W3NR If one built directly from source, the path is "/usr/local/share", but that detail doesn't matter, since the documentation is available from the Help...Documentation menu at the top of the Xlog GUI. Sorry...the correct menu is Help...Manual. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Updates to xlog - they're coming.....
xlog 2.0.16 is available: http://download.savannah.nongnu.org/releases/xlog/ Simple update to include JS8 mode and ADIF 3.0.9. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Updates to xlog - they're coming.....
HI everybody, Due to the holidays and a death in the family, I have been unable to do any work on xlog or my other ham radio projects for the last couple of weeks. I've written myself a note to upgrade to the most recent ADIF spec (to pull in JS8CALL mode), and to update the country file. I just wanted you to know that I'm still planning to get to it, when life calms down a bit. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] A few xlog patches
On 11/11/18 2:18 PM, Werner Koch wrote: On Thu, 8 Nov 2018 12:32, w...@gnupg.org said: Associating such profiles with a log file would also be very useful. I only wonder on how to put such meta data into the flog (?) log files xlog works with. Any ideas? Maybe it is easier to write a separate config file for each log file iff that log file is in contest mode. To avoid disturbing the current layout and behaviour I will next implement such a contest flag; a flag allows to enable features like coloring the callsign etc. If someone is interested in a tarball for testing, just let me know. Shalom-Salam, Werner Hi Werner, I agree that there is no immediate need to modify the code to be GTK-3 compliant. I am interested in a tarball and a screenshot of the main window. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] A few xlog patches
On 11/6/18 4:17 AM, Werner Koch wrote: Hello Andy, Hi Werner, On Tue, 6 Nov 2018 05:59, kb1...@mval.net said: 1. Change the color of a new callsign when it has been worked. The above seems like it would be a relatively simple, but useful addition. I just fixed a little bug. :-) 2. Just one button to set date and UTC to the current time. It does not make sense to be able to set the current time I'm curious...did you remove a button from the GUI? Do you have a screenshot? https://eifzilla.de/scratch/xlog-1.png I removed the date button because the UTC button also fills in the date. This also shows the reordered fields. It might be better to have an in-entry button on the right side to fill in the UTC and for contests it should be done anyway at save-time. I have a friend who has wished for a) a better/different order in the New QSO frame, or b) the ability to add/delete those boxes at will, for different contests, and c) the ability to enter a QSO *without* needing the mouse. My friend's chief complaint is that tabbing over unused info boxes is error prone and should be unnecessary. Toward that end, I'm curious about your changes. That is also my idea. I am thinking about a configurable order of the fields including a save button etc. Recently we had an SSB fieldday and I used some Windows program for logging. That was really convenient and worked pretty well - without clicking. We should also have such an option. Context specific checks would also be useful. If there is a way to rearrage/omit the fields, in a user customizable way, I think that will meet the needs of the majority of users. For example, in a 6m contest, the exchange might be callsign, signal report, and grid locator, which is challenging to do with the current software. Right. The software should lead you through the QSO during a contest. I am interested in your ideas. I'd like to find a way to maintain a balance between the casual users of Xlog and those who would like the tool to be more user friendly for contest logging. Re-adding the date button and its mnemonic would be simple and could be the default. So that a new field ordering can be done as an option. I guess I will first work on a configurable order of the new QSO fields and add a configurable save button. BTW, is GTK-2 set or would migrating to GTK-3 be okay? I can live with both. I am OK with migrating to GTK-3. If this happens, my conservative proposal for the Savannah repository is as follows: a) modify the code to use GTK-3 without addition or loss of functionality b) start adding features one at a time with thorough testing c) release a new version when it is ready Regarding your other email, kudos on implementing a configurable order of fields. I'm wondering if this ordering is global (for all *.xlog files), or if it can be different for each log? Salam-Shalom, Werner Thanks, Werner, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] A few xlog patches
On 11/5/18 2:32 AM, Werner Koch wrote:
Hello!
Hello Werner,
As the maintainer of the Xlog software, I'd like to thank you for your
enthusiasm and willingness to share your ideas and code with the community.
Now that my transceiver sits close to my monitor I started to make real
use of xlog. It is a nice and small Unix program and should be
sufficient for me. However, there are a couple of peculiarities: For
example on Saturday I did some contest QSOs and got one dup response
("we already had a QSO"). The worked before windows showed that QSO but
I didn't realized that fast enough. So a better indication is needed to
make such things obvious. I did some patches:
1. Change the color of a new callsign when it has been worked.
The color is changed on an exact match. It would be better to also
indicate a fuzzy match here. The whole thing is pretty important to
quickly check whether a station has already been worked; for example
in a contest.
Using a fixed color is a bit crude but it is a first step for an
improved answer-back during data entry.
The above seems like it would be a relatively simple, but useful addition.
2. Just one button to set date and UTC to the current time.
It does not make sense to be able to set the current time but keep
the existing date. Better one button for this. Note that the date
can anyway be edited manually to any value.
I'm curious...did you remove a button from the GUI? Do you have a
screenshot?
3. Change the order of fields in the QSO frame
Except when typing in old log paper entries or similar, there is no
reason that the order must follow the order in the log windows.
From a usage point of view the new order seems to be better. For
example the band and mode is rarely changed and should thus not get
into the way when logging a new QSO. The call and the RSTs should
be the first and easiest to enter data. Actually the UTC should
even come after the call but I didn't do that because another patch
should fill in the UTC at save-time - this is a better for contests.
I have a friend who has wished for a) a better/different order in the
New QSO frame, or b) the ability to add/delete those boxes at will, for
different contests, and c) the ability to enter a QSO *without* needing
the mouse. My friend's chief complaint is that tabbing over unused info
boxes is error prone and should be unnecessary. Toward that end, I'm
curious about your changes.
For example, in a 6m contest, the exchange might be callsign, signal
report, and grid locator, which is challenging to do with the current
software.
as well as a few supporting changes. My goal is to make xlog ready for
real contest use up to a level that it can compete with whatever the
other hams in my club are using on Windows. I also looked at fldigi,
which is a great set of tools, but given that I am more a C and Gtk+ guy
I decided to give xlog a try.
Given that I basically lost all my CVS knowledge, I took the Savannah
xlog2 repo and imported it into a new Git repository for my local work.
You can find it at
git://git.gnupg.org/people/wk/xlog.git
Now the question is whether you like my changes at all and, if so, how
shall I send you the patches?
I would also like to discuss possible new features here to see whether
my patches make sense for a wider community. The next feature I am
looking into is an automatic RST+nnn counter and faster and more safe
contest logging options.
I am interested in your ideas. I'd like to find a way to maintain a
balance between the casual users of Xlog and those who would like the
tool to be more user friendly for contest logging.
Thanks for sharing!
73,
Andy
Xlog Maintainer
--
Andy Stewart (KB1OIQ)
Founder: Worcester Linux Users' Group
Founder: Chelmsford Linux Meetup Group
President: PART of Westford, MA (WB1GOF)
___
Xlog-discussion mailing list
Xlog-discussion@nongnu.org
https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] HOWTO install from source tarball
Hi Everybody, I've received several questions recently about how to install xlog from the source tarball. 1) Download the latest xlog from here: http://download.savannah.nongnu.org/releases/xlog/ 2) Note that as of this writing, the latest version is 2.0.15, so the desired file would be: xlog-2.0.15.tar.gz 3) The rest of these instructions should be done as root and within a terminal window. On Ubuntu systems (and perhaps others), one accomplishes this in a terminal window by typing the "sudo -i" command, typing the password when prompted, and then notice the new prompt starting with "#". 4) On "Andy's Ham Radio Linux", I created /usr/local/tarballs. Copy the downloaded xlog-2.0.15.tar.gz to that directory, or mentally adjust the following instructions, depending on where your downloaded file lives. 5) cd /usr/local/src 6) tar xzvf ../tarballs/xlog-2.0.15.tar.gz 7) That will cause a lot of files to be written to the hard disk, in a subdirectory called xlog-2.0.15. 8) cd xlog-2.0.15 9) ./configure If this step fails, read the INSTALL file for instructions about additional software packages that might need to be installed, such as hamlib. The names of these software packages, and the process for installing them, vary depending on your Linux distribution. 10) make 11) make install 12) /usr/local/bin/xlog 13) In the xlog GUI, look at the Help->About menu to be sure you're running version 2.0.15. If any of the steps causes an error, stop and resolve the problem before continuing. Note that most source tarballs require the standard 3 commands to build them: ./configure make make install 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] update from 2.0.13 to 15? how?
On 11/25/2017 11:44 AM, Steve Yates wrote: Is it difficult for the author to get the Repositories updated with the latest software version? For security purposes some of us prefer to use the more vetted Repositories rather than download directly from a site, any site. If we do the latter we might as well be using Windows. That being said, I really like XLog for its simplicity and functionality. I do look forward to better ADIF support in the new version. Now if someone with more brains than I could come up with a modern contest logger for Linux I wouldn't need Windows at all. :-) Thanks for all of the work! 73, Steve - AA5TB HI Steve, I have tried to get updated versions into the Debian and Ubuntu repositories for the last to releases, to no avail. Savannah is a well trusted site, and note also that there is a signed file with the tarball that I've uploaded. If you trust me, then you trust that which I've uploaded, once you've verified the signature matches. If you don't trust me, it won't be any better than what Debian/Ubuntu distribute, since they get it from me. That said, once one has downloaded the tarball, the process is quite standard: sudo -i cd /usr/local/src tar xcvf xlog-.tar.gz cd xlog- Read the INSTALL file for detailed instructions. ./configure make make install Regarding a "modern context logger" for Linux, perhaps cqrlog would better meet that need. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog 2.0.15alpha2 is available
Hi Everybody, Please try xlog 2.0.15alpha2 and let me know a) if you tried it, and b) if you see any problems. I fixed the sort by date / sort by callsign functions. There were a few other minor tweaks. I'm looking into the possibility of deleting dupes en masse at the behest of the user. I haven't yet found a good way to do it. I might have to table this request, but let me take one more good look at the code. Download from here: http://download.savannah.nongnu.org/releases/xlog/xlog-2.0.15alpha2.tar.gz 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-2.0.15alpha1 is available
Hi Everybody, I found some errors in version "2.0.15alpha" which I've fixed for "2.0.15alpha1". If you ran xlog from a terminal, they were the Glib-Critical and Glib-Warning messages that looked bad but the program appeared to work OK. I've fixed the ones that I could create. I also modified the scoring window so it properly shows all of the bands. Finally, the 60m band is now consistently referred to as "5" in places where MHz are displayed. It has moved around over the years, and different countries have different allocations. "5" seemed to be the safest thing to do. Please download and test it and let me know what you find. Previous warnings about alpha software still apply. http://download.savannah.nongnu.org/releases/xlog/xlog-2.0.15alpha1.tar.gz Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog 2.0.15alpha is available for testing
=== Resending since I don't think this went out last night as I expected. My apologies if you get this twice. === Hi Everybody, xlog 2.0.15 ALPHA is available. It may take a while for all mirrors to be updated. Changes: * Updated to support ADIF version 3.0.6 * ADIF2 export has been removed * ADIF import required a LOT of work * New bands, modes, and submodes were added * minor update to xlog.cfg to support the above * Update country file Download Location: http://download.savannah.nongnu.org/releases/xlog/ WARNING WARNING WARNING WARNING!! BE VERY CAREFUL!!! This is ALPHA quality software with a LOT of edits. I STRONGLY recommend backing up the entire contents of your ~/.xlog directory BEFORE trying this new version of software. This software is NOT TO BE USED for anything other than testing. I CANNOT be responsible for data loss. Please BE CAREFUL! You have been warned. OK, with that out of the way, I'd like people to please test the following: * Be sure that your existing *.xlog files can be read correctly * Export to ADIF v3 and make sure the information is correct ** Note that MODES and SUBMODES are different with ADIF3 * Try importing ADIF files created from tools other than xlog * Export to other formats to make sure nothing was broken If you encounter a problem, please provide the following: a) a copy of whatever file xlog was asked to read b) a copy of your ~/.xlog/xlog.cfg file c) What exactly did you do? d) What did you expect to happen? e) What actually happened? Please email that information to me at: kb1...@mval.net If you test xlog and don't see any problems at all, please tell me! That is also good information. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Test 4.5.6...please ignore
-- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Importing N1MM CWT logs into Xlog
On 08/14/2017 10:16 PM, Cranz (Nick) Nichols wrote: Just to be clear, the issues I was trying to address were with N1MM Logger - not XLog. XLog was working fine and I remain a appreciative fan. cln - Nick WB5BKL Lake Buchanan, TX No worries, Nick. Thanks for being a fan! :-) 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Importing N1MM CWT logs into Xlog
On 08/13/2017 07:45 PM, Cranz (Nick) Nichols wrote: For the very tiny fraction that use N1MM (Windows) for the CWTs and use XLog (Linux) for their general logger, this might be of interest: <http://wb5bkl.blogspot.com/2017/08/importing-n1mm-adif-export-files-into.html> Best regards - cln - Nick WB5BKL Lake Buchanan, TX HI Nick, Thank you for your note about N1MM and importing its ADIF files into Xlog. ADIF version 3.0.6 was just released today (13-aug-2017), and while I plan to add that support very soon, it won't happen until after the ARRL New England Convention, which will be held on September 8-10, 2017. I will be doing 3 presentations at that convention, and unfortunately, Xlog development will have to take a back seat until I finish with those presentations. Once I get into creating the enhancements for Xlog, I will look at the ADIF import issue that you mentioned, and I will see what can be done. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] I have made changes to the 2.0.14 tarball that includes the new FT8 mode
On 07/31/2017 01:17 PM, Jerry Davis wrote: I have made changes to the 2.0.14 tarball that includes the new FT8 mode. How do I upload them to y'all? Please send me any proposed changes. FYI: FT8 is not officially supported in the ADIF specification 3.0.5, which is why I haven't added it. Sometime soon, I'll add ADIF 3.0 support. 73, Andy xlog maintainer -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog 2.0.14 on macOS Sierra
On 12/29/2016 01:46 PM, Andy Stewart wrote: hamlib-utils.c:625:30: error: length modifier 'L' results in undefined behavior or no effect with 'd' conversion specifier [-Werror,-Wformat] g_string_printf (digits, "%Ld", programstate.rigfrequency); ~^~ hamlib-utils.c:625:30: note: did you mean to use 'll'? *change to ll* The code wants to print a long double. My version of gcc accepts %Ld. Is there a way to express a long double for printf() with the compiler version you're using? I'm sorryI think you were trying to tell me "%lld". I tried it and it compiles but I haven't tested the code yet. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] RELEASED: Version 2.0.13
Hello everybody, Version 2.0.13 has been released! It includes the following: - Changes for xlog version 2.0.13 - 2015-apr-19 * Fixed date in cabrillo3 output to be: -mm-dd * Fixed date in EDI output to be: yymmdd * Fixed QSORecords in EDI output * Updated cty.dat to 20150420 (cty-2505) -- brand new! * Fixed Bug #44547: Added JT9 modes * Fixed Bug #44259: broken dupe checking The code is on its way to being released in Debian and Ubuntu, which typically takes a few days. The code can be downloaded from here: http://download.savannah.gnu.org/releases/xlog/xlog-2.0.13.tar.gz Please wait a few hours for the mirrors to be updated. Many thanks to all of you for testing the beta releases and providing bug reports with data for reproducing those bugs. It was most helpful! Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Version 2.0.13 beta 3 is available
HI everybody, Version 2.0.13 beta 3 is available for testing. Please give the mirror sites a few hours to acquire the file. http://download.savannah.gnu.org/releases/xlog/xlog-2.0.13beta3.tar.gz This most recent update fixes the QSORecords field in an EDI output file. The complete list of changes for 2.0.13 is shown below, as copied from the ChangeLog: - Changes for xlog version 2.0.13 - 2015-apr-19 * Fixed date in cabrillo3 output to be: -mm-dd * Fixed date in EDI output to be: yymmdd * Fixed QSORecords in EDI output * Updated cty.dat to 20150304 (cty-2504) * Fixed Bug #44547: Added JT9 modes * Fixed Bug #44259: broken dupe checking I am not planning to make any additional changes for 2.0.13 since I believe I have fixed all of the problems reported to me. Please test this version and let me know if it works or if you encounter any problems. Thanks(!), and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] EDI
On 04/18/2015 04:16 AM, ew...@tut.by wrote: Hello All ! - LSoft=xlog version 2.0.13beta2 [Remarks] [QSORecords;] 150407;1822;EW1BH;6;59;;59;;;ko33vt;23 - QSORecords - no QSO number 150407;1822;EW1BH;6;59;;59;;;ko33vt;23 - fixed, ok ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion Thank you Alex for your report! I will try to fix the QSORecords. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Released: 2.0.13 beta 2
On 04/17/2015 04:51 AM, Pierfrancesco Caci wrote: Andy == Andy Stewart andystew...@comcast.net writes: Andy Hi everybody, Andy Please try this beta release: Andy http://download.savannah.gnu.org/releases/xlog/xlog-2.0.13beta2.tar.gz I get a redirect to http://mirror.lihnidos.org/GNU/savannah//xlog/xlog-2.0.13beta2.tar.gz which gives 404. Please try again. It takes a short time for all of the mirrors to receive a copy of the file. Please let me know if you have success. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Released: 2.0.13 beta 2
On 04/17/2015 12:13 PM, Pierfrancesco Caci wrote: Andy Please let me know if you have success. Thanks, now it worked. Dupe check works. check all logs requires a bit of patience, but in the end it shows the dupes. Pf Pierfrancesco: Thank you for testing the new dupe code and for reporting your findings. How many QSOs are in all of your logs, and how many dupes? -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Released: 2.0.13 beta 2
Hi everybody, Please try this beta release: http://download.savannah.gnu.org/releases/xlog/xlog-2.0.13beta2.tar.gz I believe it fixes two bugs since the previous beta: a) dupe checking now prints proper dupes in one or many logs b) EDI date printing Please especially check the EDI date printing if English is not your locale setting. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] EDI
On 04/11/2015 11:58 AM, ew...@tut.by wrote: Hello All In .xlog file mont in russian like apr=апр ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion I suspect that this is a language related issue. Thank you for sending me your xlog file. I have recreated the problem and I will try to fix it in the next few days. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] EDI export
On 12/08/2014 03:07 PM, Alex wrote: Hello all ! Now bug report from sent edi file in time format like bad format (file export from xlog) 20140002;1801;EW1BH;6;59;;59;;;ko33vt;23 but correctly like 140002;1801;EW1BH;6;59;;59;;;ko33vt;23 73s ! Please try version 2.0.13beta to see if the problem is fixed. http://download.savannah.gnu.org/releases/xlog/xlog-2.0.13beta.tar.gz 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Fixes for 2.0.13
HI everybody, Please try xlog 2.0.13 beta. I have added the following: * Fixed date in cabrillo3 output to be: -mm-dd * Fixed date in EDI output to be: yymmdd * Updated cty.dat to 20150304 (cty-2504) * Added JT9 modes I'll let it sit for a couple of days while people try it. If you have any issues, please let me know. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] (no subject)
On 05/11/2014 10:51 AM, Alex wrote: Hello All ! Please add focus to the record CALL after cleaning with ctrl-A. Hello Alex, If you press ctrl-K, the fields will be populated and focus will be on the CALL. And worked before window with EW1A eg, show - EW1A, EW1AA, EW1ABC etc - maby after call EW1A add space and find correctly only EW1A ? Now CALL+space no find any call... This is working as expected. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Version 2.0.12 has been released
HI Everybody, Version 2.0.12 is available (once the mirrors get updated): http://download.savannah.gnu.org/releases/xlog/ Help-About to be sure you've got the correct version. - Changes for xlog version 2.0.12 - 2014-apr-01 * Updated cty.dat to 20140331 (cty-2404) Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Save
On 12/06/2013 06:54 AM, Ed wrote: On 12/06/2013 01:33 AM, Andy Stewart wrote: On 12/05/2013 07:21 PM, Ed wrote: Andy is it possible to save on enter instead of 5 minutes ? Ed W3NR Settings-Preferences-Logs Sorry, I just missed that checkbox. I'll blame old age and poor eyesight. Ed No problem, Ed. :-) -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] TX RST
On 12/06/2013 07:05 AM, Ed wrote: On 12/06/2013 01:32 AM, Andy Stewart wrote: On 12/05/2013 07:12 PM, Ed wrote: Unless I've just missed it somewhere, click on TX (RST) and it sends 509 and logs 509. No big deal, but it needs corrected. Ed W3NR HI Ed, Please try the real 2.0.11. pre is a prerelease version. When I bring up xlog and click the TX(RST) box, nothing happens - the text entry box stays blank. In the Settings-Default menu, it is also blank. Are you connected to a rig? Is Hamlib enabled? I'll need to duplicate the problem before I can investigate a fix. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] TX RST
On 12/05/2013 07:12 PM, Ed wrote: Unless I've just missed it somewhere, click on TX (RST) and it sends 509 and logs 509. No big deal, but it needs corrected. Ed W3NR Ed, can you be more specific? Which version of xlog? What precisely did you do? Did you setup something in the Settings-Defaults menu? 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Save
On 12/05/2013 07:21 PM, Ed wrote: Andy is it possible to save on enter instead of 5 minutes ? Ed W3NR Settings-Preferences-Logs -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] New 3 character call signs
On 11/11/2013 01:50 AM, Alastair Couper wrote: Please try xlog-2.0.11pre1.tar.gz Looks like it is working as intended. Thanks much! Question: Why does my xlog executable end up being 1.9MB? The executable from the latest launchpad PPA was only ~.5MB. Compiled on Ubuntu 12.04 with low latency kernel. ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion I'm happy that it is now working for you! Thanks for reporting the bug with your patient explanation so I could reproduce and fix it. I'll wait a little while before releasing 2.0.11 so others will have a chance to try it. Please reply to this email thread if you try the pre1 version. On my 64-bit machine, the executable is 1.6MB in size. I am using Ubuntu 12.04.3 LTS. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] New 3 character call signs
Hi Everybody, Please try xlog-2.0.11pre1.tar.gz, which is making its way to the mirrors now. The pre1 version fixes the 3-character callsign issue reported by Alastair. The pre1 version also contains all of the fixes from the pre version. Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] New 3 character call signs
On 11/07/2013 01:08 AM, Alastair Couper wrote: Andy, I have the latest cty.dat file just fine. It is the behavior of xlog in processing it that I am commenting on, and would hope could be changed a bit. If I type K9W in the call sign entry window, then xlog will find all the examples of K9Wxx in my log. It will also count *all* of those K9Wxx calls as Wake Island, when only K9W is Wake Island. So it throws the DXCC count off on the bands where I have worked K9Wxx but not K9W. The other somewhat recent 3 letter calls act the same, N8S, K5D... Al HI Al, Thanks for the more detailed description of the issue. I'll take a look in a day or so, see if I can reproduce the problem, and then work on a fix. It seems like I fixed something similar not too long ago. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] New 3 character call signs
On 11/05/2013 06:02 PM, Alastair Couper wrote: The recent use of 3 character call signs, like K9W, causes xlog to miscalculate DXCC scoring. If there is an entry in the cty.dat file that adds K9W to the Wake Island list: ...,=K9W; then if I type K9W into the callsign entry box, all calls of the form K9W** are then listed, which is OK. But all those additional calls are used in the DXCC scoring for Wake Island, even though they are just plain USA. One of those pesky bugs no one thought of when 3 character calls didn't exist. Thanks to the devs for keeping this program alive. I have 40,000 QSO now in my general log, and xlog has no problem with stability. Hello Alastair, K9W has been added to the Wake Island list in the most recent cty.dat file, which will be included in the next xlog release (or a more recent one if it exists). I can see it specifically in the 20131009 release, and there is one release more recent. One can get this file for themselves from here: http://www.country-files.com/cty/cty.dat grep VER cty.dat (shows the version of the file) Put the file in this location: /usr/share/xlog/dxcc/cty.dat OR /usr/local/share/xlog/dxcc/cty.dat depending upon where your xlog has been installed. Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] andy's email address bouncing
On 09/27/2013 05:21 AM, Joop Stakenborg wrote: This is what I get: andystew...@comcast.net mailto:andystew...@comcast.net (generated from kb1...@arrl.net mailto:kb1...@arrl.net) SMTP error from remote mail server after initial connection: host mx1.comcast.net http://mx1.comcast.net/ [68.87.26.147]: 554 imta04.westchester.pa.mail.comcast.net comcast 74.115.253.198 Comcast block for spam. Please see http://postmaster.comcast.net/smtp-error-codes.php#BL00 Andy, can you provide an alternative email address? Regards, Joop HI Joop, Are people sending to my kb1...@arrl.net email address and receiving this message? I had this problem fixed once before. If this ISP (comcast) continues to block my legitimate email, I may need to switch. I think they're blocking my email from SourceForge, too. My direct email address is: andystew...@comcast.net Thanks for letting me know that there is a problem. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] date format
HI John, Thanks for your explanation and your patience. I like to hear how people are using xlog. It also helps me understand what to do to reproduce a problem, and then I have a method for testing potential fixes. I believe TSV is a generic tab separated variable format. It is possible to modify the way the date is printed in the TSV file. I want to be sure that my assumption about this being a generic format is correct so I don't break other things if I make this modification. I created my own TSV file and tried to import it into LibreOffice Calc, but it keeps putting it into LibreOffice Write. I'm using the File-Open menu in Calc to read in the TSV file, but in the very long list of file types, I don't see TSV. How did you read it in and get it to populate the spreadsheet? Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] date format
On 07/16/2013 05:18 PM, HA5OGL wrote: I started to use xlog. I want to ask is there any way to modify the date format? Does it use the format according to the system'd default locale? Any pointers how to change it in the code? BTW is there any way to save the logs in CSV format? Thw .xlog format is odd to me. Thanks, 73s de HA5OGL Levente Hi Levente, John, and others, I have modified the xlog code to output the date in the TSV file in ISO 8601 format. My example TSV file looks like this: 2008-01-31 0400KD5CQX 7 CW 569 When importing this file into LibreOffice Calc, one needs to tell the import GUI that the first column is a date in YMD format. Once that is done, the spreadsheet is populated and it knows that this is a date. Afterwards, if one wants a different date format, one can change it with Format-Cells. This is working for me with LibreOffice version 3.5.7.2. This modification will be in the next xlog release (version 2.0.9). Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Updates to v 2.0.7? -AA3EJ
On 05/29/2013 02:37 PM, Ed wrote: On 05/29/2013 01:41 PM, D.R. wrote: Gentlemen, Are there going to be updates to Xlog v2.0.7? .. 1. Xlog v2.0.7 still NOT in the current Ubuntu repository, re-compilation necessary to solve Remarks field problem.. 2. Auto new call Look-up still not implemented from QRZ or HamQth servers.. 3. Worked Before window columns NOT inter-changeble... Havn't seen an update to this super problem. I use it daily!!.. Thanks, 73's Dave, AA3EJ aa3e...@gmail.com Current version is 2.0.8 You need to talk to the Ubuntu maintainers, they keep the repository up to date. (Good luck with that one). Ed W3NR I have contacted the Debian maintainer. Once xlog gets into Debian, then it can get into Ubuntu. However, one need not wait - the source code is available immediately. :-) Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog 2.0.8 is released
On 05/24/2013 07:59 AM, Chris Story wrote: Andy, All, Are we due for any changes to the manual? Chris Story K6RWJ HI Chris, There have been no GUI changes with the last two minor releases, just internal bug fixes. I've not seen any issues with it. I hope everybody has had a chance to look at the manual that Chris created. I think he did a very find job! I hope you do, too. Please offer feedback. To read the new manual, in the menu bar: Help-Manual The manual will appear in your favorite browser. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Version 2.0.7 released
HI Everybody, There was an xlog bug that was exposed by some Unity themes where the xlog remarks box was not properly displayed, making it difficult/impossible to enter remarks. This problem has been fixed in version 2.0.7. This was documented as Ubuntu bug #38637. It was a one line fix that is probably invisible to others. However, since I was doing a release, I included an updated country file also. Feel free to download it from here at your convenience: http://download.savannah.gnu.org/releases/xlog/ I have requested the inclusion of this version into Debian, and from there into Ubuntu. Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] (no subject)
On 03/03/2013 02:44 AM, Alex wrote: Hello ! move or copy to /home/urhomename/.xlog directory more than one xlog files and rerun xlog... Hello Alex, I have many *.xlog files in my ~/.xlog directory. I setup xlog to load 4 of them when I start xlog. I have 4 tabs. There is nothing put into the New QSO field when I do this. I cannot duplicate the issue that you are describing. Would you please give me more information? Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] (no subject)
On 03/02/2013 11:55 AM, Alex wrote: Hello ! if you open another tab, the fields are automatically entered data from the last QSO this log. But next time, after cleaning, the fields are not entered when changing tab. 73s ! HI Alex, I'm using version 2.0.6 of xlog. When I open xlog, I have one tab. Then, I do Log-Open and get a second tab. I do not see any data in the New QSO fields. I can switch tabs back and forth, but the New QSO boxes are not filled with data. The only time the New QSO boxes get data are: a) when I explicitly enter data b) when I select a QSO Perhaps I misunderstand what you are trying to describe. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Version 2.0.6beta4 has been released
On 02/25/2013 07:45 AM, Ed wrote: On 02/24/2013 08:57 PM, Andy Stewart wrote: HI everybody, I have just posted the tarball for xlog2.0.6beta4, which I hope will be the last beta for version 2.0.6. Unless there is a big problem, there won't be any more beta releases. Any remaining issues can wait until 2.0.7. Can't get the manual to open. I'm assuming you are calling it in a web browser. I use Chrome if that will help. Ed W3NR Hi Ed, Point your browser directly to this page and tell me if it works: /usr/local/share/doc/xlog/manual/output/html/index.html (Probably: file:///usr/local/share/doc/xlog/manual/output/html/index.html) Try another browser and tell me if that works. I assume you did: Help-Manual Somewhere, there is a setting for the default browser. Mine is set to rekonq but I'd love it to be Firefox. Where does the setting for this attribute live? Thanks, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog 2.0.6beta2 is released
On 02/17/2013 11:40 PM, Andy Stewart wrote: HI Everybody, xlog 2.0.6beta2 has been released. ...and just as quickly, I put beta3 out there since I found a last minute bug that I didn't like. I took beta2 down to avoid any confusion. Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog 2.0.6beta2 coming shortly...
HI gang, I'm in a coding sort of mood as of late. I'm indoors watching the end of the blizzard that dropped at least 18 of snow at my house. I'd like to get a real release of Xlog out the door. I've added one last quick bug fix, which I'll post this weekend as 2.0.6beta2. Note: I haven't posted it *yet* - I'll send another email when it is available. My ulterior motive is this: I'd like to crank out a new version of my Linux ham radio CD, and I'd like the latest, greatest Xlog to be on it, ideally from the Ubuntu repository. I know that a lot of great work has occurred on the documentation - thanks, Chris! I'll get an update and find out when this will be available for release. Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Cabrillo: more accurate frequencies?
HI gang, In the task list, I see an entry about a requested future feature. In the Cabrillo log format, one can log the band or the frequency in kHz. In Xlog, the exported Cabrillo format only puts the band, and gives the user no option to use the more accurate frequency. Is this still a feature that people would like to see? If so, would somebody please provide me an Xlog formatted log containing the very accurate frequency information as might be entered when using hamlib? Thanks, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog 2.0.6 beta1 is out...
HI Everybody, I've just put xlog 2.0.6 beta1 onto the server. Please allow 24 hours for propagation to the mirrors. Distribution maintainers: please don't incorporate this version. In addition to the ADIF v2 and Cabrillo v3 updates of the original beta release, the following have been addressed: a) MFSK mode ambiguity during ADIF import/export - the ADIF 2.2.7 specification says MFSK8 and MFSK16 are legal modes, not MFSK, as is output by at least one commonly used logger. xlog is now more forgiving of this case on import and exports legal ADIF without silently failing as was the case in the original 2.0.6 beta. b) Cosmetic repairs to the scoring window - Some field were not completely displayed (long country names and long callsigns, on the left of the scoring window). This drove me nuts and I think it is fixed. Please try this: bring up the scoring window and click a QSO with a W0 callsign - notice the long country name on the left of the scoring window? Is it all there? It should read United States CO, IA, KS, MN, MO, ND, NE, SD (on 2 lines). c) use of X instead of 0 in the scoring window to indicate yes, you got it (similar to the use of X in the QSL in/out). I decided against the use of the check box since I don't understand the unicode issues (if any) that might result from its use. Please give it a try and let us know your results - good, bad, otherwise. :-) Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Feature request -- export individual entries to a new log
On 12/15/2012 10:20 AM, Peter Spotts wrote: Hi Andy, I wonder if at some point, it might be possible to highlight a set of individual log entries for export into their own log...a bit like a reverse merge, perhaps. HI Pete, I've logged this as bug #37937 for future consideration. Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog 2.0.6 beta1 is out...
On 12/16/2012 05:53 PM, Ed wrote: Good work Andy, thanks Ed W3NR Thanks, Ed, for testing it, for the report, and for your kind words. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Testme: version 2.0.6beta
On 12/11/2012 10:17 AM, Stephen Gilbert wrote: Hi Andy..tested the new bit of code today and the ADIF import/export seems to work fine now ---well done!! That's one thing out of the way!!! What is next?? Stephen G3OAG HI Stephen, With your positive feedback that the problem has been fixed, I'll probably wait until this weekend and release it as version 2.0.6. I have received other positive feedback, too. Thanks, Stephen, and everybody else, who has tested 2.0.6beta. Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Testme: version 2.0.6beta
On 12/06/2012 10:00 AM, Stephen Gilbert wrote: As Andy says, it is easy just to remove the unwanted bands in the Preferences, but somebody on the planet may be glad of the new bands in xlog. It took me 10 seconds to remove everything below 1.8Mhz and above 144Mhz. I have been testing the IMPORT/EXPORT and have come up a with a problem. I successfully IMPORTED a 17000 QSO .adi file which I had exported from CQRLOG...which all went into xlog correctly - although the earliest QSO was displayed at the top and the newest QSO at the bottom of the list - I prefer the newest QSO at the top of the screen. I then EXPORTED the new xlog log to a new .adi fileafter deleting the old log, and re-imported the new .adi file made with xlog 2.06. However, only part of the log was importedstrange. Is the EXPORT working properly Stephen G3OAG Hi Stephen, Thank you for sending that rather large ADIF file. I have duplicated the problem. With your file, the new ADIF v2 EXPORT malfunctions. The resulting exported file only has about 3500 QSOs instead of 17,196 QSOs. I have not yet found the root cause. I tried this same experiment with xlog 2.0.5 and I discovered no problems, so something seems to be amiss with 2.0.6beta. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog
On 12/05/2012 02:55 PM, Pierfrancesco Caci wrote: Alex == Alex ew...@tut.by writes: Alex Hello All ! Alex 1st try new beta: Alex After installing and running - change the list of scoring - added unused Alex default bands and lost used bands. Alex (30 mhz and 0.501mhz - by default ! :) yeah, looks like the new bands shifted the old ones around. not a big deal, as it does not touch the logs. HI everybody, I think the scoring window needs a little bit of improvement (or maybe my understanding of its function needs improvement). I will work on it once version 2.0.6 exits beta testing and is released. If one goes to the Settings-Dialogs_and_Windows-Scoring menu, one can select the desired bands to display in the scoring window. I selected all of the choices. If I resize the scoring window and make it really wide, I can see all of the bands. There is also a scroll bar in case the window is insufficiently wide. Yes, the new bands shifted the old bands, but this is customizable as described. I think you are saying that your preferred band settings changed, and that surprised you. Is this correct? I had to add some code due to the new bands, and via the aforementioned mechanism, one should be able to restore the scoring window to display the desired bands. Please let me know if this is not the case. Thanks! Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Testme: version 2.0.6beta
Hi everybody, It may take 24 hours for you to see it, but I have posted version 2.0.6beta of xlog. Distribution maintainers: please do not incorporate this version. Features: * ADIF support updated to version 2.2.7 * Cabrillo support updated to version 3 * User preference: Are you sure you want to quit? As a result of adding updated ADIF support, one will notice a large(!) number of newly supported modes, and a new band (560m). Please test this version and provide feedback! Please do NOT use it on the golden copy of your logs. Make backup copies of your logs before you try this version! It is a beta version, after all. :-) Any bugs that existed in version 2.0.5 that are not listed in the features of 2.0.6beta probably still exist. We'll get to thosesomeday. If you report bugs, the following are most helpful to me: a) what you did, *exactly*, so I can do it, too! b) what you expected the software to do c) what the software actually did d) data so that I can reproduce the problem (maybe a piece of a .xlog file, ADIF file, etc. as appropriate) Thanks! Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] What's new with xlog ?
On 11/14/2012 07:26 AM, Ed wrote: On 11/14/2012 04:57 AM, Stephen Gilbert wrote: Hi Andy...I think before trying to include new features, some of the existing problems need to be looked at. HI everybody, I'm really glad that people are sufficiently interested in xlog to keep writing to this email list! I understand that there are many issues that need to be addressed, and I will become more expedient at addressing them as I learn how the code works. Adding Cabrillo v3 export support was needed IMHO and fairly easy to add. I will finish the Cabrillo v3 support with the addition of the import support. I gain confidence manipulating the code with these small successes. I would like the next couple of releases to implement a small number of fixes or features as I learn the code. To use a baseball analogy, I'd rather hit a couple of successful singles as the new maintainer than to take a big swing at a home run and miss. Joop created the xlog2 tree at version 2.0.5 so I'd have a solid starting point. The xlog tree is still in place. I would like to create a clean slate with the bug reports and start fresh. If ADIF output is not up to specs, please file a bug so we can track the issue and it won't be forgotten. A pointer to a current ADIF spec will help a lot. I'm also aware of the scoring window issue and confusion caused by the use of 0 as an indication of goodness. Chris KC2SYK will, I think, be filing an enhancement request :-) for this issue. I'm not up to date on the CTY.DAT issue. If someone can explain the problem in a bug report, that would be most appreciated, again, so the issue isn't lost. Joop has been very helpful to me in this transition, for which I thank him. Thanks, everybody, for all of the helpful suggestions. Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] What's new with xlog ?
HI gang, After all of the fanfare..nothing.what's up with that? Well, life gets busy, soldering needs to get done, and I do play on the air once in a while. ;-) I'm often running QRP CW with the SKCC folks. Codewise, I have been familiarizing myself with the xlog code, and in my sandbox I have Cabrillo v3 export working. I've kept Cabrillo v2 for those who might wish to use it. I now am starting to work on Cabrillo v3 import. I also plan to add a preference checkbox for the Are you sure you wish to exit dialog. Frankly, I hate this darn dialog, but others might like it, so I'll make it a preference, defaulted to the current behavior of asking. Once I get those features working, I'll check it in (once I figure out how to label it all) so people can test it and offer feedback on the new features. At some point thereafter, it will be released as version 2.0.6. ...and that's the way it is, Tuesday, November 13th, 2012. Have a lot of fun, and 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Test 1 2 3...
4...5...6 -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Test 1 2 3...
On 10/25/2012 08:54 PM, Andy Stewart wrote: 4...5...6 7...8...9 -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
