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

Add #reading-styles-from-another-filetype subsection, based on

Browse Source 
patch by Matthew Brush (thanks).



git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@5643 ea778897-0a13-0410-b9d1-a72fbfd435f5
This commit is contained in:
Nick Treleaven 2011-03-29 13:26:39 +00:00
parent 8640d845d0
commit f94f860f3f
3 changed files with 1011 additions and 967 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
ChangeLog
View File

@ -1,3 +1,10 @@
2011-03-29 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
* doc/geany.txt, doc/geany.html:
Add #reading-styles-from-another-filetype subsection, based on
patch by Matthew Brush (thanks).
2011-03-28 Colomban Wendling <colomban(at)geany(dot)org>
* src/document.c, src/document.h, src/editor.c, src/keybindings.c:

1953
doc/geany.html
View File

File diff suppressed because it is too large Load Diff

18
doc/geany.txt
View File

@ -3727,6 +3727,24 @@ italic emphasis.
To define named styles, see the filetypes.common `[named_styles]
Section`_.
Reading styles from another filetype
************************************
You can automatically copy all of the styles from another filetype
definition file by using the following syntax for the ``[styling]``
group::
[styling=Foo]
Where Foo is a filetype name. The corresponding ``[styling]``
section from ``filetypes.foo`` will be read.
This is useful when the same lexer is being used for multiple
filetypes (e.g. C/C++/C#/Java/etc). For example, to make the C++
styling the same as the C styling, you would put the following in
``filetypes.cpp``::
[styling=C]
[keywords] Section
``````````````````