Replies: 2 comments
-
Very good idea. Make user customization easy. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I also like the idea, but existing custom prompts are not intended to be permanent; rather, they serve as examples for the user. The user should be able to change or remove them freely. If these are considered standard prompts, perhaps we should add a new property, such as visible=true/false, to hide them. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem:
Currently, if a user adds their own custom prompts in
configuration.lua
, these edits are overwritten or lost when a new version of the file is released. Manually merging the config each time is error-prone and tedious.Proposed solution:
Allow users to define their own prompts in a separate file — for example my_config.lua.
This file would be loaded automatically and merged into the main configuration.
It allows user-specific customization (extra prompts or override existing ones) that survives version upgrades.
How it works:
Users create a my_config.lua file in the same directory.
The config loader adds this snippet at the end of
configuration.lua
(right beforereturn CONFIGURATION
):my_config.lua.sample
:Benefits:
Feedback welcome!
I have yet not tested the code more than that it looks like it works. What do you say about the idea? Too complicated? Good? You have a better idea? Not needed?
Beta Was this translation helpful? Give feedback.
All reactions