Allan,
Ruby 1.9 can be supported by VIM with a patch which I sent to Tobias months
ago. I submitted to vim-devel, but without response.
If anyone want this patch (vim support to ruby 1.9) I will be happy to send.
On Mon, Jul 20, 2009 at 10:25 AM, Allan McRae wrote:
> Caină wrote:
>
>> It also la
Hi all,
Tobias, i`m without a machine, so, i can`t check the vim version. Did you
compile new vim with witch version of ruby?
On Sat, May 9, 2009 at 10:24 AM, Thomas Bohn wrote:
> On 2009-05-05 00:22 -0700, Tobias Kieslich wrote:
>
> > Finally, the new vi* packages are up.
>
> One more question
Mauricio,
I'm from Brazil too, part of Arch Linux Brasil team. Please, shows up in
#archlinux-br at irc.freenode.org, maybe anyone can help you more fast. If
not, came to archlinux-br list at google groups.
Best.
On Sun, Apr 19, 2009 at 8:44 PM, richard terry wrote:
> On Mon, 20 Apr 2009 09:26:
Hi Alper!
Here in Brazil we are planning some like that for the FISL (Internation
Forum of Open Software - Fórum Internacional de Software Livre) at June
24-27. Me and Hugo Doria are planning a lecture for that, and a Arch Linux
user group, which have a space for all interested in our distro. If an
I had that once. Only works after a manual reboot.
On Tue, Mar 3, 2009 at 9:35 PM, Leonid Grinberg wrote:
> Hello,
>
> Every once in a while -- not too frequently to be unusable, but
> certainly enough to be annoying -- the keyboard in KDE will simply
> lock up. Mouse will still work fine, and ke
I sent a mail right now for him, i'was clean up the build tree. Thanks
for remember me.
On Wed, Feb 18, 2009 at 1:39 PM, Grigorios Bouzakis wrote:
> On Wed, Feb 18, 2009 at 01:29:28PM -0300, Kessia 'even' Pinheiro wrote:
>> Hi all,
>>
>> I'm doing a reco
I forgot, need recompile gvim too, obvious.
On Wed, Feb 18, 2009 at 1:29 PM, Kessia 'even' Pinheiro
wrote:
> Hi all,
>
> I'm doing a recompile of ruby for version 1.9. The needed are, in that order:
>
> - recompile ruby to version 1.9 (no change)
> - recom
Hi all,
I'm doing a recompile of ruby for version 1.9. The needed are, in that order:
- recompile ruby to version 1.9 (no change)
- recompile vi and vim [applying the new patch's until version 108,
arch today only apply 65] and applying a patch for make compatible
with ruby1.9, it's done already.
Hi,
Maintain both version only depends of the developer, he'll maintain
both? And it can broke any actual package?
On Fri, Feb 6, 2009 at 4:46 AM, Ondřej Kučera wrote:
> Hi,
>
>> We can alway have a ruby package and a ruby18 package at a later date,
>> much like what will happen when I make pyth
Hi,
On Thu, Feb 5, 2009 at 10:56 AM, Ondřej Kučera wrote:
> Hi,
>
>
>
> True. But at the end of the day it goes down to works/doesn't work as a
> whole and as long as the gems used by Rails are broken, Rails are
> effectively broken too. :-(
>
> Ondřej
>
>
> --
> Cheers,
> Ondřej Kučera
True, b
I think the problem isn't the Rails, but the Gems. Until I know, Rails
2.2.2 are compatible with Ruby 1.9. But some developers don't upgrade
their gems code to work with Ruby 1.9.X, so, sometimes apps will break
with a upgrade. But, it depends only from developers of used gems.
--
Kessia Pinheiro
Amanai,
The question: do you use any packages from community repo?
On Thu, Jan 22, 2009 at 9:09 AM, Amanai wrote:
>
>>
>> Why not just installing the xpi-file for Firefox directly from the mono
>> project? It works really great. Ok, it's not compiled from source, but
>> it's available for i586 a
Yeah! I don't know if its only a coincidence, but we made the jre from
the sources a week ago, also posting in Sun's bugtracker. So, i'm
think if it had some influense (crazy thoughts)... =)
On Tue, Dec 16, 2008 at 8:19 PM, Geoffroy Carrier
wrote:
> On Tue, Dec 16, 2008 at 23:19, Amanai wrote:
>
atus[0]=open&percent[0]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=
On Thu, Jul 3, 2008 at 9:20 PM, Angel Velásquez <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, Jul 4, 2008 at
Hi everyone,
I did a snort instalation using the package from extra, but i got some
problems. The package does not works after a fresh install. The
problems are:
- There are some problematic links with /usr/src/lib/snort_*
- The conf /etc/snort/snort.conf doesn't load the rules, because the
rules
15 matches
Mail list logo
