Search
1000 results for “Ctrl_R”
-
CW: email client opinions
Switched to #Thunderbird as my main #email client, partly to see what life is like outside of #mu4e . So far I'm very pleasantly surprised.
Adding all my accounts (or at least the 5-ish I actually use) was a breeze, the UI is snappy (#Emacs really should do something about UI latency btw, it occasionally freezes even on my relatively high end workplace workstation), managing spam works much better.
Also the little UX touches, like the (optional, but on by default) confirmation dialog when you send an email with Ctrl-Enter, or the way it warns you if you mentioned an attachment but didn't attach anything... *mwah* *chef kiss*
Will I miss mu4e's query language? Maybe, but since I've given up on high volume mailing lists, I haven't really needed it. And to be honest, I didn't find the query language's syntax all that intuitive.
I do kinda miss mu4e's keyboard shortcuts. :moomin_hmm:
I'm curious to see how well Thunderbird will do on the full-text search front, because there were way too many times when I couldn't find something in mu4e. Although I think mu4e still fares better than #RoundCube.
edit: Forgot my biggest gripe: trying to print PDF attachments from mu4e was a pain. -
Cómo modificar en Firefox el desagradable sonido que reproduce al buscar un texto que no encuentra
Al buscar un texto en Firefox mediante Ctrl+F si no encuentra el texto buscado, Firefox reproduce un sonido bastante desagradable. Vamos a modificar eso para que reproduzca uno de nuestro sistema -
Kurvadopíčidoprdelezasraný. Jen chci říct, že ten, kdo ve webové aplikaci s hromadou free-text polí vymyslel tu genitální fíčuru, že CTRL+Backspace skočí na předchozí stránku, je úplnej čůrák. To nikdy nedopíšu píčivole. Konec hlášení. #hate
-
https://maildrop.cc/ to my rescue against these aggressive sign up to continue reading, pop ups.
the best thing about it is that there is no signup required — it is free for anyone to use when you need a quick, disposable email address.I was using Ctrl, Shift +C then deleting the pop up element, but now the pop up is on literally every fucking page so throwaway email address time.
-
https://maildrop.cc/ to my rescue against these aggressive sign up to continue reading, pop ups.
the best thing about it is that there is no signup required — it is free for anyone to use when you need a quick, disposable email address.I was using Ctrl, Shift +C then deleting the pop up element, but now the pop up is on literally every fucking page so throwaway email address time.
-
https://maildrop.cc/ to my rescue against these aggressive sign up to continue reading, pop ups.
the best thing about it is that there is no signup required — it is free for anyone to use when you need a quick, disposable email address.I was using Ctrl, Shift +C then deleting the pop up element, but now the pop up is on literally every fucking page so throwaway email address time.
-
https://maildrop.cc/ to my rescue against these aggressive sign up to continue reading, pop ups.
the best thing about it is that there is no signup required — it is free for anyone to use when you need a quick, disposable email address.I was using Ctrl, Shift +C then deleting the pop up element, but now the pop up is on literally every fucking page so throwaway email address time.
-
https://maildrop.cc/ to my rescue against these aggressive sign up to continue reading, pop ups.
the best thing about it is that there is no signup required — it is free for anyone to use when you need a quick, disposable email address.I was using Ctrl, Shift +C then deleting the pop up element, but now the pop up is on literally every fucking page so throwaway email address time.
-
RT @om_patel5: DIESER 17-JÄHRIGE SOFTWARE-INGENIEUR HAT SICH ÜBER CLAUDE CODE HERGEMACHT UND ES ALS VÖLLIGEN MÜLL BEZEICHNET. DIESER MANN SCHREIBT SEIT 2008 CODE. ER NUTZTE KI SEIT MÄRZ. ER HAT DEN 5X MAX PLAN SEIT DEM ERSTEN TAG. ANFANGS WAR ER BEGEISTERT. 3-4 SITZUNGEN LIEFEN PARALLEL IN TMUX DEN GANZEN TAG. COMMITS IN SEKUNDEN. ANTWORTEN IN SEKUNDEN. IMPLEMENTIERUNGEN IN MINUTEN. ER HATTE DIE LIMITS KAUM ERREICHT. DANN KAM OPUS 4.7 UND ALLES BRACH ZUSAMMEN. VORHER NACHHER: " "commit this" dauerte Sekunden. Jetzt 30 Sekunden. " "implement this plan" dauerte Minuten. Jetzt 45 Minuten. " Terminal-Resizing wrappte Text sauber. Jetzt werden Zeilen vermischt und Diffs abgeschnitten. " ctrl+o zeigte den vollen Denkprozess. Jetzt zeigt es nichts Nützliches. " Es sagt jetzt "fast fertig mit Denken", was niemandem hilft. " Er erreicht ständig die Limits, auch nachdem er gelernt hat, Opus für Planung und Sonnet für Änderungen zu trennen. DER SCHLIMMSTE TEIL: ES IGNORIERT ANWEISUNGEN. ER HAT CLAUDE TAUSENDE MAL GELEHRT, KURZE TIMEOUTS (10-15 SEKUNDEN) FÜR NETZWERKPROGRAMMIERUNG ZU VERWENDEN. ER HATTE ES IM GEDÄCHTNIS. INNERHALB EINES IMPLEMENTIERUNGSZYKLUS WECHSELT CLAUDE ZURÜCK ZU 30S, 60S, 5 MINUTEN. ER HAT CLAUDE EIN MILLIARDE MAL GELEHRT "NIEMALS AUTO-COMMIT". NACH EINER WEILE FÄNGT CLAUDE WIEDER AN, AUTO-COMMITS DURCHZUFÜHREN. DER MANN NUTZT /caveman MODE FÜR KÜRZE. CLAUDE VERGESST ES UND SPÜLT NACH JEDER IMPLEMENTIERUNG EINEN TEXTWALL AUS. CLAUDE KANN SICH SCHON EINE EINFACHE 200-LINIGE PLANUNG NICHT MEHR MERKEN. DER PLAN SAGTE: "ÄNDERE DIE SIGNATUR VON handleinput, DAMIT SIE BYTES STATT &[u…
mehr auf Arint.info
#AI #ClaudeCode #DeveloperLife #Opus47 #SoftwareEngineering #TechFrustration #arint_info
-
RT @om_patel5: DIESER 17-JÄHRIGE SOFTWARE-INGENIEUR HAT SICH ÜBER CLAUDE CODE HERGEMACHT UND ES ALS VÖLLIGEN MÜLL BEZEICHNET. DIESER MANN SCHREIBT SEIT 2008 CODE. ER NUTZTE KI SEIT MÄRZ. ER HAT DEN 5X MAX PLAN SEIT DEM ERSTEN TAG. ANFANGS WAR ER BEGEISTERT. 3-4 SITZUNGEN LIEFEN PARALLEL IN TMUX DEN GANZEN TAG. COMMITS IN SEKUNDEN. ANTWORTEN IN SEKUNDEN. IMPLEMENTIERUNGEN IN MINUTEN. ER HATTE DIE LIMITS KAUM ERREICHT. DANN KAM OPUS 4.7 UND ALLES BRACH ZUSAMMEN. VORHER NACHHER: " "commit this" dauerte Sekunden. Jetzt 30 Sekunden. " "implement this plan" dauerte Minuten. Jetzt 45 Minuten. " Terminal-Resizing wrappte Text sauber. Jetzt werden Zeilen vermischt und Diffs abgeschnitten. " ctrl+o zeigte den vollen Denkprozess. Jetzt zeigt es nichts Nützliches. " Es sagt jetzt "fast fertig mit Denken", was niemandem hilft. " Er erreicht ständig die Limits, auch nachdem er gelernt hat, Opus für Planung und Sonnet für Änderungen zu trennen. DER SCHLIMMSTE TEIL: ES IGNORIERT ANWEISUNGEN. ER HAT CLAUDE TAUSENDE MAL GELEHRT, KURZE TIMEOUTS (10-15 SEKUNDEN) FÜR NETZWERKPROGRAMMIERUNG ZU VERWENDEN. ER HATTE ES IM GEDÄCHTNIS. INNERHALB EINES IMPLEMENTIERUNGSZYKLUS WECHSELT CLAUDE ZURÜCK ZU 30S, 60S, 5 MINUTEN. ER HAT CLAUDE EIN MILLIARDE MAL GELEHRT "NIEMALS AUTO-COMMIT". NACH EINER WEILE FÄNGT CLAUDE WIEDER AN, AUTO-COMMITS DURCHZUFÜHREN. DER MANN NUTZT /caveman MODE FÜR KÜRZE. CLAUDE VERGESST ES UND SPÜLT NACH JEDER IMPLEMENTIERUNG EINEN TEXTWALL AUS. CLAUDE KANN SICH SCHON EINE EINFACHE 200-LINIGE PLANUNG NICHT MEHR MERKEN. DER PLAN SAGTE: "ÄNDERE DIE SIGNATUR VON handleinput, DAMIT SIE BYTES STATT &[u…
mehr auf Arint.info
#AI #ClaudeCode #DeveloperLife #Opus47 #SoftwareEngineering #TechFrustration #arint_info
-
RT @om_patel5: DIESER 17-JÄHRIGE SOFTWARE-INGENIEUR HAT SICH ÜBER CLAUDE CODE HERGEMACHT UND ES ALS VÖLLIGEN MÜLL BEZEICHNET. DIESER MANN SCHREIBT SEIT 2008 CODE. ER NUTZTE KI SEIT MÄRZ. ER HAT DEN 5X MAX PLAN SEIT DEM ERSTEN TAG. ANFANGS WAR ER BEGEISTERT. 3-4 SITZUNGEN LIEFEN PARALLEL IN TMUX DEN GANZEN TAG. COMMITS IN SEKUNDEN. ANTWORTEN IN SEKUNDEN. IMPLEMENTIERUNGEN IN MINUTEN. ER HATTE DIE LIMITS KAUM ERREICHT. DANN KAM OPUS 4.7 UND ALLES BRACH ZUSAMMEN. VORHER NACHHER: " "commit this" dauerte Sekunden. Jetzt 30 Sekunden. " "implement this plan" dauerte Minuten. Jetzt 45 Minuten. " Terminal-Resizing wrappte Text sauber. Jetzt werden Zeilen vermischt und Diffs abgeschnitten. " ctrl+o zeigte den vollen Denkprozess. Jetzt zeigt es nichts Nützliches. " Es sagt jetzt "fast fertig mit Denken", was niemandem hilft. " Er erreicht ständig die Limits, auch nachdem er gelernt hat, Opus für Planung und Sonnet für Änderungen zu trennen. DER SCHLIMMSTE TEIL: ES IGNORIERT ANWEISUNGEN. ER HAT CLAUDE TAUSENDE MAL GELEHRT, KURZE TIMEOUTS (10-15 SEKUNDEN) FÜR NETZWERKPROGRAMMIERUNG ZU VERWENDEN. ER HATTE ES IM GEDÄCHTNIS. INNERHALB EINES IMPLEMENTIERUNGSZYKLUS WECHSELT CLAUDE ZURÜCK ZU 30S, 60S, 5 MINUTEN. ER HAT CLAUDE EIN MILLIARDE MAL GELEHRT "NIEMALS AUTO-COMMIT". NACH EINER WEILE FÄNGT CLAUDE WIEDER AN, AUTO-COMMITS DURCHZUFÜHREN. DER MANN NUTZT /caveman MODE FÜR KÜRZE. CLAUDE VERGESST ES UND SPÜLT NACH JEDER IMPLEMENTIERUNG EINEN TEXTWALL AUS. CLAUDE KANN SICH SCHON EINE EINFACHE 200-LINIGE PLANUNG NICHT MEHR MERKEN. DER PLAN SAGTE: "ÄNDERE DIE SIGNATUR VON handleinput, DAMIT SIE BYTES STATT &[u…
mehr auf Arint.info
#AI #ClaudeCode #DeveloperLife #Opus47 #SoftwareEngineering #TechFrustration #arint_info
-
RT @om_patel5: DIESER 17-JÄHRIGE SOFTWARE-INGENIEUR HAT SICH ÜBER CLAUDE CODE HERGEMACHT UND ES ALS VÖLLIGEN MÜLL BEZEICHNET. DIESER MANN SCHREIBT SEIT 2008 CODE. ER NUTZTE KI SEIT MÄRZ. ER HAT DEN 5X MAX PLAN SEIT DEM ERSTEN TAG. ANFANGS WAR ER BEGEISTERT. 3-4 SITZUNGEN LIEFEN PARALLEL IN TMUX DEN GANZEN TAG. COMMITS IN SEKUNDEN. ANTWORTEN IN SEKUNDEN. IMPLEMENTIERUNGEN IN MINUTEN. ER HATTE DIE LIMITS KAUM ERREICHT. DANN KAM OPUS 4.7 UND ALLES BRACH ZUSAMMEN. VORHER NACHHER: " "commit this" dauerte Sekunden. Jetzt 30 Sekunden. " "implement this plan" dauerte Minuten. Jetzt 45 Minuten. " Terminal-Resizing wrappte Text sauber. Jetzt werden Zeilen vermischt und Diffs abgeschnitten. " ctrl+o zeigte den vollen Denkprozess. Jetzt zeigt es nichts Nützliches. " Es sagt jetzt "fast fertig mit Denken", was niemandem hilft. " Er erreicht ständig die Limits, auch nachdem er gelernt hat, Opus für Planung und Sonnet für Änderungen zu trennen. DER SCHLIMMSTE TEIL: ES IGNORIERT ANWEISUNGEN. ER HAT CLAUDE TAUSENDE MAL GELEHRT, KURZE TIMEOUTS (10-15 SEKUNDEN) FÜR NETZWERKPROGRAMMIERUNG ZU VERWENDEN. ER HATTE ES IM GEDÄCHTNIS. INNERHALB EINES IMPLEMENTIERUNGSZYKLUS WECHSELT CLAUDE ZURÜCK ZU 30S, 60S, 5 MINUTEN. ER HAT CLAUDE EIN MILLIARDE MAL GELEHRT "NIEMALS AUTO-COMMIT". NACH EINER WEILE FÄNGT CLAUDE WIEDER AN, AUTO-COMMITS DURCHZUFÜHREN. DER MANN NUTZT /caveman MODE FÜR KÜRZE. CLAUDE VERGESST ES UND SPÜLT NACH JEDER IMPLEMENTIERUNG EINEN TEXTWALL AUS. CLAUDE KANN SICH SCHON EINE EINFACHE 200-LINIGE PLANUNG NICHT MEHR MERKEN. DER PLAN SAGTE: "ÄNDERE DIE SIGNATUR VON handleinput, DAMIT SIE BYTES STATT &[u…
mehr auf Arint.info
#AI #ClaudeCode #DeveloperLife #Opus47 #SoftwareEngineering #TechFrustration #arint_info
-
RT @om_patel5: DIESER 17-JÄHRIGE SOFTWARE-INGENIEUR HAT SICH ÜBER CLAUDE CODE HERGEMACHT UND ES ALS VÖLLIGEN MÜLL BEZEICHNET. DIESER MANN SCHREIBT SEIT 2008 CODE. ER NUTZTE KI SEIT MÄRZ. ER HAT DEN 5X MAX PLAN SEIT DEM ERSTEN TAG. ANFANGS WAR ER BEGEISTERT. 3-4 SITZUNGEN LIEFEN PARALLEL IN TMUX DEN GANZEN TAG. COMMITS IN SEKUNDEN. ANTWORTEN IN SEKUNDEN. IMPLEMENTIERUNGEN IN MINUTEN. ER HATTE DIE LIMITS KAUM ERREICHT. DANN KAM OPUS 4.7 UND ALLES BRACH ZUSAMMEN. VORHER NACHHER: " "commit this" dauerte Sekunden. Jetzt 30 Sekunden. " "implement this plan" dauerte Minuten. Jetzt 45 Minuten. " Terminal-Resizing wrappte Text sauber. Jetzt werden Zeilen vermischt und Diffs abgeschnitten. " ctrl+o zeigte den vollen Denkprozess. Jetzt zeigt es nichts Nützliches. " Es sagt jetzt "fast fertig mit Denken", was niemandem hilft. " Er erreicht ständig die Limits, auch nachdem er gelernt hat, Opus für Planung und Sonnet für Änderungen zu trennen. DER SCHLIMMSTE TEIL: ES IGNORIERT ANWEISUNGEN. ER HAT CLAUDE TAUSENDE MAL GELEHRT, KURZE TIMEOUTS (10-15 SEKUNDEN) FÜR NETZWERKPROGRAMMIERUNG ZU VERWENDEN. ER HATTE ES IM GEDÄCHTNIS. INNERHALB EINES IMPLEMENTIERUNGSZYKLUS WECHSELT CLAUDE ZURÜCK ZU 30S, 60S, 5 MINUTEN. ER HAT CLAUDE EIN MILLIARDE MAL GELEHRT "NIEMALS AUTO-COMMIT". NACH EINER WEILE FÄNGT CLAUDE WIEDER AN, AUTO-COMMITS DURCHZUFÜHREN. DER MANN NUTZT /caveman MODE FÜR KÜRZE. CLAUDE VERGESST ES UND SPÜLT NACH JEDER IMPLEMENTIERUNG EINEN TEXTWALL AUS. CLAUDE KANN SICH SCHON EINE EINFACHE 200-LINIGE PLANUNG NICHT MEHR MERKEN. DER PLAN SAGTE: "ÄNDERE DIE SIGNATUR VON handleinput, DAMIT SIE BYTES STATT &[u…
mehr auf Arint.info
#AI #ClaudeCode #DeveloperLife #Opus47 #SoftwareEngineering #TechFrustration #arint_info
-
Join Kurt Trowbridge for *Ctrl+Alt+Delegate* at #MidCamp2026!
💡 Learn how to:
🔑 Delegate effectively
📈 Scale your impact
🤝 Build stronger teams📍 Room 312 | Wed 10:00–10:45 AM CDT
🔗 Register: https://midcamp.org/tickets
👨💻 Learn more: https://www.midcamp.org/events/2026/sessions/ctrl-alt-delegate-keys-to-the-shift-from-developer-to-leader -
RE: https://mastodon.ktachibana.party/@Soybean/116480400932649929
#Filco majestouch convertible 2 是我用的最久的一把
中途 A 键坏了，我还自己买了个电烙铁把它修好
后来蓝牙连接经常出现卡键和断连（不确定是周围蓝牙设备太多了还是主控老化了），mini USB 又太不方便，（又没有无线接收器连接方式），Cheery 专利又到期导致机械键盘平价化，换了把便宜国产的。然而同样是 Cherry 红轴，便宜国产的手感要差很多
它自带 Ctrl 和 Caps Lock 互换（附带额外的键帽），侧刻的键帽，Fn + Windows 键 = 菜单键，F 数字键带媒体控制，感觉是最全面的一把键盘 -
SOLUTION: @gumnos came up with the idea of piggy-backing
:nohlonto control-l for refresh:nmap <C-L> :nohl<CR><C-L imap <C-L> <Esc>:nohl<CR><C-L>aHey #vim wizards,
The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and
:nohlis a little clumsy to type in a hurry.I wanted to map
:nohlto an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.Any ideas?
" map Ctrl-/ to :nohl nmap <c-Slash> :nohl<CR> imap <c-Slash> <Esc>:nohl<CR>a -
SOLUTION: @gumnos came up with the idea of piggy-backing
:nohlonto control-l for refresh:nmap <C-L> :nohl<CR><C-L imap <C-L> <Esc>:nohl<CR><C-L>aHey #vim wizards,
The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and
:nohlis a little clumsy to type in a hurry.I wanted to map
:nohlto an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.Any ideas?
" map Ctrl-/ to :nohl nmap <c-Slash> :nohl<CR> imap <c-Slash> <Esc>:nohl<CR>a -
SOLUTION: @gumnos came up with the idea of piggy-backing
:nohlonto control-l for refresh:nmap <C-L> :nohl<CR><C-L imap <C-L> <Esc>:nohl<CR><C-L>aHey #vim wizards,
The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and
:nohlis a little clumsy to type in a hurry.I wanted to map
:nohlto an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.Any ideas?
" map Ctrl-/ to :nohl nmap <c-Slash> :nohl<CR> imap <c-Slash> <Esc>:nohl<CR>a -
SOLUTION: @gumnos came up with the idea of piggy-backing
:nohlonto control-l for refresh:nmap <C-L> :nohl<CR><C-L imap <C-L> <Esc>:nohl<CR><C-L>aHey #vim wizards,
The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and
:nohlis a little clumsy to type in a hurry.I wanted to map
:nohlto an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.Any ideas?
" map Ctrl-/ to :nohl nmap <c-Slash> :nohl<CR> imap <c-Slash> <Esc>:nohl<CR>a -
SOLUTION: @gumnos came up with the idea of piggy-backing
:nohlonto control-l for refresh:nmap <C-L> :nohl<CR><C-L imap <C-L> <Esc>:nohl<CR><C-L>aHey #vim wizards,
The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and
:nohlis a little clumsy to type in a hurry.I wanted to map
:nohlto an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.Any ideas?
" map Ctrl-/ to :nohl nmap <c-Slash> :nohl<CR> imap <c-Slash> <Esc>:nohl<CR>a -
#TIL (from a Firefox 150 release press article, of all places) that there's a native Gtk emoji picker accessible with `Ctrl-.` 🤯️
And there goes my main UX issue with #PhanpySocial, which only has an emoji picker for your custom instance emoji. Maybe that means fewer blobcats in my future
-
Reminder system, component #381.6: https://starbeamrainbowlabs.com/msg.html
By writing a message and using the *send tab to device feature*, I can send myself little messages I know I'll see when I sit down at that target device.
It's also got a feature to help with furiganising 日本語のかんじ with ctrl + f ✨
#WebBrowsing #Reminders #LifeHacks #Tool #Japanese #日本語 #Furigana #HowDoITag
-
Reminder system, component #381.6: https://starbeamrainbowlabs.com/msg.html
By writing a message and using the *send tab to device feature*, I can send myself little messages I know I'll see when I sit down at that target device.
It's also got a feature to help with furiganising 日本語のかんじ with ctrl + f ✨
#WebBrowsing #Reminders #LifeHacks #Tool #Japanese #日本語 #Furigana #HowDoITag
-
Reminder system, component #381.6: https://starbeamrainbowlabs.com/msg.html
By writing a message and using the *send tab to device feature*, I can send myself little messages I know I'll see when I sit down at that target device.
It's also got a feature to help with furiganising 日本語のかんじ with ctrl + f ✨
#WebBrowsing #Reminders #LifeHacks #Tool #Japanese #日本語 #Furigana #HowDoITag
-
We just posted our CTRL-OS April update on the NixOS Discourse!
What's new:
→ CTRL-OS 26.05 is coming (5-year LTS based on NixOS 26.05)
→ New security tracker at security.ctrl-os.com
→ Nvidia Jetson Orin Nano support
→ Roadmap: FIDO Device Onboarding & Cyber Resilience Act complianceFull update: https://discourse.nixos.org/t/ctrl-os-april-update-5-year-lts-downstream-of-nixos/76912
-
Sharing a post I read:
📑 Shell Tricks That Actually Make Life Easier (And Save Your Sanity) | Larvitz Blog
Watch someone backspace 40 characters instead of pressing CTRL+W, and you’ll understand why this list exists.
https://blog.hofstede.it/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/
-
@wrog @dougmerritt @ramin_hal9001 @screwlisp @cdegroot
Funny, I couldn't recall "~" being important at all so had to go check. See https://codeberg.org/PDP-10/its/src/branch/master/doc/_teco_/tecord.1132 and while I do see a few uses of it, they seem very minor.
I read this into an Emacs editor buffer and did "M-x occur" looking for [~] and got these, all of which seem highly obscure. I think it is probably because in the early days there may have been a desire not to have case matter, so the upper and lower case versions of these special characters (see line 2672 below) may have once been equivalent or might have some reason to want to reserve space to be equivalent in some cases. Remember that, for example, on a VT52, he CTRL key did not add a control bit but masked out all the bits beyond the 5th, so that CTRL+@ and CTRL+Space were the same (null) character, for example. And sometimes tools masked out the 7th bit in order to uppercase something, which means that certain characters like these might have in some cases gotten blurred.
10 matches for "[~]" in buffer: tecord.1132
1270: use a F~ to compare the error message string against a
2017: case special character" (one of "`{|}~<rubout>").
2235: the expected ones, with F~.
2370: kept in increasing order, as F~ would say, or FO's binary
2672: also ("@[\]^_" = "`{|}~<rubout>").
4192:F~ compares strings, ignoring case difference. It is just
4446: this option include F^A, F^E, F=, FQ, F~, G and M.
4942: string storage space, but begins with a "~" (ASCII 176)
4977: character should be the rubout beginning a string or the "~"
4980: "~" or rubout, then it is not a pointer - just a plain number.If I recall correctly, this also meant in some tools it was possible if you were using a control-prefix con CTRL-^ to have CTRL-^ CTRL-@ be different than CTRL-^ @ because one of them might set the control bit on @ and the other on null, so there was a lot of ailasing. It even happened for regular characters that CTRL-^ CTRL-A would get you a control bit set on #o1 while CTRL+^ A would get you the control bit set on 65. Some of these worked very differently on the Knight TV, which used SAIL characters, I think, and which thought a code like 1 was an uparrow, not a control-A. There were a lot of blurry areas, and it was hell on people who wanted to make a Dvorak mode because it was the VT52 (and probably VT100 and AAA) hardware that was doing this translation, so there was no place to software intercept all this and make it different, so that's probably why something as important as Teco treaded lightly on making some case distinctions.
But if someone remembers, better, please let me know. It's been 4+ decades since I used this stuff a lot and details slip away. It's just that these things linger, I think, because they were so important to realize were live rails not to tread upon. And because I did, for a while, live and breathe this stuff, since I wrote a few TECO libraries (like ZBABYL and the original TeX mode), so I guess practice drills it in, too.
-
@wrog @dougmerritt @ramin_hal9001 @screwlisp @cdegroot
Funny, I couldn't recall "~" being important at all so had to go check. See https://codeberg.org/PDP-10/its/src/branch/master/doc/_teco_/tecord.1132 and while I do see a few uses of it, they seem very minor.
I read this into an Emacs editor buffer and did "M-x occur" looking for [~] and got these, all of which seem highly obscure. I think it is probably because in the early days there may have been a desire not to have case matter, so the upper and lower case versions of these special characters (see line 2672 below) may have once been equivalent or might have some reason to want to reserve space to be equivalent in some cases. Remember that, for example, on a VT52, he CTRL key did not add a control bit but masked out all the bits beyond the 5th, so that CTRL+@ and CTRL+Space were the same (null) character, for example. And sometimes tools masked out the 7th bit in order to uppercase something, which means that certain characters like these might have in some cases gotten blurred.
10 matches for "[~]" in buffer: tecord.1132
1270: use a F~ to compare the error message string against a
2017: case special character" (one of "`{|}~<rubout>").
2235: the expected ones, with F~.
2370: kept in increasing order, as F~ would say, or FO's binary
2672: also ("@[\]^_" = "`{|}~<rubout>").
4192:F~ compares strings, ignoring case difference. It is just
4446: this option include F^A, F^E, F=, FQ, F~, G and M.
4942: string storage space, but begins with a "~" (ASCII 176)
4977: character should be the rubout beginning a string or the "~"
4980: "~" or rubout, then it is not a pointer - just a plain number.If I recall correctly, this also meant in some tools it was possible if you were using a control-prefix con CTRL-^ to have CTRL-^ CTRL-@ be different than CTRL-^ @ because one of them might set the control bit on @ and the other on null, so there was a lot of ailasing. It even happened for regular characters that CTRL-^ CTRL-A would get you a control bit set on #o1 while CTRL+^ A would get you the control bit set on 65. Some of these worked very differently on the Knight TV, which used SAIL characters, I think, and which thought a code like 1 was an uparrow, not a control-A. There were a lot of blurry areas, and it was hell on people who wanted to make a Dvorak mode because it was the VT52 (and probably VT100 and AAA) hardware that was doing this translation, so there was no place to software intercept all this and make it different, so that's probably why something as important as Teco treaded lightly on making some case distinctions.
But if someone remembers, better, please let me know. It's been 4+ decades since I used this stuff a lot and details slip away. It's just that these things linger, I think, because they were so important to realize were live rails not to tread upon. And because I did, for a while, live and breathe this stuff, since I wrote a few TECO libraries (like ZBABYL and the original TeX mode), so I guess practice drills it in, too.
-
@wrog @dougmerritt @ramin_hal9001 @screwlisp @cdegroot
Funny, I couldn't recall "~" being important at all so had to go check. See https://codeberg.org/PDP-10/its/src/branch/master/doc/_teco_/tecord.1132 and while I do see a few uses of it, they seem very minor.
I read this into an Emacs editor buffer and did "M-x occur" looking for [~] and got these, all of which seem highly obscure. I think it is probably because in the early days there may have been a desire not to have case matter, so the upper and lower case versions of these special characters (see line 2672 below) may have once been equivalent or might have some reason to want to reserve space to be equivalent in some cases. Remember that, for example, on a VT52, he CTRL key did not add a control bit but masked out all the bits beyond the 5th, so that CTRL+@ and CTRL+Space were the same (null) character, for example. And sometimes tools masked out the 7th bit in order to uppercase something, which means that certain characters like these might have in some cases gotten blurred.
10 matches for "[~]" in buffer: tecord.1132
1270: use a F~ to compare the error message string against a
2017: case special character" (one of "`{|}~<rubout>").
2235: the expected ones, with F~.
2370: kept in increasing order, as F~ would say, or FO's binary
2672: also ("@[\]^_" = "`{|}~<rubout>").
4192:F~ compares strings, ignoring case difference. It is just
4446: this option include F^A, F^E, F=, FQ, F~, G and M.
4942: string storage space, but begins with a "~" (ASCII 176)
4977: character should be the rubout beginning a string or the "~"
4980: "~" or rubout, then it is not a pointer - just a plain number.If I recall correctly, this also meant in some tools it was possible if you were using a control-prefix con CTRL-^ to have CTRL-^ CTRL-@ be different than CTRL-^ @ because one of them might set the control bit on @ and the other on null, so there was a lot of ailasing. It even happened for regular characters that CTRL-^ CTRL-A would get you a control bit set on #o1 while CTRL+^ A would get you the control bit set on 65. Some of these worked very differently on the Knight TV, which used SAIL characters, I think, and which thought a code like 1 was an uparrow, not a control-A. There were a lot of blurry areas, and it was hell on people who wanted to make a Dvorak mode because it was the VT52 (and probably VT100 and AAA) hardware that was doing this translation, so there was no place to software intercept all this and make it different, so that's probably why something as important as Teco treaded lightly on making some case distinctions.
But if someone remembers, better, please let me know. It's been 4+ decades since I used this stuff a lot and details slip away. It's just that these things linger, I think, because they were so important to realize were live rails not to tread upon. And because I did, for a while, live and breathe this stuff, since I wrote a few TECO libraries (like ZBABYL and the original TeX mode), so I guess practice drills it in, too.
