Blog: 2023-11-08: Difference between revisions
No edit summary |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 21: | Line 21: | ||
</pre>So now I'm looking into https://github.com/Byron/gitoxide |
</pre>So now I'm looking into https://github.com/Byron/gitoxide |
||
--- |
---- |
||
A quick distraction that I saw a notification on https://github.com/pechorin/any-jump.vim/issues/92, which I'm going to call a #favissue |
A quick distraction that I saw a notification on https://github.com/pechorin/any-jump.vim/issues/92, which I'm going to call a #favissue |
||
--- |
---- |
||
After fighting an html canvas for like an hour trying to get a png with a large margin to display, I realized it was probably rendering the image but the image was just white where it was being rendered. This makes me think of this failure mode as something worth noting: when something is working but it looks like it's not working #frustratingfailuremode |
|||
---- |
|||
LINK ROLL UP |
|||
https://harelang.org/blog/2022-11-27-hare-is-boring/ |
|||
https://en.wikipedia.org/wiki/Taft%E2%80%93Hartley_Act |
|||
https://en.wikipedia.org/wiki/Computer_People_for_Peace |
|||
https://github.com/jaraco/irc |
|||
https://en.wikipedia.org/wiki/Antonio_Gramsci |
|||
https://github.com/jaraco/irc |
|||
https://www.irchelp.org/ |
|||
https://asciinema.org/a/542159 |
|||
https://www.littlevillagecreative.com/ |
|||
https://bouncingdvdlogo.com/ |
|||
https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol |
|||
https://en.wikipedia.org/wiki/Proportionality_(law)#International_law |
|||
https://prezi.com/p/edit/lnctinxkcxfx/ |
Latest revision as of 19:53, 8 November 2023
11-08!!! What a day!!!!!!! #11:08
Thinking of working on fish smart-case tab completion again: https://github.com/fish-shell/fish-shell/issues/7944
and already upon being confused as to how to get to my github branch, I am thinking of exploring a new git client, since git makes this super confusing. Here's what it looked like when I tried to use my git switch-to-upstream-branch without an argument to see how it's supposed to work:
fish-shell $ git switch-to-upstream-branch remote: Enumerating objects: 2420, done. remote: Counting objects: 100% (2130/2130), done. remote: Compressing objects: 100% (749/749), done. remote: Total 2420 (delta 1536), reused 1826 (delta 1376), pack-reused 290 Receiving objects: 100% (2420/2420), 1.93 MiB | 8.67 MiB/s, done. Resolving deltas: 100% (1611/1611), completed with 181 local objects. From https://github.com/fish-shell/fish-shell * [new branch] Integration_3.7.0 -> origin/Integration_3.7.0 * [new branch] for-riir-parser -> origin/for-riir-parser f9d21cc21..f81c9cba5 master -> origin/master + b9a84b6f5...55b628b1f riir-parser -> origin/riir-parser (forced update) fatal: missing branch or commit argument
So now I'm looking into https://github.com/Byron/gitoxide
A quick distraction that I saw a notification on https://github.com/pechorin/any-jump.vim/issues/92, which I'm going to call a #favissue
After fighting an html canvas for like an hour trying to get a png with a large margin to display, I realized it was probably rendering the image but the image was just white where it was being rendered. This makes me think of this failure mode as something worth noting: when something is working but it looks like it's not working #frustratingfailuremode
LINK ROLL UP
https://harelang.org/blog/2022-11-27-hare-is-boring/
https://en.wikipedia.org/wiki/Taft%E2%80%93Hartley_Act
https://en.wikipedia.org/wiki/Computer_People_for_Peace
https://en.wikipedia.org/wiki/Antonio_Gramsci
https://asciinema.org/a/542159
https://www.littlevillagecreative.com/
https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol
https://en.wikipedia.org/wiki/Proportionality_(law)#International_law