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

List:       kde-bugs-dist
Subject:    [Bug 40656] indent in kate should help spotting the errors
From:       tnagy <tnagy () eleve ! emn ! fr>
Date:       2003-12-05 1:01:11
[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=40656     




------- Additional Comments From tnagy@eleve.emn.fr  2003-12-05 02:01 -------
A plugin ?
Then what about moving the syntax highlighting into a plugin then ? :)

And about the current user interface .. since the highlighting is a property of the \
document currently edited like the indentation, why are not they gathered in a common \
feature "File type" ? Will people actually use a php highlighting for latex files ?

Concerning the memory consumption, since the katepart is a shared library, the memory \
used is supposed to be shared between the editors. If twenty katepart editors are \
opened (in kdevelop?), will the editor memory consumption be multiplied by twenty ? 

The autoindentation is really an important feature for programmers, and while astyle \
parses whole files, in practice what is needed is to autoindent a line given the \
previous ones (to spot the common errors, etc) like in emacs or vim. The "indent \
while you type" feature is just to autoindent both the current and the new line after \
the enter key is pressed then. The "autoindent all files" or "autoindent a region" \
features could indeed be put in a plugin (it is autoindent some lines) ?

I do not know if vim uses such a method, but it can reformat entirely \
katehighlight.cpp or katedocument.cpp in less than one second :)


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