From: Rainer M Krug <r.m.krug@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org Writer's room
Date: Fri, 07 Dec 2012 14:11:51 +0100 [thread overview]
Message-ID: <50C1EB17.6090803@gmail.com> (raw)
In-Reply-To: <CAN_Dec_66H5QZOyNo_VKaAR-6Y62RHOtZXu9s9ZusoUhSS=hGQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/12/12 13:57, Matt Price wrote:
> On Fri, Dec 7, 2012 at 3:39 AM, Rainer M Krug <r.m.krug@gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> On 06/12/12 16:51, Matt Price wrote:
>>> On Thu, Dec 6, 2012 at 9:15 AM, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>>>>
>>>> On 12/06/12 20:09 PM, Matt Price wrote:
>>>>> On Thu, Dec 6, 2012 at 3:08 AM, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>>>>>> 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.
>>>>>>
>>>>> those are 3 powerful tools I hadn't used before. org-toc not working for me at the
>>>>> moment though, there might be something wrong with my .emacs setup...
>>>>
>>>> Yeah, some of that's out of date. Actually, since Org looks like it will be slowly
>>>> migrating over to a basis on org elements, that's probably a good direction to look.
>>>> `org-element-parse-buffer' will return a data structure for the current buffer that would
>>>> be ideal for creating a tree visualization.
>>>
>>> hmm, just looked at the output of that command and the data structures look like:
>>>
>>> (headline (:raw-value "The Function of Copyright" :begin 489 :end 610 :pre-blank 0
>>> :hiddenp outline :contents-begin 517 ...) (section (:begin 517 :end 610 :contents-begin
>>> 517 :contents-end 610 :post-blank 0 :parent #1)))
>>>
>>> Those integers are char numbers in the buffer -- would this list then have to be updated
>>> for every character stroke? Hmm, I also can pretty much see how to get each :raw-value and
>>> turn it into text that's presented in a buffer... but I don't understand how to associate
>>> that text with the existing headline in an org file. Speedbar seems like a much easier
>>> option, but while the org-mode parser is nowworking for me(yay!) I can't make the
>>> same-frame package work (sr-speedbar)! Gosh darn it!
>>>
>>> ANyway, thanks eveyrone, I'm going to keep needing help on this so if you have more
>>> suggestions please keep them coming..
>>
>> Looking forward to the right side of the three... As the left side is using existing
>> packages, could you post the commands needed to make it work? I only have it on the right
>> side, and I assume you are using hooks to start sr-speedbar?
>>
>
> I don't have the speedbar interface running properly yet (no time the last couple of days).
> sr-speedbar is not working right for me, so I am tryng some code from emacswiki (which is also
> posted in various places around the web):
>
> http://emacswiki.org/emacs/SpeedBar#toc1
OK - waiting for news on this front. For the time, I will be using the sr-speedbar.
>
> I'm noticing a few issues:
>
> - at least on my machine, it's not easy to click on a heading that has subheadings. THe trick
> is probably to make some improvements to the underlying org/speedbar integration.
True - works only for the "last" headers.
> - when speedbar is running in the same frame as other windows, it isn't so good at determining
> where it should open new buffers. Binding the clicks to my writers-room-pop-buffer function
> should fix that. - the builtin speedbar browsers are awesome, but I think it would be better to
> have a stripped-down interfacd that only showed the project you're working on. I guess the way
> to do that would be to extend speedbr with a new major or minor mode. (
> http://www.gnu.org/software/emacs/manual/html_node/speedbar/Major-Display-Modes.html#Major-Display-Modes
>
>
). It doesn't look that ocmplicated but I need to learn a bunch
> before I do it...
Agreed - would be very useful.
>
> All the code I have (not much) is still available at the github repo I posted at the beginning
> of this thread, https://github.com/titaniumbones/org-writers-room/
>
> I tried adding some speedbar stuff but it's very very rough! If you feel like improving it --
> that would be just super... In any case go ahead and try it ou. It doesn't do much and I'm
> pretty sure it an't do any harm to your files, but I would love some feedback. Thanks,
I unfortunately know nothing about elisp so I won't be of any help here, except testing.
If you announce some testable versions, I would be happy using them and give feedback.
Cheers,
Rainer
> Matt
>
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlDB6xYACgkQoYgNqgF2egq1rgCcDy5AEcG0DcD+CaysrfgzZfGI
ql4AnAuw4+xNmKLus81jQTJVKmuaL7Pz
=4IEa
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-07 13:12 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
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 [this message]
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=50C1EB17.6090803@gmail.com \
--to=r.m.krug@gmail.com \
--cc=Rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=moptop99@gmail.com \
/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.