Nabble - Vim - Ruby - Dev

Re: Some regexp pattern breaks the syntax highlighting.

2009-09-12T03:09:06Z

On Sat, Sep 12, 2009 at 1:46 PM, Tim Pope <vim-ruby-devel@...> wrote:
> On Sat, Sep 12, 2009 at 12:37:52PM +0900, Morita Sho wrote:
>> As result, the regexp pattern \( will not be interpreted as an escaped character
>> if that pattern will not be displayed. Removing the "display" keyword for
>> rubyRegexpEscape solves the problem for me.
>
> Nice detective work.

+1 Our favourite kind of user. :)

Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Some regexp pattern breaks the syntax highlighting.

2009-09-11T20:46:33Z

On Sat, Sep 12, 2009 at 12:37:52PM +0900, Morita Sho wrote:
> As result, the regexp pattern \( will not be interpreted as an escaped character
> if that pattern will not be displayed. Removing the "display" keyword for
> rubyRegexpEscape solves the problem for me.

Nice detective work. I've pushed up your fix.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Some regexp pattern breaks the syntax highlighting.

2009-09-11T20:37:52Z

Some updates:

After some investigations, I suspect that the following line in
syntax/ruby.rb is problematic.

syn match rubyRegexpEscape "\\[].*?+^$|\\/(){}[]" contained display

As far as I understand it, this matches a regexp escape character. I think the problem is
the "display" keyword. According to Vim manual:

display *:syn-display*

If the "display" argument is given, this item will be skipped when the
detected highlighting will not be displayed. This will speed up highlighting,
by skipping this item when only finding the syntax state for the text that is
to be displayed.

As result, the regexp pattern \( will not be interpreted as an escaped character
if that pattern will not be displayed. Removing the "display" keyword for
rubyRegexpEscape solves the problem for me.

Thanks,
--
Morita Sho <morita-pub-en@...>
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Some regexp pattern breaks the syntax highlighting.

2009-09-11T13:17:18Z

Hi,

Some regexp pattern breaks the syntax highlighting.

How to reproduce the problem:

First of all, create a ruby script as following and open it with Vim.

% cat test.rb
func /\(/
puts

At this point, the script will be highlighted correctly.
Then, hit Ctrl-E to scroll down the window (the line "func /\(/" goes
out of the screen), and hit Ctrl-L to redraw. After redrawing the window,
the line "puts" will be highlighted wrongly as a regexp literal.

It seems that the highlighting works if the line "func /\(/" is visible,
but won't work if the line "func /\(/" is out of the screen.

I tested latest syntax/ruby.vim pulled from git repository, but it doesn't
solve the problem.

Thanks,
--
Morita Sho <morita-pub-en@...>

_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

(debian,ruby,Qt) no completion for Qt with vim

2009-05-28T16:50:09Z

hello,

I have a little/big problem with vim and ruby.
little because almost all works fine : on debian I installed vim,vim-ruby,ruby1.8,qt4-qtruby, and Qt.
on vim I have the syntax coloring that's working, and a program like "print require 'Qt4' " returns true : Qt4 is recognized.

but I have not the completion for Qt : if I enter "a=Qt:: " +CTRL X+CTRL O, I have the messsage "pattern not found" .

on vim I have:
:set ofu? => omnifunc=rubycomplete#Complete
:set ft? => filetype=ruby
:filetype => all 3 are ON

can you help me to have the completion?
or maybe I have made a mistake, an oversight.

thx,

olivier.

Re: Things I wish to do in VIM but currently cannot.

2009-05-18T20:12:37Z

Have you tried turning on the format options in your ~/.vimrc file? type :help format-options to see a full list of what you can set, but adding :set fo+=aw2tq should allow you to do the type of text-wrapping that you're looking for.

kunjaan wrote:

Hi,
Is there someway I can make the VIM line break after 80 characters. I dont want the text to wrap around but create a new line. And I wish it would break off the complete last word. So instead of fo in the previous and o in the next line, can it break with foo in the next line?

Im also facing some problems, I looked around in the forum and didnt find any solutions discussed. Im sorry if this has been resolved earlier.

1. When I end my comment and press enter, I get a # in the new line. This is cool but when I delete # and want to start a line of code, I dont get syntax highlighting there. IT=t still thinks what Im typing is a comment. Is this a bug or am I doing it wrong?

2. One more thing is that I have set the shiftwidth to 4. But when I press Ctrl+S to save the document, the cursor jumps to the beginning of the sentence. I then need to manually go back to my original position to begin the code. Is there a way I can resolve this?

Thank you for reading this. I am new to Ruby and Vim. I hope you guys help me out.

Things I wish to do in VIM but currently cannot.

2009-04-27T17:10:24Z

Hi,
Is there someway I can make the VIM line break after 80 characters. I dont want the text to wrap around but create a new line. And I wish it would break off the complete last word. So instead of fo in the previous and o in the next line, can it break with foo in the next line?

Im also facing some problems, I looked around in the forum and didnt find any solutions discussed. Im sorry if this has been resolved earlier.

1. When I end my comment and press enter, I get a # in the new line. This is cool but when I delete # and want to start a line of code, I dont get syntax highlighting there. IT=t still thinks what Im typing is a comment. Is this a bug or am I doing it wrong?

2. One more thing is that I have set the shiftwidth to 4. But when I press Ctrl+S to save the document, the cursor jumps to the beginning of the sentence. I then need to manually go back to my original position to begin the code. Is there a way I can resolve this?

Thank you for reading this. I am new to Ruby and Vim. I hope you guys help me out.

Re: Indent problems with symbols containing keywords - solved?

2009-03-25T11:17:31Z

I tried to git-clone from rubyforge instead of git hub, which was dumb.
(http://rubyforge.org/scm/?group_id=16)

HEAD works fine, thanks. Sorry for the trouble.

Tim Pope wrote:

> On Tue, Mar 17, 2009 at 12:51:25AM +0100, Cezary Bagiński wrote:
>> Hi,
>>
>> The following gives the wrong indent (vim 7.1.314, Ubuntu):
>>
>> ---------(after indent its the same)-------
>> class AAA
>> def aaa
>> a = [ :title,
>> :from,
>> :until,
>> ]
>> end
>> end
>> -----------------
>>
>> It seems the 'until' is matched, even when it's a symbol. I dug through
>> the 'syntax/ruby.vim' I already had, since the rubyforge git access is
>> broken (?).
>>
>> The following is the best I could think of:
>>
>> add the \@<! pattern to ignore symbols, replacing all instances of
>> keyword matchers, like:
>>
>> \\<\$while\\|until\\|for\$\\>")'
>>
>> with:
>>
>> \\<\$while\\|[:]\@<!until\\|for\$\\>")'
>>
>> I did it for just the until keyword and it seems to work fine.
>
> This appears to already be in effect in the latest version of Vim-Ruby.
>
> Cheers,
> Tim
> _______________________________________________
> vim-ruby-devel mailing list
> vim-ruby-devel@...
> http://rubyforge.org/mailman/listinfo/vim-ruby-devel

_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Indent problems with symbols containing keywords - solved?

2009-03-23T06:34:50Z

On Tue, Mar 17, 2009 at 12:51:25AM +0100, Cezary Bagiński wrote:

>
> Hi,
>
> The following gives the wrong indent (vim 7.1.314, Ubuntu):
>
> ---------(after indent its the same)-------
> class AAA
> def aaa
> a = [ :title,
> :from,
> :until,
> ]
> end
> end
> -----------------
>
> It seems the 'until' is matched, even when it's a symbol. I dug through
> the 'syntax/ruby.vim' I already had, since the rubyforge git access is
> broken (?).
>
> The following is the best I could think of:
>
> add the \@<! pattern to ignore symbols, replacing all instances of
> keyword matchers, like:
>
> \\<\$while\\|until\\|for\$\\>")'
>
> with:
>
> \\<\$while\\|[:]\@<!until\\|for\$\\>")'
>
> I did it for just the until keyword and it seems to work fine.

This appears to already be in effect in the latest version of Vim-Ruby.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Indent problems with symbols containing keywords - solved?

2009-03-16T16:51:25Z

Hi,

The following gives the wrong indent (vim 7.1.314, Ubuntu):

---------(after indent its the same)-------
class AAA
def aaa
a = [ :title,
:from,
:until,
]
end
end
-----------------

It seems the 'until' is matched, even when it's a symbol. I dug through
the 'syntax/ruby.vim' I already had, since the rubyforge git access is
broken (?).

The following is the best I could think of:

add the \@<! pattern to ignore symbols, replacing all instances of
keyword matchers, like:

\\<\$while\\|until\\|for\$\\>")'

with:

\\<\$while\\|[:]\@<!until\\|for\$\\>")'

I did it for just the until keyword and it seems to work fine.

Could the problem be caused by Vim treating the ':' char as part of a
keyword?

Thanks in advance.

_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Options Dump When Using vim-ruby On Ruby

2009-01-08T11:32:27Z

Thanks a lot! Your help made it obvious that I put a carriage return in my "autocmd" lines.

Tom Purl
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Options Dump When Using vim-ruby On Ruby

2009-01-06T16:52:09Z

Actually you don't even need the 'omnifunc' line since we set it in
the filetype plugin.

Regards,
Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Options Dump When Using vim-ruby On Ruby

2009-01-06T16:49:49Z

On 1/7/09, Tom E Purl <tep2@...> wrote:

>
>
> I'm receiving a lot of strange errors when I try to use vim-ruby on Windows.
> Any help that anyone can give me would be greatly appreciated.
>
> Every time I start up vim or gvim, I get the following error:
>
>
> Error detected while processing E:\apps\vim\_vimrc:
> line 243:
> E492: Not an editor command: omnifunc=rubycomplete#Complete
> E486: Pattern not found: rubycomplete_buffer_loading = 1
> E486: Pattern not found: rubycomplete_classes_in_global = 1

<snip>

> Here's the pertinent lines in my _vimrc file:
>
> " Ruby goodies
> autocmd FileType ruby,eruby set
> omnifunc=rubycomplete#Complete

set omnifunc=rubycomplete#Complete

> autocmd FileType ruby,eruby let
> g:rubycomplete_buffer_loading = 1

let g:rubycomplete_buffer_loading = 1

> autocmd FileType ruby,eruby let
> g:rubycomplete_classes_in_global = 1

let g:rubycomplete_classes_in_global = 1

<snip>

Regards,
Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Options Dump When Using vim-ruby On Ruby

2009-01-06T08:03:16Z

I'm receiving a lot of strange errors when I try to use vim-ruby on Windows. Any help that anyone can give me would be greatly appreciated.

Every time I start up vim or gvim, I get the following error:

Error detected while processing E:\apps\vim\_vimrc:
line 243:
E492: Not an editor command: omnifunc=rubycomplete#Complete
E486: Pattern not found: rubycomplete_buffer_loading = 1
E486: Pattern not found: rubycomplete_classes_in_global = 1

When I actually try to open a Ruby file, I get a dump of all of my configuration options. This dump is 20 pages long.

Here's how I installed vim-ruby:

E:\apps\ruby\bin>ruby -S gem install vim-ruby
Successfully installed vim-ruby-2007.05.07
1 gem installed

E:\apps\ruby\bin>ruby -S vim-ruby-install.rb

Possible Vim installation directories:
1) F:/vimfiles
2) E:/apps/vim/vimfiles

Please select one (or anything else to specify another directory): 2
autoload/rubycomplete.vim -> E:/apps/vim/vimfiles/autoload/rubycomplete.vim
compiler/eruby.vim -> E:/apps/vim/vimfiles/compiler/eruby.vim
compiler/ruby.vim -> E:/apps/vim/vimfiles/compiler/ruby.vim
compiler/rubyunit.vim -> E:/apps/vim/vimfiles/compiler/rubyunit.vim
ftdetect/ruby.vim -> E:/apps/vim/vimfiles/ftdetect/ruby.vim
ftplugin/eruby.vim -> E:/apps/vim/vimfiles/ftplugin/eruby.vim
ftplugin/ruby.vim -> E:/apps/vim/vimfiles/ftplugin/ruby.vim
indent/eruby.vim -> E:/apps/vim/vimfiles/indent/eruby.vim
indent/ruby.vim -> E:/apps/vim/vimfiles/indent/ruby.vim
syntax/eruby.vim -> E:/apps/vim/vimfiles/syntax/eruby.vim
syntax/ruby.vim -> E:/apps/vim/vimfiles/syntax/ruby.vim

Here's the pertinent lines in my _vimrc file:

" Ruby goodies
autocmd FileType ruby,eruby set
omnifunc=rubycomplete#Complete

autocmd FileType ruby,eruby let
g:rubycomplete_buffer_loading = 1

autocmd FileType ruby,eruby let
g:rubycomplete_classes_in_global = 1

map <leader>mr <ESC>:rubyf %<CR>

...and here's my Vim version and compile flags:

:version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec 9 2008 07:09:33)
MS-Windows 32-bit console version
Included patches: 1-68
Compiled by digitectNO@...
Big version without GUI. Features included (+) or not (-):
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments +cryptv +cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+find_in_path +float +folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak
+lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +multi_byte_ime/dyn +multi_lang +mzscheme/dyn -netbeans_intg
-osfiletype +path_extra +perl/dyn -postscript +printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent
-sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title -toolbar
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim
-xterm_save -xpm_w32
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL="perl58.dll" -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL="python25.dll" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL="msvcrt-ruby18.dll" -DDYNAMIC_RUBY_VER=18 -DFEAT_MZSCHEME -DDYNAMIC_MZSCHEME -DDYNAMIC_MZSCH_DLL="libmzsch370.dll" -DDYNAMIC_MZGC_DLL="libmzgc370.dll" -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL="tcl84.dll" -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_OLE -march=i386 -Iproto -I/cygdrive/c/PERL/lib/CORE -I/cygdrive/c/PYTHON25/include -I/cygdrive/c/RUBY/lib/ruby/1.8/i386-mswin32 -I/cygdrive/c/PROGRA~1/MzScheme/include -I/cygdrive/c/Tcl/include -s -mno-cygwin
Linking: gcc -s -o gvim.exe -luuid -lole32 /cygdrive/c/Tcl/lib/tclstub84.lib -lwsock32 -mwindows -lcomctl32 -lversion -loleaut32 -lstdc++

Here's also a couple of other things to consider:

* Ruby is installed on a thumb drive,and its path is E:\apps\ruby
* I also have Jruby installed on this machine, and Jruby appears in my $PATH before ruby. I tried putting ruby before jruby in my path, but that didn't make a difference.

The good news is that the big feature that I can use omnifunc with Ruby. The bad news is that I have to page through 20 pages of configuration information every time I open a ruby file.

Has anyone ever seen an error like this before?

Thanks in advance!

Tom Purl
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

fuzzyfinder.vim and rubygems 1.3.1 are not compatible

2009-01-04T18:45:36Z

I get this error when running vim with fuzzyfinder.vim and fuzzyfinder_textmate.vim:

Error detected while processing function InstantiateTextMateMode:
line 17: LoadError: /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- fuzzy_file_finder

(with rubygems 1.3.0 everything works fine)

any idea how to solve this?
Thanks!

Re: Vim/Ruby release!

2008-08-01T18:29:56Z

On Sat, Aug 02, 2008 at 11:02:03AM +1000, Doug Kearns wrote:
> My only concern is that in working around it we neglect making
> improvements to Vim's Ruby interface. I know Tim was doing some work
> on it last year but I'm not sure of the end result.

I stalled out when debating just what sort of backwards incompatible
changes were acceptable. Parts of the API are horribly broken but I
know Bram greatly values backwards compatibility. I haven't discussed
it with him.

That, and I don't really have a way to test it on Windows. The way
the dynamic linking works on Windows means there is a big chunk of
if_ruby.c that's essentially in a #if 0 block on my setup.

If I could find a solution for Windows testing I'd be willing to take
it up again.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Git migration

2008-08-01T18:21:20Z

On Sat, Aug 02, 2008 at 10:56:22AM +1000, Doug Kearns wrote:

> On Sat, Aug 2, 2008 at 7:56 AM, Tim Pope <vim-ruby-devel@...> wrote:
> > Okay, since nobody raised any objections I'm preparing to make the
> > migration to git official. Here's a status report.
> >
> > Mark created a vim-ruby account on github and pushed up my import to
> > it. He and I are currently the only collaborators. Any other
> > maintainers who would like to continue in that role should send me
> > their github accounts so I can add them. In a few weeks, I'll
> > probably "retire" anyone who hasn't responded.
>
> I don't feel particularly strongly about it one way or the other, but
> I thought we were planning on using RubyForge for the 'official' repo?

There's no mechanism in rubyforge to switch SCMs. You could put in a
support request I suppose. Now that I know group accounts are kosher,
though, I'm slightly biased towards github anyways. The good news is
it's easy to move a git repository so we're not really committed
either way.

> > I'm going to advise we continue maintaining the changelog until we
> > decide on a replacement practice. Please write well formed commit
> > messages as well (a subject line around 50 characters or less, a blank
> > line, then an optional body wrapped to 72 characters).
>
> While I'm quite partial to the GNU ChangeLog format this does seem
> like redundant work. Aren't there a few tools to generate a GNU
> ChangeLog anyway?

I'm sure we could find or write something if it came down to it.
Meanwhile, I'm now rethinking my suggestion to continue maintaining
it. A versioned ChangeLog is a constant source of conflicts when
merging.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-08-01T18:02:03Z

2008/7/15 Mark Guzman <segfault@...>:

<snip>

> I've had a completion project running in the background and would like some
> feedback on the overall concept. I'm spawning a ruby process per buffer to
> handle completions for that buffer. Completion uses rinda in the embedded
> ruby env to communicate with the ruby processes and provide a list of
> values.
>
> All of that is to get around some of the embedding flakiness that's come up.
>
> Thoughts...

Could you refresh my memory as to these issues?

My only concern is that in working around it we neglect making
improvements to Vim's Ruby interface. I know Tim was doing some work
on it last year but I'm not sure of the end result.

Regards,
Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Git migration

2008-08-01T17:56:22Z

On Sat, Aug 2, 2008 at 7:56 AM, Tim Pope <vim-ruby-devel@...> wrote:
> Okay, since nobody raised any objections I'm preparing to make the
> migration to git official. Here's a status report.
>
> Mark created a vim-ruby account on github and pushed up my import to
> it. He and I are currently the only collaborators. Any other
> maintainers who would like to continue in that role should send me
> their github accounts so I can add them. In a few weeks, I'll
> probably "retire" anyone who hasn't responded.

I don't feel particularly strongly about it one way or the other, but
I thought we were planning on using RubyForge for the 'official' repo?

<snip>

> I'm going to advise we continue maintaining the changelog until we
> decide on a replacement practice. Please write well formed commit
> messages as well (a subject line around 50 characters or less, a blank
> line, then an optional body wrapped to 72 characters).

While I'm quite partial to the GNU ChangeLog format this does seem
like redundant work. Aren't there a few tools to generate a GNU
ChangeLog anyway?

> If there are no substantial objections, in the next few days I'm going
> to make it official by updating any documentation I find. I'll also
> create a CVS commit deleting everything and adding a text file
> pointing to the new repository.

Thanks for working on this.

Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Git migration

2008-08-01T14:56:03Z

Okay, since nobody raised any objections I'm preparing to make the
migration to git official. Here's a status report.

Mark created a vim-ruby account on github and pushed up my import to
it. He and I are currently the only collaborators. Any other
maintainers who would like to continue in that role should send me
their github accounts so I can add them. In a few weeks, I'll
probably "retire" anyone who hasn't responded.

I blew away the initial import and replaced it with one with the $Id$
tags collapsed, greatly reducing the noise in the history. Thomas
Adam raised a few theoretical objection but I don't think they really
apply in our case. If anyone (including Thomas) disagrees, let me
know.

I'm going to advise we continue maintaining the changelog until we
decide on a replacement practice. Please write well formed commit
messages as well (a subject line around 50 characters or less, a blank
line, then an optional body wrapped to 72 characters).

If there are no substantial objections, in the next few days I'm going
to make it official by updating any documentation I find. I'll also
create a CVS commit deleting everything and adding a text file
pointing to the new repository.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T14:22:37Z

On Tue, 15 Jul 2008 17:17:15 -0400
Tim Pope <vim-ruby-devel@...> wrote:
> On Tue, Jul 15, 2008 at 05:11:34PM -0400, Tim Pope wrote:
> > There's a lot of annoying $Id: ...$ chatter in the history. I can
> > squash them all to $Id$ to eliminate that noise if people think
> > that's a good idea. One of the first commits on the new repository
> > needs to get rid of them entirely since git doesn't support it.
> > (Do we need some sort of replacement identifier like a version
> > number?)

gitattibutes allows for $id$ expansion on git checkout -- and it's
useful when preserving history for a project migrating to GIT, for
instance.

> Err, one more thing. Is it worth rethinking the ChangeLog policy?

c.f. git shortlog to generate such a file.

-- Thomas Adam

--
"It was the cruelest game I've ever played and it's played inside my
head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T14:17:15Z

On Tue, Jul 15, 2008 at 05:11:34PM -0400, Tim Pope wrote:

> Okay, I've done a prototype of the import and put it on github:
>
> http://github.com/tpope/vim-ruby
> git clone git://github.com/tpope/vim-ruby.git
>
> Before officially switching over, does anyone see anything wrong? I'm
> looking for things like "you misspelled my name".
>
> There's a lot of annoying $Id: ...$ chatter in the history. I can
> squash them all to $Id$ to eliminate that noise if people think that's
> a good idea. One of the first commits on the new repository needs to
> get rid of them entirely since git doesn't support it. (Do we need
> some sort of replacement identifier like a version number?)

