From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Org Writer's room
Date: Wed, 5 Dec 2012 11:01:21 -0500 [thread overview]
Message-ID: <CAN_Dec8PfDXZCAYjwCNowwj=fgYdyQY_5vfpCp=1KEr2mKw71w@mail.gmail.com> (raw)
Hi Everyone,
Prompted by a couple of recent threads on help-gnu-emacs
(http://comments.gmane.org/gmane.emacs.help/87787), I am trying to
create a minor mode for org that would implement some of the cool
features of Scrivener
(http://www.literatureandlatte.com/scrivener.php).
Scrivener is a closed-source but still very cool authoring tool for
writers. After testdriving it, I find that Scrivener's interface
really makes it easy to concentrate on writing while still being aware
of the overall structure of a big project. Lots of my daughter's
friends use it for National Novel Writing Month, in which they try to
write a 50,000 word novel in 30 days; and I'm finding that more and
more of my students have switched to Scrivener from Word or
Libreoffice, over which it offers a lot of improvements (though it's
not so good atthings like footnotes).
Emacs is pretty different from Scrivener (!!), but I still think we
could implement some of its features, and that doing so would make
emacs/org-mode a *way* better environment for writers. So I've
started working on org-writers-room.el. I'm a terrible coder, and I
can't think in Lisp at all, so I think the code is pretty bad! And
right now it doesn't do much -- just sets up the basic window layout
and define one or two functions But the ambitions are described in
more detail on the github repository:
https://github.com/titaniumbones/org-writers-room
I would be really grateful for feedback from both coders and writers.
I'd especially love it if anyone had some ideas on how to implement
the missing features, or better yet, was able to write some code for
the project! As I say, I feel a little over my head when it comes to
elisp.
Thanks very much!
Matt
next reply other threads:[~2012-12-05 16:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 16:01 Matt Price [this message]
2012-12-05 23:08 ` Org Writer's room Andrew Hyatt
2012-12-06 0:22 ` Rasmus
2012-12-06 0:44 ` Alan L Tyree
2012-12-06 2:21 ` Matt Price
2012-12-06 7:12 ` Scot Becker
2012-12-06 8:08 ` Eric Abrahamsen
2012-12-06 8:36 ` Jambunathan K
2012-12-06 9:11 ` Rainer M Krug
2012-12-06 9:14 ` Rainer M Krug
2012-12-06 10:28 ` Rainer M Krug
2012-12-06 10:51 ` David Engster
2012-12-06 11:25 ` Rainer M Krug
2012-12-06 11:55 ` Matt Price
2012-12-06 11:58 ` Rainer M Krug
2012-12-06 11:50 ` Matt Price
2012-12-06 12:00 ` Rainer M Krug
2012-12-06 12:07 ` David Engster
2012-12-06 12:26 ` Rainer M Krug
2012-12-06 11:59 ` Matt Price
2012-12-06 12:09 ` Matt Price
2012-12-06 14:15 ` Eric Abrahamsen
2012-12-06 15:51 ` Matt Price
2012-12-07 8:39 ` Rainer M Krug
2012-12-07 12:57 ` Matt Price
2012-12-07 13:11 ` Rainer M Krug
2012-12-06 4:21 ` Yagnesh Raghava Yakkala
2012-12-06 12:00 ` Matt Price
2012-12-06 18:18 ` Yagnesh Raghava Yakkala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN_Dec8PfDXZCAYjwCNowwj=fgYdyQY_5vfpCp=1KEr2mKw71w@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).