I get `Error opening file /<path>/index.html: No such file or directory`
<path> is the path to the directory that contains the markdown file I'm trying to load.
If I open the plugin preferences and change the template to "template.html" I get a different error:
```[general] template=/home/ventsyvelev/.config/geany/plugins/markdown/markdown.conf [view] position=0 font_name=Serif code_font_name=Mono font_point_size=12 code_font_point_size=12 bg_color=#ffffff fg_color=#000000```
Geany 1.38
Ubuntu 22
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1247
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1247(a)github.com>
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
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
When "load files from the last session" is enabled, regardless of whether a project is loaded, the previously active document is reactivated when Geany is closed and restarted with a document at the command line or from a file manager. The expected behavior is to activate the newly opened document for editing.
This occurs with the default config and no plugins loaded. Does not occur in an old build from 2021-12-30. Does occur in builds dated after 2022-05-01. I did not build Geany between those dates, so don't know when the new behavior was introduced. I do not see it in the manual, nor do I see any option to revert to the old behavior.
To reproduce:
1. Open Geany.
2. Open a several of documents.
3. Close Geany.
4. Open Geany with a file from a file manager or command line.
5. Geany will open and activate the last active document. Expected behavior is to activate the newly opened document for editing.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3210
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3210(a)github.com>
PR #3125 (commit 22aac443) broke that accidentally by moving the
"switch to last used tab" to a idle callback (g_idle_add()). This
runs after opening files from the command line.
Now, the same callback is moved to libmain.c and is only registered
when there are no files from the command line.
Additionally, projects gains a private copy of the current_page loaded
from the keyfile.
Fixes #3210
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3267
-- Commit Summary --
* Restore startup behavior to focus files from the command line after session files
-- File Changes --
M src/keyfile.c (40)
M src/keyfile.h (4)
M src/libmain.c (52)
M src/project.c (1)
M src/projectprivate.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/3267.patchhttps://github.com/geany/geany/pull/3267.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3267
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3267(a)github.com>
I use msys2 to compile geany-plugin-1.38 source code ;when I excute "make j2" in msys2 ;it shows:
"collect2.exe:error :ld return 1 exit status " "make[2]: *** [makefile:762:viw.exe] Error 1";
I want to know how to solve it
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1255
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1255(a)github.com>