unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: Use of advice [was: Is it valid to call isearch-filter-predicate outside isearch?]
Date: Thu, 08 Jun 2023 03:30:52 +0200	[thread overview]
Message-ID: <875y7yivub.fsf@web.de> (raw)
In-Reply-To: <SJ0PR10MB54886B308C995172B68F1F3DF353A@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Wed, 7 Jun 2023 14:44:33 +0000")

Drew Adams <drew.adams@oracle.com> writes:

> Are you talking about an advice name or the name
> of a predicate-valued variable?

Actually, about the names of function value'd variables that we want to
use or suggest for advising.

> I'll also pointed out that predicates are
> _particularly_ useful use cases for advice, as
> the ways you can combine the advice include the
> usual logical combinations (AND, OR, NOT).

Indeed.  Maybe a lot or most of the cases of function value'd
variables are predicate valued variables.


BTW, there is a case that is not so sexy: the case of variables that can
be bound to a function but also allow other values (like nil, t, a
string).  We also have these cases in our sources.  One must not install
advises for these.

Michael.



  reply	other threads:[~2023-06-08  1:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 15:22 Use of advice [was: Is it valid to call isearch-filter-predicate outside isearch?] Drew Adams
2023-06-06 23:36 ` Michael Heerdegen
2023-06-07  2:01   ` [External] : " Drew Adams
2023-06-07  2:53     ` Michael Heerdegen
2023-06-07 14:44       ` Drew Adams
2023-06-08  1:30         ` Michael Heerdegen [this message]
2023-06-07 11:53     ` Ihor Radchenko
2023-06-07 11:49   ` Ihor Radchenko
2023-06-07 14:47     ` [External] : " Drew Adams

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=875y7yivub.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).