[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 163518] New: setting indentation for a C++ file to "C indenter"
From:       Stefan Monov <logixoul () gmail ! com>
Date:       2008-06-08 9:59:09
Message-ID: 20080608115907.163518.logixoul () gmail ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=163518         
           Summary: setting indentation for a C++ file to "C indenter"
                    doesn't make all C++ files use that indenter
           Product: kate
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kwrite-devel kde org
        ReportedBy: logixoul gmail com


Version:           3.0.80 (using 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1), compiled \
                sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.22.17-0.1-default

To reproduce:
1. open foo.cpp
2. Tools -> Indentation -> C indenter
3. open bar.cpp
4. bar.cpp does not automatically use "C indenter".

I'd normally file this as a wishlist but annma in #kde says it works for her so it \
must be a regression.

Apart from that, I believe the best (and obvious) solution solution is to keep a \
configurable list of file extensions mapped to indenters. So \
(.cpp|.cxx|.C|.c|.hpp|.h|.d|.js) maps to C indenter, (.py) maps to Python, (.sh) maps \
to Normal, (.diff) maps to None, etc. Also more advanced mimetypes (taken from magic \
numbers, or HTTP, or file-content heuristics..) could help for non-standard \
extensions. But that might be considered a separate wish.


[prev in list] [next in list] [prev in thread] [next in thread]