New answers tagged

0

I'm using Terminal on OSX, the same happens on remote Linux. I don't know about Terminal, but if you are on OSX, your mappings should work out of the box, provided that you use a recent Vim version, and a recent iTerm2 terminal. You need at least the Vim patch 8.1.2134. Having the patch 8.1.2194 also helps, because it automatically enables the ...


0

You have another option. NeoVim works with M-x out of the box when you have terminal sending ESC + sequence, which mostly every terminal could. As a summary for other answers, I think your two options are Turning using "opt as meta" off, using the actual sent code in mapping Turning using "opt as meta" on, using <esc>x type of ...


0

As stated by D. Ben Knoble, Terminal.app does not support termguicolors. I have found that using iTerm2 I can have these display perfectly.


1

You have to exit terminal's insert mode using <C-\><C-N> command and then you can use VIM commands to jump through terminal's history (e.g. gg or <C-u>). You can enter insert mode using i once again. Kudos for @Matt, who answered this question in the comments.


2

Short answer: use :terminal {command} for interactive stuff. Long answer: neovim’s :! actually communicates via subprocesses and the commands are not directly interactive due to the way the IO streams are handled. :terminal is envisioned as the replacement for this, since it does use a TTY and is interactive.


4

You can specify commands to be run using the -c argument. Therefore, this should work for you: vim -c 'terminal ++curwin' -c 'vertical terminal' If your goal is just to have two terminal windows side-by-side, there are also non-vim solutions to this which may be more appropriate depending on your use case e.g. GNU screen, tmux.


1

Check if your vim supports + register, :version output should include +clipboard. I would suggest to use other registers for that. Your normal command is wrong. Try smth like: function! CopyRun(start,stop) " This would still not work as normal commands do not take range as ex commands... exe "normal! " . a:start . "," . a:...


0

In my macOS system, the unique name of the terminal program is set in environment variable TERM_PROGRAM. Apple's inbuilt Terminal, iTerm2, WezTerm return sensible unique names that correctly identify them. As of writing this, Alcritty does not set it to any value, and Kitty terminal emulator returns wrong name "Apple_Terminal". Run echo $...


0

base16-vim themes set the colors_name variable to the theme name. base16-universal-manager is supposed to generate a single theme file under any filename for vim, I've named mine base16.vim. Because the filename is base16.vim, I set the colorscheme to base16. Inside that file, the theme is declaring let g:colors_name = "base16-onedark". I finally ...


Top 50 recent answers are included