|
From: | Juergen Sauermann |
Subject: | Re: [Bug-apl] Calling external editor from APL session |
Date: | Wed, 21 Dec 2016 13:35:36 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
Hi Alexey, I am myself not familiar with emacs and, as a matter of fact, I do not even have it installed on my machine. I believe the most efficient way to write APL programs these days is to edit the functions and variables offline in a separate .apl file which is then run in a separate window. Like you write a C/C++ program beforehand. compile it, and then execute it. With that approach you can use whatever editor you prefer and you have all the functions and variables in a single file and in a consistent state. It also simplifies the documentation and publishing of APL programs lot. You can also check-in the .apl files into a revision control system, diff them, and so on. The interactive mode of APL (including function editing) has always had severe limitations and I have provided it only for compatibility and for the elder APL programmers who are used to it. The interactive mode was definitely an improvement over the punch cards used when APL was invented, but today the capabilities of computers are very different and I would not recommend the interactive mode for newcomers to APL. The absolute cool thing with xterm (actually with X) is marking and cut-and-paste with the middle mouse button. I use it a lot in both APL and C/C++ and I have not seen any editor (not even vi/vim) being able to do that like X. And the Ctrl-C/Ctrl-V of Windows (which is unfortunately adopted by more and more GNU/Linux programs) is IMHO a pain in the back and a good reason to change to a different operating system /// Jürgen On 12/21/2016 10:39 AM, Alexey
Veretennikov wrote:
Hi, Yes Emacs support is great but what to do whith the people who don't use emacs (or can't use it comfortably for some reasons, like absense of Alt/Meta key or being on low-performance device). Blake's editor is just probably too old school :) I will try to follow the Kacper's approach combining with calling external 'xterm' with the editor. The Dyalog has convenient built-in fullscreen editor even in console mode which you can close by hitting Esc key applying changes, see example screenshot attached. |
[Prev in Thread] | Current Thread | [Next in Thread] |