Support here is *optional*, as in it does *not* require even the GIR M4 macros to be available -- but then the generated build system can't generate GIR. This avoids a hard dependency on GIR for the cost of a configure-time conditional with basic fallback definitions.
As stated in the first commit, it's mostly ripped off Peasy, maybe there are additional change required, but it seems to mostly work. However, I see a lot of scary warnings like these:
```
…/doc/geany-sciwrappers-gtkdoc-tmp.h:25: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_set_text (ScintillaObject *sci, const gchar *text);' at '*'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:25: syntax error, unexpected ')', expecting ',' or ';' in 'void scintilla_object__GI__MARK_set_text (ScintillaObject *sci, const gchar *text);' at ')'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:43: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_start_undo_action (ScintillaObject *sci);' at '*'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:64: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_end_undo_action (ScintillaObject *sci);' at '*'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:84: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_set_marker_at_line (ScintillaObject *sci, gint line_number, gint marker);' at '*'
```
@codebrainz @kugel-
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1112
-- Commit Summary --
* Add support for building GIR
* Force enabling GObject-Introspection for distcheck
-- File Changes --
M Makefile.am (2)
M configure.ac (12)
M doc/Makefile.am (69)
-- Patch Links --
https://github.com/geany/geany/pull/1112.patchhttps://github.com/geany/geany/pull/1112.diff
---
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/pull/1112
This is probably a bug in scintilla / ctags / whatever. Please forward appropriately.
Save the following as a normal file:
```
Hello [lovely
world](http://example.com/with/very/long/URL/that/cant/be/wrapped/reasonabl…
Asdf
```
Note that the line breaks are important. `Asdf` should be on the forth line.
Open this file in geany, move the cursor to the end of the line (right after the closing parenthesis that closes the link) and press 'return'. ('Enter' has the same effect.)
Expected behavior: a new line appears. Duh. (Nothing else should change.)
Actual behavior: a new line appears … and everything afterwards is also part of that link. At least that's what the syntax highlighting suddenly indicates. The whole rest of the file is affected; it doesn't reset at paragraph boundaries or any other sane "well no kind of formatting can cross this point anyway" border.
Manual workaround: find the "link" that caused all this, insert a character before it and delete it again. This seems to cause re-parsing of the link, and this time it works.
```
$ geany --version
geany 1.27 (git >= d1fcd9f) (kompiliert am 2016-01-03 mit GTK 2.24.29, GLib 2.46.2)
```
---
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/971
1. Open a file
2. Scroll to the end (common if working on, say, a book)
3. Close the file
4. Open the file again, to continue working on your book
Notice the cursor position is 1:1, instead of where you left off.
---
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/1117
I don't recall specifically enabling the XML Snippets plugin, but it appears to conflict with the internal XML tag closing mechanism in some way. I recently ran into an issue editing an XSL stylesheet where typing the closing bracket (`>`) would crash Geany. I disabled the XML Snippets plugin, and Geany didn't crash when typing the closing bracket, while allowing Geany to create the closing tag using the built-in function.
What does XML Snippets do that the `XML/HTML tag auto-closing` built-in feature doesn't? Should XML Snippets be removed?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/318
When I select one character, the <b>sel</b>ection count and the <b>col</b>umn number are correct, but when I extend the selection by one character, the <b>sel</b>ection increases by 4 not 1, although the <b>col</b>umn number only increases by the expected value of 1.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/745
Hi,
Scintilla uses LexLisp.cxx for Lisp and Scheme, but Geany uses Lisp only. I use GIMP and Script-Fu and I would like to see the syntax :)
If it possible, [geany-master-scheme.zip](http://www118.zippyshare.com/v/VoUXDqTp/file.html) (new/modif. files):
```
data/filedefs/filetypes.scheme
data/filetype_extensions.conf
data/Makefile.am
src/filetypes.c
src/filetypes.h
src/highlighting.c
src/highlightingmappings.h
```
Regards,
---
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/982
At the moment if symbols of the same name are defined in identically named files, it's hard to distinguish which file is which because there's no path in the popup.
The popup should show part of the path until a directory where the paths differ so it's possible to distinguish the different files. At the same time there should probably be some top limit for the length of the paths as they can make the popup too wide.
---
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/1069
The auto-close brackets does work only for the first outer brackets (parenthesis,curly braces,square brackets), if one wants to have further brackets inside they are not auto-closed. It would be great if auto-closing where possible for any number of times and depth inside other same-brackets.
The following will happen if want 2 times brackets inside each other:
[[]
(()
{{}
it would be great if it could happen like this:
[[]]
(())
{{}}
---
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/1041