Add a CLI argument to redbot
to add cog paths to [p]paths
#6506
Labels
Category: Core - Command-line Interfaces
This is related to Red's CLIs (redbot, redbot-launcher, redbot-setup).
Status: In Progress
There's a PR open to deal with this, or an org member is working on this internally
Type: Feature
New feature or request.
Milestone
Type of feature request
Other
Description of the feature you're suggesting
I propose a
--cog-paths
flag for theredbot
CLI. This flag would add a colon-separated list of cog paths to[p]paths
, and would not persist through restarts (just like other CLI flags).Example usage:
--cog-paths /workspaces/FooCogs:/workspaces/BarCogs
Anything else?
So, for some context, I develop my cogs for Red inside of a Dev Container. Here's what that looks like. Then, I use Visual Studio Code's Run & Debug feature to actually run Red. The initial setup process for this development environment is as follows:
redbot-setup
[p]addpath /workspaces/SeaCogs
inside of Discord to add the project directory to the bot as a cog path.If this feature request is implemented, I could add
--cog-paths /workspaces/SeaCogs
to my VSCode Run & Debug configuration, removing one initial setup step to get up and running.Discussed in the Red Discord Server, in #feature-ideas: https://discord.com/channels/133049272517001216/133049878837329920/1332807433650704534
The text was updated successfully, but these errors were encountered: