FW: [Bug 144354] filetype is not stored

[Matthew Woehlke]

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.)

> 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)?

I would see KATE doing this by storing "shadow files", although that 
(considering my comments and your comments) seems ridiculous for the 
benefit. As we've both agreed, that's what modelines are for. :-)

> Last but not least: Is the filetype-information preserved in kdevelop
> while the file is not open? So if I close the file and re-open it I
> think I have to set the file-type again - no? If that is the case (i.e.
> its not stored between close and open) than there's no point in adding
> the information to the session file, as its lost later on when the file
> is closed.

Agreed; I didn't get that either. It sounds like the request is to 
persist information about opened files when closing and restarting 
KDevelop, with no mention of persisting between closing and opening of 
files, which, as you say, makes no sense. :-)

Thanks for the feedback/support. :-)

-- 
Matthew
PIE INCOMING!!!