Skip to content

User plugins #287

Description

@toyboot4e

Background

Details

We should at least document workarounds for the following cases.

[WIP] Case 1. Add your own plugin

Step 1. Override the nixpkgs for plover-flake to match the package versions:

inputs.plover-flake.inputs.nixpkgs.follows = “nixpkgs”;

Step 2. Use plover-flake.packages.plover to build your own plugin.

TODO: write a working example here

For now, please refer to this comment as an example.

Case 2. Overwrite a broken package that comes with plover-full

This case can be resolved in the same way as Case 1.

broken packages are marked like this:

meta.broken = true;

[WIP] Case 3. Overwrite a non-broken package that comes with plover-full

Currently, plover-full is not flexible enough for this. Change withPlugins to overwrite packages?

[WIP] Case 4. Dictionary plugins

Future ideas

  • Option A. Expose makePloverPlugin.
    • We should support GUI plugins, too, but that's not easy.
    • Keeping the current state also makes sense.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions