aboutsummaryrefslogtreecommitdiff
path: root/test/functional/autocmd/tabnewentered_spec.lua
Commit message (Collapse)AuthorAge
* tabpage: "tabnext #" switches to previous tab #11734butwerenotthereyet2020-01-20
|
* tabpage: :tabs indicates previous tabpage's curwinWe're Yet2020-01-19
|
* tabpage: disallow go-to-previous in cmdline-win #11692butwerenotthereyet2020-01-09
| | | | | | | | | | | | | | After cbc8d72fde4b19176028490934ff7a447afe523c when editing the command in the command editing window (q:, q/, q?) it was possible to switch to the previous tab. Doing so put Nvim in a bad state. Moreover, switching tabs via the other available mechanisms (gt, gT, <C-W>gt, <C-W>gT) is not possible when in the command editing window. Here, the behavior is prevented. It is no longer possible to switch to the previous tab when editing the command in the command editing window. The solution is to share code between gt, gT, and g<Tab>. Specifically, goto_tabpage_lastused now calls through goto_tabpage rather than directly calling goto_tabpage_tp. Doing so works well because all the validation enjoyed by gt and gT is present in goto_tabpage.
* tabpage: track last-used tabpage #11626butwerenotthereyet2020-01-02
| | | | | | | | | In a multi-window scenario, it is possible to return focus to the last accessed window via n_CTRL-W_p. However, in the case of a multi-tab scenario, there was previously no way to return focus to the last accessed *tab*. Here, that ability is added via n_g<tab>. Additionally, the index of the previous tab is exposed via tabpagenr('#'), mirroring the existing functionality of winnr('#').
* API: deprecate nvim_command_outputJustin M. Keyes2019-12-02
|
* api: change nvim_command_output behaviorJustin M. Keyes2018-01-10
| | | | | | | | | | | | | | | | | | | Implement nvim_command_output with `execute({cmd},"silent")`. Behavior changes: - does not provoke any hit-enter prompt - no longer prepends a newline char - does not capture some noise (like the "[New File]" message, see the change to tabnewentered_spec.lua) Technically ("bug-for-bug") this a breaking change. But the previous behavior of nvim_command_output meant that it probably wasn't used for anything outside of tests. Also remove the undocumented `v:command_output` variable which was a hack introduced only for the purposes of nvim_command_output. closes #7726
* Windows: enable more testsJustin M. Keyes2017-01-13
|
* Mark some functional tests as pending in WindowsRui Abreu Ferreira2016-08-26
|
* Merge #4984 'Trigger TabNewEntered with <CTRL-W>T'Justin M. Keyes2016-06-28
|\ | | | | | | Closes #4979
| * [RFC] Fix #4979: Trigger TabNewEntered also with <CTRL-W>TDimitri Merejkowsky2016-06-28
|/ | | | Original patch by @fmoralesc
* functests: Check logs in lua codeZyX2016-06-10
| | | | | | It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
* test/functional: clean up according to luacheck (part 2)Marco Hinz2015-11-23
|
* Add TabNewEnteredFelipe Morales2015-02-16
TabNewEntered is triggered after vim has entered a buffer in new tab.