Marcel van der Boom @mrb@mastodon.nl

Upgrading to #emacs 27 Mostly for the json stuff.

Byte juggling finished for my laptop. Now running 2 SSDs with #btrfs in raid1 profile. Backup of disk goes to NAS with rsync. (Want to add some sort of snapshotting to that)

I'm juggling terabytes

#newdisks #btrfs

#TIL dd also copies the disk/fs UUIDs when cloning a disk

😠

Migrating my #emacs config to a #lsp (https://langserver.org) based setup.

Easy to start, but this will take quite a while to configure for an efficient workflow.

Also, an emacs-lisp language server is not in the list, first thing I looked for. Duh.

Hmm, I was under the *impression* that _some_ text `formatting` was supported by mastodon
( see https://github.com/tootsuite/mastodon/issues/853 )

Is that instance specific? Am I missing something?

The amount of mail without the required 'Message-ID' and 'Date' headers crossed my annoyance-threshold.

Here's a solution, using postfix:

In postfix/main.cf:

`always_add_missing_headers = yes
header_checks=pcre:$config/header_checks.pcre`

In postfix/header_checks.pcre:

`/^Date:[ ]*$/i STRIP`

This has two effects:

- if Date: header is blank, it will be stripped and logged that this is done
- missing required headers will be generated by postfix, including stripped ones

If you're doing any work with #postgresql , get a copy of #stellar It's a huge time-saver! Creates and restores database snapshots quickly. Much faster than pg_dump/pg_restore

https://github.com/fastmonkeys/stellar

Trying to get #arch running natively on my Asus C101PA ("flip") after rage-quitting chromeos due to lack of #yubikey and #trezor support.

Mostly done. Biggest hurdle now: suspend by putting the lid down doesn't resume, halts the machine.

Is there an accepted number of attempts to master #paredit before being allowed to give up?

#emacs

@mdbraber Any ETA for upgrading the instance mastodon.nl to version 3.x ?

Migrated to mu(4e) from notmuch for my email; took me "only" 3 days.

Main reasons:
- rationale of 'state in maildir only' helps me keep sane when using many machines
- refiling messages is natively supported
- format=flowed support
- UI of mu4e, especially compose and attachment handling
- less glue needed to have a complete workflow

Things I lost:
- remote use over ssh (although the 'mu server' paradigm gives me hope)
- tagging

It's all a lot simpler now.

#emacs #mu4e #notmuch

I have been trying to get 'format=flowed' composition right in #emacs #notmuch message-mode for about a year now I think, and I'm still failing.

I feel all the ingredients are there, but I haven't found the right recipe yet.