<span class="mw-page-title-main">Things I did with Claude on a Week-End</span>
Fabrice P. Lauss𝕪s hun Web

Things I did with Claude on a Week-End

This is the Elephants' graveyard where I put big projects which have been tackled and, sometimes, even fulfilled beyond expectations.

TeX to unicode

This is the first one I completed, on 25 July (2026). That was the goal:

Find a way to map TeX-to-Unicode on the go, without passing by https://www.unicodeit.net/, e.g., instead of Ctrl+Shift+U opening a u and inviting a unicode character (for em-dash), do something like Ctrl+Shift+Alt Gr+U invites a TeX command that parses into unicode, such as g^{(2)}(\tau) turning into g⁽²⁾(τ).

and it resulted in the mighty TeX2unicode. This was better than I intended, so a big success for a first try, that went beyond expectations, although those were very high. The wonders of AI and the power of the tool!

Prettify glosses

On the next day, 26 July (2026), this one went down too:

Prettify the listing of my glosses in my diary, so that instead of, e.g., for July (2026):

* [[July 22|22]]: Gloss on {{Malygin85b}}
* [[July 22|22]]: Gloss on {{Howell04a}}
* [[July 22|22]]: Gloss on {{Edgar12a}}
* [[July 23|23]]: Gloss on {{Moreau12a}}
* [[July 23|23]]: Gloss on {{Lantz15a}}

which renders as

Have something more styleish and tidy, e.g., with a manicule and some grouping:

Indentation should be neater, which is also part of the task.

I use Palmyrene numerals 𐡻, 𐡺, 𐡹 (they normally read from right to left) which are beautiful glyphs for Palmyrene Aramaic, the language of Palmyra (in present-day Syria) from roughly the 1st century BCE to the 3rd century CE:

Fix llw2wl when there is network failure

I met with a network failure, so some files could not be uploaded:

laussy@azag:~$ !llw
llw2lw --doit
Running in write mode
Enter the start datetime (YYYY-MM-DD [HH:MM:SS], default: 2026-07-23 22:59:26): 

== Pages to push ==
2026
July (2026)
Oemrawsingh02a
Template:Mostafavi25a
Things to do with Claude on the week-end

== Files to push ==
File:Screenshot 20260723 231737.png
File:Screenshot 20260723 235846.png
File:Screenshot 20260724 000205.png
File:Screenshot 20260724 001310.png
File:Screenshot 20260724 002100.png

Uploaded: File:Screenshot 20260723 231737.png
Uploaded: File:Screenshot 20260723 235846.png

== Failures ==
File:Screenshot 20260724 000205.png: Invalid CSRF token.
File:Screenshot 20260724 001310.png: Invalid CSRF token.
File:Screenshot 20260724 002100.png: Invalid CSRF token.
2026: Invalid CSRF token.
July (2026): Invalid CSRF token.
Oemrawsingh02a: Invalid CSRF token.
Template:Mostafavi25a: Invalid CSRF token.
Things to do with Claude on the week-end: Invalid CSRF token.
Log file updated: /home/laussy/comp/lw/llw2lw-log.txt

When this is the case, on next attempt, they should be uploaded again, as opposed to filed as "backed-up" or "synced". Importantly, this must not concern files taken from syncy which also generate an error but of duplication.

Claude took care of this and it appears now to be robust to such failures.

Restore Right-Click Image Menu services

There was some nice KIM service-menu way to get essential shortcuts at the tip of your ring finger but this became nightmarish to install and maintain, so I essentially gave it up. Claude could probably bring this back in an efficient/portable way, to do things like:

  • Compress images
  • Move files (say to bib repository)

etc.

It did, and the list of things he's servicing is in LaussyMenu.