From: Joost Diepenmaat <joost@zeekat.nl>
To: help-gnu-emacs@gnu.org
Subject: Re: Start-Up Loading of Speedbar
Date: Mon, 15 Sep 2008 19:36:57 +0200 [thread overview]
Message-ID: <871vzlcnuu.fsf@zeekat.nl> (raw)
In-Reply-To: lJwzk.311$W06.115@flpi148.ffdc.sbc.com
"J. D. Leach" <jdleach04@sbcglobal.net> writes:
> And the winner is...The Joosts, both of them (Kremers and Diepenmaat).
>
> Thanks tremendously. I rather thought that there was some line such as was
> suggested, that could be inserted into the .emacs file, but I have only
> ventured into modifications of that document when I was absolutely certain
> of what I was doing.
One thing you can do to experiment is to write testing code in the
*scratch* buffer and call M-x eval-buffer to run it. Or maybe easier:
type M-x ielm to start an interactive elisp prompt, which will execute
each complete form you enter.
> I think what is throwing me most is the unique terminology and the lisp
> coding style. I mean, where else in the computer field can you yank back
> something after you killed it (I call that resurrection), play with atoms
> and not get radiation sickness, and split your buffers? To the uninitiated
> neophyte, such nomenclature and concepts can defun the learning experience.
The language emacs uses for certain concepts seems mostly strange
because a lot of it was invented before the concepts were widely
used. There are good reasons to keep it the way it is, though.
> I must admit, there have been feeble attempts on my part to learn about
> Emacs in the past, but have heretofore quickly abandoned those attempts due
> to the arcane language and inscrutable key-bindings. I just had not spent
> enough time trying to discern the unique logic of the system. Thankfully,
> my attitude has changed, I just needed to stick with it.
My real appreciation for emacs grew tremendously when I started learing
common lisp, and from there, emacs lisp (which are pretty
similar). Learning the basics of lisp will help you a lot when messing
with emacs - from basic configuring to writing your own extensions.
If you want to get the most out of emacs, I recommend you read at least
a bit of the elisp manual, and/or possibly read a bit of the "practical
common lisp" book, which may be a little gentler, and a lot of which
translates to elisp:
http://gigamonkeys.com/book/
--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/
next prev parent reply other threads:[~2008-09-15 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 15:44 Start-Up Loading of Speedbar J. D. Leach
2008-09-15 15:54 ` Joost Kremers
2008-09-15 17:13 ` J. D. Leach
2008-09-15 17:36 ` Joost Diepenmaat [this message]
2008-09-15 17:54 ` Joost Kremers
2008-09-15 18:48 ` J. D. Leach
2008-09-15 15:58 ` Joost Diepenmaat
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=871vzlcnuu.fsf@zeekat.nl \
--to=joost@zeekat.nl \
--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).