happens

6 ms·

1. 31.▲
   by happens 3y ago

   Had that problem for a while too, but you can actually really easily set the TERM variable for every ssh connection separately from your local TERM. Just put the following in your ~/.ssh/config: Host * SetEnv TERM=xterm-
2. 32.▲
   by happens 4y ago

   Nice! I tried something similar at github.com/happenslol/qwer, I'll look at yours to see what you did differently :-)
3. 33.▲
   by happens 4y ago

   So, this syncs through a hosted server somewhere? Can I host my own? That information should be front and center imo, I didn't see in anywhere in the Readme.
4. 34.▲
   by happens 4y ago

   I'm not familiar with the performance characteristics of fish, so I can't really speak to that. I only remember that the developers of asdf themselves had problems with resolver/shim performance and even temporarily implement
5. 35.▲
   by happens 4y ago

   Thanks, that's a helpful perspective. I saw that there's also specific packages for things like node versions, so that might be an alternative to writing overlays in some cases. I'm just concerned about packages without any s
6. 36.▲
   by happens 4y ago

   Interesting, thanks for sharing! I'll have a look over the weekend.
7. 37.▲
   by happens 4y ago

   Yes it does! It uses the pre-cmd hook of shells and sets the environment, similar to how direnv works.
8. 38.▲
   by happens 4y ago

   You can find it at https://github.com/happenslol/qwer . Be warned though, it's heavily lacking in documentation and polish, although all core features are working. I've just added a bit of info to the Readme,
9. 39.▲
   by happens 4y ago

   I feel like they're just hitting the limits of a bash+shims based approach. I understand why they've done it, but in the end an implementation in a compiled language will beat that approach most of the time. There are issues since
10. 40.▲
    by happens 4y ago

    I've written a rust version of asdf over the last few months, both as an exercise and to fix a few issues I've been having with it - like noticeably slower tool startup times due to the shims resolving the version (my version basi
11. 41.▲
    by happens 5y ago

    Thanks, that's very insightful. I feel like especially in larger projects, going for a monorepo approach where the integration tests are just another package that runs on the entire repo makes what you're doing very powerful.
12. 42.▲
    by happens 5y ago

    How do you write your tests? I love go, but when it comes to testing I'm torn between having a more standardized setup with BDD tests (but worse ergonomics), or completely free-form tests with just a simple assertion library (but bette