From: Matt Price <moptop99@gmail.com>
To: Bob Newell <bobnewell@bobnewell.net>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: multiple indirect buffers, and limiting to a drawer
Date: Wed, 2 Oct 2013 05:50:54 -0400 [thread overview]
Message-ID: <CAN_Dec-qoL8OsfeNDTKHHKy0-Gj5qdc8yHiVzWc3BAOrHP5M8g@mail.gmail.com> (raw)
In-Reply-To: <87mwmskcyp.fsf@bobnewell.net>
On Tue, Oct 1, 2013 at 3:28 PM, Bob Newell <bobnewell@bobnewell.net> wrote:
> Aloha Matt,
>
> For some while I've been also working on my "writer-mode" for org-mode,
> and run into similar problems. (However, I don't think I ever intend
> writer-mode for general release; it will probably just remain something
> I use myself.)
>
> I ran into similar problems, trying to emulate Scrivener and others. I
> only seem to be able to figure out a thin nav panel on the left and a
> bigger text panel on the right. I didn't get around the problem with
> virtual buffers having the same modal properties as the main buffer. In
> particular, buffer-local key bindings carry over from the index buffer
> to the main buffer, which is A Royal Pain.
This in particular is something I wish could be solved. Just reading
the documentation it looks as though using "mike-indirect-buffer"
instead of "clone-indirect-buffer" will permit one to set all the
modal properties of the new buffer independently, though it may be
frustrating to address the indirect bufffer in a function called from
the first buffer (maybe not, though?). cf.
http://www.gnu.org/software/emacs/manual/html_node/elisp/Indirect-Buffers.html
and http://www.emacswiki.org/emacs/IndirectBuffers
>
> But perhaps I'm looking for different features than you are. Mainly, I
> wanted a template system for scenes, characters, etc. (easy enough), a
> lot of statistics, both global and per-story (not conceptually difficult
> but took much time), and a good darkroom mode (much more of a challenge
> than I expected, and seems to vary among environments/releases, etc.;
> that is to say, most of the published emacs darkroom code didn't work
> for me).
>
> I've also got some fluff such as typing sounds, word frequency analysis,
> a name generator, etc.
>
> It's nothing special but I use it every day. However, I'm more than
> willing to throw it over and use your code once it's developed! I'm sure
> you're coding it much, much better and with concepts that are better
> thought through.
That sounds pretty great, actually. So, I would love to see what you have.
>
> A hui hou,
>
> --
> Bob Newell
> Honolulu, Hawai`i
lucky!
prev parent reply other threads:[~2013-10-02 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 13:44 multiple indirect buffers, and limiting to a drawer Matt Price
2013-10-01 17:19 ` Thorsten Jolitz
2013-10-02 10:13 ` Matt Price
2013-10-02 11:19 ` Thorsten Jolitz
2013-10-01 21:37 ` Myles English
2013-10-02 9:54 ` Matt Price
[not found] ` <87mwmskcyp.fsf@bobnewell.net>
2013-10-02 9:50 ` Matt Price [this message]
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_Dec-qoL8OsfeNDTKHHKy0-Gj5qdc8yHiVzWc3BAOrHP5M8g@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=bobnewell@bobnewell.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 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).