𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 
  • 0 Posts
  • 56 Comments
Joined 2 years ago
cake
Cake day: August 26th, 2022

help-circle



  • You want Upspin. I want Upspin. But Upspin never went anywhere (it’s at least 7 years old… ever heard of it?), and I personally believe that it was because it’s a royal PITA to set up, and because the tutorial had instructions that expected you to be using GCS. If you wanted to do everything on your LAN, it was even harder.

    It’s got all the of the features you mention, and it’s really the only system that does what it does; I really did try in the early days to get it running, and failed. It still has the caveat:

    Upspin has rough edges, and is not yet suitable for non-technical users.

    and, at 7 years old, if it hasn’t gotten anywhere yet, I think it never will. Commits trickle in, but there’s really no significant progress in usability.

    Read the mission statement. It’s glorious. And then wallow in despair that nothing else does this, and it’s a zombie project.


  • Plus, I had gotten to a place where my tiling WM, tmux, terminal tabs, and vim tabs were all competing for keyboard shortcuts, and it was driving me crazy.

    I admit, this is so bad that occasionally - and especially if I make the mistake of stopping to think about it - my brain freezes and I can’t remember the chord for a few second. What helped immensely was first kmonad, then Kanata, and finally a QMK keyboard. I use exactly the same keys for navigation, create, delete, etc operations, and only vary the layer key - WM under my pinky, tmux under my index finger. Helix has it’s own bindings and ways of managing windows that are different enough as to not really confuse me, and I don’t use terminal tabs at all, so it’s really only WM and tmux. But, yeah: a Helix split window, in a split tmux tab, in a split herbstluftwm window can occasionally get me stuck for a few second as I unbox all the layers.



  • This is a lot like what I do. Where possible, my apps are TUIs, so terminals dominate. At any given point I have 4 tmux sessions with around 6 tabs in each. I haven’t refined that, though, because my editor (Helix) also has window support and many editing tasks (yank/paste) are easier with Helix windows that with multiple helix sessions running in different tmux tabs. This works best with full-screen terminals, and I find myself closing tmux panels to open helix windows… I need to refine this.

    A few apps are GUI. Browsers, PDF viewers, graphics editors. Those are all full-screen.

    How do you use the sliding feature this way, though, and how is it better than just having separate desktops? Do you use multiple displays, or only one?








  • A while ago, I wrote a tool to generate change logs from commit messages. It grabs all commits from a tag to the previous tag, and collates them into a Keep A Changelog format.

    An unintended consequence is this is that my commit messages are in keepachangelog format; the tool just groups messages by type and adds the version and date decoration, and then inserts the text at the right place in the file.

    It’s fantastic. Because I know the commit messages will end up in the changelog, it encourages me to describe the commits in terms of:

    Adds blah blah Changes blah blah Fixes blah blah

    Anything that doesn’t start with a keyword is discarded, so I can still jot notes in the commit, but by far the biggest benefit is that it’s completely broken me of the habit of reiterating the code change that I committed, and write the reason for the commit in descriptive language.

    Having a little reinforcement such as tooling can do wonders for building good habits.

    Postscript I don’t know if anyone cares about this – it’s pretty specific to my workflow, but if you want to see the tool, it’s just a shell script. The only non-standard tool it needs is ripgrep. You pipe some set of commit logs to it, and it collates them into sections. In the repo is a very Mercurial+bookmarks function that’ll automatically grab and generate a section for the latest bookmark. But it boils down to something like this:

    hg log -vr v0.0.4:v0.0.3 -P v0.0.3 | changelog
    

    I only use git when I absolutely have to, so I don’t know what the equivalent command for that is; but here:

    • I use -v because I want the full commit. For a given commit, if there are multiple changes, I put each on its own line. Both git and hg only print the first line of each commit message by default, so to get all lines of commit log messages with Mercurial, -v is needed.
    • -r v0.0.4:v0.0.3 generates logs in reverse chronological order, from the commit with bookmark v0.0.4 to the one with bookmark v0.0.3. This should work with tags, too.
    • -P v0.0.3 prunes the v0.0.3 commit, so that its message doesn’t get included with the v0.0.4 log entry.




  • I’ve gone months between updates. On servers, that’s a little more risky because it CVEs, which can also apply to the kernel, but LTS is probably safe enough there: if there’s a kernel CVE, LTS will be updated.

    I’ve had trouble with pinning the kernel before, though. Last time I did it, I went several months and forgotten I’d done it, and my system got itself wedged because some package was expecting a newer kernel; it took me a while to figure out.

    LTS might be a better option, since that will be caught be dependency management. Pinning can cause version dependency mismatch issues.


  • I… I don’t get this. The trains are functioning as batteries? Regenerative braking is nice, but why is only a third going to power the trains themselves? Why not 100%? TFA says they’re issuing the “spare electricity” in the grid; “spare?”

    These aren’t perpetual motion machines; they’re not violating the third law, and they consume more energy than they produce. Most off these article is about the (obvious) benefits of adding regenerative braking to subways around the world, regardless of cost; what confuses me is: why are they spending money and effort to route regenerative braking into other uses, which is what the title literally says (“trains”, not “train power grid”). It seems like an inefficient and circuitous way to tap other demands into a subway power grid.

    Unless what’s really happening is that Barcelona is just tapping other demands into the (robust) subway power grid, and coincidentally adding regenerative braking, and someone decided to make the wild conceptual link that the power being fed back into the grid by braking is part of the overall power being used by new sinks. Which is like saying that my piss is being used to provide drinking water, because it goes back into the overall water cycle one way or another.