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: Learning "my emacs" from the start (was: Generating a listing of all symbols)
Date: Sat, 19 Apr 2014 22:57:49 +0200	[thread overview]
Message-ID: <87oazxca0i.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: 3defe928-5d2e-4d3b-bc26-f595f275f840@googlegroups.com

Hans BKK <hansbkk@gmail.com> writes:

> I am learning customization before ordinary usage in
> editing very intentionally

Do both at the same time. You are using Emacs when you
customize Emacs. Also, how do you know what makes sense
to configure, and what doesn't, without using the
program to begin with? Seems to me, you are thinking of
implementing an idea from scratch, and then be done
with it. That's very seldom a good way. It is much
better to incorporate configuration in normal usage -
do one improvement every day, instead. It should be an
evolutionary processes, if you will, not a single
Hercules-deed.

> emacs' value as a portable lifetime meta-OS
> dev/org/comms platform is far more important to me
> than its comparatively trivial role as an editor.

Say what?! The *editor* is the thing you use when you
do all those things you mention.

A computer system is data, organized into files. Which
an editor manipulates (as well as creates, deletes,
etc.) The editor is by far the single most important
tool for general computer work.

Emacs isn't exactly an OS in the non-interactive kernel
sense (though you can schedule things with Emacs).

> The whole point to me of bothering with the learning
> curve [1] of a complex platform like emacs is to
> create my own highly-customized version, and the
> keybindings seems (again, to me) to be a logical
> place to start, ideally before getting sucked into
> the vanilla-emacs shift-Alt-Ctrl-Super-Meta-Cmd (IMO
> sorry-but-insane ancient-legacy) default keybindings
> for routine navigation and editing usage.

Some of the Emacs default keybindings are great, for
example the M-f, C-p, etc. for cursor movements.

Some are not so good. Those that are not so good are
either too long (involve lots of keydowns) *or* they
are what I call "far" - so you have to *reach* for
them, and then reset your hands to start typing again.

A third category (that I don't like) is in "non-typing
modes" (e.g., w3m, browsing man-pages) when the whole
keyboard is available (as there isn't any typing) - to
still use long, bulky combinations. Use one letter
keydowns instead! "a" for append, "p" for previous, and
so on.

One of my favourite customization that I setup for
every and all modes (that I use) - just to give an
example how I think it should be, in general - is M-i
and M-k (for scroll up one line, and down one line,
respectively). If you try those out with correct hand
positions, you should notice what minimal hand (finger)
movement they require.

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


  reply	other threads:[~2014-04-19 20:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 20:10 Learning "my emacs" from the start (was: Generating a listing of all symbols) Hans BKK
2014-04-19 20:57 ` Emanuel Berg [this message]
2014-04-20  8:06 ` Eli Zaretskii
2014-04-20 10:39   ` Learning "my emacs" from the start Thien-Thi Nguyen
2014-04-20 11:04     ` Eli Zaretskii
2014-04-20 14:12       ` Thien-Thi Nguyen
2014-04-20 14:13         ` Eli Zaretskii
2014-04-22  8:47           ` Nicolas Richard
2014-04-22 16:40             ` Eli Zaretskii
2014-04-20 13:00     ` Florian v. Savigny
2014-04-20 13:29       ` Florian v. Savigny
2014-04-20 14:50       ` Thien-Thi Nguyen
2014-04-21  8:26         ` Florian v. Savigny
     [not found]         ` <mailman.19974.1398068777.10748.help-gnu-emacs@gnu.org>
2014-04-21 13:12           ` Hans BKK
     [not found] ` <mailman.19908.1397981214.10748.help-gnu-emacs@gnu.org>
2014-04-20 13:23   ` Learning "my emacs" from the start (was: Generating a listing of all symbols) Rusi
2014-04-20 17:13     ` Bob Proulx
2014-04-20 18:51       ` Eli Zaretskii
     [not found]       ` <mailman.19947.1398019903.10748.help-gnu-emacs@gnu.org>
2014-04-21 14:37         ` Rusi
2014-04-21 19:01           ` Bob Proulx
2014-04-21 20:16             ` Robert Thorpe
2014-04-21 20:22             ` Robert Thorpe
2014-04-21 21:00             ` Eli Zaretskii
     [not found]           ` <mailman.20014.1398106904.10748.help-gnu-emacs@gnu.org>
2014-04-22  1:37             ` Rusi
2014-04-20 17:12 ` Hans BKK
2014-04-20 20:36   ` Robert Thorpe
2014-04-20 20:41   ` 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=87oazxca0i.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).