HN user

johncoltrane

1,564 karma
Posts5
Comments1,281
View on HN

hjkl AND the cursor keys equally suck for moving the cursor because they only move by one line or by one character.

jjjllllljjh is just as bad as <Down><Down><Down><Right><Right><Right><Right><Right><Down><Down><Left>. There are much better ways to move around and touch-typists and non-touch-typists would be better off learning them instead of obsessing over hjkl: :help motion.txt.

hjkl are more of a cult/status thing anyway because they are not _that_ touch-typing-friendly to begin with, and they suck just as much as the cursor keys for moving the cursor around.

Insisting so much on hjkl is silly. No one is using an ADM-3A in 2026, so the official documentation should let users use the more intuitive cursor keys and downgrade hjkl to what they have always been since vi: __ham-fisted alternatives to the cursor keys__.

I was 11 when I started roleplaying with gamebooks. I vaguely remember L'œil Noir as a classic among "Livres dont vous êtes le héros". The same year I saw the older kids play a full D&D campaign with the adults during summer camp. In the following months Casus Belli and Jeux & Strategies, two magazines dedicated to RPGs, gradually replaced comics… and we eventually put together an "official" club at our middle school, where we played D&D for a while, and more games as we discovered them: MEGA II, Paranoia, Rêve de dragons, le JRTM, Call of Cthulu, Zone, etc.

Fond memories of Laelith ;-).

The problem is that compositors typically don't have the notion of 3D scene.

It's all just a stack of layers, one window per layer. There is no shadow to speak of, only a mask around the window that provides the illusion of shadow. So there is no real interaction between all those items, no source of light, no distance, and no way to do ray tracing or some other techniques.

Assuming you already had a ~/.vimrc, the only non-defaults in that list are:

    :let no_man_maps=1
    :let loaded_matchparen = 1
    :set comments=""
    :set matchpairs=""
    :set paste
All the other lines set options to their default value, which is pointless.

The values for 'comments' and 'matchpairs' are incorrect, they should be:

    :set comments=
    :set matchpairs=
Enabling 'paste' by default is a very bad idea, with lots of side-effects.

Setting the following variable is useless if you don't enable the 'man' plugin, but maybe you do it manually during a session. I don't know. YMMV.

    :let no_man_maps=1

Conspiracy theorists have that special ability to jump to the most implausible conclusions from the smallest amount of facts.

I tried to watch The Age Of Disclosure and, well… Everyone in it manages to stay relatively reasonable during the first fourth of the movie. Until they decide that the most likely explanation of all those unexplained phenomenons is a race of technologically advanced extraterrestrials hiding at the bottom of the ocean for thousands of years.

It went from "we don't know anything" to "it's threatening aquatic ETs" in a heartbeat. It was almost scary.

You can try what Apple calls "fast user switching", which is actually pretty fast. The last (and only) time I used it, my days were split half-and-half between two projects for two clients, each with its own infrastructure. I did that primarily to help me focus but it had one pretty cool perk that I've been missing ever since: isolated accounts meant that I never had to worry about which Git/$SAAS/whatever user was currently authenticated and managing keys and such was a breeze as there was no "managing" needed, really.

I could do it because I had _some_ level of control on my work machine. Now that I work for a much larger organisation… I can't even imagine how hard it would be to have such a setup.

I don't know how usable it is in practice if you are switching contexts every 10 minutes, though.

Good work!

FWIW, I use Chrome 145.0.7632.117 on a M1 MacBook Pro and I just got a notification suggesting me to "correct" the o'rer tab because it used too much resource. I was looking at the details of my Transilien station.

Also, looking a the same "details" popin, I see some irrelevant info when I click on the "alert sign" of a Transilien line (Line N in this case): something about bus stops.

I have a couple of questions about the API:

I've looked at the data provided by IDFM and SNCF a few times but I was never able to find a way to match a commercial train number, say "134671", to a physical train number, say "211L" or "Z50421/22" or the more complicated EVN. Did you, by any chance come upon such a thing?

Also, could you confirm that the only data available concerns _departure_ times?

Good luck.

I prefer my background dark so light colorschemes are not really an area I've explored seriously. Also, dark colorschemes are much easier to design than light ones due to the disproportionate amount of light a white, say, background emits compared to the amount emitted by text. It dramatically reduces the number of colors you can use.

I have one here: https://github.com/romainl/vim-sweet16 but it is intentionally weird and essentially unmaintained.