just/notes

48 lines
2.0 KiB
Plaintext
Raw Normal View History

2016-09-29 21:45:53 -07:00
notes
-----
2016-10-02 22:31:15 -07:00
polyglot:
2016-10-07 17:57:35 -07:00
- get the extracted script and test its structure
2016-10-09 17:45:00 -07:00
- can I add rust docs for the command/binary?
- change name to "a polyglot command runner"
- comment code
2016-10-09 17:45:00 -07:00
- fix docs (note that shell is invoked with -cu, explain -c and -u)
- publish to github and cargo
- spam facebook, reddit
wishlist:
- preludes:
may be nice to allow all recipes in a given langauge to share
functions, variables, etc. could have a "prelude" recipe
which was included as a prefix to other recipes
- windows support: currently calling 'sh', which won't work on windows
2016-10-05 16:08:13 -07:00
- args can be passed after --, or with some special syntax:
a: 1 2 3 :
- should also add an annotation for recipes
a FOO BAR, export variables FOO and BAR with args
fail if doesn't get two arguments
2016-10-05 16:08:13 -07:00
- indent for line continuation
2016-10-05 14:00:51 -07:00
- use launch recipes asyncronously
2016-10-02 22:31:15 -07:00
- ~/.justfile:
2016-09-29 21:45:53 -07:00
. is this for non-project specific commands, so that when you
type .j in any directory, it uses it as a justfile?
. or is it for commands which are useful across projects?
2016-10-02 22:31:15 -07:00
- super complex recipe lines:
a: b c # run b and c, then a
b | a: c # run c, then b, and pipe output of b into a
a >> a.log: # run a and append output to a.log
a B C: # a takes B and C as command line args, like j a HELLO BOB
# can enforce at command line
2016-09-29 21:45:53 -07:00
- what is the story for allowing justfiles in subdirectories?
use a different name, like 'subjustfile' or 'jfile'.
recurse up to the justfile, but add recipes in any jfile
that you find along the way. recipes in justfile are accessible,
and run from the justfile dir. recipes in jfile are run from jfile
dir. refuse to run if a recipe in justfile and jfile conflict
- rust is a given, so one option is to write a very simple shell
2016-10-02 22:31:15 -07:00
command parser and use that instead of the system shell. this
would make recipes work across systems with incompatible shells.
additionally, we could also define a mode where it will only call
commands from cargo, which would make recipes work across systems
with incompatible userlands 'rc' or 'cargo cult' is a great name