I'm using Geany 1.30.1 on Windows 7.
After happily editing a file over some time, suddenly Geany refuses to save it with this error message:
I know that Windows sometimes grabs a lock on a file when I'm just looking at it with another tool, but I am pretty sure that the only way I'm operating on this file since the last bootup of my machine, is by editing it in Geany. Still, for the safe side, I run the [Handle](https://technet.microsoft.com/en-us/sysinternals/bb896653) utility to see whether someone has a handle to either the file or the directory where the file is in - nothing. I also used Geany's "File/Properties" to check, whether maybe the file secretly became readonly; this is also not the case. Finally I turned on the gio_unsafe_save_backup and tried again, but same result. Note that it is a local file, so there can't be network issues involved either.
Then I tried "save as" with "rename", to store it under a new name in the same directory. This was refused with the same error message. I could see that the file got renamed, but still had the old content. This is weird: If the cause would be a directory lock, the rename should ALSO have failed.
Needless to say that it is not a disk space problem either.
I resolved the problem temporarily by using the following strategy:
1. Using "Save as" to save it to a completely different directory.
2. Copying the file back (on the command line)
3. Closing the Buffer in Geany
4. Reopening it
I then checked with my remaining open files in Geany. Modifying the buffer and saving, caused the same error with two of the files, while it worked fine with two others. One of the two where the error occured too, belonged to a different directory, while all the others - including those which could be saved - belonged to the same directory as the file where the problem occured initially.
I don't see yet in what respect the two files which did not have the problem, differed significantly from the two files where the problem occured.
Closing Geany, starting it, and I can continue editing like normal, but my feeling is that it will be only a question of time until the problem occurs again. Is there anything I can do to help the Geany developers to nail down the cause of this strange problem?
--
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/1500
Given that Markdown has lots of undefined semantics, this may very well be a valid interpretation of certain broken Markdown documents. But I guess most would agree that the priority should be the other way around.
Example: (Save as `something.md` and open with Geany)
_This is "underlined"
```
should_be code
```
This sentence is considered code, because the
"matching" underscores had priority (?)
Note that the "stray underline" can also occur in HTML inline-comments, where they don't stand for underlining anyway.
<!-- Like this one. I know very well that this won't usually appear. -->
--
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/1439
1- Enable Tools -> Split Window -> Side by side
2- Open one file in both left and right sides
3- Change cursor position in one side so that cursor and scroll position in 2 sides are different
4- Type something in the right side, then press Control + Z
5- The cursor and scroll position in left side changes (unexpectedly) to the position of right side, so that you loose where you were (writing something in a different part of the same file)
---
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/988
I'm using Geany 1.33 on Windows 10 and invoke it from command line for an empty (zero byte) file. Though in the Geany preferences on the Files page the "Default end of line characters" combobox is set to "Windows (CRLF)", pressing enter and saving in the empty file will write Unix (LF) line endings.
--
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/1950
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
This is nice for when the application / the system is crashing, or there is a power outage.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/905
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