On Tuesday 07 July 2009 09:51:30 am David Rosenstrauch wrote:
> David C. Rankin wrote:
> > Thanks Armando.
> >
> > One of these days I will have to learn LVM. That's one part of the
> > filesystem schemes I haven't gotten to yet.
>
> Highly recommended that you adopt LVM into your bag of tri
Try it, though. I'm Brazilian and I use some UTF-8 multibyte
characters (a small subset of it comparing with the Cyrillic alphabet,
which I presume you use) and I have no problems with files named with
UTF-8 characters.
When I first tried ZSH, I ditched it because of it, but it's been a
long time
>> Has anyone noticed that ctrl-c randomly stops working in the new bash?
>
> You might also consider taking this opportunity to switch to ZSH.
I've just installed it, then I read this .. and it's a deal breaker:
Q: Does zsh support UTF-8?
A: zsh's built-in printf command supports "\u" and "\U"
clemens fischer wrote:
> For a few days now I noticed some programs not working, like "lzma" or
> "xz" from the "xz-utils". They segfault and "xz --help" says:
>
> $ /usr/bin/xz --help
> /usr/bin/xz: unrecognized option '--'
> /usr/bin/xz: Try `/usr/bin/xz --help' for more information.
>
> S
On Tue, Jul 7, 2009 at 16:17, clemens
fischer wrote:
> For a few days now I noticed some programs not working, like "lzma" or
> "xz" from the "xz-utils". They segfault and "xz --help" says:
Are you using [testing]? When is the last time you updated those
programs and/or libraries?
For a few days now I noticed some programs not working, like "lzma" or
"xz" from the "xz-utils". They segfault and "xz --help" says:
$ /usr/bin/xz --help
/usr/bin/xz: unrecognized option '--'
/usr/bin/xz: Try `/usr/bin/xz --help' for more information.
So I went to compile the original sour
David C. Rankin wrote:
Thanks Armando.
One of these days I will have to learn LVM. That's one part of the
filesystem schemes I haven't gotten to yet.
Highly recommended that you adopt LVM into your bag of tricks. It's
pretty brilliant!
Here's some basic intro pointers if you want
Excerpts from Damjan Georgievski's message of Mon Jul 06 18:46:08 -0400 2009:
> Has anyone noticed that ctrl-c randomly stops working in the new bash?
You might also consider taking this opportunity to switch to ZSH.
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
Allan McRae wrote:
Manne Merak wrote:
Anyone else also having problems changing the background image in
KDE4 plasma desktop.
Trying to browse to a folder with images in it crashes Plasma.
Any chances of giving us some useful information? What KDE are you
using (in [extra], [kde-unstable], a
Manne Merak wrote:
Anyone else also having problems changing the background image in KDE4
plasma desktop.
Trying to browse to a folder with images in it crashes Plasma.
Any chances of giving us some useful information? What KDE are you
using (in [extra], [kde-unstable], a KDEmod flavour). A
Anyone else also having problems changing the background image in KDE4
plasma desktop.
Trying to browse to a folder with images in it crashes Plasma.
Manne
Damjan Georgievski wrote:
> Has anyone noticed that ctrl-c randomly stops working in the new bash?
> I use rxvt-unicode 9.06-2 and it happens in a terminal where ctrl-c
> worked while typing bash commands, it will suddenly stop working ie
> bash will not recognise the key-press.
>
> If I start pyt
Damjan Georgievski wrote:
Has anyone noticed that ctrl-c randomly stops working in the new bash?
I use rxvt-unicode 9.06-2 and it happens in a terminal where ctrl-c
worked while typing bash commands, it will suddenly stop working ie
bash will not recognise the key-press.
If I start python in the
Am Sonntag, den 05.07.2009, 19:07 +1000 schrieb Allan McRae:
> Roman Kyrylych wrote:
> > On Fri, Jul 3, 2009 at 16:15, Allan McRae wrote:
> >
> >> fix -w (FS#15330), compress info pages
> >>
> >> Signoff both.
> >>
> >
> > Signed off (x86_64).
> >
>
> Any i686 signoff? The -w issue bre
>> Has anyone noticed that ctrl-c randomly stops working in the new bash?
>> I use rxvt-unicode 9.06-2 and it happens in a terminal where ctrl-c
>> worked while typing bash commands, it will suddenly stop working ie
>> bash will not recognise the key-press.
>
> There was a bug which stopped ctrl-c
Not really, I was aiming for a vimcurrent symlink like debian but taht
was opposed as there seems to be another standard location. Hopefully I
will have another and maybe final vim in teesting by the weekend and
once that is done there will be some documentation(probably in the wiki)
but certainly
On Tue, Jul 7, 2009 at 8:10 AM, Tobias Kieslich wrote:
> As far as vi/vim(7) in extra is concerned, it was always installed in
> /usr/share/vim. So vim files location has NOT changed yet again. vim
> files in testing are getting installed into /usr/share/vim/vim72 but
> that is the future.
Ah, tha
On Tue, 7 Jul 2009 01:19:41 +0200
Henning Garus wrote:
> On Tue, Jul 7, 2009 at 12:46 AM, Damjan
> Georgievski wrote:
> > Has anyone noticed that ctrl-c randomly stops working in the new
> > bash? I use rxvt-unicode 9.06-2 and it happens in a terminal where
> > ctrl-c worked while typing bash com
As far as vi/vim(7) in extra is concerned, it was always installed in
/usr/share/vim. So vim files location has NOT changed yet again. vim
files in testing are getting installed into /usr/share/vim/vim72 but
that is the future.
-T
On Tue, 07 Jul 2009, Magnus Therning wrote:
> It seems tha
19 matches
Mail list logo
