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
Fixes #1069 by implementing the suggestions there.
See commit messages for details. tl;dr: the goto-symbols popup will show more of the paths, but as little as possible. The common prefix is stripped and the longest common sub-path is ellipsized.
Example: Assume the popup would show utils.h twice (/home/kugel/geany.git/src/utils.h and /home/kugel/geany.git/build/dest/include/geany/utils.h.
The popup would show:
src/utils.h
build/dest/include/geany/utils.h
Additionally, as per @elextr suggestion and for a frequent use-case of mine, the ellipsis is introduced for long common substrings, which I often have due to having the same code base checked out multiple times (my workflow at work requires this).
So, /home/kugel/checkout_a/path/to/project/src/main.c and /home/kugel/checkout_b/path/to/project/src/main.c shows as:
checkout_a/.../main.c
checkout_b/.../main.c
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1445
-- Commit Summary --
* utils: add functions to process file name list
* symbols: provide a bit more path information in the goto-symbol popup.
* gtkdoc: add support for array annotions
* api: export new utils_strv_shorten_file_list() function
-- File Changes --
M doc/Doxyfile.in (2)
M scripts/gen-api-gtkdoc.py (7)
M src/plugindata.h (2)
M src/symbols.c (13)
M src/utils.c (193)
M src/utils.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/1445.patchhttps://github.com/geany/geany/pull/1445.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/1445
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
Hi,
is it possible to start creating a new file in an existing instance from shell? I'd like to use a keyboard shortcut to start a new file, but `geany` with no arguments opens a new instance (not useful).
If it can't be done, how likely are you to implement it? Ideally, this would be a commandline parameter (something like the opposite of `-i`).
--
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/1512
Tested on Fedora 27 using stock Geany available from repo.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/645
-- Commit Summary --
* Ported 'Debugger' plugin to GTK+3.
-- File Changes --
M build/debugger.m4 (4)
M debugger/src/bptree.c (6)
M debugger/src/btnpanel.c (15)
M debugger/src/cell_renderers/cellrendererbreakicon.c (66)
M debugger/src/cell_renderers/cellrendererbreakicon.h (14)
M debugger/src/cell_renderers/cellrendererframeicon.c (57)
M debugger/src/cell_renderers/cellrendererframeicon.h (6)
M debugger/src/cell_renderers/cellrenderertoggle.c (9)
M debugger/src/dconfig.c (47)
M debugger/src/debug.c (43)
M debugger/src/dpaned.c (5)
M debugger/src/gui.c (2)
M debugger/src/plugin.c (2)
M debugger/src/stree.c (2)
M debugger/src/tpage.c (62)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/645.patchhttps://github.com/geany/geany-plugins/pull/645.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-plugins/pull/645
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
On Debian 8 (amd64)
libgtk-2.24.25-3
libglib-2.42.1-1
I have a .c file opened in geany. I click on the `debug` tab in the lower left corner. Over on the right, I click the arrow to run. Geany crashes.
I set a breakpoint in the file. Do everything mentioned above. Geany crashes.
Both geany and the plugin were installed from the Debian 8 repo.
Should I build geany and the plugin from source? Install from backports? Any suggestions how I might get the debugger working?
--
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/491
In scope debugger, the debug | debug console window is white on black which is very difficult to read. I can use Edit | Prefs to change the background colour to white but the "foreground colour" does not affect the text colour. This remains light grey and very poor contrast against white bg.
The only other colour selector I can find is the long line marker ( vertical line ).
Is there an option to set the debug console text colour, or a hack to alter it ?
If not could someone with a little familiarity with the code point to where I can modify this in the source.
thx
--
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/671