all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: conditionals in elisp
Date: Tue, 27 Oct 2009 19:37:05 +0100	[thread overview]
Message-ID: <87eioou1im.fsf@galatea.local> (raw)
In-Reply-To: mailman.9572.1256664440.2239.help-gnu-emacs@gnu.org

Harry Putnam <reader@newsguy.com> writes:

> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>
> [...]
>
>> Whatever.  Results 1 - 50 of about 151,000 for emacs lisp
>> cheatsheet. (0.58 seconds) ^^^^^^^^^^^^
>
> Aside from being horribly lazy, not to mention stupid... I'm also
> apparently blind.... I asked about `if else conditionals'... and using
> a string I would never have thought of to search for that topic I
> repeated your search..finding in a blazing .58 second... exactly 0
> references to that topic (at least in the first two pages).

Why can't you see these links on the first page returned by Google?

http://steve-yegge.blogspot.com/2008/01/emergency-elisp.html

There's even the "Emacs Lisp for Perl Programmers"
http://obsidianrook.com/devnotes/elisp-for-perl-programmers.html on
it.


Granted, contrarily to what I expected, there's no cheat sheet for
emacs lisp, just for emacs.  This is not bad, since the later would
help you know how to get help about the if operator, (typing C-h f if
RET).

In anycase, you should have been able to find at least the two links
above that are accessible from the first page of results given by
google.


> I'll admit I gave up after the second page... Oh, wait I take it
> back, there is mention of your posts on this thread.  But then, those
> don't mention anything about the topic either.

Yes, that's a funny side effect.   That's why google search should be
done first! ;-)



> I wasn't thinking, tutorial either, since, again I've tortured myself
> with a few in the past. And a tutorial by its nature will take in a
> lot more than what I was after.  I wanted examples... and that is what I
> posted about.

The problem is that you shouldn't have to ask what syntax is if in
lisp, if you knew the first thing about lisp.  You can realy learn all
there is to know about lisp in five minutes. (Of course, then you need
a lifetime to ponder the consequences, but nonetheless, five minutes
is all you need to know it all).


> In fact I see now that looking for something similar to `if else' in
> perl or shell scripting is really a mistake.  It looks quite different
> in elisp (at least syntactically). . I'm not sure I ever would have
> recognized it ... had I found examples.
>
> What I saw was mostly about emacs commands.  Something I actually know
> a fair bit about after over a decade using emacs..  Maybe not by
> standards of this list, but by a wider standard I do.
>
> Thanks for your input. Pascal, I seem to have reached beyond your
> patience level.. this time.  But you have provided many helpful posts
> to me direct and indirect over the yrs and I thank you for that.

Just tell us when you have five minutes to learn all there is to know
about lisp ;-)


-- 
__Pascal Bourguignon__


  parent reply	other threads:[~2009-10-27 18:37 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
     [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 [this message]
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=87eioou1im.fsf@galatea.local \
    --to=pjb@informatimago.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.