I tried to code a plugin for copilot but soon realized that your api doesn't allow low level control of scintilla or I'm too noob to realize how. Copilot only needs to grab context from current cursor position (say 200 chars before and after), then it will suggest autocompletion options. Btw, Copilot is not the only tool for the task, I plan to add and OpenAI backend that can be gracefully replaced by LocalAI for 100% private and off-line coding (so no IP issues). Devs can choose to train/finetune their own LLM if they wish, plug it into LocalAI and let the geany plugin take care of the rest.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3543
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3543(a)github.com>
It would be so perfect to have those elements in the Customize Toolbar, so one could place them in the toolbar for a fast access:
- Show Line Endings
- Show White Space
- Line Wrapping
- Show Line numbers
- Hide/show menu bar (or even more perfect: menu-symbol, like in Firefox)
Or, is there a tutorial how to add elements in the Customize Toolbar?
By the way, the White Spaces are too small and nearly invisible.
--
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/2690
I was working on a C program in linux, and realized C++ would be a better fit. So I copied the program and gave it the .cpp extension. then I spent a bunch of time figuring out all the weird errors i was getting, before realizing the file retained the build commands from gcc.
The program has the same file name, only the extension had changed. new files with different filenames did not have this issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3525
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3525(a)github.com>
This patch adds a simple API allowing LSP plugins to take control of certain Geany built-in features and disabling their implementation in Geany. Currently, autocompletion, calltips, and going to definition/declaration is supported.
Plugins should define the Lsp struct, fill the pointers to the functions implementing the features they override, and register themselves using the lsp_register() call. Similarly, they should unregister themselves using lsp_unregister() when they don't want to provide the Lsp features any more, or, latest, when the plugin gets unloaded.
Each of the currently supported features is implemented using two functions - one checking whether Lsp plugin will override Geany's behavior of this feature, and the other function implementing the feature. For instance for autocompletion:
- autocomplete_available(doc) should return TRUE if the plugin performs autocompletion for the doc's filetype. This function is used to deactivate Geany's autocompletion when the Lsp plugin supports it.
- autocomplete_perform(doc) calls the corresponding interface of the LSP server (which responds asynchronously so when autocomplete_perform() is executed, the results won't be available yet)
The Lsp struct is padded with an array large enough to allow additions of many more functions to the struct and allowing binary compatibility with older LSP plugin versions not implementing all the functions. It's just mandatory that all plugins zero-initialize the allocated Lsp struct (either by creating it on the heap or by allocating it using g_new0() or similar function). NULL pointers in this struct are handled gracefully.
The current implementation supports only a single LSP plugin. However, if in the future arises the need for more LSP plugins running in parallel (e.g. a specialized LSP plugin for certain language together with the current "generic" LSP plugin), the implementation could be extended to support a list of Lsp structs and trying to call the functions defined by them one by one. The current interface should already be sufficient to support such an implementation.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3571
-- Commit Summary --
* Add API for LSP plugins
-- File Changes --
M meson.build (3)
M src/Makefile.am (2)
M src/editor.c (32)
M src/keybindings.c (11)
A src/lsp.c (107)
A src/lsp.h (59)
M src/symbols.c (9)
-- Patch Links --
https://github.com/geany/geany/pull/3571.patchhttps://github.com/geany/geany/pull/3571.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3571
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3571(a)github.com>
For some reason I don't yet know, Travis fails fairly randomly building GP: I seen problems with `dh-marshal` (possibly due to out-of-tree build? but why is it random?) and now with WebHelper's enums (there doesn't seem to be an error but the enum types are missing (although they are present in Git).
--
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-plugins/issues/650
I use geany with webhelper on debian 8.3 x 32.
On my previous PC (also with debian 8) I had the same problem but it disappeared after update of debian, geany and plugins.
Now I have new laptop with up-to-date debian and with the same problem. I have geany ver.1.26 and webhelper ver. 1.26+dfsg-1.
No difference which site or local html file I use, webhelper itself works great. But when I press web inspector button or choose 'inspect element' from right-click menu, geany immediately crashes.
If I start geany from terminal. after the crash I see:
> a@b:~$ geany
Segmentation fault
a@b:~$
Geany is the best lightweight IDE ever and I hope You'll help me to solve the problem.
TY in advance!
---
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-plugins/issues/412
After starting geany 1.37.1 Debian GNU/Linux 10 (buster) with a markdown-file that was opened already yesterday, the preview is not working (see below) until the moment I edit the file again. Phew, quite difficult to explain exactly, sorry.
The shown 'error' in the preview is: _The current document does not have a Markdown filetype_
Not a big issue for me but I still wanted to post 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-plugins/issues/1062