On Mi, 18 Apr 2018, Christian Brabandt wrote:
> Bram,
> can you please include the following change in the next runtime update?
Here is another small doc patch. This might explain the following behaviour:
./vim --clean '-c :e foobar' -c ':au WinEnter <buffer> echom "Entering Window
for buffer ". expand("<amatch>")'
Then do `:tabedit ~/.vim/vimrc` and you'll notice a new message
,----
| Entering Window for buffer /home/chrisbra/code/vim-src/src/foobar
`----
diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index 25c5e0f96..0c72fe451 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -1074,9 +1074,10 @@ WinEnter After entering another window.
Not done for
If the window is for another buffer, Vim
executes the BufEnter autocommands after the
WinEnter autocommands.
- Note: When using ":split fname" the WinEnter
- event is triggered after the split but before
- the file "fname" is loaded.
+ Note: For split and tabpage commands the
+ WinEnter event is triggered after the split
+ or tab command but before the file "fname" is
+ loaded.
*WinLeave*
WinLeave Before leaving a window. If the window to be
entered next is for a different buffer, Vim
Mit freundlichen Grüßen
Christian
--
Die größte Ersparnis, die sich im Bereich des Denkens erzielen läßt,
besteht darin, die Nicht-Verstehbarkeit der Welt hinzunehmen - und
sich um den Menschen zu kümmern.
-- Albert Camus
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
