Veit Kannegieser's repo

[__NM64__]

Off-topic:

What's with the fullwidth slash?

I'm a certified weeb and therefore have Japanese kana enabled, and it uses fullwidth characters. I'm a weirdo that doesn't like how narrow a traditional slash looks in words like and/or to the point of making the slash not very noticeable and to the point of such words looking almost more like "andor" with slightly spaced kerning.

Wait until you hear that I have shift+tab mapped to emdash — shift+backspace the multipication symbol × and shift+caps lock as division ÷ as well

[adoxa]

Off-topic:
This is a situation where a reaction comes in handy, since not replying seems rude, but there's really nothing to say. Having said that, now I notice your signature has both - normal slash for cores/threads, fullwidth for Haswell／Intel.

[Gemmaugr]

Off-topic:

What's with the fullwidth slash?

I'm a certified weeb and therefore have Japanese kana enabled, and it uses fullwidth characters. I'm a weirdo that doesn't like how narrow a traditional slash looks in words like and/or to the point of making the slash not very noticeable and to the point of such words looking almost more like "andor" with slightly spaced kerning.

Wait until you hear that I have shift+tab mapped to emdash — shift+backspace the multipication symbol × and shift+caps lock as division ÷ as well

Just a head's up that the currently most common way for a layman to identify AI text is through M-Dashes (which no one uses), 3-4 point lists, and emoji use. Just in case you get into trouble over it somewhere.

[Moonchild]

Off-topic:
Detecting A.I. slop isn't just about emdashes — it's also about bullet point lists, over-use of emoji , and this exact sentence structure!

[__NM64__]

Off-topic:
We're really junking up this thread now, huh?

Just a head's up that the currently most common way for a layman to identify AI text is through M-Dashes (which no one uses), 3-4 point lists, and emoji use. Just in case you get into trouble over it somewhere.

I had emdash mapped since before LLMs were really a thing, and 99.99% of my use of the emdash isn't even in sentences since I aesthetically prefer using a hyphen. In particular, I put emdash on the tab key for a reason, that being I use an emdash for long lines with no break e.g. ———————— or for sort of longer dividers like "1.2.3 — issue with thing" as well "[2025-09-04 — A1b]　filename goes here.txt" (oh yeah, full width spaces are a thing I do too).

One thing in particular is that, at least in American English grammar, an emdash shouldn't have spaces around them while, if you instead use a dash in the same way you'd use an emdash, you should put spaces around them. In other words, this is wrong:

isn't just about emdashes — it's also about

Again, at least in American English, that should be either "about emdashes—it's also" or "about emdashes - it's also. This isn't meant to be a grammar criticism, but rather pointing that LLMs very much use emdashes without spaces, and not only is it something I basically never do (I don't like the look of it) but I don't even use emdashes in that way.

If it really becomes an issue, I can just as easily map shift+tab to be the slightly-shorter endash instead

EDIT: Turns out that an endash is actually the proper character to use rather than a hyphen if you want spaces before and after the dash, e.g. "about emdashes – it's also", so maybe I'll actually just change my shift+tab key to an endash right now!

EDIT 2: Yeah, turns out I think I like the aesthetics of a fullwidth hyphen over an emdash anyway, e.g. ー for situations where I feel an endash – isn't long enough, but an endash still works perfectly for long lines with no break e.g. –––––––––––––––––––– Though a fullwidth hyphen doesn't look great in signatures on this forum and looks a little elevated off-center... oh wait, I can cheat and use a double endash instead which is the teeniest bit longer than an emdash

[BenFenner]

Off-topic:

Just a head's up that the currently most common way for a layman to identify AI text is through M-Dashes (which no one uses)

I do—all the time.

I've seen that YouTube video as well, and boy is it obnoxious that em dashes are now a sign of AI use.

Because i had to correct metadata, the current update must be taken once as
sudo apt-get --allow-releaseinfo-change update,
otherwise it will fail with
E: Repository 'https://kannegieser.net/palemoon sse2_gtk2 InRelease' changed its 'Origin' value from 'palemoon.com' to 'palemoon.org'
I am sorry for the mistake.

Thank you for this note. I have a Linux machine I haven't booted up in a while and just ran into this. I'm all set now!
(Searching thee forum for this solution was much harder than it should have been).

[jarsealer]

Is there going to be a release for PM 34.0.1 arm64? MX-23 repo already has 34.0.1 version https://mxrepo.com/MX23packages.html, but there's no .deb link for arm64 shown, even though they build for it.

