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 <dl1...@darc.de>: > 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 <logfilename>' > > 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 <n0...@sbcglobal.net>: > > > On Fri, 22 Nov 2019 15:06:14 +0100 > > Joop Stakenborg <joop.stakenb...@xs4all.nl> 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. > > > -- "Do what is needful!" Ursula LeGuin: Earthsea --
