unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mathias Dahl" <mathias.dahl@gmail.com>
To: "Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: emacs-devel@gnu.org
Subject: Re: Suggestion for C-t (transpose-chars)
Date: Fri, 20 Jul 2007 12:30:18 +0200	[thread overview]
Message-ID: <7dbe73ed0707200330k6eb5abc3wbcbb254addaacc2b@mail.gmail.com> (raw)
In-Reply-To: <87lkdbl8az.fsf@debby.local.net>

> With a prefix argument ARG C-t allows to *drag* a character ARG
> characters away.  Even though the respective code is impressively
> elegant I think it would be more helpful when one could *transpose*
> two characters ARG characters away from point!

I am totally impressed that people use these commands! I suspect it
takes quite a while getting into the habit and actually do this,
instead of simply DEL DEL DEL ... and retype. I am even more impressed
when thinking about there being people that even used the prefix arg
to this command. Wow! What brain power it must have taken to get that
habituized. At tops at would use the occacional C-t after misspelling
`the' as `teh'. As you might suspect I don't use this command much, so
take my opinion lightly, but I do agree that what Dieter suggests
sound more useful than the current behavior. Also, in hope that I can
learn as well, I would love to hear about in which scenarios people
end up using this.

> I guess this would also be helpful for non-touch-typists.  Isn't it
> the case that one confuses only the sequence of two *neighbouring*
> characters and realises that very often after typing one or two
> additional ones?  I find myself often typing C-b, C-b, C-t and C-e.
> With the suggested change it would save 4 keystrokes (C-2 and C-t).

A comment about counting keys like this, I think it is misleading to
count that as 4 keystrokes, typing the same key twice is in my opinion
much easier than moving the fingers to type another one so I think it
should count as 3, or maybe 3.2... :) Also, and this is a very
uninformed opinion from one that have been touch typing (still
learning) for some months, but isn't the `t' slightly easier to type
than the `2', even more reducing the win?

Anyway, I just wanted to present some counter-arguments, maybe not
even good ones. :) Still, I agree that the proposed behavior sounds
more useful than the current one.

/Mathias

  reply	other threads:[~2007-07-20 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  9:43 Suggestion for C-t (transpose-chars) Dieter Wilhelm
2007-07-20 10:30 ` Mathias Dahl [this message]
2007-07-20 13:05   ` Dieter Wilhelm
2007-07-20 11:31 ` Eli Zaretskii
2007-07-20 18:55   ` Dieter Wilhelm
2007-07-20 19:14     ` Stefan Monnier
2007-08-07 20:56       ` Dieter Wilhelm
2007-07-20 20:06     ` Eli Zaretskii
2007-07-27  0:28       ` Dieter Wilhelm
2007-07-31 17:05         ` Richard Stallman
2007-08-07 21:29           ` Dieter Wilhelm

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=7dbe73ed0707200330k6eb5abc3wbcbb254addaacc2b@mail.gmail.com \
    --to=mathias.dahl@gmail.com \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=emacs-devel@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.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).