all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers@rgrjr.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Richard Stallman <rms@gnu.org>,
	Pedro  Andres Aranda Gutierrez <paaguti@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Re: cond*
Date: Sun, 24 Dec 2023 20:53:36 -0800	[thread overview]
Message-ID: <25993.2768.715540.322081@orion.rgrjr.com> (raw)
In-Reply-To: <SJ0PR10MB5488D879940089C0714AB0C0F399A@SJ0PR10MB5488.namprd10.prod.outlook.com>

   From: Drew Adams <drew.adams@oracle.com>
   Date: Mon, 25 Dec 2023 03:49:30 +0000

   > I fail to see how using "t" is consistent with cond . . .
   > 
   > In fact, none of Richard's "three" options strike me as truly
   > palatable . . .
   > 
   > . . . I did want to point out what I thought was a severe drawback
   > of using "t", since no one else seemed to have noticed.

   Yes, this is essentially what I and others
   have said.  It might be less confusing if
   the name `cond*' weren't used, as that
   really invites exactly such confusion . . .

If I have not added anything by my inattention, then I apologize for not
reading your (and others') posts more closely.  At least we seem to be
on the same page re cond*.

					-- Bob



  reply	other threads:[~2023-12-25  4:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23  6:17 Re: cond* Pedro Andres Aranda Gutierrez
2023-12-25  1:32 ` Bob Rogers
2023-12-25  3:49   ` [External] : " Drew Adams
2023-12-25  4:53     ` Bob Rogers [this message]
2023-12-29  3:51     ` Richard Stallman
2023-12-29  7:11       ` Eli Zaretskii
2023-12-31  3:15         ` Richard Stallman
2023-12-29  3:51     ` Richard Stallman
2023-12-26  4:03 ` cond* Richard Stallman

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=25993.2768.715540.322081@orion.rgrjr.com \
    --to=rogers@rgrjr.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@gmail.com \
    --cc=rms@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.