Preferences

mechanicum
Joined 179 karma

  1. Maybe Subscribe with Reeder[0], 1Password[1], Userscripts[2]. The RSS and HTML icons are obviously fairly generic, so not 100% sure.

    [0]: https://reederapp.com

    [1]: https://1password.com

    [2]: https://github.com/quoid/userscripts

  2. More than two, e.g. there’s also the Inline Images Protocol supported by iTerm2 and WezTerm.

    Kovid documented his rationale at some length here: https://github.com/kovidgoyal/kitty/issues/33

  3. Definitely S01E01, @ ~55-58 minutes. I just watched it.
  4. I mean, 25 years and 27 inches later, and only reappearing after the queen Hudson served had died, with no tale of exactly where he’d been or how he got back… the cynical explanation would be that he was simply a different man claiming to be Hudson in the hope of a handout from the restored monarchy.
  5. These have been available since mid-2022:

      :insert-output Run shell command, inserting output before each selection.
      :append-output Run shell command, appending output after each selection.
      :pipe, :| Pipe each selection to the shell command.
      :pipe-to Pipe each selection to the shell command, ignoring output.
      :run-shell-command, :sh, :! Run a shell command
    
    The placeholder for the current file is %{buffer_name} (not as bad as it looks, the command line has tab completion for basically everything).
  6. Cmd + click places multiple carets on macOS. Apparently – I never touch the mouse when I’m editing in Helix. I don’t know which modifier it is on other platforms.

    I’m not sure if replicating Sublime’s Ctrl + D is possible or not, but there are other ways to achieve every use case for it I can immediately think of. e.g. I think I’d typically be doing `<space>h` to select every instance of the symbol under the cursor, or using `s`elect to reduce a selection to a match, possibly yanked and pasted.

  7. It uses old style figures rather than lining, if that’s what you mean by “higgledy-piggledy”. See https://practicaltypography.com/alternate-figures.html#oldst...
  8. I don’t think so, no. This is how it works today: https://www.gov.uk/check-job-applicant-right-to-work

    If your new hire is a British or Irish citizen, you ask for their passport on their first day and retain a photo/scan. In most cases this means that a layperson has to verify that the (possibly foreign) document is genuine, but I don’t think fake passports are a statistically meaningful problem.

    If they have a visa or, probably most likely in recent years, EU right to remain, they will have a share code for online verification. That takes you to a page with their details and a passport-style photo that you can download as PDF for your records.

    Identifying whether someone has the right to work has never been a problem. If somebody is working illegally, it’s because the employer is either knowingly employing them illegally, or doesn’t care/bother to check (or even know that they’re legally required to do so – a perennial problem with early stage startups in London, in my experience).

  9. A small practical example of how you might use this: https://imgur.com/mTS0vHO

    Helix on the left and a Clojure repl at top-right in terminal panes. Portal data viewer in a browser pane at bottom-right.

  10. You can have that. Cmd-Opt-Shift-V or H to split with a different profile, or use the move/swap options in the context menu to put any panes in the same tab after creation.
  11. When you say Terminal app, do you really mean shell commands? i.e. do you want to run something in Terminal.app that will demonstrate the expanded colour range?

    Try btop, a resource monitor with true colour support and 37 builtin themes.

  12. I know. My question is, isn’t the reason the command line tools work the way they do simply that they’re essentially the BSD programs (give or take an Apple patch), with BSD options, not because they needed to work that way for Apple to get the OS certified?

    Even if macOS wasn’t UNIX-certified, Apple would still be unwilling/unable to include the GNU software due to the license. I can’t see the Apple of today implementing a full suite of non-GNU software but with GNU-style options either.

    So, POSIX compliant or not, there’s probably no world where `grep -P` works out of the box on a Mac.

  13. > because macOS is adhering to the UNIX specification

    Isn’t it rather that Darwin was based on BSD 4.4? I’d imagine GPL 3.0 is a bigger impediment to them ever migrating to GNU tools than any desire to be UNIX certified.

  14. The % register contains the path for the current buffer, you can insert that into prompt commands with <C-r>%. <C-w> at the command prompt deletes the last word, which in this case will be the filename of the current buffer, leaving the directory path.

    So:

    :o <C-r>%<C-w>new-filename<ret>

    Would open a new buffer at /path/to/the/previous/buffer/new-filename. The file isn’t created on disk until you explicitly write, so :w! to save the first time.

    If you literally just wanted to create a new file instead of opening a buffer, you could do that from inside Helix with :run-shell-command (aliases sh or !) instead of another terminal:

    :sh touch <C-r>%<C-w>new-filename<ret>

    The :o method has the advantage of LSP integration. For example, when I create a new .clj file that way in a Clojure project, the new buffer is pre-populated with the appropriate (ns) form, preselected for easy deletion if I didn’t want it.

  15. It’s about hand movement, not desk space.

    The “missing” keys are on additional layers reached via a modifier key, or by overloading keys on tap/hold, or by increasingly esoteric methods the smaller the board gets: chording, tap dance, etc. They’re typically no less accessible than capital letters, while allowing you to keep your fingers on the home row.

    For me, the additional keys on my larger keyboards rarely prove useful in practice. I end up mostly using the same subset available on the 60% I’m typing on now – it’s quicker and more comfortable than reaching over to the dedicated key.

  16. It’s common niggle but, as far as I know, nobody is sure of the precise rationale for placing every key, only the broad explanations of the layout that Dvorak published and promoted. The layout wasn’t based only on letter frequency but they attempted to account also for bigram frequency, frequency of repetition within words, frequency with which words are used, and with an objective of rhythmic alternation between hands.

    Consider also that it was developed in the 20s and 30s. Nowadays you could throw some moderately hefty compute at almost everything of note written in the English language and come back to an error-free analysis after lunch, but who knows how representative was the corpus they analysed, painstakingly and manually. It might have made perfect sense with their data set.

    Ultimately, the English language didn’t evolve to be easy to type, there will always be compromises somewhere, and the English of today isn’t the English of a century ago anyway. I imagine you’d get quite a different layout if you based it on Gen Z text messages or something.

    Personally, I can’t help but note that Dvorak’s first name was August.

  17. I think they mixed up their sources. The jeep/ox comparison appears to be from the 1944 US Navy report: https://archive.org/details/APracticalExperimentInSimplified...

    (Typewriting Behavior, for the curious: https://archive.org/details/in.ernet.dli.2015.74878/page/n11...)

  18. I’m curious what led to that conclusion. As far as I remember, making concurrency easier to manage was always presented as one of Clojure’s primary objectives. It’s fundamental to the design e.g. a major motivation for all core data structures being immutable.

    STM, atoms and agents were there from the beginning. I think futures and promises were added in 1.1. core.async is from 2013. Even popular third-party libraries like promesa and manifold are around 10 years old at this point.

    I think flow promises to make it easier to orchestrate core.async, specifically, in complex applications, but the essential primitives are far from new and I don’t consider them any harder to use than JavaScript.

  19. On that page they have Cmd + Esc mapped as the shortcut for the global system menu (see “Teleport”), and it looks like the CEO is a NeoVim user[0].

    I guess they anticipate users hitting escape a lot. Making it a large target doesn’t strike me as a worse use of the space than dividing function keys into blocks of 4, and more likely to be intentional than an artefact of generative AI.

    [0] https://www.linkedin.com/feed/update/urn:li:activity:7353029...

  20. I don’t think that necessarily follows. The age of the surviving fragments today isn’t the whole story.

    We could presumably infer it still wasn’t “missing” as recently as a thousand years ago from later sources referring to it, even if the specific text (or oral tradition) those authors knew of hasn’t survived.

    Like how we know about some of now lost Greek plays, originally written in the 5th century BC, because they were still being performed in Imperial Rome and writers of that time described them, even the details of how they were staged.

  21. As an alternative, perennial HN recommendation atuin (https://atuin.sh) logs time, duration and exit code (among other data) for every command.

    That way you only have to look at it when you need it, and you can also figure out what you were doing last week/month/year if necessary.

  22. They bundled it into the Traders & Barbarians expansion.
  23. At least on Mac, when you install them locally, Creative Cloud makes them available to every app like any other font.

    They’re just regular OpenType files, albeit with “beware of the leopard” levels of filesystem obfuscation, so it’s fairly trivial to divorce them from Creative Cloud’s control if you want/need to.

    And on the web, Typekit is just CSS and woff(2), so again, no (technical) impediment to doing whatever you want with them.

  24. > This tool doesn't really create sparklines, but it does create small charts

    The gif at the top doesn’t demonstrate everything included. From the text:

    “There are currently three variations: bars, dots, and dot-lines (line charts with tiny dots at the joints between segments), each of which has five weight variants.”

    See also their examples page: https://beta.observablehq.com/@tomgp/after-the-flood-i-spark...

    I’d call delivery as ligatures a trade-off. Much easier to make it scale with text on the web when embedded inline, it’ll match the text colour for free, and the underlying numeric data are trivially retrievable and machine-readable. Compare the example on the Sparkline wikipedia page, which don’t scale with the text and are almost invisible when using their own dark mode.

  25. Relative to their traditional construction material, twigs, it’s probably no worse.
  26. I mean, doing that is pretty much what made him (semi-)famous in the first place (https://gist.github.com/chitchcock/1281611).
  27. Clojure has doc and source functions. For example:

      user=> (doc clojure.core)
      -------------------------
      clojure.core
        Fundamental library of the Clojure language
    
      user=> (doc +)
      -------------------------
      clojure.core/+
      ([] [x] [x y] [x y & more])
        Returns the sum of nums. (+) returns 0. Does not auto-promote
        longs, will throw on overflow. See also: +'
    
      user=> (source +)
      (defn +
        "Returns the sum of nums. (+) returns 0. Does not auto-promote
        longs, will throw on overflow. See also: +'"
        {:inline (nary-inline 'add 'unchecked_add)
        :inline-arities >1?
        :added "1.2"}
        ([] 0)
        ([x] (cast Number x))
        ([x y] (. clojure.lang.Numbers (add x y)))
        ([x y & more]
          (reduce1 + (+ x y) more)))
  28. It’s 100% a niche interest, they’re not going to become the mainstream option.

    But it’s a niche (competitive gamers and mechanical keyboard enthusiasts) with deep pockets, to whom “buying a new keyboard” is basically no barrier at all.

  29. Some old IBM keyboards had a solenoid built in, thumping the inside of the case with every key press to provide feedback. For example: https://www.youtube.com/watch?v=1qw6ebySet0&t=906s

    Probably the most practical DIY option.

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal