aboutsummaryrefslogtreecommitdiff
path: root/test/functional/core/startup_spec.lua
Commit message (Collapse)AuthorAge
...
* test: fix failure on Windows (allow ".exe")Justin M. Keyes2019-09-13
| | | | ref 77594d55f709
* startup: fail if --embed with -es/-Es #10753glacambre2019-09-13
| | | | Closes https://github.com/neovim/neovim/issues/10031
* Merge #10973 'vim-patch:8.1.1197'Justin M. Keyes2019-09-08
|\
| * vim-patch:8.1.1197: when starting with multiple tabs file messages is confusingJan Edmund Lazo2019-09-08
|/ | | | | | Problem: When starting with multiple tabs file messages is confusing. Solution: Set 'shortmess' when loading the other tabs. (Christian Brabandt) https://github.com/vim/vim/commit/c75e81262347e47a69faabd72caf89fec3f06e8f
* Merge #10098 'win: fix msg_puts_printf()'Justin M. Keyes2019-08-12
|\
| * Add test for #7967erw72019-06-09
| |
* | main: do event_init before early_init #10183Daniel Hahler2019-06-12
|/ | | | | | Fixes https://github.com/neovim/neovim/issues/10172 * move log_init to event_init * move init_signs to end of early_init
* Fix issue where test failserw72019-06-04
|
* test: clear(): `args_rm` parameterJustin M. Keyes2019-04-27
|
* startup: -es/-Es (silent/batch mode): skip swapfile #8540Justin M. Keyes2019-04-10
| | | | To use Nvim as a scripting engine the side-effects of swapfiles and user config should be avoided by default.
* startup: Use $XDG_CONFIG_DIRS/nvim/sysinit.vim if it existsJames McCoy2018-12-16
| | | | Closes #8994
* Fix crash if --embed is used more than onceJames McCoy2018-10-03
|
* startup: delete empty stdin buffer if other files were openedJustin M. Keyes2018-06-18
| | | | | | | | | DWIM: avoid empty buffer 1 when stdin was empty. If other files were specified at startup, we assume that stdin is only accidentally not-a-TTY: user did not intend to send text from it. ref #8560 ref #8561
* startup: go to buffer 2 if stdin is emptyJustin M. Keyes2018-06-18
| | | | | | | | | | | | If stdin is not a TTY we read it into buffer 1, as text. But if the stdin pipe is empty, Nvim was most likely invoked for some other reason. DWIM: select buffer 2 (if it exists). Example: echo file1 | xargs nvim closes #8560 closes #8561 ref https://github.com/equalsraf/neovim-qt/issues/417
* startup: fix -E/-Es without `-u NONE`Justin M. Keyes2018-06-17
| | | | | | | | | | Before this change, -E/-Es without `-u NONE` reads stdin as Ex commands. It should always read stdin as text (into buffer 1), like this: echo foo | nvim -Es +'%p' foo echo foo | nvim -Es -u NORC +'%p' foo
* Ex mode: use getexline() instead of getexmodeline()Justin M. Keyes2018-06-17
| | | | | | | | | | | | | | | | | | | | | This changes Ex mode (Q, -e) to work like Vim's "improved Ex mode" (gQ, -E). That brings some small behavior differences, but should not impact most Ex scripts (unless, for example, they depend on mappings being disabled--but that can be solved for -e by skipping user config). Before this change: * the screen test hangs. After this change: * Q acts like gQ. * -e/-es differs from -E/-Es only in its treatment of stdin. This moves towards potentially removing getexmodeline(). (HINT: That does NOT mean "removing Ex mode", it means removing the Vi-compatible Ex mode, which differs from Vim's "improved Ex mode" only in some minor details (e.g. mappings are disabled).) ref #1089 :-)~
* test: fix startup_specJustin M. Keyes2018-06-10
| | | | | This behavior was changed (improved) by 5861dc596687 which actually makes -E more faithful to Vim's behavior.
* cleanup, test interactive -EJustin M. Keyes2018-06-04
|
* win/startup: remove --literalJustin M. Keyes2018-06-04
| | | | | | | | | | | | | | | Fixes 2 failing tests in startup_spec.lua. The Windows-only `--literal` option complicates support of "stdin-as-text + file-args" (#7679). Could work around it, but it's not worth the trouble: - users have a reasonable (and englightening) alternative: nvim +"n *" - "always literal" is more consistent/predictable - avoids platform-specific special-case Unrelated changes: - Replace fileno(stdxx) with STDXX_FILENO for consistency (not motivated by any observed technical reason).
* startup: allow explicit "-" file arg with --headlessJustin M. Keyes2018-06-04
|
* startup: fix -es/-Es so they are actually silentJustin M. Keyes2018-06-04
| | | | | | silent-mode (-es/-Es) has been broken for years. The workaround up to now was to include --headless. But --headless is not equivalent because it prints all messages, not the limited subset defined by silent-mode.
* startup: stdin as text instead of commandsJustin M. Keyes2018-06-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Treat stdin as text by default (so the "-" file is not needed): echo foo | nvim It works with file args (implemented in next commit), too: echo foo | nvim file1.txt file2.txt Why? Because: - Execution of input is (1) almost always unintentional/confusing, and (2) potentially destructive. - Avoids the need for time-delayed warning. #7659 - The _common_ case is to open text in a buffer, not send commands. Note: - Not for Ex-mode (-es) because it is used by scripts. But maybe `-Es`? - Not for --headless, because stdio may be a protocol stream and may be used for any purpose by stdioopen(). To treat stdin as Normal-mode commands, use `-s -` instead: echo ifoo | nvim -s - Other alternatives: - Replay a register. E.g. the following mostly works, except @q aborts on any "beep" (e.g. if the cursor can't move). nvim -c '%d q|norm @q' - - Future: Let `:%source` work with unsaved buffer contents? closes #2087 closes #7659
* test: startup_spec: cmd.exe escapingJustin M. Keyes2017-11-04
|
* test: has("ttyin"), has("ttyout")Justin M. Keyes2017-11-04
generated by cgit (git 2.34.1) at 2026-10-20 02:28:53 +0000