From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: operations on path lists
Date: Sat, 4 Feb 2023 21:28:14 +0300 [thread overview]
Message-ID: <Y96jvuHPXiXaw8O6@protected.localdomain> (raw)
In-Reply-To: <87y1pdkg6p.fsf@dataswamp.org>
* Emanuel Berg <incal@dataswamp.org> [2023-02-04 17:55]:
> Jean Louis wrote:
>
> > (cond ((file-directory-p file) (expand-file-name file))
> > (t nil))
>
> (when (file-directory-p file)
> (expand-file-name file) )
I am aware of it, I prefer using `cond' as I get more clarity.
You may get more clarity with `when'.
Btw. it reminds me that I also have `rcd-unless':
(defmacro rcd-unless (condition &optional message &rest body)
(declare (indent 2))
`(cond (,condition
,@body)
(t (rcd-message ,message))))
So I use it this way:
(rcd-unless nil
"Cannot execute"
(message "OK I execute"))
I am not sure if I will keep it, but I like it. `rcd-message' you can replace with `message' to understand it.
As often I have situation where in the `unless' condition I want to tell to user "why" it does not work. So message is displayed in mini buffer.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-04 18:28 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
2023-02-08 20:09 ` Jean Louis
2023-02-04 18:28 ` Jean Louis [this message]
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
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=Y96jvuHPXiXaw8O6@protected.localdomain \
--to=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.
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).