public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Walch <walch.martin@web.de>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: kconfig: NEW: syntax highlighting for Kconfig files in KDE
Date: Sat, 13 Sep 2014 00:32:09 +0200	[thread overview]
Message-ID: <27129446.btpinNW7pO@tacticalops> (raw)

The text editors in KDE (Kate, KWrite, KDevelop, etc.) now support
highlighting Kconfig files. This will ship with KDE SC 4.14.1, older versions
back to KDE 4.4.0 can easily get it by running Kate and using the download
dialog at >Settings >Configure Kate... >Editor Component: Open/Save
>Modes & Filetypes >Download Highlighting Files...

Kate automatically applies this highlighting style to all files with names
that start with "Kconfig" unless some other pattern applies (e.g. *.c).

The highlighting should be pretty accurate with the usual formatting
scheme that most syntax highlighters of KDE apply and it comes with code
folding support and spell checking. However, it still lacks an indenter.
It also has no other fancy stuff like accurate auto-completion or jumping
to a declaration.

While the infrastructure of Kate Part primarily targets highlighting
syntactically valid files (not caring about invalid syntax), this highlighter
also underlines anything that will lead to a syntax error when running *conf.
Bad characters that do not lead up to a syntax error, but which will be
silently ignored, are red with a light red background.

This all comes at the cost of rather high cpu usage. You may notice when
loading large files, depending on your hardware. Also, automatic spell
checking on large files may slow things down. If you intend to open hundreds
of Kconfig files at once, expect it to take a long time.

Please report bugs either to me via email (subject start [kconfig.xml]) or
in the bug tracker of KDE at https://bugs.kde.org/

Regards
Martin Walch
-- 


                 reply	other threads:[~2014-09-12 22:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27129446.btpinNW7pO@tacticalops \
    --to=walch.martin@web.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox