ratrocket

Maybe I have my bash/readline vi mode configured specially to do this, but if I want to delete the entire line and type a new one (from anywhere in that line), I do something simpler than either of these alternatives:

<esc>S

Esc exits insert mode (of course) and capital S erases the line and puts you in insert mode at column 0 (just like in (n)vim, right?).

Like I said, maybe I configured that? But 'S' is standard vim-stuff... (I'm not able to double check my config at the moment).

[Edit: right after hitting submit I realized that my way is perhaps "arguably" simpler because I do have to hit shift to get capital S. So I'm also hitting three keys...]

discussed in 2016: https://news.ycombinator.com/item?id=10872209 (53 comments)

Is that the blue windy or the red windy? I can never keep them straight!

I'm not positive, but I think they've already run that playbook once or twice. They are IN the cycle.

Last things first: on my phone I only run syncthing "on demand", so I can't actually answer your question. Maybe someone else can chime in? From the little I've brushed up against the issue you're referring to, I think there's a way to have it not get killed, but it seems like it might be a little bit of a hassle.

On the transfer, here is what I could dig up:

The github issue about it was deleted, but archive.org has copies: https://web.archive.org/web/20251215062049/https://github.co...

HN discussion of same (with another link to the syncthing forum): https://news.ycombinator.com/item?id=46184730

Lobsters discussion: https://lobste.rs/s/urbcpw/potential_security_breach_syncthi...

(and here is the announcement that the official android syncthing app was being discontinued: https://forum.syncthing.net/t/discontinuing-syncthing-androi...)

No shortage of reading if you have the time! I'm quite happy to be running just the "standard" package (although, yeah, I should've pointed out that I don't run in continuously on my phone...)

Adding to the many other great uses of termux already here, the most useful lately for me is running Syncthing. After the "drama" with the Syncthing android client (my understanding: official development stopped due to onerous requirements from the Google, then the most popular fork was transferred to a new owner in a less-than-fully-trustworthy manner), being able to just run syncthing from the command line is a breath of fresh air.

I highly recommend using Unexpected Keyboard along with termux (a recommendation I myself almost certainly got from HN).

Not commenting on the larger gist of the comment, only:

> I've been having RSI pain on my right hand due to using mouse too much and in un-ergonomic positions

If you can, try using a left-hand vertical mouse. I use an Evoluent but there are a million brands. Get a cheapo and try it out. I figure it took me about a week to adjust and my wrists have been happier ever since.

Similar to a sibling comment, and perhaps not really applicable (since this isn't a company making something people can buy...), but the MNT Reform is amenable to fitting a custom/ergonomic keyboard also (I hadn't seen the Framework in the sibling comment, it looks very cool!).

I don't know how to link to it directly, but midway down this article there's a picture and some more links of an MNT Reform (apparently completely home-built) with a very cool, "thumb-centric", column staggered ergo keyboard:

https://mntre.com/media/reform_md/2022-07-01-july-update.htm...

(search for "More great mods from the community..." heading if interested)

I would very much like to have a keyboard like either of those on my laptop. The stares you'd get when in public!!

I also type "startx". Never saw the point of a display manager (which might be my own shortcoming!).

I read it to mean the author used "desktop environments" prior to that, so KDE or Gnome, as opposed to a "bare" window manager.

On digital ocean (at least) you can upload your own images and boot droplets directly from them.

In the past I've used a script called "alpine-make-vm-image" to run alpine images in digital ocean.

https://github.com/alpinelinux/alpine-make-vm-image

(Maybe that script does some magic to make booting a droplet directly from the image possible. On that I plead ignorance :)

Has "dc" the calculator fallen this far out of favor?! :)

> dc is the oldest surviving Unix language program.

https://en.wikipedia.org/wiki/Dc_%28computer_program%29

I used "dc" (the calculator) just earlier this week. Kids these days? :)

One way I compare the git to jj transition (if it happens, or for whom it happens) to the svn to git transition is: branching in svn was awful. It was heavyweight and you were signing up for pain later down the road. Git made branching easy and normal, almost something you barely need to think about. jj does a similar thing for rebasing. For someone whose familiarity with git is clone, pull, push, merge, creating branches (so, basic/working/practical familiarity but even "rebase -i" might be pushing the limits)- for someone like that what jj offers is a similar "lift" of a feature (rebase) from "scary" to "normal" similar to what git did for branching compared to svn.

That's just one aspect of the whole thing, and of course if you're a git rebase wizard (or have tools that make you that) then this won't seem relevant. But I think for a lot of people this might be a salient point.

(To address sibling comment: If I were colorblind, I would lead with that in any conversation about syntax highlighting; I am not colorblind.)

To answer the question: it's a feeling, like lots of things in software development. I tried "no syntax highlighting", found that I liked it, and I no longer use syntax highlighting. To say "specifically" how it's "better"... I'm not even saying it's better. "I like no-syntax-highlighting" is the statement I'm making (which, when it comes to syntax highlighting, is a statement a lot of people have issues with). So, from my personal experience, I take issue with the statement that no-syntax-highlighting is making things "difficult for the sake of it".

Try this out for analogy: I ate Red Baron pizzas every Friday night for 15 years, then I heard about homemade pizza 10 years ago. I tried making homemade pizza. It was good! ("I tried it and liked it") Now I only eat homemade pizza on Fridays. How is homemade pizza specifically better? It's better because I like it more. That's all there is to it. It's a preference.

(For the analogy to work, you have to like or at some point have liked Red Baron frozen pizzas. I happen to like them... the analogy is flawed though, I admit!)

(Let me preempt criticism that I'm comparing Red Baron frozen pizzas to syntax highlighting. I am not. It's only about the preference, not the object of the preference.)

Not the person you're replying to, but when they said "extraction" I believe they're talking about extracting pages from a PDF (like "splitting" the PDF apart, page-wise), not text. At least that's a thing I've used qpdf for in the past.

I wouldn't argue that the vim default (of not allowing backspace beyond where you entered insert mode) is ergonomic, but I do prefer and exclusively use the default vim behavior. It's just what I'm used to at this point (24 years using vim/nvim) and if I set it the "ergonomic" way, it's disorienting.

So, ergonomic or not, some people do prefer the default -- at least one person :).

To each their own. I quit using syntax highlighting about 10 years ago and won't ever go back (been programming for 25 years, vim/neovim user for 24 years). I just like it better, it works for me. It definitely does not make things "difficult for the sake of it" (for me). There are dozens of us! :)

(As to the rest: I use a pretty minimal set of plugins and I use the built in nvim C-o/C-p or C-x C-o/p "dumb" autocomplete. At least I think it's built in...)

To save anyone else the search:

mini.nvim site: https://nvim-mini.org/mini.nvim/

repo: https://github.com/nvim-mini/mini.nvim

From TFA it sounds like they didn't do semver prior to this release but now will:

  > What versioning strategy will Immich use?
  >
  > Starting with v2.0.0, we will now follow semantic versioning.

(edit for formatting)

Make that three :). Alpine is my "daily driver" on my laptop. I have several very long lived cloud VMs running it too. I know it has the reputation as "just" a container OS, but it's a pretty regular Linux distro. I think it's a joy to use on a daily basis! (I also believe it can't be that uncommon to daily drive it.)

If your update is the simplest version, a "git pull" -- then you're incorporating commits that have not "stewed" long enough for anyone to be burned. You might win the lucky ticket! (Saying this as someone who rarely updates nvim plugins, out of forgetfulness, not principle, and when they are updated I believe it IS a simple "git pull"...)

"Lynx is the text web browser": https://lynx.invisible-island.net/

Must be a generational thing :)

I'd describe myself the same as you did in your first paragraph here, and wanted to say that with LSP, your "rename function call" example in vim (well, I switched to neovim some years ago) is (mostly) `<Leader>rn` (default in my LSP setup, I'll paste the relevant line below) when the cursor is on the symbol. That will change the name in all open buffers. Annoying thing is that it doesn't (ofc) change the name in "log lines", so it's helpful to pre-`*` on the symbol name so you can go back and `n.n.n.`. (I've always wanted to "wire up" something to also detect those log lines and change them at the same time, but... ya know.)

The line in my nvim config that sets up the LSP "rename" is:

  vim.api.nvim_buf_set_keymap(0, 'n', '<Leader>rn', '<cmd>lua vim.lsp.buf.rename()<CR>', opts)

I mention this because in spite of using vim/neovim for over 20 years, I still learn new things (from HN comments and elsewhere) -- which is part of why I love it.

(To your larger point -- I concur... btw)

If you have 336 minutes to spare (although it's highly amendable to 1.5x listening) you can listen to four episodes of Behind the Bastards podcast asking and answering that very question over four episodes from 2023:

https://www.iheart.com/podcast/105-behind-the-bastards-29236...

https://www.iheart.com/podcast/105-behind-the-bastards-29236...

https://www.iheart.com/podcast/105-behind-the-bastards-29236...

https://www.iheart.com/podcast/105-behind-the-bastards-29236...

The last episode listed there has the description "Robert sits down with Matt Lieb to discuss Scott Adams's worst novel, God's Debris." so if one really likes the book being discussed, probably best to go into that episode with an open mind.

Yes, that is completely true -- transitive dependencies are a problem. What I suggested only works in the simplest cases and isn't a great solution, more of a bandaid.

Depending on your circumstances (and if the license of the action allows it) it's "easy" to fork the action and use your own fork. Instant "pinning".

You can consciously harness "target fixation" for good purposes, though. It would be more difficult to talk about that side the coin if it were referred to as "hazard fixation".