all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brad Collins <brad@studiojungle.net>
Subject: Re: emacs documentation for (La)TeX
Date: Fri, 26 Dec 2003 10:10:17 +0700	[thread overview]
Message-ID: <wkisk4uvdy.fsf@studiojungle.net> (raw)
In-Reply-To: <871xqsil1r.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Thu, 25 Dec 2003 23:34:24 +0100")

Kai Grossjohann <kai@emptydomain.de> writes:

> Joe Corneli <jcorneli@math.utexas.edu> writes:
>
>> The main difference between info lookup and describe-function is that
>> the latter (typically) has links to the source, whereas the former
>> doesn't.
>
> Ah, links to the source.  That is useful indeed.

Well it links to the *documentation* in the source, not the whole source
itself.

The wonderful thing is that C-h f/m/c are internal documentation--it's
in context with what you are doing or looking at in a way that an
external manual--even the very good info manuals, can not do.

This is why Emacs is called a self-documenting editor--because it not
not only lets you peek under the hood to see what's going on, it tells
you exactly what's going on why you do it.

Try 'C-h k h" 

,----[ C-h k h ]
| h runs the command self-insert-command
| (self-insert-command N)
|    which is an interactive built-in function.
| 
| Insert the character you type.
| Whichever character you type to run this command is inserted.
`----

This really blew me away when I first saw it.  Typing the 'h' key runs
the command self-insert-character which inserts the character into the
buffer. 

The question that I think many people would ask is, why would
I need or even want to know this?

This is what sets Emacs apart from everything else in the world of
software--it changes the relationship that the user has with the
software and encourages you to understand and tinker with everything.

Emacs forces you to drop your illusions about text and to understand
that practically everything in computing is just plain text when you
boil away the fat and fur.

This explains the obsession that people who have drunk the Emacs
Cool-Aid have with trying to do everything in Emacs.  After you
understand that, say email, is just plain text, you want to start
using the power of Emacs to edit and work with. 

So if Emacs is an editor, for editing text, you can also think of
Emacs itself as a collection of text files (written in elisp) which
can in turn be edited by Emacs.  The purpose of Emacs then, (at least
one reason) is to edit Emacs....

b/

--
Brad Collins
Chenla Labs
Bangkok, Thailand

  reply	other threads:[~2003-12-26  3:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AZe1u-00038Z-U8@monty-python.gnu.org>
2003-12-25 22:23 ` emacs documentation for (La)TeX Joe Corneli
2003-12-25 22:30 ` need double save-excursion -- why? Joe Corneli
     [not found] ` <mailman.628.1072394739.868.help-gnu-emacs@gnu.org>
2003-12-25 22:34   ` emacs documentation for (La)TeX Kai Grossjohann
2003-12-26  3:10     ` Brad Collins [this message]
     [not found] <E1AYzMh-0004iH-6u@monty-python.gnu.org>
2003-12-24  3:44 ` Joe Corneli
     [not found] <E1AYhTJ-0004l8-M8@monty-python.gnu.org>
2003-12-23 18:19 ` Joe Corneli
     [not found] ` <mailman.527.1072207300.868.help-gnu-emacs@gnu.org>
2003-12-23 20:28   ` Kevin Rodgers
     [not found] <E1AYWTr-0002OH-0w@monty-python.gnu.org>
2003-12-22 21:14 ` Joe Corneli
     [not found] ` <mailman.487.1072131422.868.help-gnu-emacs@gnu.org>
2003-12-22 22:36   ` Jesper Harder
2003-12-25 16:33   ` Kai Grossjohann
     [not found] <E1AX8MA-0007qZ-00@linux183.ma.utexas.edu>
     [not found] ` <20031220172409.GA2259@miwie.in-berlin.de>
2003-12-22  4:13   ` Joe Corneli
     [not found]   ` <mailman.451.1072070152.868.help-gnu-emacs@gnu.org>
2003-12-22 15:36     ` Kai Grossjohann
2003-12-22 16:50     ` Jesper Harder

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wkisk4uvdy.fsf@studiojungle.net \
    --to=brad@studiojungle.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.