-
Notifications
You must be signed in to change notification settings - Fork 156
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
Need for two shells #207
Comments
Hi @arkandel, Currently that's the best way of doing it. In version 2 of vdebug (which will be released when I get some time to spend on it) the "Waiting for a connection" thing doesn't actually block your vim, so you could potentially run a background command through vim instead. You could check out the version 2 branch as it is an play around? |
Ah, right, that'd be convenient. I tried running commands through vim but that didn't pan out, I suppose that's why. I'll give version 2's branch a try, it's great to know you're working on adding features. Very much appreciated. |
I hope this is not too inappropriate, but I just wanted to chime in and say I'm also super grateful for vdebug so far, and pumped to see the prospect of a 2.0! |
Ha, not inappropriate at all @evert! It's encouraging to see people interested in the project. |
Until 2.0 comes out, would the following achieve what you need?
|
For users of Tmux this issue can be solved by the following plugin: https://github.com/christoomey/vim-tmux-runner |
I have at least a kludge to solve this problem. Basically I launch a shell command that sleeps for 1 second and then runs the script (in my case python). While the shell command is sleeping I then launch VdebugStart. Code is below. If anybody has any improvements to this let me know as I am very much in my infancy of writing vim scripts. :function! RunDebug() |
You all can start testing the async stuff by using the v2-integration branch |
Hey folks,
I've been using vdebug lately and it's really useful. I was wondering if anyone had a solution for the following issue:
I'm mostly debugging PHP over CLI on Linux. When I am doing so now I first hit F10 from vim to start connecting, then from a second shell I run php on the script while exporting the XDEBUG_CONFIG variable.
While this works, it's a bit annoying to have to use two consoles. Does anyone have a way (perhaps a workaround) to avoid this? I tried running a script from within vim after hitting F10 but that didn't work out.
Thanks in advance. :)
The text was updated successfully, but these errors were encountered: