Johannes Altmanninger

> > yeah I think we could have build_tools/[fix.sh](http://fix.sh/) > > that would run build_tools/update_translations.fish, > > formatting and others like "cargo clippy --fix". > Yes but [check.sh](http://check.sh/) does a...

> (`build_tools/style.fish --all` > can take over 2 seconds!, but the whole script can take over 75 > seconds, so it doesn't make much difference). I realized that I have...

> but I don't think we can reasonably make Fluent work for shell scripts Okay so your reasoning is: if we re-use our gettext extraction logic to generate *.ftl files,...

> > > close the PR via message. > Maybe adding a trailer like `PR: 12345` to each commit that is part of a PR Yeah we can try that....

> And the following does not work: > ```fish > echo hello # comment \ > world > ``` > It prints `hello` and then tries to execute a command...

> > One way to write inline comments is > > > > echo hello $(: comment) \ > > world > > > > which works in most shells....

I think you may be able to opt out of this on a case-by-case basis by typing quotes into the prompt but that disables some completions. > typing my query,...

> Frankly, these tools are terrible, and we need something better. could use a semantic diff tool. I didn't find a treesitter parser, which would enable tools like difftastic

Thanks for writing this up. Clearly it's a bug in Terminal.app, so regardless of whether we add a workaround, we should report a bug (though Terminal.app tends to be slow...

> I have just noticed that Apple has a short > explanation that states the hostname should be included to > desambiguate between local and remote hosts, :^) > I...