From: "Alfred M. Szmidt" <ams@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: rms@gnu.org, philipk@posteo.net,
michelangelo.rodriguez@gmail.com, emacs-devel@gnu.org
Subject: Re: Question about `cond*'
Date: Thu, 03 Oct 2024 00:51:37 -0400 [thread overview]
Message-ID: <E1swDoP-00020z-Ku@fencepost.gnu.org> (raw)
In-Reply-To: <87y135257r.fsf@melete.silentflame.com> (message from Sean Whitton on Thu, 03 Oct 2024 12:14:16 +0800)
> > I can only assume it was a mistake. The question is should the feature
> > be called `cond-star' or `cond*'.
>
> I think `cond*' is a more natural name for the feature.
> That is what users will think of -- to do (require 'cont-star)
> would require a little extra bit of trivial knowledge.
>
> I called the file `cond-star.el' to avoid the inconvenience that
> an asterisk in the file name could cause. But it woukd be better
> if users did not have to know that file name.
>
> `cond*' really ought to be preloaded.
Given that it isn't used in a single place yet, and we have repeatedly
refused to preload cl-lib, that does not seem appropriate.
cl-lib isn't preloaded for other reasons (Emacs Lisp isn't Common
Lisp), cond* is part of the Emacs Lisp language, and that would be a
good reason to preloaded it so that it can be more widley used.
next prev parent reply other threads:[~2024-10-03 4:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 8:35 Question about `cond*' Michelangelo Rodriguez
2024-10-01 15:58 ` Eli Zaretskii
2024-10-01 17:05 ` Michelangelo Rodriguez
2024-10-01 18:13 ` Philip Kaludercic
2024-10-03 3:35 ` Richard Stallman
2024-10-03 4:14 ` Sean Whitton
2024-10-03 4:51 ` Alfred M. Szmidt [this message]
2024-10-03 5:18 ` Sean Whitton
2024-10-03 7:12 ` Eli Zaretskii
2024-10-04 7:54 ` Andrea Corallo
2024-10-06 3:18 ` Richard Stallman
2024-10-06 5:28 ` Sean Whitton
2024-10-06 6:27 ` Eli Zaretskii
2024-10-01 18:15 ` Stefan Kangas
2024-10-01 18:19 ` Eli Zaretskii
2024-10-02 4:41 ` Alfred M. Szmidt
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=E1swDoP-00020z-Ku@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michelangelo.rodriguez@gmail.com \
--cc=philipk@posteo.net \
--cc=rms@gnu.org \
--cc=spwhitton@spwhitton.name \
/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.