Re: Development Emacs based on Emacs and magit.

["André A. Gomes" <andremegafone@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Hongyi Zhao <hongyi.zhao@gmail.com>

>> Thank you for pointing this out. Considering that Emacs is patched so
>> frequently, has it already implemented a complete
>> workflow/module/macro/function to wrap the steps described here [1]
>> with just several or one keystroke?
>
> No, because we don't want to force anything on the contributor's
> workflow.  Developing a change is not a one-keystroke thing, it
> requires writing the code, testing it, sending the patch, receiving
> review comments, modifying the code accordingly, etc. etc.  I don't
> see how this could be done with a single keystroke, even in principle.

I agree with Eli.

Even if such a single keystroke exists, how could it be useful?
Sculpting a patch is a creative activity, to some extent.  The drudgery
that might be associated with it is mitigated by a manifold of tools.
Those can be grabbed and composed as the wizard wishes.  Indeed, there's
no "ultimate" or "general" tool that mitigates all the drudgery.  But
that's obvious, no?  Tools can't get "ahead" of the problems they solve.
Perhaps that single keystroke would be yet another layer that obscures
the required real (creative) work.  There's no "recipe book" to
follow---it's part of the fun.

From my perspective, the "system" that handles patches in Emacs is
developed enough.  In fact, as an outsider, I gaze at it in awe.

The bottleneck is doing the creative work, NOT sharing it.  When the
wizard loves his craft, they go to ANY lengths to show it.  The
idiosyncrasies of the reviewing entity are not an issue.


--
André A. Gomes
"Free Thought, Free World"