From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org Writer's room
Date: Thu, 06 Dec 2012 16:08:56 +0800 [thread overview]
Message-ID: <87fw3jfvqf.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAN_Dec84q9a5NHYk=Wyiw8s=s3x=itS3D9sS8ga-Z0jhNtSXdw@mail.gmail.com
Matt Price <moptop99@gmail.com> writes:
> On Wed, Dec 5, 2012 at 7:44 PM, Alan L Tyree <alantyree@gmail.com> wrote:
>> On 06/12/12 11:22, Rasmus wrote:
>>>
>>> Andrew Hyatt <ahyatt@gmail.com> writes:
>>>
>>>> This sounds like an interesting project. My advice is to make a few
>>>> screenshots that give people an idea what you are working towards.
>>>> Of course, they could be completely fake, but it would be helpful to
>>>> understand for people like me who haven't used Scrivener.
>>>
>>> I would also like to see this. It sounds nice when I read your
>>> description, but I still don't fully appreciate the idea.
>>>
>>> –Rasmus
>>>
>> I'm also very interested. I haven't used Scrivener -- what features do you
>> see as making org a *way* better writing environment?
[...]
> To start with I would like to just replicate this window structure,
> because it keeps you focused on writing, while having the larger
> structure available if you feel the need to flit around a bit. The
> third screenshot shows a semi-fake, still very primitive version of
> what I'd like to have. (I haven't figured out a good way to do the
> metadata yet).
I *really* like the idea of having a right-hand pane available showing
properties around the current point -- it could include properties from
the PROPERTIES drawer, from the structure returned by
`org-element-property', text properties, and maybe properties of the
current headline parent. I'm sort of envisioning what you get from the
"inspect element" command in Firefox.
For the left-hand pane, org-toc and org-panel in the contrib directory
(or even the org-goto interface) might provide some inspiration.
Ugh, sounds like a lot of work.
E
next prev parent reply other threads:[~2012-12-06 8:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 16:01 Org Writer's room Matt Price
2012-12-05 23:08 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fw3jfvqf.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.