Re: KDE 3.5.6 and task grouping

Dnia niedziela, 18 lutego 2007, Marcin Król napisał: > Since I've upgraded to KDE 3.5.6 Konsole windows aren't grouped anymore. > Anyone knows if this is a bug or new feature? I can't see any new option > in KDE Control Center or Konsole itself to change this behaviour. This > is very annoying when

Re: KDE 3.5.6 and task grouping

> Try rebuilding kdebase without -grouplayer.patch and report back :) Tried that already. No change. M. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: KDE 3.5.6 and task grouping

On Sunday 18 of February 2007, Marcin Król wrote: > Since I've upgraded to KDE 3.5.6 Konsole windows aren't grouped anymore. > Anyone knows if this is a bug or new feature? I can't see any new option > in KDE Control Center or Konsole itself to change this behaviour. This > is very annoying when yo

KDE 3.5.6 and task grouping

Since I've upgraded to KDE 3.5.6 Konsole windows aren't grouped anymore. Anyone knows if this is a bug or new feature? I can't see any new option in KDE Control Center or Konsole itself to change this behaviour. This is very annoying when you have 30+ konsole windows which are not grouped on task b

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:31:54PM +0100, Cezary Krzyzanowski wrote: > Dnia 18-02-2007, nie o godzinie 13:17 +0100, Tomasz Pala napisał(a): > > Means what? I don't see vim here. As default `encoding` (internal > > setting for buffers etc) is latin1 (as I don't use gvim for anything but > > LaTeX an

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 12:50:25PM +0100, Tomasz Pala wrote: > > set fileencoding=iso8859-2 > > > set fileencodings=ucs-bom,utf-8,iso-8859-2,latin1 > > And how should it work? Because it does not. New-enough VIM is needed (older version had big problems with "fileencoding" sett

Re: utf-8 encoding in specs

On Sunday 18 February 2007, Arkadiusz Miskiewicz wrote: > On Sunday 18 of February 2007, Marcin Król wrote: > > > what about AC-branch, RA-branch and other branches that weren't > > > converted to utf? > > > > AC-branch remains non UTF until rpm will handle UTF specs properly at > > least on en_US

Re: utf-8 encoding in specs

On Sunday 18 of February 2007, Marcin Król wrote: > > what about AC-branch, RA-branch and other branches that weren't > > converted to utf? > > AC-branch remains non UTF until rpm will handle UTF specs properly at > least on en_US and all pl_PL locales. Is this not working for someone else than Ha

Re: utf-8 encoding in specs

> what about AC-branch, RA-branch and other branches that weren't > converted to utf? AC-branch remains non UTF until rpm will handle UTF specs properly at least on en_US and all pl_PL locales. M. ___ pld-devel-en mailing list pld-devel-en@lists.pld-lin

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 04:15:12PM +0100, Andrzej 'The Undefined' Dopierała wrote: > On Sun, Feb 18, 2007 at 01:31:01PM +0100, Jakub Bogusz wrote: > > > au BufReadPre *.spec setlocal fencs=utf-8,iso-8859-2,latin1 > > > au BufNewFile *.spec setlocal fenc=utf-8 > > > > update: > > au BufReadPre *.s

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:31:01PM +0100, Jakub Bogusz wrote: > > au BufReadPre *.spec setlocal fencs=utf-8,iso-8859-2,latin1 > > au BufNewFile *.spec setlocal fenc=utf-8 > > update: > au BufReadPre *.spec setlocal encoding=utf-8 fencs=utf-8,iso-8859-2,latin1 > au BufNewFile *.spec setlocal encodi

Re: utf-8 encoding in specs

On Sunday 18 February 2007, Jakub Bogusz wrote: > update: > au BufReadPre *.spec setlocal encoding=utf-8 fencs=utf-8,iso-8859-2,latin1 > au BufNewFile *.spec setlocal encoding=utf-8 fenc=utf-8 > > (needed if default encoding is latin* and spec contains non-latin chars) i'd add there also: ts=4 sw

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:31:01PM +0100, Jakub Bogusz wrote: > > update: > au BufReadPre *.spec setlocal encoding=utf-8 fencs=utf-8,iso-8859-2,latin1 > au BufNewFile *.spec setlocal encoding=utf-8 fenc=utf-8 All the specs where converted? If so, that's ok for me. -- Tom Pala <[EMAIL PROTECTED]

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:31:54PM +0100, Cezary Krzyzanowski wrote: > > So how should this work? One needs to set encoding to utf-8 (not fileencoding*). Either by vim-line in specs (like I've suggested) or by hand or eventually (semi)global (e.g. like qboosh wrote). -- Tom Pala <[EMAIL PROTECT

Re: utf-8 encoding in specs

Dnia 18-02-2007, nie o godzinie 13:17 +0100, Tomasz Pala napisał(a): > Means what? I don't see vim here. As default `encoding` (internal > setting for buffers etc) is latin1 (as I don't use gvim for anything but > LaTeX and don't have unicode locale) it simply won't work. So how should this work?

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:18:29PM +0100, Jakub Bogusz wrote: > On Sun, Feb 18, 2007 at 01:10:36PM +0100, Jakub Bogusz wrote: > > On Sun, Feb 18, 2007 at 12:50:25PM +0100, Tomasz Pala wrote: > > > On Sun, Feb 18, 2007 at 12:41:04PM +0100, Arkadiusz Miskiewicz wrote: > [...] > > > > put these to .vi

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:10:36PM +0100, Jakub Bogusz wrote: > > > > And how should it work? Because it does not. > > > > Summary(pl.UTF-8): Edytor plikĂłw binarnych oparty na bibliotece > > ncurses > > it needs: > set encoding=utf-8 > additionaly. I know that. The other guys don't. > A

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 02:08:32PM +0200, Elan Ruusamäe wrote: > > > > And how should it work? Because it does not. > utf-8 is before iso8859-2: So? fileencoding!=encoding It's all in the docs. > > set fileencodings=ucs-bom,utf-8,iso-8859-2,latin1 > > works here with and without those lines, dun

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:10:36PM +0100, Jakub Bogusz wrote: > On Sun, Feb 18, 2007 at 12:50:25PM +0100, Tomasz Pala wrote: > > On Sun, Feb 18, 2007 at 12:41:04PM +0100, Arkadiusz Miskiewicz wrote: [...] > > > put these to .vimrc and no need for meesing with spec files > > > > > > set fileencodin

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 01:04:23PM +0100, Cezary Krzyzanowski wrote: > > [EMAIL PROTECTED] bin]$ grep Summary > \(pl /home/users/czarny/rpm/SPECS/memprof.spec > Summary(pl.UTF-8): Narzędzie do profilowania i detekcji wycieków > pamięci Means what? I don't see vim here. As default `encodin

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 12:50:25PM +0100, Tomasz Pala wrote: > On Sun, Feb 18, 2007 at 12:41:04PM +0100, Arkadiusz Miskiewicz wrote: > > > > # vim:encoding=utf-8 > > > > > > > > > line to all the converted specs. Any objections? > > > > > > +1 > > > > -1 > > > > put these to

Re: utf-8 encoding in specs

On Sunday 18 February 2007, Tomasz Pala wrote: > On Sun, Feb 18, 2007 at 12:41:04PM +0100, Arkadiusz Miskiewicz wrote: > > > > # vim:encoding=utf-8 > > > > > > > line to all the converted specs. Any objections? > > > > > > +1 > > > > -1 > > > > put these to .vimrc and no need f

Re: SPECS (AC-branch): microcode_ctl.spec - 1.16

Elan Ruusamäe wrote: > On Sunday 18 February 2007, Andrzej Zawadzki wrote: >> glen wrote: >>> Author: glen Date: Sun Feb 18 10:51:51 2007 GMT >>> Module: SPECS Tag: AC-branch >>> Log message: >>> - 1.16 >> If we still have kernel 2.6.16 in AC the

Re: utf-8 encoding in specs

Dnia 18-02-2007, nie o godzinie 12:50 +0100, Tomasz Pala napisał(a): > On Sun, Feb 18, 2007 at 12:41:04PM +0100, Arkadiusz Miskiewicz wrote: > > put these to .vimrc and no need for meesing with spec files > > > > set fileencoding=iso8859-2 > > > set fileencodings=ucs-bom,utf-8,i

Re: SPECS (AC-branch): microcode_ctl.spec - 1.16

On Sunday 18 February 2007, Andrzej Zawadzki wrote: > glen wrote: > > Author: glen Date: Sun Feb 18 10:51:51 2007 GMT > > Module: SPECS Tag: AC-branch > > Log message: > > - 1.16 > > If we still have kernel 2.6.16 in AC then microcode must stay i

Re: utf-8 encoding in specs

On Sun, Feb 18, 2007 at 12:41:04PM +0100, Arkadiusz Miskiewicz wrote: > > > # vim:encoding=utf-8 > > > > > > line to all the converted specs. Any objections? > > > > +1 > > -1 > > put these to .vimrc and no need for meesing with spec files > > set fileencoding=iso8859-2

Re: utf-8 encoding in specs

On Sunday 18 of February 2007, Cezary Krzyzanowski wrote: > Dnia 18-02-2007, nie o godzinie 11:45 +0100, Tomasz Pala napisał(a): > > I suggest adding: > > > > # vim:encoding=utf-8 > > > > line to all the converted specs. Any objections? > > +1 -1 put these to .vimrc and no need for meesing with s

Re: SPECS (AC-branch): microcode_ctl.spec - 1.16

glen wrote: > Author: glen Date: Sun Feb 18 10:51:51 2007 GMT > Module: SPECS Tag: AC-branch > Log message: > - 1.16 If we still have kernel 2.6.16 in AC then microcode must stay in version 1.14. With higher version on 2.6.16 I've got error: mi

Re: utf-8 encoding in specs

Dnia 18-02-2007, nie o godzinie 11:45 +0100, Tomasz Pala napisał(a): > I suggest adding: > > # vim:encoding=utf-8 > > line to all the converted specs. Any objections? > +1 [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.o

utf-8 encoding in specs

I suggest adding: # vim:encoding=utf-8 line to all the converted specs. Any objections? -- Tom Pala <[EMAIL PROTECTED]> http://vfmg.sourceforge.net/ http://tccs.sourceforge.net/ ___ pld-devel-en maili

Re: cvs ro?

On Sun, Feb 18, 2007 at 11:24:53AM +0100, Tomasz Pala wrote: > cvs [server aborted]: "commit" requires write access to the repository > > anyone? Sorry, bad CVS/Root after disk crash. -- Tom Pala <[EMAIL PROTECTED]> http://vfmg.sourceforge.net/

cvs ro?

cvs [server aborted]: "commit" requires write access to the repository anyone? -- Tom Pala <[EMAIL PROTECTED]> http://vfmg.sourceforge.net/ http://tccs.sourceforge.net/ ___ pld-devel-en mailing list pl