From: Richard Riley <rileyrgdev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs standards with regions
Date: Mon, 24 Nov 2008 22:26:23 +0100 [thread overview]
Message-ID: <ggf679$lbp$1@news.motzarella.org> (raw)
In-Reply-To: mailman.1152.1227560873.26697.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Xah Lee <xahlee@gmail.com>
>> Date: Mon, 24 Nov 2008 10:15:28 -0800 (PST)
>>
>> I have little doubte, that when each of these features were considered
>> in emacs, lots of diehard tech geekers think they are utterly stupid.
>
> Well, you should doubt it, because tech geekers had no problems at all
> with including CUA mode in Emacs. The only reasons why it took so
> long for CUA mode to become part of Emacs is that (1) there was a need
> to find a way of doing that without losing important Emacs key
> bindings like C-x and C-y, and (2) the satisfactory technical solution
> was not ready in time for Emacs 22.1, and so was deferred to the next
> major release.
>
>> for example, consider the naming of things. For example, when a emacs
>> user tried to read the online doc of comment-dwim, quote: “If the
>> region is active and `transient-mark-mode' is on, ...”. For more than
>> 99% of professional programers, they'll go: “What the heck is
>> transient mark??”
>>
>> and if you ask them what is “CUA”, they'd go “HUH????”
>
> No problems here, since those ``professional programmers'' simply
> don't read documentation. So they will never be stumped by this
> terminology. But if they would somehow, by sheer mistake, manage to
> read that, there's a Glossary section which explains everything.
Certainly it not being on by default was a bit weird for me. I believe
Emacs 23 it is default to be on.
Even the documentation appears to think the old behaviour was a bit
strange when transient mode mark was not on:
from
(emacs) Persistent Mark
,----
| Emacs does not show where the mark is located--you have to remember.
| The usual solution to this problem is to set the mark and then use
| it soon, before you forget where it is.
`----
I think I sense a bit of an agenda in that info snippet :-;
next prev parent reply other threads:[~2008-11-24 21:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 15:03 Emacs standards with regions Richard Riley
2008-11-24 16:46 ` Xah Lee
2008-11-24 18:15 ` Xah Lee
2008-11-24 21:07 ` Eli Zaretskii
[not found] ` <mailman.1152.1227560873.26697.help-gnu-emacs@gnu.org>
2008-11-24 21:26 ` Richard Riley [this message]
2008-11-25 3:40 ` Jason Rumney
2008-11-25 10:16 ` Xah Lee
2008-11-25 15:55 ` Jason Rumney
2008-11-25 15:57 ` Richard Riley
2008-11-25 18:01 ` Reiner Steib
2008-11-25 20:31 ` Teemu Likonen
2008-11-25 20:47 ` Xah Lee
2008-11-25 23:55 ` Alan Mackenzie
2008-11-26 8:19 ` Andreas Röhler
[not found] ` <mailman.1274.1227687564.26697.help-gnu-emacs@gnu.org>
2008-11-26 14:45 ` Xah Lee
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ggf679$lbp$1@news.motzarella.org' \
--to=rileyrgdev@gmail.com \
--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.
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).