MinusGix
MinusGix
It is a common mistake to write a textbox like `` where in fact, the author meant to write `` so as to have the value stored in the variable...
A macro like `widget` can only be used (properly) within a passage with a specific tag, that of `[widget]`, and so giving an warning if it is used outside of...
It would be good to have the ability to send asynchronous requests, and handle the result via a callback. Ex: Sending a command to a spawned LSP server shouldn't typically...
Currently `LapcePlugin` is defined as: ```rust #[allow(unused_variables)] pub trait LapcePlugin { fn handle_request(&mut self, id: u64, method: String, params: Value) {} fn handle_notification(&mut self, method: String, params: Value) {} }...
There's various pieces of the API that should probably be hidden or made non-constructable. Hiding functions would allow us to later replace or alter the code behind them without breaking...
Currently, one can respond to a request (received in `handle_request`) by using `object_to_stdout`, but that is a poor API. Here's my idea of the function definition for responding: ```rust ///...
A nice way, like #8, for sending requests is desirable. However, we run into the issue that the plugin author needs to handle any responses from the editor that they...
There should be a function to easily send a notification to the client from a plugin. This can currently be achieved via `object_to_stdout`, but in a somewhat unpleasant manner and...
Related: https://github.com/lapce/lapce/pull/579
The Floem (UI library) version of Lapce ~~will be~~ has been merged into the `master` branch ~~soon~~. Once that occurs, bringing it completely up to feature parity with the druid...