Lizardsquid, maker of noises @lizardsquid@computerfairi.es

I think I'm going to go lie down for a bit, which means I won't be on masto until tomorrow

goodnight ♥

it's time..... for...

くコ:彡

Interesting tidbit I just read about The Invasion (which I've nearly finished watching now) – this was the last story to feature the cybermen until 1975 (7 years later)

sneerp

Unfortunately it's part of a build system, so I can't rename it - it has to be stack.yaml

I can't set it to work on both because I need these lines on my system:

nix:
enable: true

and those lines don't work without nixos.

I can't use the global gitignore because I have stack.yaml in other repositories that use stack, and I have to commit the file in those.

and the .git/info/exclude file doesn't seem to work

I'm working in a repository made by someone else, and it includes a build file.

This build file should NOT change upstream, however in order for it to build on my system I needed to make some OS-specific changes to the file.

Is there a way to tell git "hey, don't commit this file, and just leave it the way it is" without either removing my modifications to the file or sending my modifications upstream?

I think the organising sheet turned into a todo list, and todo lists never work

Well the organising sheet (first image) didn't work out – I didn't use it for a month.

But the "fill in a dot when you successfully do a task" sheet (second image) has been working well

(no image descriptions because I don't have the energy right now, and they're very visual organisation systems)

Sometimes, this happens: one post repeats itself into my feed forever, until it's all full up

hjdskghsdjkghksd

image description: A site which says "One day you will find here a user guide"

wait hold on, there's not even a manual, these are compiling instructions