Anton Astashov

Results 87 comments of Anton Astashov

Does this icon work? ![image](https://user-images.githubusercontent.com/12795/73376356-ef86ec00-4282-11ea-958a-558aae2a7a96.png) It should give you copiable output.

Yeah, sure, though the version deployed is currently differs from what is in this repo - it's written in Elm now. I need to update the repo it sometime to...

Frankly, never tried to run it this way. Will try to take a look at that this weekend, thanks for reporting. :)

Umm, sorry, still didn't check/fix that issue. :( You can try mvim for now, it works just fine. :)

Weird. Try to run this command from your logs just from console: ``` rdebug-vim --file /Users/twojcik/.vim/bundle/vim-ruby-debugger/tmp/ruby_debugger --output /Users/twojcik/.vim/bundle/vim-ruby-debugger/tmp/ruby_debugger_output --socket /var/folders/ky/bzrkq4v1661c7wpbvjxj7h4w0000gn/T/vkenQjL/6 --logger_file /Users/twojcik/.vim/bundle/vim-ruby-debugger/tmp/ruby_debugger_log --debug_mode 1 --vim_executable mvim --vim_servername --separator ++vim-ruby-debugger-separator++ --...

Hmm, you should get the PID after executing this command... And you use Rails >= 3.0, right?

Hmm, and if you just run `script/rails server` from console, it starts the server correctly?

That sucks. :( The only thing I could recommend to do - debug rdebug-vim, which is part of 'debugger-xml' gem, and figure out why the PID is not printed as...

No problem. :) Feel free to create the Pull Request there, if you find the source of the issue.

Oh, great! I actually even don't have Windows now, and I can't check it. Could you please create a pull request with that patch for me (or maybe even a...