Replies: 1 comment 2 replies
-
Hi!
Don't worry about it, that's what they're made for! Feedback is always appreciated and it's not like I'm flooded with it.
Actually, I don't even think so: this is behavior specific to the current project since it is only about managing its configuration and not about Cargo itself. I therefore find this valid.
I agree. A simple idea I had in the past was to have a command to spawn an editor on it. It would have simplified the process a tiny bit, but not much more. The thing I want to avoid is automated, opaque and behind-the-scenes edition of the configuration. However, having new commands dedicated to it would make it more explicit and thus more user-friendly in that aspect. Still, the edition would have to be tested to be as stable as possible, i.e. not reformat every line in order to add only one. It could end up being a big stack of caveats, but at least the interaction would be explicit. Regarding the design, I'll have to properly think about it, but as a first idea: maybe add these commands as sub-subcommands, for example
❤️ |
Beta Was this translation helpful? Give feedback.
-
It would be nice to have a simple way of adding crates to the
liner.toml
and installing them which does not include needed to edit theliner.toml
by handas long as you do not have any custom config you can always just re-import all the installed crates. But still always having to enter a second command after installing a crate feels a bit sluggish.
it could also be a
add
/remove
command which edits theliner.toml
and runsliner ship
which an extra flagbut this would just be
liner install
with a different coverI am opening this as a discussion since I feel like it kinda falls under
note:
maybe there is already a simpler way that I just missed
sry if I am a bit annoying by opening all these issues, i have just discovered this project and really love the idea
Beta Was this translation helpful? Give feedback.
All reactions