The Requirements section of the devhelp plugin page under http://plugins.geany.org lists the following items:
- GTK >= 2.16
- libwebkitgtk >= 1.1.18
- libdevhelp 1.0 >= 2.30.1 or libdevhelp 2.0 >= 2.32.0
Looking at the makefile I see this requirements:
```
[gtk+-2.0 >= ${GTK_VERSION}
webkit-1.0 >= ${WEBKIT_VERSION}
libwnck-1.0 >= ${LIBWNCK_VERSION}
gconf-2.0 >= ${GCONF_VERSION}
gthread-2.0
zlib])
```
On my Ubuntu machine only ```libwebkit``` and ```libwnck``` were missing. Not sure if the list on the plugin page should be extended.
--
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-plugins/issues/626
I’ve been using Geany with patches whereby [typeahead search](https://developer.gnome.org/gtk3/stable/GtkTreeView.html#gtk-tree-v… in the symbols list and in [TreeBrowser](http://plugins.geany.org/treebrowser.html) uses [`g_str_match_string`](https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-str-match-string) instead of simply matching by prefix.
Now, when I type “ba”, it finds not just `bar` but also `foo_bar` and `foo-bar`, etc. (not `FooBar` though).
It’s convenient.
The change itself is simple (all the heavy lifting is in GTK+/GLib), but I’m pretty sure this behavior cannot be made the default, as it might cause too many false positives, and would break habits.
What do you think of having such a feature as an option?
If suitable, what do you think its granularity should be? Should it be a checkbox for every tree view where it makes sense, like “Use fuzzy search in symbols list”, “Use fuzzy search in documents list” and so on?
(Also, I’m not sure it should be just [`g_str_match_string`](https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-str-match-string). Maybe typing “ba” should find `FooBar` as well. Maybe typing “fb” should find `foo_bar`, like in [Commander](http://plugins.geany.org/commander.html).)
--
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/1466
## Abstract
You can't replace the license templates such as "gpl" with your own ones.
## Steps to reproduce
1. `echo "test template" > ~/.config/geany/templates/test`
1. `sed -i 's/{gpl}/{test}/' ~/.config/geany/templates/fileheader`
1. (Re-)open Geany
1. File → New (with template) → main.c
## Expected behavior
```
/*
* ...
* test template
*/
```
## Actual behavior
```
/*
* ...
* {test}
*/
```
--
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/1391
#1017 continuation, new (last) attempt.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1752
-- Commit Summary --
* Add AutoIt syntax highlighting and Ctags parser for AutoIt
-- File Changes --
M ctags/Makefile.am (1)
M ctags/main/parsers.h (3)
A ctags/parsers/autoit.c (121)
M data/Makefile.am (3)
A data/filedefs/filetypes.autoit (72)
M data/filetype_extensions.conf (1)
M scintilla/Makefile.am (1)
A scintilla/lexers/LexAU3.cxx (910)
M scintilla/scintilla_changes.patch (2)
M scintilla/src/Catalogue.cxx (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (9)
M src/highlightingmappings.h (35)
M src/symbols.c (8)
M src/tagmanager/tm_parser.c (5)
M src/tagmanager/tm_parser.h (1)
M tests/ctags/Makefile.am (1)
A tests/ctags/simple.au3 (32)
A tests/ctags/simple.au3.tags (5)
-- Patch Links --
https://github.com/geany/geany/pull/1752.patchhttps://github.com/geany/geany/pull/1752.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/1752
Fix #864
Note that I didn't workout regex since it seems to break group number conventions.
Also for this to work we must reset LANG envvar (maybe provide an option?) since gcc translates words "error", "warning", "note".
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1649
-- Commit Summary --
* warning support
-- File Changes --
M data/filedefs/filetypes.common (1)
M src/build.c (14)
M src/build.h (2)
M src/editor.h (3)
M src/filetypes.c (3)
M src/filetypes.h (11)
M src/highlighting.c (7)
M src/msgwindow.c (48)
M src/msgwindow.h (6)
-- Patch Links --
https://github.com/geany/geany/pull/1649.patchhttps://github.com/geany/geany/pull/1649.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/1649
Hi.
OS: Windows 7 64bits
Geany version: 1.26
In "Edit>Preferences>Files>Default encoding" I selected IBM850 as default encoding in all options, new files and open files, but all files are opened with 1252 encoding. With new files there is no problem.
Thank you.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/900
If the long line marker is disabled in *Preferences* → *Editor* → *Display*, the keybinding for *Format* → *Join lines* doesn’t work.
Unlike *Reflow lines/block*, the *Join lines* operation does not need to know anything about long lines, so shouldn’t require the marker.
--
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/1591
Please consider adding an <b>Unflow paragraph</b> command - the opposite of
<b>Reflow Lines/Block</b> The use case for this is to make it easy to type in
<b>Geany</b> and then paste the results into the Gmail or Github editor
Incidentally, <b>Reflow Lines/Block</b> indicates that the conception of a
block of line is already endogenous to <b>Geany</b> and thus I believe that the
concept of extending the highlighting of lines to the line numbers columns
should be considered an extension of an existing capability
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/802
Hi,
I changed the shortcut of join lines to `Ctrl + J`, then tried to join lines.
Seems following behavior exists:
- It will join all following lines, till a line start with blank char (while space / new line).
- If the current line start with blank char, it won't join.
Is it possible to customize to following behavior:
- Only join current line and the next line, despite the content of this or next line.
This seems to be the behavior of vim with `Shift` + `J`.
--
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/2031
Is there a way to enclose selected text in HTML tags with a keyboard shortcut?
For example, for selected `text`, after using a shortcut it becomes `<(cursor)>text</(cursor)>`,
and then after typing `tag` and pressing space (or using any key moving the cursor or inserting whitespace) it becomes `<tag (cursor)>text</tag>`.
--
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/1863