FW: [Bug 144354] filetype is not stored

Andreas Pakulat apaku at gmx.de
Wed Apr 18 15:43:42 UTC 2007


On 18.04.07 10:34:41, Matthew Woehlke wrote:
> Andreas Pakulat wrote:
> > On 18.04.07 09:34:20, Matthew Woehlke wrote:
> >> Maciej Pilichowski wrote:
> >>> ------- You are receiving this mail because: -------
> >>> You are the assignee for the bug, or are watching the assignee.
> >>>          
> >>> http://bugs.kde.org/show_bug.cgi?id=144354         
> >>>
> >>> ------- Additional Comments From bluedzins wp pl  2007-04-18 15:52 -------
> >>> Matthew thank you for the help, however... :-)
> >>>
> >>> Note, that when somebody open a file in KDevelop and reset the encodings... well, it is all she/he has to know. 
> >>>
> >>> I've just take a look at the doc you pointed out, and it appears that you have to notice that filetype storing does not work (and that's bad -- because you can lost some work, besides -- the principle of the least surprise should not be violated), you have to find the solution, you have to learn how to write a modeline spec...
> >>> Comparing it to encodings mentioned above it is quite a challenge, especially when you are close to your deadline with work.
> >>>
> >>> Storing filetype in KDevelop seems to be quite natural feature -- KDevelop already stores a list of opened files and their attributes.
> >> Any comments from the KDevelop side?
> > [snip a bunch of stuff with which I 100% agree :-)]
> 
> ...would you mind if I copied some/all of your explanations to the bug 
> report? (I'm still trying to get a response out of kwrite-devel, but my 
> knee-jerk reaction is to close this as wontfix, and you clearly seem to 
> be in agreement.)

Uhm, no of course copy all you want (just forgot to add that to the op)
and same for my answers in this mail.

> > Also somehow this bug sounds as if it should be on kdevelop, not on
> > kate. Kate has no way of storing such information except in its config
> > file, which will be cluttered soon. 
> 
> Because KDevelop could do something like this with less 
> overhead/clutter, I redirected it here (also because Maciej was talking 
> about KDevelop), however I see two problems. 1: Why should only KDevelop 
> benefit? 2: Can KDevelop even retrieve the needed information through 
> KTextEditor (especially when it only applies to KATE)?

1. exactly, as soon as you get out of kdevelop, or even just import
the project on another computer or account (the .kdevses file is
nonshareable) you'll have to start over again
2. I have no idea, I didn't bother to look.

Andreas

-- 
Good news from afar can bring you a welcome visitor.




More information about the KDevelop-devel mailing list