564 karma · joined June 20, 2011
Because with four-digit years this kind of date would never have fit into a signed 32-bit integer. Incidentally, this shows that the timestamp was taken into use after Y2K, since none of the pre-millennium years would have fit.
But I agree it shouldn't technically be too hard to standardize the settings so that your browser could communicate to each site what the user consents to. The hard part is enforcing compliance - we already had Do Not Track, which had very little effect.
I agree that the ancient terminology is a problem with Emacs. People who are used to Emacs don't want to change it, but it is alien to all new users. Funnily enough, in vi (a competing old text editor that predates current UI standards) "yank" means "copy".
Another example is "window" and "frame", which mean the opposite that you would think if you have used any modern windowing system. A similar problem (that is not strictly about terminology) is the way "undo" works. It is more powerful than the standard undo/redo system, but it can be very confusing when you encounter it the first time. Repeated "undo" commands work the way they do in other programs, but once you run any other command, the undo operations go in the undo history just like other commands and are themselves undoable, so the way to cancel an undo operation (which is called "redo" in many other programs) is to type some character and then run "undo" twice.
https://www.emacswiki.org/emacs/KillingAndYanking https://www.gnu.org/software/emacs/manual/html_node/emacs/Ki...
The basic idea is that your clipboard ("kill ring") can contain many entries, so you can kill several lines (or words, sentences, functions, what have you) and then yank them back at other locations. Yanking copies the most recently killed text, but you can use another command to replace it with previous entries until you find the right one. Thus you don't have to fear losing the clipboard while performing intermediate operations.
Readline-type libraries typically implement a small subset of the Emacs kill-ring features, so you really need to try Emacs to appreciate the full range of the concept.
The linenoise README mentions "sensibility for small easy to understand code". It's not really explained further in the README, but I suppose the point is that you can read the ~1200 lines of source code and get a feel for it yourself.
* headlines
** in a hierarchy
* and back to level 1
1. and numbered lists
2. [ ] and clickable items
...and all the other features, but I would be interested in seeing what kind of improved workflows or routines are enabled by using org-mode in some actual work. name & value & comment \\
long name here & 1 & one\\
x & 2 & two \\
and the columns line up at the & characters by adding suitable whitespace. Imagine some control character that you could insert in source code: next&Ancestor &= current->next;
previous&Ancestor &= null;
and the corresponding parts would line up in consecutive blocks, like elastic tab stops but even inside words by stretching the existing whitespace around the words."Why aren't you coming to the company party?"
"Because that would likely exacerbate my chronic headache and I might be unable to work for several days."
"Oh wow, is it that bad? Have you tried acupuncture? My cousin had a headache and that really helped..." And a few minutes later: "Come on, the party will be fun, how bad could it be?"
I've learned to manage my condition well enough that people generally don't notice any problems. I've probably tried any remedies you can come up with, and so far the best way to cope is to live a boring life and go to bed at the same time every night after a peaceful evening. But because I'm not writhing in pain during the conversation, some people seem to think that I'm just coming up with excuses to not come to their party or whatever they are asking me to do.
I remember a Greek-born colleague writing the uppercase Omega as just an underlined letter O. I suppose that shape is probably the idea behind the flourishes in the typeset Omega.