Err, one more thing. Is it worth rethinking the ChangeLog policy?
My general feeling is that the git history is so easy to work with,
keeping a ChangeLog is no longer necessary. But I do see value in
consistently maintaining it throughout the projects history rather
than switching to the SCM log halfway through. Food for thought.
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T14:11:34Z

On Wed, Jul 16, 2008 at 05:23:22AM +1000, Doug Kearns wrote:
> On Wed, Jul 16, 2008 at 3:53 AM, Tim Pope <vim-ruby-devel@...> wrote:
> <snip>
>
> > I will investigate creating a git repository on Rubyforge in the near
> > future. Could you make me a project admin on vim-ruby?

Okay, I've done a prototype of the import and put it on github:

http://github.com/tpope/vim-ruby
git clone git://github.com/tpope/vim-ruby.git

Before officially switching over, does anyone see anything wrong? I'm
looking for things like "you misspelled my name".

There's a lot of annoying $Id: ...$ chatter in the history. I can
squash them all to $Id$ to eliminate that noise if people think that's
a good idea. One of the first commits on the new repository needs to
get rid of them entirely since git doesn't support it. (Do we need
some sort of replacement identifier like a version number?)

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T13:43:32Z

2008/7/15 Mark Guzman <segfault@...>:
> Afaik github is free for open source projects, they have a 100mb repo
> size limit on free accts. It's only when you want private or very large
> repos that payment is required.

