From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Samuel Wales" <samologist@gmail.com>
Subject: feature request: org-patch command
Date: Sat, 25 Oct 2008 21:25:11 -0700
Message-ID: <20524da70810252125n5c623ffeoe9114f80ee069c22@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KtxBl-0003OU-8z
	for emacs-orgmode@gnu.org; Sun, 26 Oct 2008 00:25:17 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KtxBj-0003Nu-1p
	for emacs-orgmode@gnu.org; Sun, 26 Oct 2008 00:25:16 -0400
Received: from [199.232.76.173] (port=42788 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KtxBi-0003Nr-Rj
	for emacs-orgmode@gnu.org; Sun, 26 Oct 2008 00:25:14 -0400
Received: from nf-out-0910.google.com ([64.233.182.190]:7378)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <samologist@gmail.com>) id 1KtxBi-0005lR-NX
	for emacs-orgmode@gnu.org; Sun, 26 Oct 2008 00:25:15 -0400
Received: by nf-out-0910.google.com with SMTP id c7so560402nfi.26
	for <emacs-orgmode@gnu.org>; Sat, 25 Oct 2008 21:25:11 -0700 (PDT)
Content-Disposition: inline
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

To make it easier to patch correctly, perhaps it would help if you
could visit an org file, and simply call an org-patch command that
would do something like this:

  - create a directory as a sibling to the org source dir if it does not exist
  - put the original and a copy in it
  - remind the user to put it in load-path in front of org
  - let you edit the copy
  - give you hints on org coding style
  - remind you to use short functions that do only one thing
  - tell you how to instrument for testing
  - remind you of gnu requirements
  - tell you to run org-patch-diff to create a temporary buffer with
the correct diff output

At least, if I wanted to, say, correct a typo in an org function, I
wouldn't bother unless I could do it this easily, for fear of getting
it wrong.