On Saturday, April 11, 2015 at 10:30:27 AM UTC+5:30, Yuri wrote:
> Once in a while I get into this after accidentally typing the wrong command:
> # vim some-file | some-cmd
> bash: some-cmd: command not found
> Vim: Warning: Output is not to a terminal
> ^C
>
> Ctrl-C doesn't kill vim. So I have
On Saturday, April 11, 2015 at 10:30:27 AM UTC+5:30, Yuri wrote:
> Once in a while I get into this after accidentally typing the wrong command:
> # vim some-file | some-cmd
> bash: some-cmd: command not found
> Vim: Warning: Output is not to a terminal
> ^C
>
> Ctrl-C doesn't kill vim. So I have
On 04/11/2015 19:32, Nazri Ramliy wrote:
This will break existing scripts that depend on the current default
behavior and that's not good.
You motivation for the patch is to work around accidentally typing
vim some-file | some-cmd.
I do make the same mistake myself but I don't think this is
Hi,
Yuri schrieb am 11.04.2015 um 07:00:
Once in a while I get into this after accidentally typing the wrong command:
# vim some-file | some-cmd
bash: some-cmd: command not found
Vim: Warning: Output is not to a terminal
^C
Ctrl-C doesn't kill vim. So I have to press Ctrl-Z and then
On Sat, Apr 11, 2015 at 8:00 AM, Yuri y...@rawbw.com wrote:
Once in a while I get into this after accidentally typing the wrong command:
# vim some-file | some-cmd
bash: some-cmd: command not found
Vim: Warning: Output is not to a terminal
^C
Ctrl-C doesn't kill vim. So I have to press
On 04/11/2015 00:06, Sergey Alyoshin wrote:
kill %1 after ctrl-z in bash.
Why vim even starts when the output isn't a terminal? This Warning:
Output is not to a terminal should be the terminal error.
Usually text programs that print with colors fall back into non-colored
output mode, and vim
On 11 April 2015, Yuri y...@rawbw.com wrote:
On 04/11/2015 00:06, Sergey Alyoshin wrote:
kill %1 after ctrl-z in bash.
Why vim even starts when the output isn't a terminal?
It's useful in various situations, such as batch runs, or debugging
raw escape sequences sent to the terminal.
On 04/11/2015 19:32, Nazri Ramliy wrote:
This will break existing scripts that depend on the current default
behavior and that's not good.
What scripts are you talking about?
Yuri
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
On 04/11/2015 04:58, LCD 47 wrote:
It's useful in various situations, such as batch runs, or debugging
raw escape sequences sent to the terminal.
Since tolerance to non-terminal is something that obviously only a very
tiny fraction of users needs, I made this patch that makes such
On Sun, Apr 12, 2015 at 6:50 AM, Yuri y...@rawbw.com wrote:
Since tolerance to non-terminal is something that obviously only a very tiny
fraction of users needs, I made this patch that makes such tolerance a
non-default behavior. New command line option --allow-non-term enables the
old
10 matches
Mail list logo
