blocks|key|1781332|text|我回答了我自己的问题！您必须重定向终端输入和输出：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1781333|#!/bin/tcsh
vi+my_file+<+`tty`+>+`tty`|code-block|syntax|javascript|1781334|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I answered my own question! You have to redirect terminal input and output:

<pre><code>#!/bin/tcsh
vi my_file &lt; `tty` &gt; `tty`
</code></pre>

blocks|key|1781341|text|我能够在bash%2BCygwin%2BTerminator下获得所需的行为|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1781342|#!/bin/bash
vim+foo|code-block|syntax|javascript|1781343|运行脚本，vim加载，没有错误消息，行为正常。毫无疑问，在我们的设置之间有几十个变化，所以我不能冒险猜测是什么造成了不同。我很好奇它是什么，但你让它工作了，这是重要的部分。|1781344|entityMap|0|LINK|mutability|MUTABLE|url|http://software.jessies.org/terminator/^0|G|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

I was able to get the desired behavior under bash+Cygwin+<a href="http://software.jessies.org/terminator/" rel="nofollow noreferrer">Terminator</a>:

<pre><code>#!/bin/bash
vim foo
</code></pre>

Run the script, vim loads, no error messages, behaves as normal. There are undoubtedly dozens of variations between our setups, however, so I can't hazard a guess as to what makes the difference. I'm curious what it is, but you got it working, which is the important part.

blocks|key|427120|text|出现这个错误的原因是，当您在您的环境中启动一个shell时，它是在一个子shell中启动的，这个子shell没有将STDIN和STDOUT连接到TTY+--可能是因为这是在某种类似于管道的东西中。当您重定向时，您将打开一个直接连接到设备的新连接。因此，例如，您的命令行将|type|unstyled|depth|inlineStyleRanges|entityRanges|data|427121|$+vi+<+`tty`+>+`tty`|code-block|syntax|javascript|427122|转到|427123|$+vi+<+/dev/ttys000+>+/dev/ttys000|427124|因此，您实际上并没有使用旧的STDIN/STDOUT，而是创建了两个新文件并将它们映射到vi进程的STDIN/STDOUT。|427125|现在，告诉我们你用这个做了什么，我们将告诉你如何避免这种杂乱。|427126|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

The reason you're getting the error is that when you start a shell in your environment, it's starting in a subshell that has STDIN and STDOUT not connected to a TTY — probably because this is in something like a pipeline. When you redirect, you're opening a new connection directly to the device. So, for example, your command line turns 

<pre><code>$ vi &lt; `tty` &gt; `tty`
</code></pre>

into

<pre><code>$ vi &lt; /dev/ttys000 &gt; /dev/ttys000
</code></pre>

So you're not really using your old STDIN/STDOUT, you're creating two new files and mapping them to your vi process's STDIN/STDOUT.

Now, tell us what you're doing with this and we'll tell you how to avoid this kludge.

blocks|key|427168|text|绝对一点儿没错。:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|427169|编写脚本并让其调用EDITOR环境变量，该变量将设置为"emacsclient“。然后启动Emacs，执行M-x+server-start，切换到shell+buffer+(M-x+shell)并执行脚本。Emacsclient将弹出要编辑的内容，C-x+#将充当“完成”命令，并根据您的选择返回到已完成或已中止编辑的脚本。|offset|length|style|CODE|427170|好好享受吧。|427171|编辑:我的意思是说，现在Emacs是我的终端程序。我有几十个shell缓冲区，从来不用担心会丢失输出，并且可以使用Emacs的所有功能来操作和分析终端输出。并让Emacs脚本生成shell的输入。实际上很棒。例如，在编辑源代码或处理邮件或执行几乎任何Emacs操作时，在shell缓冲区中查看Tomcat输出是非常方便的。当出现Tomcat堆栈跟踪时，我可以快速响应它。|427172|entityMap^0|0|1H|G|2F|9|3G|5|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]|$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

Absolutely. :-)

Write your script and have it call the EDITOR environment variable, which you will have set to "emacsclient". Then start up Emacs, execute <code>M-x server-start</code>, switch to a shell buffer (<code>M-x shell</code>) and execute your script. Emacsclient will pop up the thing to be edited and <code>C-x #</code> will act as a "done" command and take you back to your script with edits completed or aborted, as you choose.

Enjoy.

Edit: I meant to add that these days Emacs IS my terminal program. I have dozens of shell buffers and never have to worry about losing output and can use all the power of Emacs to manipulate and analyse the terminal output. And have Emacs scripts generate input to the shells. Awesome actually. For example, watching Tomcat output scroll by in a shell buffer while editing sources or processing mail or doing most any Emacs thing is very convenient. When a Tomcat stack trace appears I can quickly respond to it.

blocks|key|1781405|text|将终端tty设置为一个变量，然后通过该变量重定向编辑器i/o。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1781406|在脚本中：|1781407|#!/bin/sh

