From: Thomas B. <br...@ph...> - 2008-03-16 17:55:49
|
Hello, a few days ago we prepared a package with kile 2.0.1rc1. Among other fixes it includes one important fix concerning codeceompletion. Get it here http://kile.sourceforge.net/download.php. To be sure if we catched all bugs in the codecompletion we would like to get some feedback on this. So if you hit the famous "codecompletion stops working bug", https://bugs.kde.org/show_bug.cgi?id=155044, please try this version and report back. Thanks, Thomas |
From: Thomas B. <br...@ph...> - 2008-03-29 10:06:58
|
On Sunday 16 March 2008 18:55, Thomas Braun wrote: > Hello, > > a few days ago we prepared a package with kile 2.0.1rc1. > Among other fixes it includes one important fix concerning codeceompletion. > Get it here http://kile.sourceforge.net/download.php. > > To be sure if we catched all bugs in the codecompletion we would like to > get some feedback on this. > > So if you hit the famous "codecompletion stops working bug", > https://bugs.kde.org/show_bug.cgi?id=155044, please try this version and > report back. Hi, so that does "no feedback" mean? No bugs or no testers? Thanks :) Thomas |
From: Thibaut C. <li...@th...> - 2008-03-31 15:29:40
|
Le 29 mars 08 à 11:06, Thomas Braun a écrit : > > so that does "no feedback" mean? > No bugs or no testers? I've just arrived. Don't worry, I'll test it, especially if it fixes the annoying bug about completion deactivating itself... Give me a few days. Regards, -- Thibaut Cousin http://www.thibaut-cousin.net |
From: Thibaut C. <li...@th...> - 2008-04-13 03:53:58
|
Le 29 mars 08 à 11:06, Thomas Braun a écrit : > On Sunday 16 March 2008 18:55, Thomas Braun wrote: >> Hello, >> >> a few days ago we prepared a package with kile 2.0.1rc1. >> Among other fixes it includes one important fix concerning >> codeceompletion. >> Get it here http://kile.sourceforge.net/download.php. >> >> To be sure if we catched all bugs in the codecompletion we would >> like to >> get some feedback on this. >> >> So if you hit the famous "codecompletion stops working bug", >> https://bugs.kde.org/show_bug.cgi?id=155044, please try this >> version and >> report back. > > Hi, > > so that does "no feedback" mean? > No bugs or no testers? I'm a bit slow about testing at the moment, as I'm on holidays. But I can tell you it compiles fines on Mac OS X (on both PPC and Intel) and I'm going to start real work on it, probably tomorrow. I'll keep you informed if I get into any bug. Apart from the code completion problem, anything I should specifically test? -- Thibaut Cousin http://www.thibaut-cousin.net |
From: Thomas B. <br...@ph...> - 2008-04-13 14:22:40
|
On Friday 11 April 2008 01:38, A Mani wrote: > On Sun, Mar 16, 2008 at 11:25 PM, Thomas Braun > > <br...@ph...> wrote: > > To be sure if we catched all bugs in the codecompletion we would like to > > get some feedback on this. > > > > So if you hit the famous "codecompletion stops working bug", > > https://bugs.kde.org/show_bug.cgi?id=155044, please try this version and > > report back. > > I checked it on both Slamd64 -12 Linux (64-bit AMD) and VectorLinux > (32-bit i86). > I could not find any of those bugs. I tried with and without including > a bib file. > > > Best > > A. Mani thanks, Thomas |
From: Thomas B. <br...@ph...> - 2008-04-13 17:48:24
|
On Sunday 13 April 2008 05:53, Thibaut Cousin wrote: > > Hi, > > > > so that does "no feedback" mean? > > No bugs or no testers? > > I'm a bit slow about testing at the moment, as I'm on holidays. But > I can tell you it compiles fines on Mac OS X (on both PPC and Intel) > and I'm going to start real work on it, probably tomorrow. I'll keep > you informed if I get into any bug. > Apart from the code completion problem, anything I should > specifically test? Hi Thibaut, actually not. I just looked at the Changelog and the rest is straight forward I suppose. But I must say I just submitted a different codecompletion fix to the repository. My previous solution from https://bugs.kde.org/show_bug.cgi?id=155044#c9 created https://bugs.kde.org/show_bug.cgi?id=160555 and this is also a nasty one. So I reverted the hole thing and took a different approach. Now it would be interesting which codecompletion fix works better: - 2.0rc1 from http://kile.sourceforge.net/download.php - revision 796505 from the kile 2.0 branch, get it with svn co svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/office Thanks for your help, Thomas |
From: Thibaut C. <li...@th...> - 2008-04-20 23:00:38
|
Le 13 avr. 08 à 19:48, Thomas Braun a écrit : > But I must say I just submitted a different codecompletion fix to the > repository. > My previous solution from https://bugs.kde.org/show_bug.cgi? > id=155044#c9 > created https://bugs.kde.org/show_bug.cgi?id=160555 and this is also > a nasty > one. > > So I reverted the hole thing and took a different approach. > > Now it would be interesting which codecompletion fix works better: > - 2.0rc1 from http://kile.sourceforge.net/download.php > - revision 796505 from the kile 2.0 branch, get it with svn co > svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/office I've worked with 2.0rc1 for a few days now, and it works perfectly well: I no longer loses autocompletion after a while. :) As for bug #160555, I haven't hit it because I don't use those features much. On the other hand, autocompletion has reverted to an old annoying behavior: when I start typing a command with braces and autocompletes it with the popup menu, I get two closing braces: one from the autocompletion of the command, and one from the autoclose feature. I was using the configuration from Kile 2.0, in which I didn't have that problem. Regards, -- Thibaut Cousin http://www.thibaut-cousin.net |
From: Thibaut C. <li...@th...> - 2008-05-02 21:49:31
|
Just to give some additional feedback... Last week I made some heavy LaTeX work with Kile 2.0.1rc1, with the application running for two days straight. I'm happy to say that the disappearing autocompletion problem never resurfaced. :) I know I had already reported about this, but it wasn't after such a long test. Regards, -- Thibaut Cousin http://www.thibaut-cousin.net |
From: Michel L. <mic...@kd...> - 2008-05-03 08:50:55
|
Hi, On Fri 02 May 2008, Thibaut Cousin wrote: > Just to give some additional feedback... Last week I made some > heavy LaTeX work with Kile 2.0.1rc1, with the application running for > two days straight. > I'm happy to say that the disappearing autocompletion problem never > resurfaced. :) > I know I had already reported about this, but it wasn't after such > a long test. Thanks. I guess Kile 2.0.1 is then ready to go. Michel |
From: Thomas B. <br...@ph...> - 2008-05-03 10:49:12
|
On Saturday 03 May 2008 10:50, Michel Ludwig wrote: > Hi, > > On Fri 02 May 2008, Thibaut Cousin wrote: > > Just to give some additional feedback... Last week I made some > > heavy LaTeX work with Kile 2.0.1rc1, with the application running for > > two days straight. > > I'm happy to say that the disappearing autocompletion problem never > > resurfaced. :) > > I know I had already reported about this, but it wasn't after such > > a long test. > > Thanks. I guess Kile 2.0.1 is then ready to go. > > Michel Well, I guess so too. But we should keep in mind that then https://bugs.kde.org/show_bug.cgi?id=160555 is a "known bug." Thomas |
From: Ivan <ia...@ho...> - 2008-05-05 16:51:59
|
HI - I am using Kile 2.0.0 in Ubuntu 8.04 and have the autocompletion bug. I'd like to update my version of Kile but I'm new to linux and failed on my first attempt. I downloaded the source file and followed directions from the KILE website but I didn't work (never got to "make"). I really like Kile and I want to keep using it without this bug. I'd appreciate any help. Ivan. |