Hello, when I try to open random txt file, Geany opens them as if they were blank. Otherwise, sometimes it won't open the file(s) at all.
Clear installation from the main website, no plugins installed, nothing configured in the program.
Geany 2.0, downloaded from the official website, Windows 10, no Geany plugins. Tried reinstalling, no good.
Is there anything related to opening such files in the "Status" tab or the statusbar at the bottom of the window?
Geany typically doesn't open files containing the NULL character.
Is there anything related to opening such files in the "Status" tab or the statusbar at the bottom of the window?
Geany typically doesn't open files containing the NULL character.
That's not the case here as when I manually load those same files in Geany, they are properly displayed. It is only when try to view them from the File Explorer. When the Geany is opened, if I go to File Explorer, right click and select Open in Geany, nothing happens. When Geany is closed, then it either opens the file(s) properly or just opens them blank, but with the dedicated tab with the filename.
When the Geany is opened, if I go to File Explorer, right click and select Open in Geany, nothing happens.
Running and not-running Geany are two different cases. When Geany is running, opening the file from explorer creates a second instance of Geany which sends the file being opened to the running Geany (which then opens it) over a network socket and quits. I can imagine some aggressive firewall settings to disable such communication. Under `Help->Debug messages` you should see errors related to IPC socket in this case.
When Geany is closed, then it either opens the file(s) properly or just opens them blank, but with the dedicated tab with the filename.
This is the real mystery and probably invalidates what I have written above as the possible cause. Do I understand it correctly that the real file name appears in the tab name? Is there anything interesting under `Help->Debug messages` or the Status tab?
This is the real mystery and probably invalidates what I have written above as the possible cause. Do I understand it correctly that the real file name appears in the tab name? Is there anything interesting under `Help->Debug messages` or the Status tab?
It seems it has to do something with the file path. So it is an ordinary txt file, which is located at: E:\apps\ABCDEF 21 Master NMT v20.0.00 Multilingual [AcbdCR]\ABCDEF 21 Master NMT v20.0.00 English ↔ Deutsch [AbcdCR]
When I try to open the file with the Geany closed, it opens file displaying nothing in it, as if it is empty, but displaying the file name in the tab. When is Geany opened, and I try to open that file within Windows Explorer, there is no reaction at all.
However I tried copying the txt file to another location, say to desktop folder. When Geany is opened, and when I try opening the file within explorer, again nothing happens, **but when the Geany is closed and I invoke the opening from the explorer, file is opening as it should**. The same goes if I copy that file one step upper in the directory hierarchy, that is, E:\apps\ABCDEF 21 Master NMT v20.0.00 Multilingual [AcbdCR]
So there is definitively some limitation regarding path length. No error or unusual messages in the Debug Messages. The txt file is ordinary file with a couple of lines, no special characters or anything peculiar, other text editors are opening it normally regardless of the path.
Also possibly the ↔ character if it's part of the file name - could be some problem with character encoding. @eht16 might know more if there are any known limitations in the Windows version.
There are definetely limitations, actually probably bugs regarding file name handling. See https://github.com/geany/geany/issues/3936 and find a list of related issues in https://github.com/geany/geany/issues/2748#issuecomment-776058604 and there are probably more reports.
Part of the problems might be solved by https://github.com/geany/geany/pull/2660, maybe also not.
In the end, either filename handling with GLib on Windows is complicated or the current code is just buggy because I never understood it well enough. Unfortunately, the result is that obviously there are quite some bugs regarding file handling.
I'm not going to work on this.
github-comments@lists.geany.org