7
In your ~/.vimrc add the line
set splitbelow
This will cause all splits to happen below (including term)
6
The still somewhat new internal terminal implementation of Vim 8 uses the StatusLineTerm highlighting group for the active window and the StatusLineTermNC highlighting group for the statusline of an inactive window.
So you might want to tweak the corresponding highlighting groups like this:
:hi StatusLineTerm ctermbg=red ctermfg=black guibg=#ff0000 guifg=...
6
From vim/src/eval.c:
static void eval_job_process_exit_cb(Process *proc, int status, void *d) {
[..]
if (data->term && !data->exited) {
data->exited = true;
char msg[sizeof("\r\n[Process exited ]") + NUMBUFLEN];
snprintf(msg, sizeof msg, "\r\n[Process exited %d]", proc->status);
terminal_close(data->...
5
You can replace the current window with a terminal using
:terminal ++curwin
:ter ++curwin " shorter form
You can create a mapping or command for convenience
nnoremap \t :terminal ++curwin<cr>
command! Terminal terminal ++curwin
5
First, your function can be simplified into
let bufnr = term_start(&shell, {"hidden": 1})
Second, it's not a problem to have buftype ==# 'terminal' and set nobuflisted together, as these are two different options. So
if bufnr
call setbufvar(bufnr, "buflisted", 0)
endif
is very much okay. However, the real question is: why you create a terminal at ...
4
You can change the name of any buffer by using the :file {name} command. However, doing so changes that alternate-file to the previous name, which you may not want in this case. The :keepalt command avoids that issue.
Putting it all together, this should do what you want
keepalt file meaningful
4
This is my solution for closing terminal windows automatically when the terminal process completes with 0 exit status.
Using Martin Tournoij's answer as a starting point I did some investigating on how to get the terminal process exit code in a TermClose event handler. You can examine buffer content to parse the [Process exited ?] line that is appended to ...
4
Thanks to Christian Brabandt, :ter ++curwin was the thing that I want.
4
You could overwrite the mapping by a buffer-local mapping. Just map <ESC> to <ESC>:
tnoremap <buffer> <ESC> <ESC>
4
You need to use :tnoremap to map keys in the :terminal window.
So if you want that to work in both normal mode of a regular buffer and of terminal windows, you need to add another set of mappings for the terminal:
tnoremap <C-J> <C-W><C-J>
tnoremap <C-K> <C-W><C-K>
tnoremap <C-L> <C-W><C-L>
tnoremap <...
4
Neovim's terminal has "a specialty": a mouse click automatically switches it to "Terminal-Normal" mode. (BTW. That's not a case for Vim, so it does not suffer from this issue.)
So it won't work from <LeftMouse>, but we can map <LeftRelease> instead:
if has('nvim')
augroup terminal_setup | au!
autocmd TermOpen * nnoremap <buffer&...
4
Full restore
If you want to restore layout with multiple termina buffers, you must restore other windows and buffers too, so it's in fact a full buffer layout restore, it's usage is not limited to terminal buffers. Three things must be done to achive that:
Split windows according to saved layout. We can use result of winlayout() to do this.
Load buffer in ...
3
Neovim uses its own internal terminal emulator for :term. You can not change that (as far as I know). The thing you can change is the command interpreter/shell that runs in that terminal. See Wikipedia for the difference: Terminal vs Shell.
You can start any command (that you have installed) in the terminal if you just specify it as the argument: :...
3
To open a terminal for running command with height 20 you can do
:new +resize20 term://command
If the terminal is ready created, you either use :resize 20 or 20<c-w>_ for height. :vertical resize 20 or 20<c-w>| for width.
3
A better way which I use (and love these days) to jump between terminal (interactive mode with all alias and path set) and vim is using CTRL+Z in normal mode. Work on terminal, and when done type fg to return back to vim right where I left.
CTRL+Z Suspend Vim, like :stop. Works in
Normal and in Visual mode.
1. Suspend and resume
Like most Unix ...
3
I ran into a similar (the same?) issue on two different installs:
NVIM v0.2.0
NVIM v0.3.1
As quanta already mentions this change in behavior might be due to the changes introduced in NVIM v0.2.1.
I have a shortcut for running things from within nvim, that splits the window, launches the terminal emulator in the new split view and executes there. After ...
3
This should work too:
augroup termIgnore
autocmd!
autocmd TerminalOpen * set nobuflisted
augroup END
3
Use :belowright:
:belowright terminal
Or, more succinctly:
:bel term
This command is a modifier and affects the command run right after it.
(Another useful modifier here is :vertical, to split vertically instead.)
3
I assume you aren't literally asking for a --start-terminal flag :) ...but you can specify a command for Vim to run after it starts up using the -c flag.
So this should be as easy as
vim -c ':term ++curwin'
When I run it I am indeed in a terminal window on the shell command line and it's the only window open. Hopefully that covers what you're asking for.
2
This seems to be related to a known bug involving not listing the terminal buffer at times. This prevents the problem set hidden. It is currently (March 2016) planned to fix this in the upcoming 0.2 release.
2
This is obviously an opiniated question. Here's my opinion.
Advantages of neovim (or Vim) terminal:
Normal mode gives the power of Vim inside a terminal window
Can use vimscript to customize mappings and commands
Advantages of tmux:
Allows persistent sessions
IMHO this is the most important aspect of tmux, because:
It allows to detach a session, then ...
2
I have made a small plugin vpager. That allows to dump the terminal output back into Vim.
The last commit in addition allows to use the output and dump it into the quickfix list. So you can simply do :make |vpager -Q and it should be loaded back in Vim.
(It might need adjustments for the errorformat setting, not sure).
excerpt from the README:
git diff | ...
2
I guess caddbuffer is currently the best way to achieve what I want.
2
If you want to paste something into the terminal window, you can use the command CtrlWReg (if you are in terminal job mode).
For your macro, that would be something along:
qqY<C-W>w<C-W>"0<C-W>wq (provided that the cursor is at the start of the line in the other window.
The error message Cannot make changes, 'modifiable' is off happens ...
2
This should do the job:
function! BnSkipTerm()
let start_buffer = bufnr('%')
bn
while &buftype ==# 'terminal' && bufnr('%') != start_buffer
bn
endwhile
endfunction
nnoremap <leader>bn :call BnSkipTerm()<CR>
It just keeps invoking :bn until it's not in a terminal window, by checking the 'buftype' setting.
2
From :h terminal-typing
CTRL-W can be used to navigate between windows and other CTRL-W commands, e.g.:
CTRL-W CTRL-W move focus to the next window
CTRL-W : enter an Ex command
2
One other thing that you can do is use <Ctrl-P> to go to the 'Previous' command. This is also works in bash terminals. You can also do <Ctrl-N> to go to the 'Next' command.
2
I would solve this in bash:
1) Move all setting that you need in login shells and non-login shells to the file .bashrc
2) Add the following to the end of your .bash_profile:
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
You could drop the if..., as the file always exists.
Background: The file .bashrc is source ...
2
The problem is that you can't really use :normal in terminal mode, since that mode is special, it doesn't really behave like Normal/Insert mode in a normal vim buffer.
Instead, you can use the term_sendkeys() function to send the buffer to the terminal.
This should work:
:execute "normal yaw\<c-w>j" | call term_sendkeys('', @0)
Or:
:execute "...
2
A little experiment:
Go to your fresh opened terminal, and do an echo:
echo 1
Leave it in terminal job mode, go back to your original window, execute:
exec "norm! \<c-w>pggyy\<c-w>pp"
You should see a new line in your current buffer, it's copied from first line of terminal buffer. As ggyy are normal mode commands, it tells us that when you ...
Only top voted, non community-wiki answers of a minimum length are eligible
