Re: TLF-1.4.0 release
* On 2019 25 Nov 13:17 -0600, Thomas Beierlein wrote: > Am Sat, 23 Nov 2019 18:30:01 -0600 > schrieb Nate Bargmann : > > > * On 2019 23 Nov 08:14 -0600, Drew Arnett wrote: > > > Resize is fine, but please continue to support 80x25 long term. I > > > don't see classic TUI losing value anytime soon. > > > > Do you mean that Tlf should enforce a minimum 80x25 terminal size as > > it has in the past? Personally, I've no problem with that. > > 'Enforcing' is a little bit difficult as (as far as I know) we can not > force a minimum size on any xwindow. But I will leave the warning in > place that you should have at least 25 lines in your terminal. By "enforcing" I was referring to the behavior where Tlf simply exited unless the terminal was at least 80x25. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
pywinkeyerdaemon
Finally knocked off some todos including porting to python3. (still runs on 2 as well) Also, finally added in message +/- controls (tested with TLF) and support for cwdaemon prosigns. (I hadn't been using these sorts of things, so hadn't missed them personally, but they've been on the TODO list too long.) +++TEST--- doesn't work unless there's a setspeed first. (I didn't find that function in the winkeyer interface.) In testing, I found that tlf sends a setspeed command at startup, so no problems. https://github.com/drewarnett/pywinkeyerdaemon Best regards, Drew n7da
Re: TLF-1.4.0 release
Agreed. I wouldn't enforce any more minimum than now. Warning makes sense. But, I can't anticipate someone doesn't have a use case where they want to use a smaller terminal. On Mon, Nov 25, 2019 at 7:16 PM Thomas Beierlein wrote: > > Am Sat, 23 Nov 2019 18:30:01 -0600 > schrieb Nate Bargmann : > > > * On 2019 23 Nov 08:14 -0600, Drew Arnett wrote: > > > Resize is fine, but please continue to support 80x25 long term. I > > > don't see classic TUI losing value anytime soon. > > > > Do you mean that Tlf should enforce a minimum 80x25 terminal size as > > it has in the past? Personally, I've no problem with that. > > 'Enforcing' is a little bit difficult as (as far as I know) we can not > force a minimum size on any xwindow. But I will leave the warning in > place that you should have at least 25 lines in your terminal. > > > > > What about a 2nd application, tlf-config or easy-tlf-config, which > > > would have the pulldown menus etc for setting up config files. Keep > > > the pulldown menus out of tlf. Once you add menus, you'll add a > > > bunch of hotkeys. One of the nice things about TLF is that there > > > aren't a bunch of live keys, especially if run out of a console or > > > terminal rather than a windows manager. > > > > That's actually a very good idea, Drew. If such a program were to > > gain good enough coverage then the :SET and :CFG commands could just > > call it instead of an editor. As for hot keys, Tlf does have quite a > > few assigned already. > > > Ok, I really like these idea. I will add it as an alternative to > the ToDo entry for the configuration menu. > > 73, de Tom > > > > -- > "Do what is needful!" > Ursula LeGuin: Earthsea > -- >
Re: TLF-1.4.0 release
Am Sat, 23 Nov 2019 18:30:01 -0600 schrieb Nate Bargmann : > * On 2019 23 Nov 08:14 -0600, Drew Arnett wrote: > > Resize is fine, but please continue to support 80x25 long term. I > > don't see classic TUI losing value anytime soon. > > Do you mean that Tlf should enforce a minimum 80x25 terminal size as > it has in the past? Personally, I've no problem with that. 'Enforcing' is a little bit difficult as (as far as I know) we can not force a minimum size on any xwindow. But I will leave the warning in place that you should have at least 25 lines in your terminal. > > > What about a 2nd application, tlf-config or easy-tlf-config, which > > would have the pulldown menus etc for setting up config files. Keep > > the pulldown menus out of tlf. Once you add menus, you'll add a > > bunch of hotkeys. One of the nice things about TLF is that there > > aren't a bunch of live keys, especially if run out of a console or > > terminal rather than a windows manager. > > That's actually a very good idea, Drew. If such a program were to > gain good enough coverage then the :SET and :CFG commands could just > call it instead of an editor. As for hot keys, Tlf does have quite a > few assigned already. > Ok, I really like these idea. I will add it as an alternative to the ToDo entry for the configuration menu. 73, de Tom -- "Do what is needful!" Ursula LeGuin: Earthsea -- pgpE6moQk532b.pgp Description: Digitale Signatur von OpenPGP
Re: tlf and the nano editor
Very nice. Glad to hear it. So it seems the new editor feature is running well. I will wait two or three more days. If no one has problems with it, I will merge the patch into the master version. 73, de Tom Am Mon, 25 Nov 2019 12:35:25 -0600 schrieb Nate Bargmann : > * On 2019 25 Nov 07:46 -0600, Joop Stakenborg wrote: > > Hi Tom, > > > > > > It works okay with 'nano' now, thanks! > > > > The weekend was, fun. Made mores than 800 Q's in the CQWWCW with > > tlf and winkeydaemon using the nanokeyer. > > Good to hear everything worked well, Joop. > > 73, Nate > -- "Do what is needful!" Ursula LeGuin: Earthsea -- pgpUluh0O7F0b.pgp Description: Digitale Signatur von OpenPGP
Re: tlf and the nano editor
* On 2019 25 Nov 07:46 -0600, Joop Stakenborg wrote: > Hi Tom, > > > It works okay with 'nano' now, thanks! > > The weekend was, fun. Made mores than 800 Q's in the CQWWCW with tlf and > winkeydaemon using the nanokeyer. Good to hear everything worked well, Joop. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: tlf and the nano editor
Hi Tom, It works okay with 'nano' now, thanks! The weekend was, fun. Made mores than 800 Q's in the CQWWCW with tlf and winkeydaemon using the nanokeyer. 73 de Joop PG4I Op 23-11-19 om 19:33 schreef Thomas Beierlein: Hi, please see the improved version on the same link as yesterday. From the commit message: Improve editor handling - Uses it also for :CFG and :SET commands - Fall back to editor defined in environment if not defined in logcfg.dat - Show warning if editor program not found @nate: I tested it with gedit and gvim -> works. What is emacs doing? 73, de Tom DL1JBE Am Fri, 22 Nov 2019 20:19:53 +0100 schrieb Thomas Beierlein : Hi all, as the fixed choice of editors is quite a nuisance I prepared a changed version for tests. Please find it at https://github.com/dl1jbe/tlf/tree/new_editor Download the code and build TLF as told in the INSTALL file. Do not forget the 'autoreconf -i' step. The new version accepts any string as editor command and will just call that program with the logfile name as parameter. That means EDITOR=my-shiny-editor in logcfg.dat will call 'my-shiny-editor ' So a simple EDITOR=nano should do afterwards. Please test and give feedback. 73, de Tom DL1JBE Am Fri, 22 Nov 2019 11:08:52 -0600 schrieb jim smith : On Fri, 22 Nov 2019 15:06:14 +0100 Joop Stakenborg wrote: I have gotten used to the GNU nano editor, but it does not seem to work with tlf. When I type :edit in the callsign field, tlf exits and returns straight away without opening nano. Both joe and vi work okay here. It is hard to debug, have to spent some time on it to see what actually happens. Maybe use gdb with a break added. I will have a look next week. 73 de Joop PG4I Hi Joop, I don't know if this helps any, but I don't have any problems running nano with tlf on ubuntu 18.04. I have *not* updgraded to tlf 1.4 yet (was going to do that this weekend.
Re: Using hamlib for CW keying
* On 2019 21 Nov 05:32 -0600, Christian Treldal wrote: > All modern rigs have keying via hamlib. I would caution, that is possible with varying degrees of support and capability. On the N1MM+ mailing list there is this recent thread that asks about a warning when CAT keying is used: https://groups.io/g/N1MMLoggerPlus/message/45927 Rich, VE3KI, weighs in later with: https://groups.io/g/N1MMLoggerPlus/message/45930 where he states: Which rig? The KY command works differently in Elecraft vs. Kenwood vs. Yaesu. The examples that have been posted in various places were for Elecraft radios. IIRC, the KY command for Kenwood radios requires a fixed-length argument (padded with blanks), which makes it essentially impossible to use substitution macros. Also as I recall, the Yaesu KY command does not send text, it selects one of the radio's own CW memories and sends that. I've not seen the code, of course, but I presume that N1MM+ is handling all of the rig control stuff internally. For Tlf and other programs using Hamlib, the rig capabilities would be queried and if rig_send_morse() is supported, it can be used, however, things like the speed up/down characters in the keying macro would need to be handled by the calling program and speed changes sent to the rig interspersed with the message text. I can see this becoming very clunky very quickly! Any given Hamlib backend will probably be coded so as to perform needed work-arounds as best as possible. Again, this is very rig specific and even Hamlib likely cannot hide certain differences. I only have access to a K3 these days. I've not seen much mention of anyone using the Hamlib send_morse function for any serious CW keying. If I could offer a wishlist item to the manufacturers, it would be for those radios incorporating a USB connector for rig control and sound card IO that a second virtual serial port be available to expose a K1EL compatible keyer. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
