Abhay Kedia wrote:
> http://bugs.kde.org/show_bug.cgi?id=119146
>
> Is there any chance that Gentoo developers could commit this fix
> to the portage, even though it is still in SVN?
Unlikely: search bugs.gentoo.org for similar kde bugs and you'll see
they get marked UPST (upstream). Normally on
On Friday 06 January 2006 19:24, Petteri Räty wrote:
>
> You can always file a bug in bugs.kde.org to request this to be
> configurable. As usual first check that the bug does not already exist.
>
While filing the bug I found a related bug and the fix is said to be committed
to svn. Here it is
htt
Abhay Kedia wrote:
> On Wednesday 04 January 2006 16:02, Neil Bothwick wrote:
>
>>I've just tried it on another box, and I do get that error when opening
>>a second file, but checking kate shows that it does have both files
>>loaded.
>>
>
> Ah...you are right. The files did get opened but that er
On Wed, 4 Jan 2006 19:42:29 +0530, Abhay Kedia wrote:
> > I set the text/plain file type to call this with only %U as an
> > argument, and it works without annoying messages.
> >
> Thanks for looking into this :)
> This works but why is it so slow in launching? The first instance loads
> instanta
On Wednesday 04 January 2006 18:40, Neil Bothwick wrote:
>
> I set the text/plain file type to call this with only %U as an argument,
> and it works without annoying messages.
>
Thanks for looking into this :)
This works but why is it so slow in launching? The first instance loads
instantaneously
On Wed, 4 Jan 2006 16:57:18 +0530, Abhay Kedia wrote:
> Ah...you are right. The files did get opened but that error pop (and
> that too twice) is quite annoying. I even tried to rename kate to
> kate.bin and created a script with name kate which calls kate.bin with
> --use option but that also giv
On Wednesday 04 January 2006 16:02, Neil Bothwick wrote:
>
> I've just tried it on another box, and I do get that error when opening
> a second file, but checking kate shows that it does have both files
> loaded.
>
Ah...you are right. The files did get opened but that error pop (and that too
twice
On Wed, 4 Jan 2006 15:27:52 +0530, Abhay Kedia wrote:
> Go to the Control Centre -> KDE components -> File
> > associations and select text/plain. Select Kate, press Edit, go to the
> > Application tab and change the command from "kate %U" to "kate --use
> > %U".
> >
> That doesn't work :(
> It sh
On Wednesday 04 January 2006 15:01, Neil Bothwick wrote:
>
> call Kate. Go to the Control Centre -> KDE components -> File
> associations and select text/plain. Select Kate, press Edit, go to the
> Application tab and change the command from "kate %U" to "kate --use %U".
>
That doesn't work :(
It s
On Wed, 4 Jan 2006 14:39:42 +0530, Abhay Kedia wrote:
> I have this same problem. Earlier on opening a file from konqueror or
> any where else the kate used to open it in the already open instance.
> How to make that behaviour default? How to get back that functionality.
> I thought that I messed
On Wednesday 04 January 2006 11:20, Roy Wright wrote:
>
> Try kate -u filename
>
> kate --help shows this option:
> -u, --use Use a already running kate instance (if
> possible)
>
I have this same problem. Earlier on opening a file from konqueror or any
where else the kate used to
Francisco Figueiredo Jr. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I just updated kde to 3.5.0.
One thing I noticed with Kate is that when I type in konsole: kate
somefile, it spawns another kate process and not reuse the already
running kate.
This used to happen with 3.4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I just updated kde to 3.5.0.
One thing I noticed with Kate is that when I type in konsole: kate
somefile, it spawns another kate process and not reuse the already
running kate.
This used to happen with 3.4.0 I had before.
Is this some new c
13 matches
Mail list logo
