HN user

idahoduncan

17 karma
Posts0
Comments13
View on HN
No posts found.

I guess so - I use built in TypeScript modes, and integrate with tsc via the built-in LSP client, eglot. Works well. Front-end specialists may disagree.

Looks like it's four years for me with beancount.

    $ git log --oneline --reverse | head -n1
    5f72575 Initial commit: January 2022
My importers take care of reconciling the common transactions, like train fares and groceries, which means my monthly session takes under an hour. The slow bits are exporting CSV statements from my banks, and reconciling transactions from amazon and the local pet supply store (is it useful in practice to track litter and treats separately? probably not).

I'm also yet to migrate to beancount v3.

I'm following this approach. One of the most interesting things so far has been observing just how separate recall and production are. There are kanji that I can recognise instantly, and recall meanings and pronunciations, but I can't visualise them at all.

I have this set up using kmonad[1], and the following config. Many punctation marks are obviously missing, but I'm sure they could be added with a little thought. The mirrored layout is toggled by holding the space key.

    (defalias
      lhs (tap-next-release spc (layer-toggle ytrewq)))
    
    (deflayer ytrewq
      _    _    _    _    _    _    _    _    _    _    _    _    _    _    _    _
           bspc 0    9    8    7    6    _    _    _    _    _    _    _    _    _
           _    p    o    i    u    y    _    _    _    _    _    _    _         _
           ret  ;    l    k    j    h    _    _    _    _    _    _    _    _    _
           lsft /    .    ,    m    n    _    _    _    _    _    _         _    _
      _    _    _    _              _              _    _              _    _    _)

1. https://github.com/kmonad/kmonad

I do this from time to time as well, although I tend to get hung up on error handling. I would say that it's a simple enough exercise if you don't care too much about reporting parse errors in a meaningful way, although I'd be happy for someone to point out an implementation of error handling that fits into one's head.

I like that Ploopy are designing and building open-source hardware. I have their Classic (1) trackball, which has been great. I recently got their new trackpad, which is better for me. Having multi-finger gestures (pinch to zoom, swipe back) is nice.

With Emacs 30 I've stopped compiling from the master branch, preferring the tagged releases.

    GNU Emacs 30.0.92 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0) of 2024-12-03
It seems that most of the features I was eager to try from the master branch at various times (starting from native comp, then tree-sitter, use-package (although I've started using elpaca instead), modus themes, transient, etc.) have been merged. A lot of great features have been added to Emacs in recent years. Kudos to the maintainers!