From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Carsten Dominik" Subject: Re: Automatically indent text when return is hit in an org buffer. Date: Mon, 17 Dec 2007 09:25:03 +0100 Message-ID: References: <87abojxj9s.fsf@enki.rimspace.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J4BHi-0007Uz-Th for emacs-orgmode@gnu.org; Mon, 17 Dec 2007 03:25:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J4BHi-0007UT-3c for emacs-orgmode@gnu.org; Mon, 17 Dec 2007 03:25:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J4BHh-0007UB-AX for emacs-orgmode@gnu.org; Mon, 17 Dec 2007 03:25:09 -0500 Received: from wa-out-1112.google.com ([209.85.146.178]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J4BHg-0005ru-EX for emacs-orgmode@gnu.org; Mon, 17 Dec 2007 03:25:08 -0500 Received: by wa-out-1112.google.com with SMTP id k34so3219983wah.10 for ; Mon, 17 Dec 2007 00:25:03 -0800 (PST) In-Reply-To: <87abojxj9s.fsf@enki.rimspace.net> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Daniel Pittman Cc: emacs-orgmode@gnu.org On Dec 10, 2007 5:31 AM, Daniel Pittman wrote: > G'day. I am a fan of `newline-and-indent', and turn it on for most of > the modes I routinely use, since it is almost always what I want done. > > org-mode rebinds the "return" key to `org-return', which acts > intelligently in the face of tables -- and calls `newline' hard-coded in > other cases. > > I would like to preserve that intelligence, but also to use > `newline-and-indent', so generated this patch to implement my desired > behaviour. > > By default this changes nothing: org behaves exactly the same way as it > did previously. > > > If this isn't the right approach I am happy to rework the patch to > better match the rest of the software. > > > Finally, while I believe that this is a trivial change and will not need > assignment papers anyway I can note two things: > > * there are copyright assignments from me to the FSF on record already > for Emacs and constituents, so I don't know if I need a new > assignment. If you have a past-and-future-changes assignment for Emacs, that would be enough. Please mail me a PDF copy of the assignment for my records. Thanks! - Carsten