Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Karl Voit :emacs: :orgmode: (publicvoit@graz.social)'s status on Saturday, 16-Aug-2025 07:10:17 JST Karl Voit :emacs: :orgmode:

   Using #Orgmode for so many years, I just recently stumbled over the Elisp function "org-copy-visible" which is practical as hell: it copies the currently visible characters.

   So you can collapse/expand, mark a region and then copy only the visible parts of it.

   Particular helpful when you paste into non-Emacs or non-orgdown situations. Or to manually generate some table of contents.

   I wonder how I was doing things so far without knowing about that feature. 🤦♂️

   #Emacs

2. Embed this notice
   Brian Campbell (unlambda@hachyderm.io)'s status on Sunday, 01-Jun-2025 13:38:47 JST Brian Campbell

   @dalias The process of normalizing to NFC is to decompose to NFD, which has a normalized ordering of combining characters, and then re-composing to NFC.

   It's possible for this to end up with more characters than you started with if you start with, say, two characters, one of which is precomposed combination of a character and two combining characters, and the third is a separate combining character

   When you decompose these into four characters, the base character and the three following combining character, the combining characters may be re-ordered for the canonical ordering.

   Then when you re-compose them, it may be the case that only the base and first combining character are available pre-composed, leaving you with one pre-composed character with the first combining character, followed by two combining characters.

   So a two-character sequence has now become a three-character sequence when normalizing under NFC.

   Contrived example: U+1EB7 U+0328 (Latin Small Letter A with breve and dot below / Combining Ogonek) normalizes in NFC to U+0105 U+0323 U+0306 (Latin Small Letter A with ogonek / Combining Dot Below / Combining Breve)

3. Embed this notice
   alcinnz (alcinnz@floss.social)'s status on Tuesday, 24-Dec-2024 05:16:21 JST alcinnz

   Yesterday I discussed getting our idiomatic computer to display text, but how about entering text?

   The keyboard would provide an interrupt everytime you press/hold a button or release it. Except the keyboard, per the SPI spec, provides "scancodes" not ASCII characters.

   So use lookuptables to convert from scancodes to ASCII. And track the state of keys like shift/capslock to determine which lookuptable to use.

   Append each typed character to the string being displayed.

   1/2!

4. Embed this notice
   mcc (mcc@mastodon.social)'s status on Saturday, 27-Apr-2024 12:44:56 JST mcc

   More rambling about problems with doing "bluesky" outside the blue sky walled garden (https://mastodon.social/@mcc/112340957577471735). Giving this one its own thread because I'm not sure I'm being fair.

   So now I have a PDS working, the first thing I'm experimenting with is: Since I have my own data hosting, can I use this to make posts that are longer than 300 characters? And if I do, what happens? I want to crosspost from Mastodon; mastodon.social allows 500 characters.

   So far the answer is: I cannot tell?!?