From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: "'Per Starbäck'" <per@starback.se>,
emacs-devel@gnu.org,
"'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Deniz Dogan'" <deniz.a.m.dogan@gmail.com>
Subject: RE: C-j considered harmful (not really)
Date: Tue, 24 Nov 2009 09:51:36 -0800 [thread overview]
Message-ID: <C2162C0B03FE4407A7C871DCBB5E1D3F@us.oracle.com> (raw)
In-Reply-To: <87bpisouau.fsf@mail.jurta.org>
> > `C-j' _IS_ newline. OK, some people don't know that. But
> > most programmers of UNIX, Linux, C, etc. do know it, and
> > others can surely learn it - no biggee. It
> > is elegant to use the key to self-insert, the same way it
> > is elegant to use the key `a' to insert an `a' character.
>
> Fine, but note that `C-j' already has different
> non-self-insert-newline semantics in other modes:
I did not say that `C-j' should _always_ be self-inserting.
The same is true for `a' or `A' and so on - such keys are often bound to other
commands in various modes.
prev parent reply other threads:[~2009-11-24 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 22:37 C-j considered harmful (not really) Per Starbäck
2009-11-16 22:51 ` Deniz Dogan
2009-11-17 10:09 ` Juri Linkov
2009-11-17 23:17 ` Xavier Maillard
2009-11-18 9:54 ` Juri Linkov
2009-11-22 20:36 ` Per Starbäck
2009-11-22 20:53 ` Deniz Dogan
2009-11-23 2:57 ` Stefan Monnier
2009-11-23 9:54 ` Juri Linkov
2009-11-23 11:11 ` Per Starbäck
2009-11-23 15:05 ` Drew Adams
2009-11-23 15:05 ` Drew Adams
2009-11-23 16:09 ` Per Starbäck
2009-11-24 17:12 ` Juri Linkov
2009-11-24 17:51 ` Drew Adams [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
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=C2162C0B03FE4407A7C871DCBB5E1D3F@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
--cc=per@starback.se \
/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.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).