agcom / dirb Goto Github PK

It's a huge cluster of copy pastas and dirty codes.

Let the user choose the name when creating something.

Make it the default action, disable-able through a flag, or vice versa.

Debug logs.

Usage: bs grep REGEX [-f [BOOL]] [-d PATH]

Usage: bs ls [-d PATH]

If given a name that matches with exactly one item's name prefix, use that item.

An error recovery strategy to find more errors without doing side-effect-non-free tasks.

Related to #36.

Usage: bs prune [-d PATH]
Removes all lock and temporary files. Note that the user should ensure that no file in the directory is under use before and during the prune call.

Do last touchs and move it out of the internal directory.

Just playing with words.

Up means update; usually means a patch update. Ow means overwrite and that's what the current Up does.

Usage: bs find LEFT OPERATOR RIGHT [-l [BOOL]] [-r [BOOL]] [-d PATH]

Set to github.com/agcom/bs.

Initialize command; create the proper data directory structure.

Currently, it does this on every call to any command; avoid that.

Parse arguments and run only side-effect free tasks; good for finding errors in the CLI call.

Using something other than stdout.

update or up or patch or pch.

Patch update a JSON.

Usage: help COMMAND

FileLock & TmpFileAsLock

Add a flag or special content to instruct the application to read stdin for the new item's content.

Make it the default action, disable-able through a flag, or vice versa.

Hidden files are used as temporary file locks.

Globally, should add *Ctx function variant to almost all functions.

Not a big deal, but is there a way to get rid of it?

query or search or find or ls or list.

What queries should be possible are not known yet.

Just write a custom CLI. I think it would come out pretty well (except that there will be no auto completion scripts).

It's no longer a sole book store (bs).

Just a suggestion which I guess it would work very well.

Do last touchs and move it out of the internal directory.

E.g. remove Repo interfaces.