Well, repo.or.cz offers 200MB for instance...

-- Thomas Adam
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T13:37:23Z

On Tue, Jul 15, 2008 at 04:31:42PM -0400, Mark Guzman wrote:

> <(15/07/08 10:26) Tim Pope>
> > On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote:
>
> > Hate to sound like a broken record, but I'd really like to make the
> > move to git. The only question I can see is who's repository will be
> > official (assuming we use github). I don't fancy a recurring payment
> > for a vim-ruby github account just for this project.
> >
> +1 to git.
>
> Afaik github is free for open source projects, they have a 100mb repo
> size limit on free accts. It's only when you want private or very large
> repos that payment is required.

The TOS prevent one person from having multiple free accounts. That
means we couldn't have a shared repository we could all push to.

> I'd assume the official repo would be at rubyforge.

I think that's the route we should take. Pity that means we can't
fully take advantage of the social aspects of github if we go that
route but for a small project like this I guess it doesn't matter.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T13:31:42Z

<(15/07/08 10:26) Tim Pope>
> On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote:

> Hate to sound like a broken record, but I'd really like to make the
> move to git. The only question I can see is who's repository will be
> official (assuming we use github). I don't fancy a recurring payment
> for a vim-ruby github account just for this project.
>
+1 to git.

Afaik github is free for open source projects, they have a 100mb repo
size limit on free accts. It's only when you want private or very large
repos that payment is required.

