Closed thacuber2a03 closed 6 months ago
We could put them under a spoiler too.
why a spoiler? /srs I don't think language plugins have anything to do with movies /j
Mostly to keep the page a bit tidier.
1) how can you spoil a table 2) is the spoiled table going to be inlined with the other plugins? because that would look kind of dumb
Test:
Plugin | Description |
---|---|
align_carets |
Align multiple carets and selections (clip) |
autoinsert |
Automatically inserts closing brackets and quotes. Also allows selected text to be wrapped with brackets or quotes. |
autosave |
Automatically saves files when they are changed |
autosaveonfocuslost |
Automatically saves files that were changed when the main window loses focus by switching to another application |
autowrap |
Automatically hardwraps lines when typing |
bigclock |
Shows the current time and date in a view with large text (screenshot) |
black * |
Integrates the black Python formatter with lite |
bracketmatch |
Underlines matching pair for bracket under the caret (screenshot) |
build * |
Provides a build system, messages window, and easily clickable errors. Supports an internal build system, and make . (screenshot) |
centerdoc |
Centers document's content on the screen and adds zen mode support (screenshot) |
colorpicker |
Color picker dialog that supports html and rgb notations. |
colorpreview |
Underlays color values (eg. #ff00ff or rgb(255, 0, 255) ) with their resultant color. (screenshot) |
...
ohhhhh ok I didn't get it lol
but I can see you guys are updating the README.md automatically, how are you going to check for language plugins, just check if the plugin starts with language_
or do something more reliable?
We could for example add a language
tag for them, like in this example https://github.com/lite-xl/lite-xl-plugin-manager/blob/eaf74ed6bcb9ea1236e15fe8124db5081059ed8b/SPEC.md?plain=1#L177
I would like them to be in a folder, a meta-plugin or plugin-pack (however you want to call it) The spoiler works for the webpage but when I am working on plugins I have to scroll through the bunch over and over again. Sure I can delete them, but they reapear whenever I git clone ...
or git checkout
.
We can definitely add them to a meta-plugin, and will probably do (like we'll probably also have an addons
meta-plugin).
I don't think we'll move them to a different directory tho, as that would break the setup for people that cloned the repo and symlinked the plugins.
wait, so does the "addons" metaplugin mean that lite-xl addons will be not there?
No no, but it means we'll use lpm to build it probably.
in the log, the languages also spam a lot makeing us scroll through them all to see the error message of a plugin that was supposed to be loaded before them
About that, we should probably auto-scroll to the error if the LogView opened automatically because of startup errors.
that also brings up another point. While reading the log, if there are new messages, the log is scrolled back to the top (if I'm not mistaken)
Yep, an annoying quirk. Would you mind opening an issue about it, so we don't forget to fix that?
I've seen it being talked in the Discord server but never seen it being tried the language plugins take a big chunk of the main list and it's hard to see the other plugins (I know you could just do a find in your browser but still) maybe you could do something like
Rendered (don't click the links, they're invalid):
Syntax highlighters