If you load geany scope, load a simple "Hello world" software written in C compiled with -g, and you start the execution with geany scope you obtain a blank window without text or buttons and geany freeze.. so geany scope is unusable...
geany scope 1.27 in Fedora 24 with italian language
reported in https://bugzilla.redhat.com/show_bug.cgi?id=1341107
---
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/433
Linux: Ubuntu trusty (3.13.0-68-generic / i686)
Geany 1.25 (built on Jul 13 2015 with GTK 2.24.23, GLib 2.40.2)
Installing from Ubuntu repositories (geany v1.23) caused the same problem, so I tried installing from ppa:geany-dev/ppa. Problem remains. All packages starting with "geany" installed, except for geany-plugin-markdown, geany-plugin-scope.
I have tried debugging a python script, (setting debug target to .py file and .pyc) - both gave me "Error laoding file" when I press the Start button
I then tried debugging a bash script (.sh) - same problem.
Then I downloaded a sample .c source file, compiled it and tried to debug it - same problem.
Starting geany from shell in order to try to get some output or stack trace did not help much. All I got was the following: (output on console immediately after pressing "OK" on "Error loading file" dialog)
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:30320): GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed
Is there any way I can get a decent stack trace of what caused the "Error loading file"?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/309
when compiling......process failed(the system cannot find the file specified)
why??????????
Windows 8.1 64bit
Geany 1.26
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/766
Hi :smiley:
I've added a keybinding for switching focus to the split window editor (in case it's enabled). This solves #631
I've set F3 as keybinding by default because:
1. Follows the idea of the other "Focus Keybindings" family: F2 -> Switch to Editor, F4 -> Terminal, F7 -> Search bar
2. Doesn't collides with any other default keybindings and has very few possibilities of collision with user-defined keybindings.
3. Even in the case it collides with other user-defined keybinding, it's not a big deal since it just grab the focus on split window only in the case it's being displayed. If user doesn't like it, he/she can always change this.
4. It's a plugin shipped along with geany.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/721
-- Commit Summary --
* Keybinding for switching focus to splitwindow. Fix #631
-- File Changes --
M plugins/splitwindow.c (16)
-- Patch Links --
https://github.com/geany/geany/pull/721.patchhttps://github.com/geany/geany/pull/721.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/721
This is an improved version of PR #637.
No more "--" - not needed.
No guard for is_osx_bundle() under Windows - does not belong here.
Split into proper sequential commits.
Fixed the encoding of options and doc_name.
Fixed the OSX bundle executable name.
Created a function to return the reproduced arguments instead of exposing global variables.
Re-tested under Windows and Linux.
There is only one problem left. As described in PR #637, under Windows, mscvrt often breaks unquoted locale strings on 2+ pieces, considering some characters "spaces". So spawn should quote any argv elements containing locale. But that must obviously be a separate PR.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/653
-- Commit Summary --
* Add reverse option parser to main
* Add support for geany executable to utils_resource_dir()
* Improve New Window: pass the proper arguments and save configuration
-- File Changes --
M src/libmain.c (121)
M src/main.h (2)
M src/plugins.c (2)
M src/utils.c (111)
M src/utils.h (17)
-- Patch Links --
https://github.com/geany/geany/pull/653.patchhttps://github.com/geany/geany/pull/653.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/653
Hi all,
I created a share object (so) - libdsso
I am trying, successfully to debug it through gdb:
gcc -g testc -lds
However, when i am trying to debug through geany, i get an error immediately:
program existed with error 127
just to mention - everything else is working just fine (compiling with static library, makefiles etc)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/837
'Geany' no longer detects if there is an instance of itself already running, thus multiple instances are starting up, instead of files being opened in the current instance.
I doubt it is a "#ifdef HAVE_SOCKET" not being defined since the mutexs (called mutants in win32) are being created with the name 'Geany'.
I suspect it had to do with recent cleanups and changes in https://github.com/geany/geany/commits/c5b0fc459a1251c824a44edb5dfab4a8feb0…
![screenshot_of_mutants](https://cloud.githubusercontent.com/assets/2829875/9657992/dba0fd70-5213-11e5-9fcd-2c270304dfb7.png)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/641
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