I'd assume the official repo would be at rubyforge.
--mg

--
Those the gods wish to destroy they call promising.

_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

attachment0 (204 bytes) Download Attachment

Re: Vim/Ruby release!

2008-07-15T12:23:22Z

On Wed, Jul 16, 2008 at 3:53 AM, Tim Pope <vim-ruby-devel@...> wrote:
<snip>

> I will investigate creating a git repository on Rubyforge in the near
> future. Could you make me a project admin on vim-ruby?

Done.

Thanks,
Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T10:53:00Z

On Wed, Jul 16, 2008 at 02:21:41AM +1000, Doug Kearns wrote:
> On Wed, Jul 16, 2008 at 12:26 AM, Tim Pope <vim-ruby-devel@...> wrote:
> > Hate to sound like a broken record, but I'd really like to make the
> > move to git. The only question I can see is who's repository will be
> > official (assuming we use github). I don't fancy a recurring payment
> > for a vim-ruby github account just for this project.
>
> I certainly have no objections.

I will investigate creating a git repository on Rubyforge in the near
future. Could you make me a project admin on vim-ruby?

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T09:21:41Z

On Wed, Jul 16, 2008 at 12:26 AM, Tim Pope <vim-ruby-devel@...> wrote:

<snip>

> Hate to sound like a broken record, but I'd really like to make the
> move to git. The only question I can see is who's repository will be
> official (assuming we use github). I don't fancy a recurring payment
> for a vim-ruby github account just for this project.

