Do you have a link to a copy of the video with captions? YouTube autogen doesn't cut it unfortunately. Or perhaps a written-form version (slide deck + transcript)?

What's in the 8% not covered by testing?

I don't have a version with captions, sorry. You can find the slidedeck at https://github.com/elves/elvish/blob/master/website/slides/2...

The remaining 8% mostly falls into the following categories:

- Code that use OS functionalities that are cumbersome to mock in tests

- Code paths that are triggered relatively rarely and I was simply too lazy to add tests for them

Nothing is impossible to cover, but for whatever reason it was too much work for me when I wrote the code.

However, it's worth mentioning that I only settled on the transcript test pattern fairly recently, and if I were to rewrite or refactor some of the untested code today I would add tests for them, because the cost of adding tests has been lowered considerably. So Elvish's test coverage is still increasing slowly as the cost of testing decreases.

Hey, thanks again for the talk and for answering my fork bomb question with a live demo!

Thanks for your question and glad that you enjoyed it!

I thought you handled the question really well. To be honest the whole talk was excellent. I'm gutted I missed it in person.

There were a lot of aspects of this talk that I thought were really great. The willingness to try something unscripted, diving into the code repo live (e.g. to show where fuzzing is used), and the discussions of the reasoning behind the design choices. Great job @xiaq. This really makes me want to try elvish out, and I usually am quite skeptical of new shells.

Thanks! Glad that the talk is working as a marketing pitch for Elvish :)

Thanks! Murex talk when??? :)

haha I can't present nearly as well as yourself but maybe one day.

It's not easy to present though. I know on HN we see a lot of very clever people give some well executed presentations and it's sometimes easy to forget how much preparation and courage it takes to perform like that. And it's great to see how engaged people were with the content too.

Sorry, this is less of a question and more just comment of appreciation.

Thanks, I appreciate the comment the appreciation :)

In vim vi or nvim :r !date gives me shell returned 2

Did you set your login shell to Elvish? Vim unfortunately relies on your shell being a POSIX shell, but you can fix that with "set shell=/bin/sh" in your rc file.

FWIW, I've just added this instruction to https://elv.sh/get/default-shell.html#vim-/-neovim

Does elvish have a command history limit? Or is it configurable? I like a nearly infinite history.

History entries are kept indefinitely.

Thanks for the reply. You may have a new user. :)