From: deskpot@myrealbox.com (Vasily Korytov)
Cc: ding@gnus.org
Subject: Re: e vs. E
Date: Wed, 19 Mar 2003 23:00:40 +0300 [thread overview]
Message-ID: <87vfyfrus7.fsf@unix.home> (raw)
In-Reply-To: <87n0jr1nci.fsf@gnufans.net> ("D. Goel"'s message of "19 Mar 2003 08:45:49 -0500")
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On 19 Mar 2003, D. Goel wrote:
> IOW, i use e much more than E, and so exchange their meanings.
>
> Do most of you too? If so, this is a request to consider exchanging
> them by default..
I would strongly suggest against such requests. Whereas I use E more
often than e and F -- than f, keyboard shortcuts are meant to be a
habbit. That is, pressing without thinking. Many people are used to e
and E. Personally I *hate*, when shortcuts are changed (breaking my
daily mail reading process, believe me) without a very good reason.
--
I accept RFC3156 and RFC1991-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2003-03-19 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 13:45 D. Goel
2003-03-19 20:00 ` Vasily Korytov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vfyfrus7.fsf@unix.home \
--to=deskpot@myrealbox.com \
--cc=ding@gnus.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 NNTP newsgroup(s).