From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: `when' vs. `and' / `unless' vs `or'
Date: Wed, 17 Oct 2018 03:25:43 +0200 [thread overview]
Message-ID: <87y3axictk.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <db21ea5f-21db-4ddd-9b66-37163a7e7faa@default> (Drew Adams's message of "Tue, 16 Oct 2018 17:16:14 -0700 (PDT)")
Le 16/10/2018 à 17h16, Drew Adams a écrit :
>> (if (or cond cond) then else) than, canonically (and (not (and (or cond
>> cond) then)) else) (not sure about a simplified version), which is the
>> way to write it without an `if', as you said you didn’t use it if the
>> condition was more than a single sexp.
>
> As I (think I) said, I use (if (or cond cond) then else), if THEN is a single sexp.
Oh sorry! I misunderstood in fact, I must be tired.
> BTW, for transforming sexps with `not', `and', and `or', for readability
> or for performance reasons, I sometimes use `notandor.el'.
>
> https://www.emacswiki.org/emacs/NotAndOr
Nice! will it be in elpa one day? ^^
Althought your Package Requirements is a list instead of a list of list
so that blocks automatical installation using package-install-file…
> Also, package `el-search.el' has similar possibilities (and many other
> good things).
Wow it seems cool, I’ll try it out when I’ve got time if I remember to.
I’ve dreamt of it I think.
next prev parent reply other threads:[~2018-10-17 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 21:05 `when' vs. `and' / `unless' vs `or' Garreau, Alexandre
2018-10-16 22:13 ` Drew Adams
2018-10-16 22:38 ` Garreau, Alexandre
2018-10-16 23:21 ` Drew Adams
2018-10-17 0:02 ` Garreau, Alexandre
2018-10-17 0:16 ` Drew Adams
2018-10-17 1:25 ` Garreau, Alexandre [this message]
2018-10-17 1:58 ` Drew Adams
2018-10-17 9:00 ` Garreau, Alexandre
[not found] ` <mailman.2299.1539766826.1284.help-gnu-emacs@gnu.org>
2018-10-17 9:49 ` Emanuel Berg
2018-10-17 15:42 ` Michael Heerdegen
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=87y3axictk.fsf@portable.galex-713.eu \
--to=galex-713@galex-713.eu \
--cc=drew.adams@oracle.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.
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).