From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ivan Andrus Subject: Re: org-writers-room sort of works! just in time for NaNoWriMo Date: Fri, 1 Nov 2013 00:07:24 -0600 Message-ID: <673BE3CF-22F6-473E-A26E-0CF6F717681E@gmail.com> References: Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vc7tL-0004sp-VP for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 02:07:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vc7tG-0006x9-JY for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 02:07:31 -0400 Received: from mail-ie0-x231.google.com ([2607:f8b0:4001:c03::231]:35365) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vc7tG-0006x4-FC for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 02:07:26 -0400 Received: by mail-ie0-f177.google.com with SMTP id e14so6715023iej.36 for ; Thu, 31 Oct 2013 23:07:26 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matt Price Cc: Org Mode Looks cool. I already opened one issue on github. :-) -Ivan On Oct 31, 2013, at 10:00 PM, Matt Price wrote: > I have just pushed a more-or-less-working version of my "Org Writer's > Room" mode to github: > > https://github.com/titaniumbones/org-writers-room > > It's a very simple set of mostly-trivial minor modes that creates a > Scrivener-like writing environment for org users. put > org-writers-room.el in your load path, load or require it, and then, > in an org-mode file, type M-x org-writers-room. This will close all > but one of your existing windows, split the remaining window into 3 > columns, and populate them as follows: > > - left-hand column contains your unnarrowed original org file. > Ideally it should be org-global-cycle'd to "children" but I can't see > how to instruct org-cycle or org-global-cycle to set visibility to a > particular level. (I would also like to have the entire "PROPERTIES" > drawer and ALL NON-HEADING CONTENTS of the heading hidden at all > times, but I can't figure that out either). > - wide center column contains an indirect buffer narrowed to the > subtree at point in the main buffer. > - right-hand column contains a second indirect buffer narrowed to the > properties drawer of the subtree at point. > > In the left-hand column, press C-c C-x b or just RET on a heading to > "activate" it and place its contents in the other two columns. > > It could definitely be a lot better but it's not so terrible! It > allows you to have an overview of the project as a whole, a clean view > of the section you're writing at the moment, and a look over at the > metadata -- the "back of the index card" from Scrivener -- to remind > you of what you're trying to do in the setion you're currently > writing. > > I would really like to make the metadata part more robust, with maybe > some functions that let you edit the property values without touching > the property names, and perhaps some fontlock trickery to make it look > prettier. Siilarly, I'd like to do a bit more with the guide and evne > with the main section. Eventually, I'd also like to make it > compatible with zotero-plain so I can start to use citations properly > in org-mode instead of inserting them post-facto in libreoffice > (ugh!). But for now I'm pleased it works at all. > > I would love it if people would try it out. It should be much more > stable than the last, awful version I posted some months ago. The > code is very simple and mostly just > > (1) rewrites the org functions for dealing with indirect buffers, so > that the indirect buffers don't need to be clones of the parent buffer > (2) changes some keybindings > (3) sets up the stable window configuration described above. > > I would really love it if some other people would try it out, and (oh > please!) suggest/implement improvements. I am well aware of my > terrible coding limitations. > > Thank you, > matt > > PS, the readme on github is a little out of date, but the code itself > is mostly documented so I hope that helps. Though there's no general > documentation at the top of the file -- oops, sorry. >