From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: keybindings again...
Date: Sat, 01 Jul 2017 00:08:49 +0200 [thread overview]
Message-ID: <867ezt6scu.fsf@zoho.com> (raw)
In-Reply-To: 375C5600-DA51-4EDC-8304-F97E3A90A89D@gmail.com
Jean-Christophe Helary wrote:
> Thank you for the pointer. Although I don't
> think I ever used a teletypewriter in my life
> :) Maybe sometimes in the 21st century we'll
> have to think about a change in
> terminology...
In computers, but also in just any brand of
engineering (and other areas as well), there
are tons of cases when terminology is either
outdated or just plain wrong. When there is
a correct term, as in "chainwheel" or
"sprocket" as opposed to "cog" (which is
incorrect, as it isn't a cod), it is good to
know about the correct terms and use them
whenever, but it is equally necessary to know
about the incorrect term. You will find
respectable books when they refer to a sprocket
as a "cog" without blinking! And know what,
that book is healthy for you to
read nonetheless!
So in most cases it is better to use the
correct term in parallel and if the technically
incorrect one dies, good, if it survives, so
be it.
Another example: There were once a newsreader
called GNUS. When a new newsreader came, and
they thought of calling it "ding" as in "ding
is not GNUS". Clever, but it didn't take.
So now it is Gnus who isn't GNUS. But it is -
only better :)
As for the ttys they are also called "the
console" or "the Linux virtual terminals" (the
Linux VTs). All those are designations are fine
and at least "tty" and "console" are also part
of technology by now: e.g., I just mentioned
the file /etc/console-setup/remap.inc in
another post; as for "tty", do
$ ls /dev/ | grep tty
> I use the compact manual [...]
Bigger always better :)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-06-30 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 2:42 keybindings again Jean-Christophe Helary
2017-06-30 2:51 ` Kaushal Modi
2017-06-30 5:10 ` Jean-Christophe Helary
2017-06-30 5:27 ` Nicolas Goaziou
2017-06-30 7:23 ` Jean-Christophe Helary
2017-06-30 22:08 ` Emanuel Berg [this message]
2017-06-30 7:56 ` Jean-Christophe Helary
2017-06-30 8:14 ` Nicolas Goaziou
2017-06-30 8:40 ` Jean-Christophe Helary
2017-06-30 9:56 ` Michael Ax
2017-06-30 5:33 ` Kaushal Modi
2017-06-30 6:17 ` Eli Zaretskii
2017-06-30 7:28 ` Jean-Christophe Helary
2017-06-30 6:22 ` Yuri Khan
2017-06-30 21:55 ` Emanuel Berg
2017-07-01 0:00 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867ezt6scu.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).