I certainly have no objections.

Regards,
Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T08:21:46Z

On Tue, 15 Jul 2008, Tim Pope wrote:

> On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote:
>> As an aside, I've got the sources mirrored here:
>> git://github.com/segfault/vim-ruby.git
>
> Hate to sound like a broken record, but I'd really like to make the
> move to git. The only question I can see is who's repository will be
> official (assuming we use github). I don't fancy a recurring payment
> for a vim-ruby github account just for this project.

I'm not up to speed on git, I admit, but I've seen traffic to the
effect that Rubyforge supports it now:

http://drnicwilliams.com/2008/04/08/git-for-rubyforge-accounts/

http://tomcopeland.blogs.com/juniordeveloper/2008/04/rubyforge-now-h.html

>
> Cheers,
> Tim

HTH
Hugh
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-15T07:26:16Z

On Mon, Jul 14, 2008 at 11:06:48PM -0400, Mark Guzman wrote:
> As an aside, I've got the sources mirrored here:
> git://github.com/segfault/vim-ruby.git

Hate to sound like a broken record, but I'd really like to make the
move to git. The only question I can see is who's repository will be
official (assuming we use github). I don't fancy a recurring payment
for a vim-ruby github account just for this project.

Cheers,
Tim
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-07-14T20:39:00Z

