Gordon Mccreight wrote in post #844159:
> I bumped into this page while looking for the same answer: namely, how
> do you stop the server when using rails.vim.
>
> Since this thread didn't help, I looked into the source code for
> rails.vim
>
> The answer is (notice the minus after the !)
> :Rserve
I have found that adding thin to my Gemfile allows me to successfully
:Rserver! thin
and
:Rserver!-
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyon
I bumped into this page while looking for the same answer: namely, how
do you stop the server when using rails.vim.
Since this thread didn't help, I looked into the source code for
rails.vim
The answer is (notice the minus after the !)
:Rserver!-
Without the minus it will kill, then restart t
Yes, it can be frustrating. I've been using vi since 1978 and emacs
since 1979. My experience includes using sed to diddle system files
on an init0 system in order to bring it up to init4. So I kind of
have the functional forms of several editors hard wired in. I've
actually had nightmares tha
7stud -- wrote:
> Rick Lloyd wrote:
>>>
>>> Why is :Rserver useful? �I hate that command.
>>>
>> Does seem kind of like belts and suspenders doesn't it?
>>
>> I've actually found that ":Rserver thin" does not work in my
>> environment. Thin is started in the background and then silently
>> dies
If you actually wanted to do this you can also use grep which may be
easier to achieve the results
Sent from my iPod
On May 3, 2009, at 11:19 PM, 7stud -- wrote:
>
> Harold wrote:
>> The issue is that rails.vim starts the server with the --daemon
>> option, so it just sits there in the backg
Rick Lloyd wrote:
>>
>> Why is :Rserver useful? �I hate that command.
>>
> Does seem kind of like belts and suspenders doesn't it?
>
> I've actually found that ":Rserver thin" does not work in my
> environment. Thin is started in the background and then silently
> dies. However, ":!thin -d sta
>
> Why is :Rserver useful? I hate that command.
>
Does seem kind of like belts and suspenders doesn't it?
I've actually found that ":Rserver thin" does not work in my
environment. Thin is started in the background and then silently
dies. However, ":!thin -d start" is the bee's knees.
You mi
Rick Lloyd wrote:
> or to avoid trusting the default just go ":Rscript server mongrel".
> If I'm not mistaken, you're probably using ":Rserver" which
> automatically starts the server in the background.
>
Ok. I get it now. This is what I need to do in rails.vim:
:Rscript server
which is equiv
or to avoid trusting the default just go ":Rscript server mongrel".
If I'm not mistaken, you're probably using ":Rserver" which
automatically starts the server in the background.
On May 3, 3:19 pm, Harold A. Giménez Ch.
wrote:
> Thin is just another webserver for ruby apps (mongrel, webrick, thi
Thin is just another webserver for ruby apps (mongrel, webrick, thin, ...)
http://code.macournoyer.com/thin/
You could've done :Rscript server to accomplish the same Rick Lloyd is
describing (which would default to whatever server you're using).
On Sun, May 3, 2009 at 9:04 PM, 7stud --
wrote:
>
Rick Lloyd wrote:
> I don't understand, when I issue the rails.vim command
> ":Rscript server thin"
> the thin server is started in the current VIM window with
> output visible.
What's a 'thin server'? As I mentioned in my op, this is what I had
been doing in Terminal:
/myapp$ ruby script/se
You can kill processes with name:sudo killall ruby
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe fro
I don't understand, when I issue the rails.vim command ":Rscript
server thin" the thin server is started in the current VIM window with
output visible. The behavior is identical to that in a terminal
window which has has the command "script/server thin" issued.
i.e. I can see the output from the
Harold wrote:
> The issue is that rails.vim starts the server with the --daemon
> option, so it just sits there in the background. :Rserver! will try to
> kill it first, and restart it from vim, but I'd just use the terminal
> for controlling your server during development.
Ok. Will do.
--
Post
The issue is that rails.vim starts the server with the --daemon
option, so it just sits there in the background. :Rserver! will try to
kill it first, and restart it from vim, but I'd just use the terminal
for controlling your server during development.
On May 3, 11:59 am, 7stud -- wrote:
> Harol
Harold wrote:
> I don't have a mac, but this is pure unix and should be applicable to
> you as well.
>
> Get the PID of the server process and kill it manually:
> $ ps aux |grep ruby
> hgimenez 30736 24.8 1.6 48772 33252 pts/0Sl+ 11:22 0:03 ruby
> script/server
> hgimenez 30802 0.0 0.0
I don't have a mac, but this is pure unix and should be applicable to
you as well.
Get the PID of the server process and kill it manually:
$ ps aux |grep ruby
hgimenez 30736 24.8 1.6 48772 33252 pts/0Sl+ 11:22 0:03 ruby
script/server
hgimenez 30802 0.0 0.0 4204 704 pts/1S+ 11
18 matches
Mail list logo
