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

List:       kwrite-devel
Subject:    Re: Default Styles
From:       "Philipp A." <flying-sheep () web ! de>
Date:       2014-02-18 13:43:44
Message-ID: CAN8d9gmeNHmijA_D+FctwzvRJHW_WkrLZUUHct00cW19-HJrqg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2014-02-17 23:49 GMT+01:00 Milian Wolff <mail@milianw.de>:

> Can you elaborate why you want to have [dsBuiltin], and how it differs from
> dsKeyword, dsFunction, dsConstant?
>

dsKeyword: keywords. class, if, else, break, continue, match, switch,
yield, function, def, try, raise, …
dsFunction: function/method declarations, i.e. the function name after the
function keyword: defun …, String …() {}, function …() {}, def …():
dsConstant: NAMES_WITH_UNDERSCORES per convention

dsBuiltin: functions, classes, etc. which are defined in the default
namespace: e.g. http://docs.python.org/3.3/library/functions.html and the
types like int, set, …, http://golang.org/pkg/builtin/

i agree, dsBuiltinValue is maybe to much. those are special
constants/singletons like true, false, null, … we could highlight them as
constants or keywords.

but i still definitely want dsBuiltin!

At least JavaScript and C++ don't have it. PHP has it though. Anyhow, this
> depends on semantic analysis (see my other email) and maybe needs a
> different
> approach. That said, why would one want to highlight exceptions differently
> from other objects? Where is this useful to know directly whether a type is
> actually an Exception?
>

the python highlighting has the builtin exceptions highlighted, which is
useful for knowing that you spelled them wrong. but probably overkill and
better done with completion.

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-02-17 23:49 \
GMT+01:00 Milian Wolff <span dir="ltr">&lt;<a href="mailto:mail@milianw.de" \
target="_blank">mail@milianw.de</a>&gt;</span>:<br><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> Can you elaborate why you want to have \
[dsBuiltin], and how it differs from<br> dsKeyword, dsFunction, \
dsConstant?<br></blockquote><div><br></div><div>dsKeyword: keywords. class, if, else, \
break, continue, match, switch, yield, function, def, try, raise, \
…<br></div><div>dsFunction: function/method declarations, i.e. the function name \
after the function keyword: defun …, String …() {}, function …() {}, def \
…():<br> </div><div>dsConstant: NAMES_WITH_UNDERSCORES per \
convention<br><br></div><div>dsBuiltin: functions, classes, etc. which are defined in \
the default namespace: e.g. <a \
href="http://docs.python.org/3.3/library/functions.html">http://docs.python.org/3.3/library/functions.html</a> \
and the types like int, set, …, <a \
href="http://golang.org/pkg/builtin/">http://golang.org/pkg/builtin/</a><br> \
<br></div><div>i agree, dsBuiltinValue is maybe to much. those are special \
constants/singletons like true, false, null, … we could highlight them as constants \
or keywords.<br><br></div><div>but i still definitely want dsBuiltin!<br> \
</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">

</div>At least JavaScript and C++ don&#39;t have it. PHP has it though. Anyhow, \
this<br> depends on semantic analysis (see my other email) and maybe needs a \
different<br> approach. That said, why would one want to highlight exceptions \
differently<br> from other objects? Where is this useful to know directly whether a \
type is<br> actually an Exception?<br></blockquote><div><br></div><div>the python \
highlighting has the builtin exceptions highlighted, which is useful for knowing that \
you spelled them wrong. but probably overkill and better done with completion.<br> \
</div></div></div></div>



_______________________________________________
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]