From: Drew Adams <drew.adams@oracle.com>
To: Drew Adams <drew.adams@oracle.com>, Jean Louis <bugs@gnu.support>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: operations on path lists
Date: Wed, 8 Feb 2023 18:46:25 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488450F1474E274EFCC5351F3D89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR10MB54887B26070F397584371C06F3D89@SJ0PR10MB5488.namprd10.prod.outlook.com>
> But if each of `if', `when', `unless', `and', and
> `or' is used in a way that says what's intended
> then it's pretty easy to understand. There's
> no guessing about whether the return value of
> a given `if' is used etc. (For me, it always
> is, or I wouldn't use `if'.)
I misspoke there. I use `if' in contexts where
the return value matters and in contexts where
it doesn't matter.
next prev parent reply other threads:[~2023-02-08 18:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 5:32 operations on path lists Samuel Wales
2023-02-04 6:32 ` Jean Louis
2023-02-04 8:06 ` Emanuel Berg
2023-02-04 17:21 ` [External] : " Drew Adams
2023-02-04 18:32 ` Jean Louis
2023-02-04 21:51 ` Emanuel Berg
2023-02-07 8:34 ` Jean Louis
2023-02-07 10:26 ` Emanuel Berg
2023-02-07 22:39 ` Jean Louis
2023-02-08 2:48 ` Drew Adams
2023-02-08 18:46 ` Drew Adams [this message]
2023-02-08 20:09 ` Jean Louis
2023-02-04 18:28 ` Jean Louis
2023-02-04 21:41 ` Emanuel Berg
2023-02-07 8:33 ` Jean Louis
2023-02-07 10:30 ` Emanuel Berg
2023-02-07 14:55 ` [External] : " Drew Adams
2023-02-07 14:55 ` Drew Adams
2023-02-04 21:44 ` Samuel Wales
2023-02-04 21:49 ` Samuel Wales
2023-02-04 14:59 ` Emanuel Berg
2023-02-07 7:35 ` Jean Louis
2023-02-07 10:27 ` Emanuel Berg
2023-02-11 8:18 ` James Thomas
2023-02-11 14:02 ` Ruijie Yu via Users list for the GNU Emacs text editor
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=SJ0PR10MB5488450F1474E274EFCC5351F3D89@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=bugs@gnu.support \
--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.