Skip to content

/ macvim

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bad interaction between guioptions=! and TerminalOpen #896

Open
lifepillar opened this issue May 30, 2019 · 1 comment
Open

Bad interaction between guioptions=! and TerminalOpen #896

lifepillar opened this issue May 30, 2019 · 1 comment

Comments

@lifepillar
Copy link
Contributor

@lifepillar lifepillar commented May 30, 2019 •
edited

When external commands are executed in a terminal window and a TerminalOpen autocommand is defined, the command may affect the current window.

To Reproduce

  1. Run mvim -N -i NONE -u vimrc where vimrc has the following content:
  set number
  autocmd TerminalOpen * set nonumber
  set guioptions=!
  1. Type :!ls (or any other :! command)
  2. You should see the line numbers have disappeared from the current window.

I am expecting that the external command is executed in a different window, hence options set in the terminal window shouldn't affect the current window, as is the case if you remove ! from guioptions.

  • Vim 8.1.950
  • OS: macOS 10.14
  • Terminal: GUI
@eirnym
Copy link
Contributor

@eirnym eirnym commented May 30, 2019 •
edited

vim core runs command in a terminal with this GUI option set, and there's no difference between ViM and MacVim in that part.

I don't know if vim always requests a buffer for it, though

I suggest to test with GVim if you're able to, and/or file a ticket there first.
@lifepillar lifepillar mentioned this issue Jun 6, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@eirnym @lifepillar