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: Sun, 20 Apr 2014 22:41:50 +0200	[thread overview]
Message-ID: <87bnvv91ip.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: 9c8cbdb3-abe9-4aae-af60-761d0c042c67@googlegroups.com

Hans BKK <hansbkk@gmail.com> writes:

> My goal isn't to flatten the "usage" learning curve,
> but to help me climb the "customizing" one faster

Again, I don't see any conflict.

This is how I did it:

Make a keystroke to go instantly to the .emacs file (or
directory of config/extension files, when .emacs starts
to get big).

When you get an idea, hit the keystroke and try to
implement it - and start small. Keystrokes, face
colors, etc. are ideal to begin with (and the result
immediately felt). Later, you can rewrite the search
function or whatever.

Sometimes in the course of daily (nightly) activity,
you get an idea, but you don't want to loose focus on
the task at hand. Then I have an interactive todo list
[1], to which I just add an item. That todo list is
never empty for me, no matter how much stuff I do :)
Again, a keystroke to bring up the todo file will get
you there instantly whenever you feel like
playing/working with Elisp extension/configurations
(this can be a pleasant way to relax
actively/constructively, as well) - so at that point,
you don't have to think "what do I do now?" - just pick
of item by item on the todo list.

OK - there are several ways to do things, and this is
just an example (but, I think, a good way) - but the
underlying principle is *activity* - activity leads to
activity. Be active, and configuration will
come. Drawing UML diagrams and the like on a blackboard
on the other hand, won't get anyone anywhere... Don't
plan, *do it*!

> and the process of putting code together and diving
> into emacs' internals is all part of that. I also
> didn't mean to put so much focus on the keybindings
> issue, just that's why I'm holding off on the
> hands-on usage

That doesn't make any sense. I hope you don't get angry
now but I just know that is incorrect. If you want to
be a boxer, you should throw 1000 punches a day. A
programmer: write 1000 lines of code a day. An Emacs
user: use Emacs all night long, and configure/extend a
couple of things every night and day.

This will *not* make you a "mechanical" moron - on the
contrary, doing the basics one million times will open
your body/mind for what is more advanced. And the more
skilled you get at the "mechanical" side to it, the
less resources does your brain have to put to it -
also, the brain will get more skilled at decoding the
signals, produced by the mechanical activity.

To "just do it" does not mean your brain shuts off!

[1] http://user.it.uu.se/~embe8573/conf/emacs-init/todo-did.el

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


      parent reply	other threads:[~2014-04-20 20:41 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
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 [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=87bnvv91ip.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).