-
Notifications
You must be signed in to change notification settings - Fork 26
Use vim terminal instead of standalone terminal window #60
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
Conversation
3ebcdb0 to
9fa69ba
Compare
|
That's some seriously cool stuff! Love the fallback to the old behavior. |
|
I'll gladly fix any bugs people find :) |
|
Works like a charm on neovim, real smooth. On vim8, an additional horizontal split is added to the output window, mirroring the buffer that was open when SClangStart was launched. This is, I'm afraid, a blocker for merge. It is also a requirement for merge to add a configuration variable that defaults to off. When a certain maturity has been achieved, we can discuss enabling it by default with the community. Documenting it prominently is fine. |
|
I can reproduce the weird behaviour you found, I'll work on it on the weekend, shouldn't be too hard.
All that said, as I was writing this I realized that we could have a varible with the following behaviour: what do you think? I don't mind the values themselves, could also be "no", "yes", and "sometimes" or any other suggestions |
|
Great!!! That's real cool. Thanks for contributing! I'm positive that the configuration option is really really important- the old behavior opens up a new window with sclang. Works fine, and you don't need to know or care about :term support, tmux or vim splits (and it's actually super userful when using a tiling window manager). I'm sure lots of people will love the new behavior, and my opinion is that it's the future of scvim, but people need to stay in control of whether and when they get it or even learn about it. That's why we use vim in the first place, isn't it? The config option's just fine- I'd suggest shortening it, perhaps g:scTerminalBuffer? I'd also suggest to scrap standalone mode- keep it simple. (These are just suggestions, not requirements) |
|
I fixed the windowing issue, but further there's still work to be done. Specifically, vim doesn't seem to close its terminal as gracefully as neovim, so I need to add proper clean up as well. |
|
Should be working properly with vim now, at least it did on my computer. |
|
Fantastic, works a charm. Thank you very much for your great work!!! Could you kindly add documentation to the README.md? One liner describing the option is fine, or elaborate a little if you think it make sense. I was thinking of enabling the internal terminal even with screen/tmux when g:TerminalBuffer="on", do you think that would make sense? |
capocasa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please describe configuration option in readme
|
It makes sense, to be honest I just forgot to include it in the code. |
|
I just checked to confirm if we really can't do without disabling by default, because by default scvim didn't open a window on executing In order to avoid dragging out the merge more than necessary I would suggest to stick to the default-off behavior as planned, and look at the defaulting behavior from different angles in a seperate PR via #62. Finally, what would you think of scrapping the new flag and using ":term" as terminal command instead to use internal? Not sure if it's more or less clear and simple. |
This pull request runs sclangpipe app inside a vim terminal buffer, making scvim independent of tmux or screen. It automatically detects if a terminal buffer is available and reverts to the old behaviour in case it's not
eee5df1 to
13472e8
Compare
|
I didn't manage to make the changes before travelling and ended not having time until now. Option description was added to |
|
Looks great! Thank you very much for your efforts, Claudio! |
This PR adds the functionality requested on #37.
If opened inside tmux or screen or if vim does not have the
:termcommand,it defaults to the old behaviour