Re: tlf and the nano editor

2019-11-22 Thread Csahok Zoltan
My 2c: try with "export EDITOR=..." 73, Zoli On Fri, Nov 22, 2019 at 07:18:35PM -0600, Nate Bargmann wrote: > My first test with EDITOR=gedit resulted in nothing happening. I ran > gedit from another terminal and it opened fine. Then I tried emacs

Re: tlf and the nano editor

2019-11-22 Thread Nate Bargmann
My first test with EDITOR=gedit resulted in nothing happening. I ran gedit from another terminal and it opened fine. Then I tried emacs from the terminal and it opened fine in the GUI. I then tested both emacs and gedit as Tlf editors and they worked fine. I'm not sure what was going on so it

Re: tlf and the nano editor

2019-11-22 Thread Nate Bargmann
* On 2019 22 Nov 15:17 -0600, Thomas Beierlein wrote: > Hi Joop, > In the case that someone forgot to specify the EDITOR= command I will > fall back to the editor specified in the environment. Very sensible, Tom. It would be interesting if someone's favorite editor could not accept a filename

Re: Using hamlib for CW keying

2019-11-22 Thread Nate Bargmann
* On 2019 22 Nov 14:31 -0600, Csahok Zoltan wrote: > Hi Christian, > > Yes, keying does work with the script. But as far I can see > there are two issues with hamlib keying: > > - in-band speed changes are not supported. one can't send "+++TEST---" > > - sending a large message could block rig

Re: tlf and the nano editor

2019-11-22 Thread Thomas Beierlein
Hi Joop, thanks for the test. It was just a quick shot for a test. I will look into it tomorrow evening. In the case that someone forgot to specify the EDITOR= command I will fall back to the editor specified in the environment. 73, de Tom Am Fri, 22 Nov 2019 20:57:59 +0100 schrieb Joop

Re: Using hamlib for CW keying

2019-11-22 Thread Csahok Zoltan
Hi Christian, Yes, keying does work with the script. But as far I can see there are two issues with hamlib keying: - in-band speed changes are not supported. one can't send "+++TEST---" - sending a large message could block rig interface until it gets queued. Given the rig protocol (KY

Re: tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
Hi Tom, it works okay for the :edit command, but you need to change the code for both the :set and :cfg commands (which allows editing of logcfg.dat), they both start the joe editor, even though I have EDITOR=nano in logcfg.dat. The code is in changepars.c Thanks, Joop Op 22-11-19 om

Re: tlf and the nano editor

2019-11-22 Thread 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

Re: tlf and the nano editor

2019-11-22 Thread Nate Bargmann
* On 2019 22 Nov 09:19 -0600, Joop Stakenborg wrote: > Forgot to edit tlf.1.in. Sorry! Just pass along your diff for it, 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:

Re: tlf and the nano editor

2019-11-22 Thread 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

Re: tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
Forgot to edit tlf.1.in. Sorry! > Op 22 nov. 2019, om 16:10 heeft Joop Stakenborg > het volgende geschreven: > > Ah well... might as well add it right away, seems to work okay here. Diff > attached! > > > > Joop > > Op 22-11-19 om 15:35 schreef joop.stakenb...@xs4all.nl >

Re: tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
Ah well... might as well add it right away, seems to work okay here. Diff attached! Joop Op 22-11-19 om 15:35 schreef joop.stakenb...@xs4all.nl: Thanks Nate! Looks really simple... Will try it out next week. Joop Op 22 nov. 2019 15:13 schreef Nate Bargmann : * On 2019 22 Nov 08:07

Re: tlf and the nano editor

2019-11-22 Thread joop . stakenborg
Thanks Nate! Looks really simple... Will try it out next week.JoopOp 22 nov. 2019 15:13 schreef Nate Bargmann :* On 2019 22 Nov 08:07 -0600, 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

Re: tlf and the nano editor

2019-11-22 Thread Nate Bargmann
* On 2019 22 Nov 08:07 -0600, 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,

tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
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.

Re: TLF-1.4.0 release

2019-11-22 Thread Nate Bargmann
* On 2019 22 Nov 00:56 -0600, Thomas Beierlein wrote: On a side note, something happened with your GPG signature as it appeared to be in "classic PGP" format to Mutt. I did the Esc-P to verify the signature and the message text disappears and all I see is the good signature. Scratches head...

Re: Using hamlib for CW keying

2019-11-22 Thread Ervin Hegedüs
hi Christian, On Fri, Nov 22, 2019 at 12:19:29PM +0100, Christian Treldal wrote: > Hi Ervin > > Den 22.11.2019 kl. 09.49 skrev Ervin Hegedüs: > > > > >ohh... :) > > > >I found it in my Dropbox :P > A memoryleak;-) perfect description :) > >Note, that I've tested now with both Python version

Re: Using hamlib for CW keying

2019-11-22 Thread Christian Treldal
Hi Ervin Den 22.11.2019 kl. 09.49 skrev Ervin Hegedüs: ohh... :) I found it in my Dropbox :P A memoryleak;-) I've been trying to convert it to Py3 , no capitals in socketserver and remove .decode("utf8") and is seems to run; but it don't send anything to the radio. hmm, sounds

Re: Don't forget Winkeydaemon!

2019-11-22 Thread SP3RXO
BTW there is other solution which working great with TLF. Winkeyer USB UDP server by OK2CQR (CQRLOG developer). UDP server allows operation of the Winkey USB by K1EL with any Linux program with UDP keyer capability. It works in the same way as the popular cwdaemon. With Winkeyer USB server

Re: Using hamlib for CW keying

2019-11-22 Thread Ervin Hegedüs
Hi Christian, On Fri, Nov 22, 2019 at 12:18:18AM +0100, Christian Treldal wrote: > > Den 21.11.2019 kl. 14.58 skrev Ervin Hegedüs: > >Hi Christian, > > > >On Thu, Nov 21, 2019 at 12:29:38PM +0100, Christian Treldal wrote: > >>A year or something ago Ervin wrote a quick Python2 script for keying

Re: Don't forget Winkeydaemon!

2019-11-22 Thread Koos van den Hout PE4KH
Quoting Nate Bargmann who wrote on Thu 2019-11-21 at 19:31: > I gathered together the various pieces and put them into Git and have > hosted the code at GitHub for some time: > https://github.com/N0NB/winkeydaemon > > Wilbert has added more contributions over the years, as have Zoltan > All that