Bug 226905 - Add support for mime-type sections to .kateconfig files
Summary: Add support for mime-type sections to .kateconfig files
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: VHI wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 23:46 UTC by Anders Lund
Modified: 2019-05-15 16:05 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2010-02-14 23:46:57 UTC
Version:           3.4.0 (using 4.4.00 (KDE 4.4.0), Chakra)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.32-ARCH

It would be nice if .kateconfig files could contain groups of variables targeting different files, matched by extension/glob or mimetype.
Comment 1 Dominik Haumann 2010-02-15 00:00:21 UTC
Ideas on IRC:

- make .kateconfig a KConfig file
- add [General] group. Those entries are valid for all mimetypes
- specializations with mimetype groups, e.g. [text/plain]
- extension matching? globs? to-be-discussed

and:
- be backward compatible! (i.e., if no groups available, fall back to old impl)
Comment 2 Lothar 2019-03-03 17:32:24 UTC
Is't it now available by ConfigDialog->FileOpen&Save->Mode&Type->Variables ?

For my taste a not so nice solution, all settings should be remembered somehow automatic in a smart way
Comment 3 Dominik Haumann 2019-05-14 13:15:50 UTC
It's already supported for a long time:
https://kate-editor.org/2006/02/09/kateconfig-files/

So this bug from Anders is fixed, or?
Comment 4 Anders Lund 2019-05-14 21:55:09 UTC
tirsdag den 14. maj 2019 15.15.50 CEST skrev du:
> https://bugs.kde.org/show_bug.cgi?id=226905
> 
> --- Comment #3 from Dominik Haumann <dhaumann@kde.org> ---
> It's already supported for a long time:
> https://kate-editor.org/2006/02/09/kateconfig-files/
> 
> So this bug from Anders is fixed, or?

I think so, I wondered why it is still active! :)
Comment 5 Dominik Haumann 2019-05-15 16:05:58 UTC
Then let's close it.