unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: Emacs internals + lisp guru question
Date: 29 Sep 2002 07:48:55 +0000	[thread overview]
Message-ID: <kk9d6qxfd7c.fsf@glug.org> (raw)
In-Reply-To: b00bb831.0209282218.740cbfc@posting.google.com

gnuist006@hotmail.com (gnuist006) writes:

> There are some functions that take a list as argument.
> Text can be read from the buffer as a string.
> There are some functions that take a "symbol" as an argument.
> A string can be converted to a symbol.

this is like poetry!

> However, when symbol is provided to the function by converting a string
>  it is not working.

move point after the close-paren for each of these forms and do C-x C-e:

(describe-function 'make-symbol)
(describe-function 'intern)
(describe-function (intern "describe-function"))

> What is the meaning of the gibberish from
> (insert (format "%s" (symbol-function 'describe-function) ))

the only gibberish i see is the white space here...........^
(which might be significant according to some demented read-table
mungers).  which gibberish are you referring to, specifically?

> What is out there to learn more about emacs/emacs_lisp and become more
> sophisticated?

grep the net for "elisp manual".  if that's too heavy, try ttn's elisp
tutorial (still incomplete but maybe you can help):

  http://www.glug.org/people/ttn/software/elisp-tutorial/

but be careful of trying to be too sophisticated:

  http://www.glug.org/people/random/flame.txt

[newsgroups trimmed.]

thi

  parent reply	other threads:[~2002-09-29  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29  6:18 Emacs internals + lisp guru question gnuist006
2002-09-29  6:47 ` D. Goel
2002-09-29 18:15   ` D. Goel
2002-09-29  7:48 ` Thien-Thi Nguyen [this message]
2002-09-29  7:50 ` Tim Josling
2002-09-29 15:33 ` Nix

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=kk9d6qxfd7c.fsf@glug.org \
    --to=ttn@glug.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).