Repository navigation
Replies: 1 comment
|
I'd try loading that plugin on its own in a temporary session, so its permission prompt doesn't have to compete with the plugin manager or another plugin. Save this as layout {
pane {
plugin location="file:/absolute/path/to/the-plugin.wasm"
}
}If the plugin needs configuration, copy those entries into a block on the From a terminal outside Zellij, start a new session: zellij --config /dev/null --layout /tmp/plugin-permissions.kdl --session plugin-permissionsReview the permissions there, then reload the plugin in your original session. Zellij reads the permission cache when the plugin requests permissions, using the plugin's location as the key. Keep the same location and user/cache environment in both sessions. This should let you use the normal permission prompt without hand-editing |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to activate Zellij plugin and it drives me nuts. As I've been adding multiple plugins (mostly bar changes as I don't like default ones). One of them is in some weird state - it needs permissions. But on initial launch I couldn't confirm it - as other plugin asked for those as well and when I accepted all windows disappeare. Now when I go to Plugin Managerthe window asking for permission shows in the background - but I can't get into it by clicking etc as all those windows disappear.
How should I deal with it? Is there other way to activate it?
That's the part of Zellij I absolutely hate. This should be a simple thing but I fight with those plugins on each new installation.
edit: is there a better way than editing
permissions.kdlin the cache?All reactions