[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-apl] Calling external editor from APL session
From: |
Kacper Gutowski |
Subject: |
Re: [Bug-apl] Calling external editor from APL session |
Date: |
Tue, 20 Dec 2016 16:07:58 +0100 |
User-agent: |
NeoMutt/20161126 (1.7.1) |
On Tue, Dec 20, 2016 at 10:30:14AM +0100, Alexey Veretennikov wrote:
> Using )HOST Vim complains "Vim: Warning: Output is not to a terminal"
> and not really useful (can't see what I type for instance).
> Same if I use popen() via ⎕FIO.
)HOST and popen are essentially the same thing and they both capture
output of the command you are running. But as they take command to
be interpreted by shell, you can explicitly redirect output to the
terminal yourself:
)HOST vim >/dev/tty
In case of vim, which reinitializes terminal settings itself and isn't
bothered by having echo disabled, this is everything you need to make
it work.
See also <https://lists.gnu.org/archive/html/bug-apl/2016-03/msg00138.html>
for working proof-of-concept implementation of what Jürgen wrote.
-k
Re: [Bug-apl] Calling external editor from APL session,
Kacper Gutowski <=
- Re: [Bug-apl] Calling external editor from APL session, Alexey Veretennikov, 2016/12/20
- Re: [Bug-apl] Calling external editor from APL session, Juergen Sauermann, 2016/12/20
- Re: [Bug-apl] Calling external editor from APL session, Alexey Veretennikov, 2016/12/21
- Re: [Bug-apl] Calling external editor from APL session, Juergen Sauermann, 2016/12/21
- Re: [Bug-apl] Calling external editor from APL session, David B. Lamkins, 2016/12/21
- Re: [Bug-apl] Calling external editor from APL session, Juergen Sauermann, 2016/12/21
- Re: [Bug-apl] Calling external editor from APL session, David B. Lamkins, 2016/12/21