unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: one key-press to comment out lines of code?
Date: Fri, 02 May 2014 01:42:23 +0200	[thread overview]
Message-ID: <87k3a5ukv4.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.469.1398984898.1147.help-gnu-emacs@gnu.org

Dale Snell <ddsnell@frontier.com> writes:

> Heh, yeah, the old terminals had keys wandering all
> over the place.  Every manufacturer had a different
> idea of where things like escape, |, \, `, ~, and so
> on belonged.  Sometimes they would change their minds
> from one model to the next.  As I recall, the DEC
> VT-101 that I learned Emacs on had the escape key
> where the /~ usually is now.  The `/~ key was between
> the =/+ and backspace keys, and the |/\ key was to
> the right of the return key.  (An awful place.  One
> had to be careful if one used those characters.)

Cool. I found the old exchange:

YT:

... was the Escape key placed anywhere else than it is
on today's keyboards? The reason I ask is - well, just
try hitting a couple of familiar shortcuts, but instead
of Meta, use Escape. I think it would take a master at
the accordion to be productive using that.

Bob Proulx:

Yes.  The escape key has been located in other
locations.  Here is an example.  On the HP HIL keyboard
it was left of the left shift key.  (Also note that
control was left of the A.)  A good keyboard layout for
the touch typist.  Everything was relatively close to
the home row.

http://www.hpmuseum.net/display_item.php?hw=575

Mostly escape has been located in the upper left
"somewhere".  Although not always left of the 1 key.

>> But perhaps you re-routed Esc for Caps Lock?
>
> No, I swapped control for caps-lock, putting the
> control key next to the A key, where it's much more
> accessible.

Yeah, I've heard a lot of people doing that. I actually
think left control is kind of close and good for the
left little finger. Caps-lock is better, yes, but is it
better enough to make it worthwhile to re-learn? Don't
know.

> Since I seldom use the caps-lock function, it doesn't
> bother me that said key was relegated to the second
> most inconvenient place on the keyboard.

I have an Emacs-only software solution for upper-case
only mode (which I get with <M-caps>). It is based on
caps-mode.el but I put some changes there, namely it
maps dashes to underscores, and, it disables itself on
a non-alphanumeric (or dash/underscore) keystroke
(i.e., most often a whitespace).

It works great in Emacs but I wish I could get it in
zsh as well. There is still the acronyms (e.g., URL),
and even more so the non-computer files (README) and
environmentals (HOME), and I'd like a caps-lock for
that.

Instead I bring up the buffer-menu (files only) on the
caps-lock key (only) in Emacs, and once there, an
additional stroke of caps-lock brings up all files. So
I can toggle all I want. Pretty clever! But there
should be one million things to do with the caps-lock
key that is more sensible than changing the case...

> (The most inconvenient position, imnsho, is the right
> control key.  Next to the left arrow key.  Ugh.)

Agreed. I actually don't have it. To the right of the
space bar, I have "Alt Graph" (which is Meta as well,
it seems), then a key with a solid diamond (seems to be
escape), and then "Compose Key" which doesn't seem to
do anything. (I actually have the compose key somewhere
else.) But: why are those keys so inconvenient? What's
stopping from using them as the control and Meta on the
left side? They are just one centimeter too far to the
right and that does it.

-- 
underground experts united:
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2014-05-01 23:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 16:14 one key-press to comment out lines of code? Sharon Kimble
2014-04-30 16:22 ` Drew Adams
2014-04-30 17:09   ` Michael Heerdegen
2014-04-30 17:18     ` Michael Heerdegen
2014-04-30 16:27 ` Dale Snell
2014-04-30 17:38 ` Andreas Röhler
2014-04-30 19:02 ` Stefan Monnier
     [not found] ` <mailman.391.1398874951.1147.help-gnu-emacs@gnu.org>
2014-04-30 19:03   ` Emanuel Berg
2014-04-30 20:54     ` Drew Adams
2014-04-30 21:06       ` Drew Adams
     [not found]     ` <mailman.414.1398891311.1147.help-gnu-emacs@gnu.org>
2014-05-01 13:54       ` Emanuel Berg
2014-05-01 14:39         ` Drew Adams
     [not found]         ` <mailman.441.1398955214.1147.help-gnu-emacs@gnu.org>
2014-05-01 15:03           ` Emanuel Berg
     [not found] ` <mailman.392.1398875301.1147.help-gnu-emacs@gnu.org>
2014-04-30 19:10   ` Emanuel Berg
2014-04-30 20:09     ` Joost Kremers
2014-05-01 14:15       ` Emanuel Berg
2014-05-01 14:31         ` Joost Kremers
2014-04-30 21:12     ` Dale Snell
     [not found]     ` <mailman.417.1398892388.1147.help-gnu-emacs@gnu.org>
2014-05-01 14:05       ` Emanuel Berg
2014-05-01 22:54         ` Dale Snell
     [not found]         ` <mailman.469.1398984898.1147.help-gnu-emacs@gnu.org>
2014-05-01 23:42           ` Emanuel Berg [this message]
2014-05-02  0:11             ` Joost Kremers
2014-05-02  1:23               ` Emanuel Berg
2014-05-03  2:01               ` Emanuel Berg
2014-05-03  2:43                 ` Emanuel Berg
2014-05-02 17:42             ` Dale Snell
     [not found]             ` <mailman.520.1399052563.1147.help-gnu-emacs@gnu.org>
2014-05-02 19:59               ` 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.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=87k3a5ukv4.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --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).