[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#46627: [External] : bug#46627: [PATCH] Add new help command 'describ
From: |
Eli Zaretskii |
Subject: |
bug#46627: [External] : bug#46627: [PATCH] Add new help command 'describe-command' |
Date: |
Tue, 02 Mar 2021 08:50:56 +0200 |
> From: Richard Stallman <rms@gnu.org>
> Date: Tue, 02 Mar 2021 01:29:06 -0500
> Cc: stefan@marxist.se, 46627@debbugs.gnu.org, dgutov@yandex.ru
>
> > "Trials" in Emacs itself are not so great, IMO.
> > Someone puts something on a branch
>
> That way of tryialing something has a drawback as you say:
>
> > trial and feedback. But the only people who try
> > it are Emacs Dev aficionados who build Emacs or
> > pull stuff from Git etc.
>
> The way I suggest handling these is to put them in the release, then
> tell people a command to run to try them. That makes it easy
> to try them out.
That is only a viable option if the new feature is opt-in and doesn't
change the default behavior in any way, shape or form. (This being an
old discussion, I no longer have a clear idea whether the above
conditions are fulfilled under your proposal.) And having the new
feature on a branch first does not in any way contradict the trial by
a larger audience later, when the feature is released.
So I don't think I understand well enough what is the issue being
discussed here, as we already do all of that.