Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Documentation] Please specify which programming languages are permissible for geany on https://www.geany.org/support/plugins/ #45

Closed
rubyFeedback opened this issue Mar 24, 2022 · 3 comments · Fixed by #46

Comments

@rubyFeedback
Copy link

Please specify which programming languages are permissible for geany on https://www.geany.org/support/plugins/.

Currently the website there does not mention this. I assume C is one permissive language here, but what about
ruby or python or lua? It would be kind of neat to write add-ons in such languages; I am quite ok with ruby and I
could re-use a LOT of code there. Python users probably feel the same, so specifying this on the homepage
would be useful, I think.

@elextr
Copy link
Member

elextr commented Mar 25, 2022

Geany itself does not constrain languages used for plugins, any language that can present a C call compatible interface and which can call C can be used. For example I once used Cython successfully (a long time ago, no guarantees it will still work, but no theoretical reasons why not).

For languages that are interpreted (eg Python or Ruby) there is a third party plugin that supports plugins in those languages, see https://github.com/kugel-/peasy.

@elextr
Copy link
Member

elextr commented Mar 25, 2022

There is also the Geanylua plugin in the Geany-plugins collection that supports writing sub-plugins in Lua.

@eht16 eht16 transferred this issue from geany/geany Jan 1, 2023
eht16 added a commit to eht16/www.geany.org that referenced this issue Jan 1, 2023
@eht16
Copy link
Member

eht16 commented Jan 1, 2023

Before the first anniversary of this issue, here we go: #46.

eht16 added a commit to eht16/www.geany.org that referenced this issue Jan 1, 2023
@dmaphy dmaphy closed this as completed in #46 Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants