HybridDog/geany
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update docs for named styles in filetypes.* files.

Browse Source 
git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@3829 ea778897-0a13-0410-b9d1-a72fbfd435f5
This commit is contained in:
Nick Treleaven 2009-06-01 14:37:53 +00:00
parent f678ee105a
commit fd2f43911d
4 changed files with 703 additions and 619 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ChangeLog
View File

@ -2,6 +2,8 @@
* src/highlighting.c:
Support named styles also for filetypes.common [styling] entries.
* doc/geany.txt, doc/geany.html, HACKING:
Update docs for named styles in filetypes.* files.
2009-05-30 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de>

1
HACKING
View File

@ -207,6 +207,7 @@ SVN version. Alternatively, edit the file by hand.
filetypes.* configuration file
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
All languages need a data/filetypes.foo configuration file. See
the "Filetype definition files" section in the manual and/or
data/filetypes.c for an example.
Programming languages should have:

1275
doc/geany.html
View File

File diff suppressed because it is too large Load Diff

44
doc/geany.txt
View File

@ -2894,9 +2894,11 @@ where ``$prefix`` is the path where Geany is installed (see
`Installation prefix`_) and $ext is the name of the filetype. For every
filetype there is a corresponding definition file. There is one
exception: ``filetypes.common`` -- this file is for general settings,
which are not specific to a certain filetype. It is not recommended
to edit the system-wide files, because they will be overridden when
Geany is updated.
which are not specific to a certain filetype.
.. warning::
It is not recommended for users to edit the system-wide files,
because they will be overridden when Geany is updated.
To change the settings, copy a file from ``$prefix/share/geany`` to
the subdirectory filedefs in your configuration directory (usually
@ -2922,7 +2924,10 @@ Format
`````````````````
In this section the colors for syntax highlighting are defined. The
format is always: key=foreground_color;background_color;bold;italic
format is one of:
* ``key=foreground_color;background_color;bold;italic``
* ``key=named_style``
Colors have to be specified as RGB hex values prefixed by
0x. For example red is 0xff0000, blue is 0x0000ff. The values are
@ -2930,6 +2935,8 @@ case-insensitive, but it is a good idea to use small letters. Bold
and italic are flags and should only be "true" or "false". If their
value is something other than "true" or "false", "false" is assumed.
For named styles, see the filetypes.common `[named_styles] Section`_.
[keywords] Section
``````````````````
@ -3072,6 +3079,33 @@ There is a special filetype definition file called
filetypes.common. This file defines some general non-filetype-specific
settings.
[named_styles] Section
``````````````````````
Named styles declared here can be used in the [styling] section of any
filetypes.* file.
For example:
*In filetypes.common*::
[named_styles]
foo=0xc00000;0xffffff;false;true
bar=foo
*In filetypes.c*::
[styling]
comment=foo
This saves copying and pasting the whole style definition into several
different files.
.. note::
You can define aliases for named styles, as shown with the ``bar``
entry in the above example.
[styling] Section
`````````````````
default
This is the default style. It is used for styling files without a
filetype set.
@ -3248,6 +3282,8 @@ marker_translucency
*Example:* ``marker_translucency=256;256;false;false``
[settings] Section
``````````````````
whitespace_chars
Characters to treat as whitespace. These characters are ignored
when moving, selecting and deleting across word boundaries