Yuya Nishihara

> jj branch create -T '"foo-" ++ change-id' Perhaps, it shouldn't be `-T ` (which usually specifies output template, and multiple `-T` aren't allowed), but a flag `--evaluate-name-as-template []..` or...

> Many Revs -> Many templates Out of curiosity, what's the purpose of bulk branch creation? Is it a pre step of some other review tooling? > Many Revs ->...

> jj branch create -r 'foo-{change-id}' It's a bit scary to apply to `jj describe -m '..'`, but should be less invasive than `template:..` prefix syntax.

`t'..'` is identical to `'t..'` in shell, and quoted version `"t'..'"` would be messy.

> let you override with `template:` or `literal:`, kind of how we let you override single-revision revsets with `all:` for some commands. The problem here is that `template: blah blah`...

Implementation-wise, jj's templater is a typed language right now (and has method name resolution based on type), so introducing first-class user object literal or heterogeneous list will add complexity. I'm...

> > Mercurial has a nasty hack to omit the last "," iirc. > > We shouldn't need to worry about that, we can just invoke `serde_json` and let it...

Yeah, it's easy if the caller expects json streams. I just mean a pure json array can't be constructed that way (and Mercurial has a workaround for that.)

> a new bug about adding template support for the node (seems like something we want, right?) Templater support will help to colorize node symbols without adding too many options,...

> ❯ jj branch forget 'foo:' > error: invalid value 'foo:' for '[NAMES]...': Invalid string pattern kind "foo" You'll need to prefix it as `exact:foo:` because `NAME` is is a...