printf("%s", name);Is this a limitation of scanf() or bad control flow?
https://piefed.blahaj.zone/c/c_lang/p/791681/is-this-a-limitation-of-scanf-or-bad-control-flow
Alexey SkobkinСегодня наконец-то добрался до этого и сел снова настраивать японский ввод с Fcitx5+Mozc.
И в этот раз настроил.
В прошлый раз делал заметно по-другому: старый fcitx, ibus, Plasma 5, X.
В этот раз Fcitx5, Wayland Launcher, Plasma 6.
И на этот раз всё завелось и изменений каких-то в системе понадобилось меньше.
Радует, что и в таких нишевых штуках линуксы становятся дружелюбнее.
Но да, надо сказать, что это всё ещё достаточно далеко от того как это работает в Windows, где просто добавляешь ещё один язык и выставляешь для него настройки ввода.
Здесь же вырубается дефолтное переключение раскладок в DE и управление ими передаётся отдельному виртуальному менеджеру ввода.
Понятно, что и в Windows под капотом скорее всего происходит что-то похожее. Но для юзера это происходит в одной точке входа. А этих наших линуксах - не так. Если нужна обычная дубовая раскладка физической клавиатуры - можно использовать обычное xkb-like переключение. А вот если нужна раскладка с вводом ромадзи и заменой по словарю - это вообще другое и пользователю об этом нужно откуда-то узнать.
Такие дела.
#Linux #language #Japanese #Wayland #Fcitx #Mozc #UX #UI #log #input
Brad LinderHyperSpace TrackPad Pro is canceled, Hyper promises refunds to Kickstarter backers
The HyperSpace TrackPad Pro was designed to be the best external TrackPad available for Windows PCs. With a large touch surface, haptic feedback, force detection, wired and wireless support, and software that lets you assign configurable actions to the four “dynamic action zones” in the corners.
Unfortunately it’s not actually going to ship. Hyper has posted an update on the Kickstarter […]
#crowdfunding #hyper #hyperspaceTrackpadOne #input #trackpad Read more: https://liliputing.com/hyperspace-trackpad-pro-is-canceled-hyper-promises-refunds-to-kickstarter-backers/
(Roughly) Daily“Do not fold, spindle, or mutilate”*…
Punched cards have a long history in machine control (dating back to Jacquard) and computing (starting with Babbage‘s Difference Engine), but it was Herman Hollerith who brought them into modern computation in the late 1880s… where punch cards remained for about 100 years. From the Smithsonian’s American History Museum…
In the late 1880s, American engineer Herman Hollerith saw a railroad punch card when he was trying to figure out new ways of compiling statistical information for the U.S. Census. His first punch card, like those used on railways, only had holes along the edges. The meaning of each hole was indicated on the card. By the time Hollerith tabulating equipment was used in the 1890 U.S. Census, holes were scattered across the cards, although their meaning was not indicated on it.
Hollerith and his employees at the Tabulating Machine Company in Washington, D.C. soon developed punched cards for use in compiling information for commercial enterprises such as railroads. They and staff of the U.S. Census Bureau prepared improved machines—these devices are shown in the object group on tabulating equipment. By the 1920s, the United States had two major manufacturers of punch card equipment, International Business Machines (the descendent of the Tabulating Machine Company) and Remington Rand (the descendent of Powers Accounting Machine Company established by Russian emigré and former Census Bureau employee James Powers). Each manufacturer developed a distinctive standard punch card. IBM cards had eighty columns of rectangular holes while those of Remington Rand had ninety columns of circular holes. Tabulating machines were widely used in both government and commerce, with cards designed to meet the needs of customers. For example, checks issued by the U.S. government often came on punch cards.
When IBM and Remington Rand began selling electronic computers in the years following World War II, punch cards became the preferred method of entering data and programs onto them. They also were used in later minicomputers and some early desktop calculators. Punch cards surviving in the Smithsonian collections reflect the widespread use of computers – they announced scores on standardized tests, served as a library cards, were part of the proof of mathematical theorems, and kept medical records. Some are printed with the names of users, from university computer centers and computer clubs to the Library of Congress to Bell Laboratories…
Browse the collection: “Punch Cards for Data Processing“
See also: here, here, and here.
* Ubiquitous warning on punch cards:
… in the 1950s, after the invention of the computer and its widespread business use, that everyone began to see punch cards. Companies sent punch cards out with bills: the telephone company, utility companies, and even department stores realized that they could save a step in their billing process, as well as making it easier for them to process the returned check, by using the cards themselves as the bills. By the 1960s, punch cards were familiar, everyday objects.
While company employees could be trusted to take care of the cards, the person in the street could not. Warnings were necessary. In the 1930s the University of Iowa used cards for student registration; on each card was printed “Do not fold or bend this card.” Cards reproduced in an IBM sales brochure of the 1930s read “Do not fold, tear, or mutilate this card” and “Do not fold tear or destroy.” I’m not sure when the canonical “Do not fold, spindle, or mutilate” first appeared; it’s one of those traditions whose author and origin is lost in the mists of time. Let’s consider the words one at a time, stop and take them seriously…
– “A Cultural History of the Punch Card” (from 1991; eminently worth reading in full)
###
As we contemplate chads (of which, punch cards produced a gracious plenty), we might spare a thought for Gerald Hawkins; he died on this date in 2003. An astronomer and author, he was best known for his work in archaeoastronomy— most of all, for his 1965 book, Stonehenge Decoded. In the early 1960s, Hawkins had used punch cards to load data modeling sun and moon movements onto magnetic tapes, then into an IBM 7090. The results led him to conclude, as the book argues, that the features at the monument were arranged in such a way as to predict a variety of astronomical events– that Stonehenge was a giant prehistoric observatory and computer. While some archaeologists are hesitant to accept Hawkins’ theories, many archaeoastronomers have built upon his work. More widely, scholars accept that the importance of astronomical alignment and large complexes being planned and constructed to fulfill cosmology has been demonstrated at other prehistoric sites, such as the Snake Mound and Cahokia in the U.S.
#archaeoastronomy #astronomy #Babbage #Census #CharlesBabbage #computing #culture #data #GeraldHawkins #HermanHollerith #history #historyOfComputing #Hollerith #input #Jacquard #punchCard #punchCards #Stonehenge #storage #Technology
U3dn
Ron PiggottWhat My Friends Mean To Me Answer #17: My friends bring momentum to my dreams. https://rons-home.net/en/living-life-lab/personal-growth/what-my-friends-mean-to-me/answer-of-the-day/2026/05/19 #input #suggestion #brainstorm
Karel 'Clock' K.@sutaio IMO the user experience (UX) of Linux is absolutely horrible.
If your Khmer keyboard doesn't work on Linux and inputs nonsense characters instead of compound vowels like ោះ ុំ in words like ខ្ញុំ បោះ , add GTK_IM_MODULE=xim into /etc/environment and logout/login from X.Fixed for me both in RPi OS (Debian) and EndeavourOS (Arch).
I had to painstakingly search through 224 photos of 5 years old paper notes to find the proper Linux workaround to figure this out again after I was forced to reinstall due to Raspberry Pi OS not officially supporting major version upgrade and serious Linux kernel bugs like Copy Fail and Dirty Frag.
It's not obvious from the problem that this should be done. Why not ship Linux with properly working Khmer keyboard in the first place?
#linux #gtk #input #keyboard #khmer #khmerunicode #bug #buggy #inputmethod #GTK_IM_MODULE #xim #ux #badux #horrible #defect #defective #khmeros #copyfail #dirtyfrag #endeavouros #arch #debian
IMO the user experience (UX) of Linux is absolutely horrible.
If your Khmer keyboard doesn't work on Linux and inputs nonsense characters instead of compound vowels like ោះ ុំ in words like ខ្ញុំ បោះ , add GTK_IM_MODULE=xim into /etc/environment and logout/login from X. Fixed for me both in Raspberry Pi OS (Debian) and EndeavourOS (Arch).
I had to painstakingly search through 224 photos of 5 years old paper notes to find the proper Linux workaround to figure this out again after I was forced to reinstall due to Raspberry Pi OS not officially supporting major version upgrade and serious Linux kernel bugs like Copy Fail and Dirty Frag.
It's not obvious from the problem that this should be done. Why not ship Linux with properly working Khmer keyboard in the first place?
#linux #gtk #input #keyboard #khmer #khmerunicode #bug #buggy #inputmethod #GTK_IM_MODULE #xim #ux #badux #horrible #defect #defective #khmeros #copyfail #dirtyfrag #endeavouros #arch #debian
THANK YOU ALL!!! - what errors should I check for and handle?
Thank you all for your kind, patient and educative responses when I obnoxiously post amateur questions! 💙 While I cannot make any promises because of how my brain works, I am almost ready to continue reading *The C Programming Language, 2nd Edition”. I just want to experiment a little bit with error handling, specifially how to handle wrong input (char VS. int, etc.) and also to learn to indentify code that runs the risk of overflow/underflow.
Question: what errors do you recommend checking for and handling?
Meanwhile, thank you all! 🥰
#include <stdio.h>
//Function declarations
int newPin();
int checkPin(int i);
//Program that prompts for, verifies and saves pins temporarily into an array
int main() {
//New pin
int pin = 0;
//History
int history[10] = {0,0,0,0,0,0,0,0,0,0};
int history_limit = 10;
int history_index = 0;
printf("Hello there! What would you like to do? (V)iew your saved pins, (S)ave a new pin or (E)xit: ");
int choice = 0;
while ((choice = getchar()) != EOF) {
switch (choice) {
case ('V'): { //Display saved pins
printf("\nYour saved pins are:\n\n");
for (int i = 0; i < history_limit; i++) printf("%d\n", history[i]);
printf("\nWhat would you like to do next? (V)iew your saved pins, (S)ave a new pin or (E)xit: ");
break;
}
case('S'): { //Prompt for and verify newly entered pin
pin = newPin();
if (checkPin(pin) == pin) {
history[history_index] = pin;
history_index++;
if (history_index >= history_limit) history_index = 0;
}
break;
}
case ('E'): goto EXIT; //Terminate program
}
}
EXIT: printf("\nGoodbye!\n");
return 0;
}
//Function definitions
//Prompt user to enter a new pin
int newPin() {
int pin = 0;
printf("This enter your pin: ");
scanf("%d", &pin);
getchar();
return pin;
}
//Verify newly entered pin
int checkPin (int i) {
int check = 0;
printf("Confirm your new pin: ");
while((scanf("%d", &check)) != EOF) {
if (check != i) printf("Mismatch! Confirm your new pin: ");
else if (check == i) {
printf("Success! Your new pin is %d. What would you like to do next? (V)iew your saved pins, (S)ave a new pin or (E)xit: ", i);
goto EXIT;
}
}
EXIT: return i;
}
//TODO
//Error handling (overflow, input data type, other?)
Ignacio PG (N.Parsons-PB48K)Aún me queda mucho por hacer tratando de pasar a archivos digitales la mayoría de los programas para ZX Spectrum y Commodore 64 (también) publicados en este curso de programación para ordenadores de ocho bits: INPUT de Marshall Cavendish.
Ya voy por el nº 51 (último, en cuanto al curso se refiere), pero luego tocará repasar todo, habiéndome dejado cosas en el tintero hasta cierto número.
Sin prisas y a mi ritmo, sigo trabajando en él.
