Currently, Geany plugins can only be written in C, Python, and Lua.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3696
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3696(a)github.com>
I should also add that it'd be quite easy to allow *opening* files with embedded NULs, I actually think it's just a matter of removing the check. However, it's likely a *lot* of features won't work right with the NULs, truncating some parts (and then, as @eht16 said it's totally fixable, but a lot of work and carefulness).
I think we discussed this in the past, and I myself wouldn't be against allowing to open those files read-only if it's something users want. However, I think others in the discussions were afraid people would still untick the read-only flag and start seeing bugs everywhere and complain, and that's probably a valid concern. We could possibly see what others would think could go wrong if we allowed opening read-only *and prevented those files from being made writable*, which would be a tad more work but probably fairly easy.
Then again, how useful would be opening those if you can't modify them? I don't know.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687#discussioncomment-7611291
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/comments/7611291(a)github.com>
Let the users choose to use the syntax highlighting engine they prefer in `Preferences`. Scintilla is still the default syntax highlighting engine. The advantage of GtkSourceView is it's much easier to add support for new languages compared to Scintilla.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3695
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3695(a)github.com>
One more addition: Geany could be changed to be able to handle any files (including NULL bytes, without a recognised encoding) but it would require a lot of efforts and it needs at someone who is willing and able to do this and also resources for for reviewing and testing.
As said earlier, it is designed as *text* editor and it does this well.
After all, Geany is not Notepad++.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687#discussioncomment-7606163
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/comments/7606163(a)github.com>
With this, you should be able to build *src/* and *plugins/* warning-free with `CFLAGS="-Wall -Wextra -g -Og -Wno-unused-parameter -Wunreachable-code -Wformat=2 -Wundef -Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Werror-implicit-function-declaration"` (or just `-Wall -Wextra -g -Og -Wno-unused-parameter -Wwrite-strings` to start with) but for some Lexilla prototype and one deprecated Lexilla call.
To review, go per-commit as it should be fairly trivial that way. Also, everything but maybe 12b30c5950eeccad2fed885745ff6cd0888d1d3a should not be controversial I think -- but please, raise any concern!
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3665
-- Commit Summary --
* Fix harmless GCC warning
* Fix fairly nasty implicit integer conversion
* "Fix" passing const arguments to spawn functions
* Add casts for irrelevant -Wwrite-strings warnings
* Remove invalid placeholder code
* Use g_*list_free_full() instead of g_*list_foreach()
* Avoid an easy-to-fix function cast
* Silence warnings on appropriate GSourceFunc casts
* Fix variable shadowing
* Only pass literals as format strings for e.g. printf-style functions
* Do not use GtkResponseType as response ID type
* Silence some -Wcast-function-type warnings
-- File Changes --
M plugins/filebrowser.c (12)
M plugins/splitwindow.c (2)
M src/build.c (40)
M src/dialogs.c (5)
M src/document.c (27)
M src/editor.c (2)
M src/filetypes.c (3)
M src/libmain.c (16)
M src/notebook.c (14)
M src/plugins.c (14)
M src/printing.c (4)
M src/search.c (10)
M src/spawn.c (10)
M src/symbols.c (2)
M src/tagmanager/tm_ctags.c (2)
M src/tagmanager/tm_workspace.c (7)
M src/toolbar.c (5)
M src/ui_utils.c (35)
M src/utils.h (4)
M src/vte.c (10)
-- Patch Links --
https://github.com/geany/geany/pull/3665.patchhttps://github.com/geany/geany/pull/3665.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3665
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3665(a)github.com>
When using the Save As dialog and after browsing to the save location, keyboard input defaults to the search feature despite the Filename text input being highlighted blue. This is non-intuitive and inconsistent with other software.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3691
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3691(a)github.com>
When Geany loads, or when I adjust the sidebar width to the left too far, it goes off screen. It should latch to the edge of screen and have a minimum width preventing it from being resized too small.
github.com>
I suspect that project organizer plugin parses some files twice, when opening a project with "Index all project files" set o Yes or Auto.
The reason for this is that the plugin parses all files but then Geany itself parses all opened files (or maybe the other way around?). So if you have a project that has many of its files already opened, it might make the opening of project needlessly slower. I believe that the plugin might safely skip files that are opened in current session (assuming it can get this information)
@techee: If you have no time to look into this, I might try to submit a PR myself. I'd just like to confirm first that this is not intentional and that there is no obvious blocker that would make this impossible.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1289
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1289(a)github.com>
Crude but working solution to #1289.
Disclaimer: I'm not really a C person, so any suggestion on how to improve the code quality are most welcome.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1290
-- Commit Summary --
* avoid parsing opened files when loading project #1289
-- File Changes --
M projectorganizer/src/prjorg-project.c (67)
M projectorganizer/src/prjorg-project.h (2)
M projectorganizer/src/prjorg-sidebar.c (10)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1290.patchhttps://github.com/geany/geany-plugins/pull/1290.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1290
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1290(a)github.com>