On Mittwoch, 6. Mai 2009 23:25 Jan de Groot wrote:
> gcc 4.4 is ABI compatible with 4.3 binaries, so this means you can
> compile and run software with 4.4 against libraries that were compiled
> against 4.3 without noticable problems. It appears you can load kernel
> modules compiled with 4.4 into
On Sun, May 3, 2009 at 14:33, RedShift wrote:
>
> With those goals set, I started looking for hardware. Here's what I've come
> up with:
>
> * Case: Silverstone LC19
> http://www.silverstonetek.com/products/p_spec.php?pno=lc19&area=usa
>
> + Fanless PSU.
> + Casefans can be removed
> + Comes with
On Wed, 2009-05-06 at 15:40 -0500, Aaron Griffin wrote:
> On Wed, May 6, 2009 at 3:15 PM, Pierre Chapuis wrote:
> > Le Wed, 6 May 2009 14:53:43 -0500,
> > Aaron Griffin a écrit :
> >
> >> Might be worth seeing if we can find a patch to fix the crash at least.
> >
> > Patching might be a good idea
Eric Bélanger wrote:
> On Mon, May 4, 2009 at 12:58 AM, Allan McRae wrote:
>
>> Upstream bug fix release.
>>
>>
>
> file 5.02 is out.
>
>
And now 5.03 :)
--
Gerardo Exequiel Pozzi ( djgera )
http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39
On Wed, 2009-05-06 at 22:50 +0200, Attila wrote:
> On Mittwoch, 6. Mai 2009 22:07 Pierre Schmitz wrote:
>
> > At least gcc-libs of 4.4 is not compatible with the one from 4.3. So some
> > apps mght stop working when compiled with 4.4 and running on a system with
> > 4.3.
>
> Hmm, than the update
On Mittwoch, 6. Mai 2009 22:07 Pierre Schmitz wrote:
> At least gcc-libs of 4.4 is not compatible with the one from 4.3. So some
> apps mght stop working when compiled with 4.4 and running on a system with
> 4.3.
Hmm, than the update is more a must than a "could be", thanks for the info.
> So yo
On Wed, May 6, 2009 at 3:15 PM, Pierre Chapuis wrote:
> Le Wed, 6 May 2009 14:53:43 -0500,
> Aaron Griffin a écrit :
>
>> Might be worth seeing if we can find a patch to fix the crash at least.
>
> Patching might be a good idea, but if you just patch the crash I think it
> will still be even mor
Le Wed, 6 May 2009 14:53:43 -0500,
Aaron Griffin a écrit :
> Might be worth seeing if we can find a patch to fix the crash at least.
Patching might be a good idea, but if you just patch the crash I think it will
still be even more dangerous to put this version of vi in core because of the
beha
Am Mittwoch, 6. Mai 2009 20:41:57 schrieb Attila:
> My next question
> is that i want to know if this will be enough or should i block more
> packages?
At least gcc-libs of 4.4 is not compatible with the one from 4.3. So some apps
mght stop working when compiled with 4.4 and running on a system w
On Wed, May 6, 2009 at 2:30 PM, André Ramaciotti
wrote:
> At least here, vi can open non-ASCII files, but as I said previously,
> it won't show the lines with non-ASCII characters. The worst thing is
> if you try to save this file, vi will save it only up to the first
> line with a non-ASCII chara
At least here, vi can open non-ASCII files, but as I said previously,
it won't show the lines with non-ASCII characters. The worst thing is
if you try to save this file, vi will save it only up to the first
line with a non-ASCII character:
$ cat test.txt
This line is fine
mas essa não (but this on
2009/5/6 Frédéric Perrin :
> I have a system whose users' real names can't be written in ASCII, and
> this being the 21st century, not the 70's, I have the real name (with
> accents) in the GECOS field in /etc/passwd. Not being a vi{,m} user, I
> just have whatever the default package for vi is ins
Hello together,
my question is about that if the toolchain update comes do i have to do it to
get no problems with the rest of my system or can i wait if i find patches or
hints to solve possible problems with my own packages?
For the case that i can wait i will block the upgrade of this packages
Hi,
that can be done, sure, however I don't like the idea of having an
extra package conflict with a core one.
We could name the package nvi, call the binaries nvi and provide a
symlink that gets replace on installing vim but all this symlinking
stuff has proved itself to be error prone.
Guys.
To avoid the problem with openoffice, just be sure you environement variable
OOO_FORCE_DESKTOP is set to gnome:
in ~/.bashrc:
export OOO_FORCE_DESKTOP=gnome
personnaly, this fixed the problem with older versions, now i see there's a
~/etc/profile.d/openoffice-beta.sh that does just tha
Le Mercredi 6 à 13:07, Jan de Groot a écrit :
> On Wed, 2009-05-06 at 07:54 -0300, André Ramaciotti wrote:
>> Just a question about this new vi package. Am I the only one having
>> problems when openning UTF-8 files? I can't even type words with
>> diacritics or vi will abort. For example, try to c
> cover the users who USE and EXPECT 'vim' but still type 'vi' (sigh)
couldn't we suggest them to make an alias ?
On Tue, May 5, 2009 at 12:49 PM, Thomas Bohn wrote:
> On 2009-05-05 19:20 +0200, tob...@justdreams.de wrote:
>
>> the current vi package is actually nvi, the purpose of that was to have a
>> smaller package for core that also would not stall any updates of
>> vim/gvim while vi sits in testing.
>
>
I was thinking more about the installation/recuperation process than
the daily usage, because it's not always possible to install vim in
such cases. That's why I was questioning only vi being in [core],
though having vim in [core] would add lots of dependencies, so I guess
it's better the way it is
On Wed, 2009-05-06 at 07:54 -0300, André Ramaciotti wrote:
> Hi,
>
> Just a question about this new vi package. Am I the only one having
> problems when openning UTF-8 files? I can't even type words with
> diacritics or vi will abort. For example, try to create a file with
> the following and then
Hi,
Just a question about this new vi package. Am I the only one having
problems when openning UTF-8 files? I can't even type words with
diacritics or vi will abort. For example, try to create a file with
the following and then open it with the new vi package:
This line will render fine
Mas essa
21 matches
Mail list logo
