You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm hacking around on it, both my config and the code inside. --outcmd is great for debugging, as well as the obvious usage for br.
I think there would be some use for an equivalent for verbs executed inside broot. A file that gathers everything that was executed inside, so someone can see the effects of their verbs.
I think this could be especially useful for anyone writing their own verbs, and for that reason I would propose it as a CLI command - rather than just an env flag targetted at broot devs. What about --outverb? --verb-out(put) would probably be my preference, but consistency probably trumps.
If you agree, I'll start working on it.
The text was updated successfully, but these errors were encountered:
Yes basically, I guess it could also be used to mark a load of files in the editor and come back to them later, but it's mainly for debugging verbs.
The reason I would say it's distinct from just using the log is that i get the impression that users are encouraged to hack around and create their own verbs, and this would make it a lot easier. If it was only for people hacking on broot itself I'd say they could use the log
Hello,
I'm loving broot.
I'm hacking around on it, both my config and the code inside.
--outcmd
is great for debugging, as well as the obvious usage for br.I think there would be some use for an equivalent for verbs executed inside broot. A file that gathers everything that was executed inside, so someone can see the effects of their verbs.
I think this could be especially useful for anyone writing their own verbs, and for that reason I would propose it as a CLI command - rather than just an env flag targetted at broot devs. What about --outverb?
--verb-out(put)
would probably be my preference, but consistency probably trumps.If you agree, I'll start working on it.
The text was updated successfully, but these errors were encountered: