@pesterhazy kv elisions are properly rendered (at the end and only one elision), plus ansi codes can be used (yay, syntax color)

And @dominicm’s colleagues fav:

this looks fantastic

is packed up in your branch already?

Re: mvn dependencies, we don't use any yet

Eventually I'd like to see if an AOT'd version of unravel would be better - that would solve the problem of shipping dependencies (and wouldn't require lumo as a production dep anymore, though we can still use it in dev)

Not yet pushed

probably easiest to inline the dependency for now (i.e. add src/)?

or vendor/

I thought about a git module too

But I found another way.

yeah?

I hate submodules with a passion

subtrees are your saviour

I've never used subtrees although I hear they are great.. but I've never had problems with submodules either, so they're my go-to way for repo-to-repo dependency management

@dominicm can you elaborate?

@pesterhazy subtrees mitigate a lot of the pain points of submodules. The https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree atlassian article is good

is it included in the standard git distro?

yeah

i'll give this a read thanks

I wish I could tell slack to not send the image, and only the text for links

we can probably disable expansions somewhere

I think it's a setting

or an admin can

I believe I've seen it in preferences

preferences > messages > scroll down

is that a personal thing? I don't want to inflict pain on others 😄

That looks good anyways 🙂 Thanks.

Sorry, didn't mean to start an OT thing like that.

haha can't say for sure, but I don't think you'll be able to modify somethingglobally without admin perms

@pesterhazy here you go ^^

you need to use the flag packed

@pesterhazy now that elisions stands out (because of ansi rendering), could it be possible to just print a number. Also commands could be /thing.

So if the user sees an underlined 12, the user know s?he has to type /12

and /thing is not readable which is a good thing

maybe even render as /12 so that the output is not readable

@pesterhazy if I use feature flags, do you prefer that I develop on a branch or on master?

I'd say on a branch - I do the same, makes for easier reviewing

ok boss