ls+%7C+while+read+a;+do+vi+$a+<+$MYTTY+>$MYTTY;+done|code-block|syntax|javascript|1781408|然后使用以下命令执行脚本：|1781409|$+MYTTY=`tty`+./myscript+>/tmp/log|1781410|entityMap^0|3|3|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

Set your terminal <code>tty</code> to a variable, and then redirect the editor i/o through that variable.

In your script:

<pre><code>#!/bin/sh

ls | while read a; do vi $a &lt; $MYTTY &gt;$MYTTY; done
</code></pre>

And then execute the script with:

<pre><code>$ MYTTY=`tty` ./myscript &gt;/tmp/log
</code></pre>

blocks|key|480120|text|在shell脚本'while‘循环中使用'pinfo’时也遇到了同样的问题。可以在脚本中使用这一行，它使用'ps‘查找当前进程号"$$“的tty，并将该tty存储在$KEY_TTY中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|480121|++KEY_TTY=/dev/`ps+%7C+grep+$$+%7C+tr+-s+'[:blank:]'+%7C+cut+-d+"+"+-f+3`|code-block|syntax|javascript|480122|稍后在脚本中，只需调用tty-only程序，并将$KEY_TTY作为输入，在我的示例中是：|480123|++pinfo+-m+$s+$page+<+$KEY_TTY|480124|对于'vi‘，应该是：|480125|++vi+$a+<+$KEY_TTY+>+$KEY_TTY|480126|优点是脚本作为一个整体仍然可以接受STDIN输入，并且'vi‘(或其他任何东西)应该可以很好地工作--而不必记得在运行脚本之前设置任何环境变量。|480127|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Had the same trouble with 'pinfo' in a shell script 'while' loop. The line can be used in the script, it uses 'ps' to find the tty of the current process number, "$$", and stores that tty in $KEY_TTY:

<pre><code> KEY_TTY=/dev/`ps | grep $$ | tr -s '[:blank:]' | cut -d " " -f 3`
</code></pre>

Later in the script, just call the tty-only proggie, with $KEY_TTY as input, in my case it was:

<pre><code> pinfo -m $s $page &lt; $KEY_TTY
</code></pre>

For 'vi' it'd be:

<pre><code> vi $a &lt; $KEY_TTY &gt; $KEY_TTY
</code></pre>

The advantage is that the script as a whole can still accept STDIN input, and 'vi' (or whatever) should work fine -- without having to remember to set any environmental variables before running the script.

blocks|key|1834409|text|我想做一些类似的事情。我想要一个别名，它可以找到我正在处理的最后一个文件，并在vi(1)中打开它进行编辑。无论如何，我不知道如何将它作为一个可读的别名(在tcsh中)，所以我只创建了一个丑陋的shell脚本(csh，因为我老了)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1834410|#!/bin/csh

set+DIR+=+"~/www/TooMuchRock/shows/"

set+file+=+$DIR`ls+-t+$DIR+%7C+head+-1`
set+tty+=+`tty`

vi+$file+<$tty+>$tty|code-block|syntax|javascript|1834411|(1)本地，vi+vi:别名为/usr/+kraftwerk:bin>+/bin/vim+-u+~/.exrc|1834412|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I wanted to do something similar. I wanted an alias that would find the last file I was working on, and open it in vi(1) for editing. Anyway, I couldn't figure out how to do it as a readable alias (in tcsh) so I just created an ugly shell script (csh because I'm old) instead:

<pre><code>#!/bin/csh

set DIR = "~/www/TooMuchRock/shows/"

set file = $DIR`ls -t $DIR | head -1`
set tty = `tty`

vi $file &lt;$tty &gt;$tty
</code></pre>

(1) kraftwerk:bin> which vi
vi: aliased to /usr/local/bin/vim -u ~/.exrc

I would like my tcsh script to launch an editor (e.g., vi, emacs):

<pre><code>#!/bin/tcsh
vi my_file
</code></pre>

This starts up vi with my_file but first displays a warning "Vim: Warning: Output is not to a terminal" and my keystrokes don't appear on the screen. After I kill vi, my terminal window is messed up (no newlines), requiring a "reset". I tried "emacs -nw", "xemacs -nw", and pico with similar results. "xemacs" works but launches a separate window. I want to reuse the same terminal window.

Is there a way to launch an editor from a script so that it reuses the same terminal window?

How do I launch an editor from a shell script?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想让我的tcsh脚本启动一个编辑器(例如vi、emacs)：#!/bin/tcshvi my_file这将使用my_file启动vi，但首先会显示警告"Vim: Warning: Output is not to to terminal“，并且我的按键不会出现在屏幕上。在我杀死vi之后，我的终端窗口被弄乱了(没有换行...

问如何从shell脚本启动编辑器？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从shell脚本启动编辑器？EN