Something strange is going on while trying to run Julia script files:
1) the .jl extension is removed: so running an "x.jl" with `EX_00_CM=julia "%f"` in "filetypes.julia" results in: file x not found.
2) if the script file name is x.jl.jl and there is a file x.jl present in the directory, but not marked as executable then there is another error message: 'Permission denied' .
The filetypes.python file structure does not differ from filetypes.julia, but Python scripts run OK without being marked as executable and are found.
What could be the reason for this weird behavior and how to fix this issue, so that Julia scripts could be run using F5 in Geany?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3908
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3908(a)github.com>
Right now only the "document-save" is fired when performing "save as" which lacks the information about the original file name (which, for instance, is necessary for the LSP client where it needs to notify the server that the "old" document was closed and the document under the new name opened).
Right now the plugin at https://github.com/techee/geany-lsp has the code using this signal commented-out - I'll uncomment it once it's added to Geany (so renaming a file might cause problems synchronizing the document with the server with the current implementation).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3572
-- Commit Summary --
* Add "document-before-save-as" signal
-- File Changes --
M doc/pluginsignals.c (11)
M src/document.c (2)
M src/geanyobject.c (7)
M src/geanyobject.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/3572.patchhttps://github.com/geany/geany/pull/3572.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3572
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3572(a)github.com>
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
Make sure the gmo files are regenerated when the corresponding po files are updated, not to have stale translations after updating a po file.
This behavior most likely changed with the switch from GLib gettext infrastructure to to plain gettext one in 32977676a90244e0410524614757d2cf214bae43.
I had a hard time finding a rationale for the behavior of not automatically updating the gmo files when their source changed; all I could find is [this](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400453#24) which suggests it's intentional. Still, at least with our configuration of `PO_DEPENDS_ON_POT=no`, which means po files are not updated all the time, the point seems moot and does more harm than good.
Fix this by manually adding the correct dependency to the main target so the gmo files are updated automatically when the po changes. The only case where I can see it performing "useless" work is when calling update-po, which will effectively update all po files, and thus rebuild all gmo files. But that doesn't sound like any kind of problem, and rather expected.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3650
-- Commit Summary --
* Autotools: regenerate gmo files when po files are updated
-- File Changes --
A po/Rules-gmo (10)
-- Patch Links --
https://github.com/geany/geany/pull/3650.patchhttps://github.com/geany/geany/pull/3650.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3650
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3650(a)github.com>
The Re-load All feature is implemented with a check if the files are modified inside the memory buffer. The buttons on the info_bar are drawn vertically, as there can be as much as five options, depending on the scenario, see picture below. See also the discussion [here.](https://github.com/geany/geany/issues/2540)
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3722
-- Commit Summary --
* Draft implementation of reload-all. Messy GUI and RESPONSE_DOCUMENT_RELOAD_ALL not handled correctly.
* Created bool unmodified_files_present to make gui button optional.
* Merge branch 'geany:master' into re-load-all
* Replaced fixed size number of button arguments with variable sized array of buttons (and responses) in document_show_message().
* Re-load All feature works functionally (but GUI needs re-work): detection if buffers are modified is built-in and user is offered a choice to reload all (and drop buffer modifications), reload only unmodified ones, or only the document in focus.
* Connected File->Re-load button and updated description.
* Switched to vertical buttons inside info_bar to avoid crowded Gtk-boxes.
-- File Changes --
M COMMITTERS (1)
M THANKS (2)
M data/geany.glade (11)
M src/callbacks.c (63)
M src/callbacks.h (2)
M src/dialogs.c (2)
M src/document.c (674)
M src/document.h (35)
M src/documentprivate.h (9)
M src/editor.c (4)
M src/keybindings.c (5)
M src/libmain.c (4)
-- Patch Links --
https://github.com/geany/geany/pull/3722.patchhttps://github.com/geany/geany/pull/3722.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3722
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3722(a)github.com>
It is possible to add it?
--
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/1854
Previously the file path could be pasted in a file dialog.
With the new nice-looking OSX file dialog in Geany 1.36, this feature is no longer there. Standard behavior in OSX is "Command-Shift G" to bring up the path dialog. It would be super great if this expected OSX behavior was implemented also in Geany
--
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-osx/issues/14
Hello!
I'm a Twitch streamer and quite often on my streams I need to zoom in the text to a really large size for a better dramatic effect. But unfortunately Scintilla imposes a very strict limitation on zoom factor (from -10 to 20): https://www.scintilla.org/ScintillaDoc.html#SCI_ZOOMIN
And I don't really know why! If I remove the `SCI_ZOOMIN` limitation condition completely in [Scintilla itself](https://github.com/geany/geany/blob/77630564ad5446df89e9973f74bd378… it works just fine and does not degrade the performance or/and the stability of Geany.
Would it be a good idea to remove the `SCI_ZOOMIN` limit completely (or at least dramatically increase it) and put that change into the `scintilla_changes.patch`? If yes, I could make a PR for that myself.
--
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/2750