Repository navigation
Palette sections, a theme picker, load in lumen info - #9
Merged
Merged
Conversation
…oved to the registry
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The palette now groups its commands under Lumen and Plugins headings, so it's clear which commands a plugin added. While you type, the section with the best match comes first. The 24 Theme: entries are replaced by one Theme… entry that opens a picker. It previews each theme as you move through the list, Enter keeps the one you're on, and Esc puts the old theme back without touching config.toml.
lumen infogains a Load line after the CPU, e.g.2.31, 1.98, 1.75 (7% of 32 threads).Pomodoro, project-layout and build-status move out of the built-ins to sn/lumen-pomodoro, sn/lumen-project-layout and sn/lumen-build-status in the registry (lumenshell/plugins#1, along with a new sn/rss reader). The old names in config.toml map to the new ones, and their
[plugin.NAME]settings and plugin data folders move with them, so nobody loses their setup.Risk: renames people's existing plugin entries, settings tables and data folders the first time they're touched. All of this is covered by tests.