@maple I got that once, too, & IDR if it was because of curl or wget.
@monorail I have so many questions about your teacher, and I fear I know the answers to them all. :<
@monorail not to mention being off by about 2-3 decades inre cobol & other early structured languages.
I forgot that the Apple Lisa Office System did this, too, in a much more flexible way. You have to copy the blank template icon to a new file icon, rename & move the icon to where you want it to live, & *then* you can open it to start editing the document.
@zac Maybe. For several years after its adoption by major distros, among the things pulseaudio couldn't do was mix sounds from different applications, things OSS, ALSA, & ESD had been doing reliably forever. Just as with bad systemd design decisions currently, Poettering's inclination was to blame everyone & everything else for not using his code properly.
@zac Lennart Poettering, the same guy who made the Linux blight called systemd, that's what. The guy just doesn't know how to make decent programs.
@Cr0wnless Some genuinely don't even know that much. They only know what the bitter voices on their radios tell them.
I wish someone made text editors & word processors that make you name & file the files you edit first, so that they would then be auto-saved without having to think about it.
The only ones that ever did (that I'm aware of) were geoWrite & geoWrite 128, bundled with GEOS versions for the Commodore 64, the Commodore 128, & the Apple II-series.
Please don't leave a Commodore 64 out in the middle of a field for who knows how many decades. But if you find one that was, please don't write it off as beyond hope, either. https://youtu.be/wVphFkaX1gg
A point & click graphical user interface is not automatically better than the command line interface.
I counted & timed each at my fastest, most mistake-free.
A mistake on the CLI just needs me to use the backspace key until the wrong letters are deleted.
A mistake in the GUI means taking time to recognize that the wrong GUI choices are up, to understand why or what I mis-clicked on, to remember how to back up, & to decide whether to back up or cancel & start over.
A point & click graphical user interface is not automatically better than the command line interface.
I'm using a tool with both, but although I have to type up to 60 characters in the CLI, it takes only 5-10 seconds, & my fingers never have to leave the keyboard.
With the GUI to do the same thing, I needed to click on 34 things, each appearing in a different place I had to point at first, take my hands off the mouse to type 4 characters, then put my hand back on the mouse, taking 40-55 seconds.
✨ Kind 'Net Help Desk fairy by day. ✨
✨ Weird & furry Unix fairy by night. ✨
✨ Sometimes a retrocomputer fairy. ✨
✨ Pays the ComputerFairi.es bills. ✨
✨ Sparkly✨shellscript✨princess. ✨
✨ Age: Mere days younger than ✨
✨ the Intel 4004 & Unix 1st Edition. ✨
✨ Follow requests welcome. ✨
✨
✨