• 0 Posts
  • 38 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • NixOS, plasma rn but sometimes jump to sway. I’d say distro is more relevant. for the most part I just have an editor and a browser open, DE doesn’t change much about my workflow. NixOS definitely does though

    chosen by my team, company at large doesn’t care but it’s nice for everyone to be on something consistent. company devices

    NixOS is a nice balance of the two

    I generally just copy my personal setup, which I’ve spent a decent amount of time on, but because I enjoy it

    not particularly, but nix supports all of the big ones

    language and stack a little bit, it’s all stuff that has good integration with nix. we deploy nix containers and then have consistent environment everywhere without having to work in a container. my team is a pretty standard team maintaining some full stack web stuff


  • I mean, I’m not a big fan of bash, the most likely default shell, so my advice would be to explore some alternate shells.

    I am a little surprised completions aren’t working in bash by default, but yeah idk if it’s possible to get the cycling through suggestions. double tap tab and it should at least list the options though.

    I’d recommend you hop between some shells and see what you like. most distros tend to keep the default shell pretty vanilla, the most change you’ll get is maybe zsh with some nicer defauls.

    nushell is great and would be my first recommendation. everything is structured like powershell, but way less verbose and more emphasis on integrating the existing cli ecosystem than pwsh’s commandlets for everything.

    fish or oh-my-zsh are things other people recommend. you don’t get structured data but they do give a better completion experience and other nice things

    I want to like xonsh, and used it for a few years, but it has the same problems pwsh has with separate ecosystems of structured commands and unstructured text. if you’re a python person though I’d consider it too though.






  • ctrl v is convention for paste, but plenty of things (ex terminals) use that for something else. this is a universal (wrt the app receiving it) keycode that means paste. it lets you bind a key, or a keyboard shortcut, to the paste key and paste in any app. without this it isn’t possible.

    it doesn’t even have to be a new programmable keyboard. there exist software key remappers for linux.

    you could remap a mouse button to paste, you could remap ctrl v to always paste regardless of the app, etc., all in software, all not possible before.