Closed #1734 via #2850.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1734#event-5390308600
> tag_parser=Meson
No such thing, you can probably just leave `tag_parser` out.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1734#issuecomment-869100826
I don't know if this is really the "right" way, but it's working for now.
After you create the file below, edit `filetype_extensions.conf` and add
`Meson=*.build`
## filetypes.Meson.conf
```
[styling=Python]
[keywords]
primary=if else elif endif foreach endforeach true false and not or in cont
Mapping extensions and creating custom filetypes are both covered in the Geany
manual.
It would be better to create a custom filetype so that the reserved words can
be changed to match meson, but personally I don't bother, meson "just works"
and I don't spend much time staring at its files.
--
Here is a typical meson.build file, from the project
gnome-builder:
project('gnome-builder', 'c',
license: 'GPL3+',
version: '3.26.4',
meson_version: '>= 0.40.1',
default_options: [
'c_std=gnu11',
'cpp_std=c++11',
Somebody could make a custom filetype using Python or maybe cmake as the base
type.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1734#issuecomment-356531002
Files are always called "meson.build"
Here is an example: https://git.gnome.org/browse/glib/plain/meson.build
Here is a configuration for the syntax highlighting library meson uses for
their documentation, which might help:
https://github.com/mesonbuild/meson/blob/master/docs/theme/extra/prism_
