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 -06

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 p

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. Fr

Re: tlf and the nano editor

As a final touch TLF now rereads the whole logfile after the editing command is finished. That was not implemented correctly before. For all that who want to experiment with a graphical editor (gedit, gvim, ...) make sure that the editor stays in foreground and blocks TLF until editing is done. Ot

Re: tlf and the nano editor

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

Re: tlf and the nano editor

Zoli's idea is the first thing I thought of, too. But the suggested method of using EDITOR from tlf config as first priority, then falling back on the shell environmental variable as 2nd priority I think would be better. I could image someone preferring some editor for most of their usual work, b

Re: tlf and the nano editor

* On 2019 23 Nov 01:18 -0600, Csahok Zoltan wrote: > My 2c: try with "export EDITOR=..." Hi Zoli, This is the setting in log_cfg.dat that I am testing with Tom's new patch to allow specifying any editor, not a shell variable. 73, Nate -- "The optimist proclaims that we live in the best of all

Re: tlf and the nano editor

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

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 m

Re: tlf and the nano editor

* 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 o

Re: tlf and the nano editor

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 Staken

Re: tlf and the nano editor

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 20:

Re: tlf and the nano editor

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 stri

Re: tlf and the nano editor

* 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: https://gi

Re: tlf and the nano editor

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 debu

Re: tlf and the nano editor

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

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 -060

Re: tlf and the nano editor

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 ex

Re: tlf and the nano editor

* 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, have

tlf and the nano editor

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. M