unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: waterloo <waterloo2005@gmail.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: help-gnu-emacs@gnu.org, dak@gnu.org
Subject: Re: How to learn elisp ?
Date: Wed, 5 Aug 2009 19:59:37 +0800	[thread overview]
Message-ID: <907065090908050459i311ae7a7sea332928b4711a84@mail.gmail.com> (raw)
In-Reply-To: <c115fd3c0908050447q6e30fdc5h6b16a6046f90e1b5@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

But I have not read Emacs Lisp Reference , It is a huge book .


2009/8/5 Tim Visher <tim.visher@gmail.com>

> On Wed, Aug 5, 2009 at 7:26 AM, waterloo<waterloo2005@gmail.com> wrote:
> > I have read the manual "An Introduction to Programming in Emacs Lisp".
> >
> > But still I can not be able to write complete code of lisp .
>
> If you've read that manual then you should be well on your way to
> writing complete elisp code.  If you're having a specific problem then
> feel free to ask about that, but you already have all the resources
> you probably should need except perhaps a friend who already knows
> elisp well.  That's what the list is here for. ;)
>
> --
>
> In Christ,
>
> Timmy V.
>
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail
>

[-- Attachment #2: Type: text/html, Size: 1343 bytes --]

  reply	other threads:[~2009-08-05 11:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 11:26 How to learn elisp ? waterloo
2009-08-05 11:47 ` Tim Visher
2009-08-05 11:59   ` waterloo [this message]
2009-08-05 12:54     ` Andy Stewart
     [not found]     ` <mailman.3941.1249477743.2239.help-gnu-emacs@gnu.org>
2009-08-06  9:32       ` Jyrki Tikka
2009-08-06 12:32         ` Elena
2009-08-06 14:59           ` Drew Adams
     [not found]   ` <mailman.3936.1249473586.2239.help-gnu-emacs@gnu.org>
2009-08-05 13:18     ` Anselm Helbig
     [not found] <mailman.3943.1249480576.2239.help-gnu-emacs@gnu.org>
2009-08-05 17:31 ` Barry Margolin
2009-08-05 17:53   ` Pascal J. Bourguignon
  -- strict thread matches above, loose matches on Subject: below --
2009-08-05 16:28 waterloo
2009-08-05 13:56 waterloo
2009-08-05 14:06 ` Andy Stewart
     [not found] ` <mailman.3945.1249481229.2239.help-gnu-emacs@gnu.org>
2009-08-05 15:49   ` A.Politz
2009-08-05 16:25     ` Richard Riley
     [not found] <mailman.3934.1249471596.2239.help-gnu-emacs@gnu.org>
2009-08-05 12:08 ` Xah Lee
     [not found] <mailman.3930.1249466928.2239.help-gnu-emacs@gnu.org>
2009-08-05 10:26 ` David Kastrup
2009-08-05 10:40   ` Thierry Volpiatto
2009-08-05 11:44 ` Elena
2009-08-06 23:28 ` despen
2009-08-05 10:08 waterloo
2009-08-05 11:24 ` Andy Stewart
2009-08-05 13:06 ` Drew Adams
     [not found] ` <mailman.3940.1249477629.2239.help-gnu-emacs@gnu.org>
2009-08-05 15:34   ` Pascal J. Bourguignon
2009-08-05 15:47     ` Drew Adams
     [not found]   ` <7cocqujmui.fsf@pbourguignon.informatimago.com>
     [not found]     ` <mailman.3950.1249487281.2239.help-gnu-emacs@gnu.org>
2009-08-05 17:21       ` Pascal J. Bourguignon
2009-08-05 17:45         ` Drew Adams

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=907065090908050459i311ae7a7sea332928b4711a84@mail.gmail.com \
    --to=waterloo2005@gmail.com \
    --cc=dak@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tim.visher@gmail.com \
    /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).