可以在带有屏幕的 vim 中执行 python 代码，但不能没有。为什么？

Question

所以，我希望能够在 Vim 中执行我的 python 代码，所以我去了这里：Running Python code in Vim 并找到了答案。我主要尝试在 GNU Screen 中工作，这就是我在 .vimrc 中添加以下代码时的工作方式：nnoremap <buffer> <F9> :exec '!python' shellescape(@%, 1)<cr>。我的 .vimrc 中的这一行通过 GNU Screen 在 Vim 中工作得很好，但我也想让它在不使用 Screen 的情况下工作，这是我的问题。

例如，如果我运行一个简单的 Python 程序

greeting = "Hello"
print (greeting)
name = input("Please enter your name: ")
print(greeting + " " + name)

然后按 F9，它会退出 Vim 并在终端提示我。在 Screen 中，它会在缓冲区（在 Vim 的底部）提示我，这是所需的行为。有人遇到这个问题或知道如何解决这个问题吗？

这是我的 .vimrc（和 .bashrc）文件，代码行在第 43 行。我为 python3 设置了它，但它表现出相同的行为，无论我设置的 Python 版本是什么。

vimrc

" use visual bell instead of beeping
"set vb
"   
" Basics {
set nocompatible " explicitly get out of vi-compatible mode
" i added this for colorshemes
"set term=xterm-256color

if $COLORTERM == 'gnome-terminal'
      set t_Co=256
  endif

syntax on
syntax enable
set background=dark

"let g:two_firewatch_italics=1 "firewatch
"colo two-firewatch "firewatch

" General {
filetype plugin indent on " load filetype plugins/indent settings
set autochdir " always switch to the current file directory 
set backspace=indent,eol,start " make backspace a more flexible
set fileformats=unix,dos,mac " support all three, in this order
set iskeyword+=_,$,@,%,# " none of these are word dividers
set mouse=a " use mouse everywhere
set whichwrap=b,s,h,l,<,>,~,[,] " everything wraps
set wildmenu " turn on command line completion wild style

" Vim UI {
set laststatus=2 " always show the status line
set linespace=0 " don't insert any extra pixel lines betweens rows
set matchtime=5 " how many tenths of a second to blink matching brackets for
set novisualbell " don't blink
set number " turn on line numbers
set ruler " Always show current positions along the bottom
set showcmd " show the command being typed
set showmatch " show matching brackets
set statusline=%F%m%r%h%w[%L][%{&ff}]%y[%p%%][%04l,%04v]
nnoremap <C-N> :next<Enter> " this replaces :next, when opening multiple files
nnoremap <C-P> :prev<Enter> " this replaces :prev, when opening multiple files

nnoremap <buffer> <F9> :exec '!python3' shellescape(@%, 1)<cr>
set confirm

" Text Formatting/Layout {
set tabstop=4
set expandtab
set shiftwidth=4 " not sure what this does?
set smarttab autoindent
set softtabstop=4 " when hitting tab or backspace, how many spaces 


" paste mode - this will avoid unexpected effects when you
" cut or copy some text from one window and paste it in Vim.
set pastetoggle=<F2>

" The 3 commands below are an experiment
" save file (ctrl-s)
"   :map <C-s> :w<cr>
" copy selected text (ctrl-c)
"   :vmap <C-c> y
" Paste clipboard contents (ctrl-v)
"   :imap <C-p> <esc>P
  " Press i to enter insert mode, and ii to exit. 
:imap jj <Esc>
:inoremap <C-S> <C-O>:w<CR>


" Filetype-Dependent Settings
filetype plugin on
filetype indent on

set modifiable

" Pathogen related
execute pathogen#infect()
call pathogen#helptags()
syntax on
filetype plugin indent on

"colorscheme molokai
highlight Comment cterm=bold

if &term =~ '256color'
  " disable Background Color Erase (BCE) so that color schemes
  " render properly when inside 256-color tmux and GNU screen.
  " see also http://snk.tuxfamily.org/log/vim-256color-bce.html
  set t_ut=
endif

bashrc

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
export TERM=xterm-256color
# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi

export NVM_DIR="/home/serge/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm

Answer 1

如果你使用:exec 从vim 运行任何东西，它总是在终端上。稍微简化一下，它或多或少类似于：当您从 vim 生成命令时，它会切换到终端并调用 终端初始化序列。 终端初始化序列的确切含义是在终端定义中编码的。例如，对于 xterm，它意味着 切换到以前使用的缓冲区并将光标设置在此缓冲区上的最后一个已知位置。对于屏幕，这意味着：将光标移动到屏幕的底线。这就是为什么它会给你 vim 缓冲区的外观。顺便说一句，对于其他类型的终端，它可能是清理屏幕并将光标移动到顶行。正如我所说 - 这是简化。如果您对技术细节感兴趣，ncurses 是值得阅读的主题。

因此，总而言之，vim 总是要求终端执行相同的终端命令序列。如果给定的命令是已知的并由终端执行，则取决于终端。

如果你想在 vim 缓冲区中运行一些东西来获取结果，你需要编写一个插件来创建一个缓冲区，并使你的命令和缓冲区之间的交互成为可能。如果有人已经编写了这样的扩展，我不会感到惊讶，但我也不能保证。