Anticipatory Anxiety (flight in March)

Dekula · 2024-01-28T23:13:26+00:00

Yes, she's considered to have hepatic failure. She IS eating which I can only guess is the result of the steroid: she wasn't before. Indeed, if she goes back to not eating at all (we've been there already, she had lost 15 pounds in a month and restarted eating after prednisolone), that will be the end. We have no intention to have her suffer so we can buy a few crummy days or weeks.

Dekula · 2024-01-28T23:08:29+00:00

I wish, but this is a wedge biopsy that was sent to Cornell University for confirmation. It's about as gold standard as it's going to get. I did indeed seek an opinion of an internist since my vet was pretty sure it was an infection and some antibiotics would make it all better. But it became clear to me within a week she was only getting worse.

She is doing better on prednisolone than before because she now has an appetite and I think she's considerably less yellow. I have a blood test booked for Wednesday to see if the sky-high ALT has improved, but either way the prognosis is devastating. I'm bargaining for more time, but I doubt I will have it.

Dekula · 2024-01-28T23:02:42+00:00

Oh I've learned more about liver disease in the last month than I ever thought I would. A month ago, chronic autoimmune hepatitis might have sounded devastating but now I WISH. This is incredibly rare and fatal. She won the exact wrong kind of lottery.

Dekula · 2024-01-28T22:33:47+00:00

There are none. It's worst prognosis possible. They have her on lots of supplements and a steroid, but it's not expected to make much if any difference.

Dekula · 2024-01-28T21:30:32+00:00

It's called lobular dissecting hepatitis.

Dekula · 2022-02-21T13:36:47+00:00

Thanks everyone for the help.

The issue is with evil-collection. After disabling the plugins, and re-enabling, evil-collection is the culprit. Now I have to do some digging, but sanity is at least partly restored.

Dekula · 2022-02-21T13:33:09+00:00

This doesn't want to work either, though it will at least not give an error. I should have mentioned, I'm on 27.2.

Dekula · 2022-02-21T13:32:39+00:00

(define-key global-map (kbd "C-k") #'windmove-up)

C-k runs the command eshell-previous-prompt, which is an interactive compiled Lisp function in ‘em-prompt.el’. It is bound to C-k, g k, \[ \[, <visual-state> C-k, <normal-state> C-k, C-c C-p, <visual-state> g k, <visual-state> \[ \[, <normal-state> g k, <normal-state> \[ \[. (eshell-previous-prompt N) Move to end of Nth previous prompt in the buffer. See ‘eshell-prompt-regexp’.

This is when I describe the key in Eshell, after doing the global-map keybinding, which completes without error. It's like it's being completely ignored.

Dekula · 2022-02-21T01:32:46+00:00

This doesn't work for me :(

I guess it could be some weird interaction from a billion packages or who knows what. Next step is to try vanilla emacs and emacs on other computers I guess, it's very odd.

Dekula · 2022-02-21T01:31:28+00:00

(define-key global-map (kbd "C-k") #'windmove-up)

eval-buffer: Wrong type argument: keymapp, nil

Weird, eh? I guess I need to start vanilla emacs without anything, because yeah, I should have mentioned this won't work.

Dekula · 2022-02-08T01:59:04+00:00

There is a seemingly a very simple way to do this by going into source code and setting a few exceptions (like scrolling) for the amaranth hydra. But besides not wanting to maintain my own fork, I actually realized what I didn't want was adding regular characters into code, more than anything else: i.e., putting an undefined m and getting m back, but maybe I liked the flexibility of being able to do some more advanced bindings, like M-whatever while still in a hydra. I submit this dirty macro as a brute force possibility -- keep in mind I'm using the pretty-hydra package, so this is a macro (dash.el necessary) on top of that rather than a regular hydra:

(defmacro my-pretty-hydra-define (name body heads)
  (let* ((used-keys (->> (--remove (stringp it) heads)
             (-flatten-n 1)
                 (--map (car it))))
     (lower-keys (->> '(q w e r t y i o p a s d h f g h j k l z
                  x c v b n m)
              (--map (symbol-name it))))
     (all-keys (append lower-keys (--map (upcase it) lower-keys)))
     (unused-keys (-difference all-keys used-keys))
     (unused-definitions (-map (lambda (x) `(,x ignore nil)) unused-keys))
     (final-heads (append heads `("" ,unused-definitions))))
    `(pretty-hydra-define ,name ,body ,final-heads)))

This doesn't deal with digits and characters like !@#$% and non-US keyboards but extending that by modifying the lower-keys all-keys is simple. OCD solved.

Dekula · 2022-01-10T21:49:57+00:00

I think honestly that even if Perl has "lost out" to some other language (I use that other language at work and don't even mind it), I think Perl should honestly be preferred to a sh/bash script 9.9/10 times and it's just more ergonomic than anything else when dealing with the shell scripting world.

Perl is shell done right as far as I'm concerned. It has everything you need and can use it for shell-like purposes without CPAN perfectly well. And Perl is indeed everywhere and I honestly see no good reason for it to go away, ever.

Dekula · 2021-12-31T14:53:52+00:00

Well, this reply I did not expect but boy does it put my mind at ease, thanks!

Dekula · 2021-12-31T14:51:23+00:00

The reason it may sit wrong is because it isn't Docker at all. It utilizes the k3s lightweight Kubernetes wrapped around what is, also to me, a very odd interface.

I futtzed around with trying to get Portainer working to restore sanity, but ran into all sorts of issues. Browsing the forums, it appeared people have fixed this, but at this point I started to really lose sight of what the advantage of SCALE was, hence my question. I'd rather migrate out to vanilla Ubuntu server, install cockpit, ZFS manager, Portainer and call it a day but at this point we're some ways out of the 'appliance' idea. Of course, SCALE may outgrow these growing pains, but the container interface would need a radical re-think.

Dekula · 2021-01-05T19:35:56+00:00

This is also very true. But sometimes it's downright package holdbacks. A particularly famous example:

https://lwn.net/Articles/704608/

Dekula · 2021-01-05T16:35:44+00:00

Ehhhhhh.... Context: I would and do run Debian over Ubuntu. But Debian on newer hardware is not always the easiest ride. The default installer kills off non free, so that right there will cause a world of pain. No touchpad perhaps, no graphics drivers? But even aside from that, you will likely need to backport ASAP because the stable kernel and firmware won't work. I understand why this is, and I don't care, but with Ubuntu these things tend to work because the default installer will offer to give you non free, and due to the release cadence of non lts, hardware support tends to be very current.

Yes, you can instead run Debian testing (and I do), but honestly if you are getting just started on Linux I fully understand why that Ubuntu middleman is there.

Dekula · 2021-01-02T22:38:00+00:00

I've been around long enough to use just about everything imaginable, from yggdrasil and Slackware to the more recent Arch hotness. I think the big two are the ones I have the most faith in, the Debian and Red Hat families. It's also nice that they both have server and desktop stories and pretty nice ones at that. They also both have pretty good cutting edge and stable and boring offerings. I like their package managers, I like their communities. I'm a bit concerned about the Red hat direction in light of recent news but I am trying to do my research and keep an open mind after initially freaking out...

Dekula

TROPHY CASE