[Moonchild]

Off-topic:

Turns out that an endash is actually the proper character to use rather than a hyphen if you want spaces before and after the dash

The only reason I don't use emdashes is because it's not easily available on my keyboard. But I do use (probably incorrectly for the grammar nazis out there) regular dashes. emdashes without spaces always look wrong to me, by the way -- probably because I come from a language background where hyphens in words are used a hell of a lot to make compound words.

[Kruppt]

<snip>MX-23 repo already has 34.0.1 version https://mxrepo.com/MX23packages.html<snip>

That is the 34.0.0 version

[__NM64__]

Off-topic:

Turns out that an endash is actually the proper character to use rather than a hyphen if you want spaces before and after the dash

The only reason I don't use emdashes is because it's not easily available on my keyboard. But I do use (probably incorrectly for the grammar nazis out there) regular dashes. emdashes without spaces always look wrong to me, by the way -- probably because I come from a language background where hyphens in words are used a hell of a lot to make compound words.

Note that I said eNdash in that quote - it was not a typo I assure you. (I guess I should have put "(not a typo)" after it...)

[Moonchild]

Off-topic:

Note that I said eNdash in that quote - it was not a typo I assure you. (I guess I should have put "(not a typo)" after it...)

I know what you said, I was just selectively quoting

By the way, the en dash has very limited use and cannot function as a colon, semicolon, comma or parenthesis. Using it that way is actually incorrect. The en dash is almost exclusively to be used as a replacement for "to" or "up to and including" in ranges, with some side use as a corner-case hyphenation character (for prefixing multi-word proper names, for example) and is even harder to access by the average person than an em dash

[Mæstro]

Off-topic:

The only reason I don't use emdashes is because it's not easily available on my keyboard.

On my (German Linux) keyboard layout, it is quite easy.
AltGr-hyphen yields the en dash, Shift-AltGr-hyphen em. I also enjoy easy access to the interpunct (for traditional British decimals) and ellipsis. Mozc, a plug-in for Japanese input, has also been easy for me to configure to type the permillage, numero, obelisk and diesis easily, as well as coming with Roman numerals by default. Non-breaking spaces have been my white whale in the quest for typographic correctness, to stop thousands and units detaching.

[Moonchild]

Off-topic:

AltGr-hyphen yields the en dash, Shift-AltGr-hyphen em. I also enjoy easy access to the interpunct

Unfortunately int'l keyboard layouts also almost invariably put symbols that are used all the time in programming under awkward keystrokes. []{}\|`#$%^&*<>_ are often problematic.

[Lucio Chiappetti]

Off-topic:
That's why I always bought USASCII kbd's

[Mæstro]

Off-topic:

That's why I always bought USASCII kbd's

I am the opposite. Even when studying in the States, I would import German keyboards so I could keep typing in a way I found familiar. Italy will always have my thanks for attempting to enshrine ¤ instead of $ as ASCII’s currency symbol. I mildly resent the fact that commercial symbols seldom used outside the USA (# and @ are stronger examples) have become embedded in these encodings because a group of technicians neglected global support when first designing these systems.

[Lucio Chiappetti]

Off-topic:
Guess you are too young ... my first kbds (excepting those of the card punches ) were all equal whether in Italy, UK, Netherlands or Germany. That's why I always wanted kbds with useful "programming" characters |{}[]#@$%\
Never cared a bit about accented letters (although they were on my Lettera 32 manual typewriter ), despite accented letters are used in Italian. Not to clutter this off topic, my opinions on this are in http://sax.iasf-milano.inaf.it/~lucio/W ... cents.html
BTW I have a terrible remembrance when I was working at ESOC in Darmstadt in the '80s. They had bought a text processor (not a program, a dedicated machine). It was a German text processor, but our secretary was British.

[Mæstro]

Off-topic:
In fact, I grew up using a manual typewriter, the Brother Deluxe 220.
Autistic children are sometimes encouraged to use one instead of a computer, probably because it is impossible to be distracted. I used it for all my school assignments which were not handwritten until, in my last year of compulsory education, my history teacher told me to stop. (I also insisted on using the old orthography, which I still use.) It is still sitting in its box with a pack of correction slips in my childhood home. Its layout closely resembles modern German computer keyboards, but that Shift-4 is +, not $, and there are no extra keys beyond Y, Ü and Ä. (German typography seldom requires the apostrophe, but the acute accent substituted.) It made sense to me that my keyboard and typewriter should use the same layout. Programming is not for me, but typography is.