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

List:       kwrite-devel
Subject:    Re: Syntax highlighting files
From:       "Ivo Anjo" <knuckles () gmail ! com>
Date:       2008-10-30 14:27:41
Message-ID: 557ea2710810300727l73dacc5em5e36405433efe74 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I was thinking: does kate really need to do those stats at startup?

According to Dominik, most of the info is cached, and the stat's are only to
see "if anything changed".
But imagine I'm opening a C file: Kate already knows that there is a C file
highlight, and opens it, and then it notices that it is a new version -- no
stat was needed for the other files.

I think the stat would only be needed when opening a file for which kate
didn't have an highlight, or when opening an highlight and kate notices it's
missing, and that could be done only when needed, not at every startup.

Ivo

[Attachment #5 (text/html)]

I was thinking: does kate really need to do those stats at startup?<br><br>According \
to Dominik, most of the info is cached, and the stat&#39;s are only to see &quot;if \
anything changed&quot;.<br>But imagine I&#39;m opening a C file: Kate already knows \
that there is a C file highlight, and opens it, and then it notices that it is a new \
version -- no stat was needed for the other files.<br> <br>I think the stat would \
only be needed when opening a file for which kate didn&#39;t have an highlight, or \
when opening an highlight and kate notices it&#39;s missing, and that could be done \
only when needed, not at every startup.<br> <br>Ivo<br>



_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel


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