all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Riley <rileyrgdev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: conditionals in elisp
Date: Tue, 27 Oct 2009 14:02:19 +0100	[thread overview]
Message-ID: <hc6r0r$23a$2@ger.gmane.org> (raw)
In-Reply-To: 87skd5t3vp.fsf@galatea.local

pjb@informatimago.com (Pascal J. Bourguignon) writes:

> Richard Riley <rileyrgdev@gmail.com> writes:
>
>> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>>
>>> LanX <lanx.perl@googlemail.com> writes:
>>>
>>>> Joe Brenner has a nice elisp <-> perl comparison table, which helped
>>>> me a lot:
>>>>
>>>> http://obsidianrook.com/devnotes/elisp-for-perl-programmers.html
>>>>
>>>> BTW: first hit googling "elisp perl" 8)
>>>
>>> Obviously, google is too hard for the OP, if he cannot be bothered to
>>> read the minimum about emacs...
>>
>> The OP was looking for a quick lookup programmers guide to common elisp
>> constructs. The elisp manual is not really quite so convenient : good
>> though it can be.
>>
>> People frequently want to modify an existing feature without learning
>> the entire emacs infrastructure.
>>
>> Pointing to existing code is one such way to help. Suggesting he parse
>> it all with perl probably not quite so helpful ..
>>
>> Personally whenever I revisit elisp I find Xah Lee's tutorial helpful at
>> times.
>
> Whatever.  Results 1 - 50 of about 151,000 for emacs lisp cheatsheet. (0.58 seconds) 
>
^^^^^^^^^^^^

cheatsheet? I would never have thought of using that word. Would many
programmers? Most people look up "reference" or "tutorial". Sometimes
people get flustered and lost and need human interaction. The op was
polite and looking for pointers.

> Notice how google is much faster than typing one's question on the
> newsgroups...

Makes one wonder why the groups are here eh? You know .. to ask people
in the know and maybe pick up a few pointers and friendly suggestions on
how best to proceed. That kind of thing.

You should set up an auto "RTFG" response.

cheers,

r.







  reply	other threads:[~2009-10-27 13:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9533.1256602126.2239.help-gnu-emacs@gnu.org>
2009-10-27  0:19 ` conditionals in elisp Pascal J. Bourguignon
2009-10-27  2:52 ` LanX
2009-10-27 10:36   ` Pascal J. Bourguignon
2009-10-27 12:09     ` Richard Riley
2009-10-27 17:03       ` Sean Sieger
2009-10-28 12:07         ` Richard Riley
     [not found]     ` <mailman.9555.1256645401.2239.help-gnu-emacs@gnu.org>
2009-10-27 12:31       ` Pascal J. Bourguignon
2009-10-27 13:02         ` Richard Riley [this message]
     [not found]         ` <mailman.9557.1256648714.2239.help-gnu-emacs@gnu.org>
2009-10-27 16:04           ` Pascal J. Bourguignon
2009-10-27 17:26         ` Harry Putnam
     [not found]         ` <mailman.9572.1256664440.2239.help-gnu-emacs@gnu.org>
2009-10-27 18:37           ` Pascal J. Bourguignon
2009-10-27 19:40             ` Harry Putnam
     [not found]             ` <mailman.9577.1256672457.2239.help-gnu-emacs@gnu.org>
2009-10-27 21:14               ` Pascal J. Bourguignon
2009-10-28 14:05                 ` David Kastrup
2009-10-28 15:55                   ` Harry Putnam
2009-10-28 17:45                   ` Pascal J. Bourguignon
2009-10-27  0:08 Harry Putnam
2009-10-27  0:25 ` Richard Riley
2009-10-27  1:03 ` Drew Adams
2009-10-27  5:33   ` Harry Putnam
2009-10-27  7:37     ` Drew Adams
2009-10-28  9:10       ` Thien-Thi Nguyen
2009-10-28 14:03         ` Drew Adams
     [not found]         ` <mailman.9621.1256738653.2239.help-gnu-emacs@gnu.org>
2009-10-28 15:42           ` LanX
2009-10-28 20:42             ` Harry Putnam
2009-10-28 16:19         ` Harry Putnam
     [not found]         ` <mailman.9630.1256746811.2239.help-gnu-emacs@gnu.org>
2009-11-02 19:31           ` Joseph Brenner
2009-10-27  5:50 ` tomas

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='hc6r0r$23a$2@ger.gmane.org' \
    --to=rileyrgdev@gmail.com \
    --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.
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.