all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Madhu <enometh@meer.net>
Cc: adam@alphapapa.net, emacs-devel@gnu.org
Subject: Re: please consider keeping defadvice around
Date: Mon, 11 Sep 2023 15:27:36 +0300	[thread overview]
Message-ID: <83pm2orj2f.fsf@gnu.org> (raw)
In-Reply-To: <20230911.080949.1745163659939409042.enometh@meer.net> (message from Madhu on Mon, 11 Sep 2023 08:09:49 +0530 (IST))

> Date: Mon, 11 Sep 2023 08:09:49 +0530 (IST)
> Cc: adam@alphapapa.net, emacs-devel@gnu.org
> From: Madhu <enometh@meer.net>
> 
> *  Eli Zaretskii <eliz@gnu.org> <83y1hdqw8t.fsf@gnu.org>
> Wrote on Mon, 11 Sep 2023 05:28:18 +0300
> >> Date: Mon, 11 Sep 2023 07:20:32 +0530 (IST)
> >> From: Madhu <enometh@meer.net>
> >>
> >> I see the obsoleting the old mechanism is a move to destroy value
> >> and invalidate a valid design, presumable based on personal
> >> prejudice.
> >
> > IMNSHO, that is a serious misrepresentation of the real reasons, which
> > were abundantly explained here.
> 
> The concerns in my first post on this thread remain valid.  The
> motivations alluded above are not enough to warrant the deprecation
> and removal of the original design

We disagree with this, and think that the motivation _is_ enough.  We
provide alternatives to defadvice that we think are better and not
less powerful.

Of course, Emacs is Free Software, so please feel free to modify your
copy such that this particular deprecation is removed.



  parent reply	other threads:[~2023-09-11 12:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 15:05 please consider keeping defadvice around Madhu
2023-09-10  8:46 ` Adam Porter
2023-09-11  1:50   ` Madhu
2023-09-11  2:28     ` Eli Zaretskii
2023-09-11  2:39       ` Madhu
2023-09-11  2:55         ` Emanuel Berg
2023-09-11 12:27         ` Eli Zaretskii [this message]
2023-09-11 12:51           ` Po Lu

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=83pm2orj2f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=emacs-devel@gnu.org \
    --cc=enometh@meer.net \
    /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.