It's interesting that vim and emacs have this sort of cultural difference where emacs users tend to have one session always open, and vim users are more likely to directly launch a new session per file. I've largely adopted the emacs approach with my usage of neovim, though still use a mix. I have a Session.vim file that opens my windows/tabs/buffers I saved, including remote files using the scp://hostname/filepath syntax. Certain files I edit often enough that I just want them always open, and arranged a particular way. I do sometimes open a one-off separate session to quickly edit a config, though. I don't wanna mess up my muscle memory by introducing too many extra buffers or possibly messing up the order (although if I did do that I could just quit out and reopen the Session.vim file to get back to my saved arrangement).
Another thing I picked up from my time with emacs was making keybinds to interact with the "other" window. One macro I use often will delete the second line of the file in my current window, save, change to the other window, delete second line, save, change back to original window. When activated from keybind it all happens approximately instantly. I also have some binds to jump to the top of the other window's file (without leaving my cursor stuck over there) and so on, letting me keep my cursor in the main area most of the time.
Vim current directory is tied to the process, while each buffer in Emacs have its own default directory.
Also the buffer’s local variable in vim comes from different sources. In emacs, a lot of stuff are tied to a major or minor mode. You only have to toggle them to switch between keybinds, syntax,…
Try taking 3 1 minute typing tests back to back at your full speed and maybe you'll feel a little something. Any discomforts I had mainly revealed themselves under heavy loads like this. If you never type a lot in a row, it can be easy to miss
I did similar as a kid, weird random typing, mostly left hand, thumb used for some of the letters, etc. If you're willing to dedicate 2-4 weeks of fully immersed proper typing, you can definitely undo the old habits. Takes a bit longer to regain your old speeds, but it's mainly the very beginning that is frustrating. Whether that's worth it is hard to say. I use both shift keys now, and a split ergonomic keyboard. The numrow is easier to hit accurately as I have internalized the placement as well as the rows of letters after a lot more typing practice (columnar stagger rather than row stagger also helps, I think, I slide my fingers straight up and know which numbers are there).
I don't use a numpad, but a friend of mine swears by them for playing roguelikes. It makes it much easier to move diagonally in a single turn.
If you play any games with keyboard and mouse, you could bind some letters/numbers from the right half of the keyboard and then place the macropad on the left so you don't have to take your hand off the mouse to hit anything.
For another idea, you could bind pgup/pgdn or scroll wheel up and down for scrolling webpages, IRC backlog, etc.
>no mention of Dvorak or Colemak? Let's have that eternal discussion again!
I prefer Workman. Used to use Dvorak. Did not see much point to Colemak or its Mod DH variant by the time I was open to switching again, Workman set out to solve those issues in its original design. To anyone coming from Qwerty these days (Workman only came out in 2010), I would just recommend skipping over Dvorak and Colemak. You can find even more esoteric layouts, but Workman is in a bit of a goldilocks zone where it's available in some OSes/keyboards by default and isn't impossible to find keycaps for (often the "colevrak" kits cover it).
>Swap Caps and Ctrl
I never liked binding caps to Ctrl or Esc, but I do bind it to Compose in my OS these days. What I'd instead recommend is getting an ergonomic keyboard with a thumb cluster, like the Pinky4 or Iris, and putting your modifiers there. My Ctrl, Alt, and Super keys are all thumb keys now and even the leftmost of them is offset a similar amount to where Alt is on a traditional keyboard, so all very comfortable to press. I also have backspace, space, and enter on thumb keys.
>use Emacs or vi keybindings,
Strongly agreed, this is huge. Vi especially as you can avoid most chords, a bit like Sticky Keys in Windows, except not awful and not something you activated by accident. I spent considerable time with Spacemacs as well as evil-mode in my own config at one point. Back to (neo)vim now, but all great choices, all better than using nano or a CUA binds editor.
I do (re-)root my phone (after each update I have to flash the Magisk-modified boot.img again), but FWIW almost nothing needs root on Android, it lets you do way more by default than iOS. I think some people equate jailbreaking and rooting when there's not really a jail to begin with. You can install a custom ROM without having root and I think that's what most people really want to do. Cleaner base system, maybe some new features. I run LineageOS without gapps and it's great. I can use `sudo` inside termux since I have root. I don't really use it for anything except to verify that Magisk reinstalled okay (I do `sudo ls /` as a quick check). Installing F-Droid doesn't need root. You can even do it on locked down TVs and Amazon tablets usually. adb works as well, not sure why someone was saying it doesn't. Hell, adb should work even without either root or a custom ROM. I use it to reboot my phone into fastboot without the button combo and then flash Magisk right after.
I agree you might not need it, but the issue is one of principle. I want it because I might need it. I don't want to find another OS that supports root if I realize I need it.
Just how I may be OK with staying at home for months with deliveries and internet access and everything else provided for me, but I want the freedom to go outside. There is rarely anything I need that's outside, to be honest. And outside is more dangerous. But I want to be able to sudo outside whenever I want for whatever reason I want.
Well, as far as I know, none of the popular Android custom ROMs prevent root, though what you found about them not wanting to support you when you run into issues is probably somewhat true everywhere. I think the idea is that if something you're doing to get root or after getting root is causing problems, it would be outside the scope of the ROM itself and not their problem. I do still get help in the #LineageOS IRC channel and mention issues in there despite being rooted. I don't mention it unless it seems relevant, but I've seen bug report forms where they specifically ask. Ultimately it's gonna come down to whether they can reproduce it, consider it an issue, and if it's a problem with the ROM or something else. I don't think they intend to be malicious. I used to work in tech support for some enterprise backup software, and if there were signs that the customer's issue was because of their OS or network or someone else's software, that wasn't our problem to fix, and as soon as we could prove that, we could usually close the case. We were only there as support for a specific piece of software, it was their problem, or at least someone else's to keep the general servers and network working. I imagine the volunteer maintainers of LineageOS don't want to help you with things unrelated to what they do either. Have not used GrapheneOS as I've never owned a Pixel, but I imagine it's a similar situation.
I think you are answering not quite what's being asked.
I think it's completely reasonable to want to be able to get root on your device. For the exact reasons you mentioned. GrapheneOS allows that.
To actually do so, it's reasonable to have a reason. Otherwise what you're doing is basically running commands with sudo "because you can", which will bite you.
To have a rooted phone just for the sake of the trophy of having a rooted phone is something generally considered worse. Better to have a rootable phone, which you root if or when you have need of it.
>To have a rooted phone just for the sake of the trophy of having a rooted phone is something generally considered worse. Better to have a rootable phone, which you root if or when you have need of it.
This is indeed pretty reasonable. Very easy to root at any time after flashing LineageOS, for example.
>I had somehow pigeonholed it as "for cloud to local or vice-versa", and never considered it for local transfer, like over my own LAN.
Huh. Exact same thoughts here. I never used rclone because I don't use AWS or similar, just lots of bare metal on and off my LAN that I can ssh to. I am quite comfortable with rsync's quirks and args, so not sure I'll quit using it, but maybe I'll try rclone next time I do a massive transfer. Similarly I've been shown that ddrescue can act as a full dd replacement, but I'm so used to dd I still tend to use it.
In sway, put the lower priority windows in another workspace, or the scratchpad, or in tabs/stacks. You can bind keys to focus specific programs by their appid/class also, so even if they're on another workspace or monitor it'll jump right there.
It sounds like the scratchpad may be especially close to what you want.
I've been on both sides of this. Absolutely sucks as a user falling prey to stalebot or some poor sap pretending to be stalebot, but when I was working in enterprise tech support it was a huge relief to close a case and get it off my plate, for any reason. We had to take 2 new cases per day minimum, update each case (I often had 20+) every few days minimum. Only a small minority were a quick and easy solution (like security vulns with a fix ready we could send the customer were the easiest). We were stuck with our cases also, you couldn't give them to someone else unless you were out sick pretty much, and you'd get them back when you returned unless by some miracle the other guy fixed their problem. An inactivity close on a stalled case was comforting, I was finally free. I think they started cracking down after a bit and said you had to check in with them 3 times x days apart first instead of just immediately closing after no word for 2 weeks, and then they wanted you to call them first. Absolute nightmare.
I think as long as the issue isn't stuck with any one person then it's easier to leave open until it's actually fixed, like the 20+ year old Mozilla bug reports. Big corpo bureaucratic nonsense just ruins everything.
Another thing I picked up from my time with emacs was making keybinds to interact with the "other" window. One macro I use often will delete the second line of the file in my current window, save, change to the other window, delete second line, save, change back to original window. When activated from keybind it all happens approximately instantly. I also have some binds to jump to the top of the other window's file (without leaving my cursor stuck over there) and so on, letting me keep my cursor in the main area most of the time.
reply