Mark Guzman wrote:
> I've had a completion project running in the background and would like
> some feedback on the overall concept. I'm spawning a ruby process per
> buffer to handle completions for that buffer. Completion uses rinda in
> the embedded ruby env to communicate with the ruby processes and
> provide a list of values.
>
> All of that is to get around some of the embedding flakiness that's
> come up.
It's worth noting that I do not intend to have that dev codebase as part
of the upcoming release. My original message was a bit vague about that,
so I felt the need to clarify.

Cheers
--mg

_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

smime.p7s (4K) Download Attachment

Re: Vim/Ruby release!

2008-07-14T20:06:48Z

Doug Kearns wrote:
>
> Mark, did you want to make those changes to rubycomplete.vim that were
> suggested by Bram a week or so ago?
>
>
Sorry I didn't reply, the maildir that I have this group going to got
corrupted due to a raid issue. Bram had CC'd me when it came up, so it
got covered that way.

As an aside, I've got the sources mirrored here:
git://github.com/segfault/vim-ruby.git

I've had a completion project running in the background and would like
some feedback on the overall concept. I'm spawning a ruby process per
buffer to handle completions for that buffer. Completion uses rinda in
the embedded ruby env to communicate with the ruby processes and provide
a list of values.

All of that is to get around some of the embedding flakiness that's come up.

Thoughts...
--mg

_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

smime.p7s (4K) Download Attachment

Re: Vim/Ruby release!

2008-06-30T08:19:35Z

On Mon, Jun 30, 2008 at 11:10:03PM +1000, Doug Kearns wrote:
> Tim and others,
>
> I've just sent the latest to Bram.

Awesome, thanks.
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel

Re: Vim/Ruby release!

2008-06-30T06:10:03Z

Tim and others,

I've just sent the latest to Bram.

Regards,
Doug
_______________________________________________
vim-ruby-devel mailing list
vim-ruby-devel@...
http://rubyforge.org/mailman/listinfo/vim-ruby-devel