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
Since distros are now not defining `python` and python 2 is dead, should be changed to `python3`, see also discussion on #2223
--
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/2615
This is the follow-up PR for #3488 and #3039 to seperate the code for generating the ctags format into a commonly used helper module and to use the ctags format also for the global PHP tags.
Works fine so far.
I noticed the return type (`typeref` in ctags speak) for symbols is not parsed correctly and so not displayed in the calltip.
This hasn't been a problem for Python as there is no return type information available. But for PHP it is.
Maybe this is related to #3049? @techee
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3512
-- Commit Summary --
* Add helper script for generating ctags files in Python
* Generate PHP global tags in ctags format
-- File Changes --
M data/tags/std.php.tags (18624)
M scripts/create_php_tags.py (39)
M scripts/create_py_tags.py (31)
A scripts/create_tags_helper.py (70)
-- Patch Links --
https://github.com/geany/geany/pull/3512.patchhttps://github.com/geany/geany/pull/3512.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3512
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3512(a)github.com>
Created by "scripts/update-nsis-functions.sh".
Changed keywords:
```diff
Changed functions:
+!assert
+!uninstfinalize
+getknownfolderpath
+getregview
+getshellvarcontext
+getwinver
+ifaltregview
+ifrtllanguage
+ifshellvarcontextall
+manifestappendcustomstring
+manifestlongpathaware
+readmemory
+sectioninsttype
Changed Variables:
+$commondesktop
+$commonlocalappdata
+$commonprogramdata
+$commonsmprograms
+$commonstartmenu
+$commontemplates
+$userappdata
+$userdesktop
+$userlocalappdata
+$usersmprograms
+$userstartmenu
+$usertemplates
```
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3487
-- Commit Summary --
* Update NSIS filetype keywords
-- File Changes --
M data/filedefs/filetypes.nsis (4)
-- Patch Links --
https://github.com/geany/geany/pull/3487.patchhttps://github.com/geany/geany/pull/3487.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3487
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3487(a)github.com>
`scripts/changelist.pl`: process ChangeLog which we do not use anymore
`scripts/cross-build-mingw.sh`: old cross build script, replaced by #3315
`scripts/rstrip-whitespace.py`: probably unused (as assumed in #2615)
There are more candidates:
`scripts/fix-alignment.pl`
`scripts/fix-cxx-comments.pl`
`scripts/warning-summary.pl`
I'm not sure if any of those are still used by anyone? @ntrel @b4n @elextr
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3486
-- Commit Summary --
* Remove obsolete helper scripts
-- File Changes --
D scripts/changelist.pl (135)
D scripts/cross-build-mingw.sh (98)
D scripts/rstrip-whitespace.py (23)
-- Patch Links --
https://github.com/geany/geany/pull/3486.patchhttps://github.com/geany/geany/pull/3486.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3486
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3486(a)github.com>
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
How incomprehensible this is! Blue Chinese can be displayed normally, while red cannot!
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1262
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1262(a)github.com>
Geany version 1.33 (raspberry pi) not reloading the modified include file.
Scenario.
Project is composed of multiple project specific include and source cpp file.
One the supporting cpp file and corresponding include file is modified to add new method.
All the changes is saved.
recompile the project and it come back with an error unknown method. The unknown method is the newly added method.
Current solution.
The force the geany to reload the h file. I have to comment out the include section that refer to this modified h file.
Predictably the compiler produce an unknown method/variable.
Uncomment the include section where the h file is defined.
Recompile the project and the problem disappear.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3533
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3533(a)github.com>