From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode outside Org-mode
Date: Thu, 04 Apr 2013 16:09:21 +0200 [thread overview]
Message-ID: <874nfm9ylq.fsf@gmail.com> (raw)
In-Reply-To: CAJcAo8uKQV-NzN9yhc1p83Pen0jVABk4fjDfZ2qj8OQogyfDnA@mail.gmail.com
Samuel Wales <samologist@gmail.com> writes:
> Great write-up, Thorsten.
thanks
> There is a whole other set of options also. I don't know if they are
> close enough for you to include, but it's worth pointing them out.
>
> These are in the general category of Org annotations. Instead of
> editing Org in a temporary buffer, you use a real, permanent Org file
> (can include an agenda file).
>
> There are two types of options: those that allow you to use Org to
> annotate external files without changing those files, and those that
> allow you to annotate external files by putting persistent markers in
> them.
>
> In both types, you can in principle do C-c ' to get to your Org agenda
> files location from your external files, and the same thing in
> reverse.
>
> The existing mechanisms include org-pua.el, org-registry.el, and
> org-annotate.el.
>
> In principle, you should be able to annotate web pages in w3m.el and
> dired entries and info notes also.
>
> To me, there is a lot of possibility here.
> It should also be possible to put an ID marker in an external file,
> which corresponds exactly to the Org IDs in a canonical entry in your
> agenda files. Then C-c ' can bounce between the external file and
> your agenda file.
please see my recent post about 'navi-mode' for Org-mode buffers.
'navi-mode' actually is a kind of permanent associated buffer tightly
coupled to the original Org-mode or source code buffer. It uses markers
to allow bouncing between the associated 'twin-buffers', but non of the
libraries you mention. However, I worked out my own system to ensure
that the *Navi* buffer is always up-to-date after modifying the
original-buffer, and to locate point at a logical position in the
navi-buffer even when the view (on the original-buffer has changed
drastically).
The temporary editing of source-code in Org-mode buffers is inspired by
org-src.el (or Org Babel), its very fast and convenient, just like
editing source-code blocks in Org-mode.
Just try it out, maybe it is similar to what you imagine (only with
different implementation).
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-04-04 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 15:39 Org-mode outside Org-mode Thorsten Jolitz
2013-03-15 16:47 ` Thomas S. Dye
2013-04-03 18:23 ` Samuel Wales
2013-04-04 14:09 ` Thorsten Jolitz [this message]
2013-04-04 20:17 ` Samuel Wales
2013-04-05 9:51 ` Thorsten Jolitz
2013-04-07 1:05 ` Eric Schulte
2013-04-07 7:49 ` Bastien
2013-04-12 1:04 ` Samuel Wales
2013-04-13 20:48 ` Samuel Wales
2013-04-12 1:19 ` Samuel Wales
2013-04-12 10:44 ` Thorsten Jolitz
2013-04-13 20:45 ` Samuel Wales
2013-04-27 8:35 ` Thorsten Jolitz
2013-04-24 14:20 ` Alexander Vorobiev
2013-04-24 18:39 ` Thorsten Jolitz
2013-04-25 17:33 ` Thorsten Jolitz
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=874nfm9ylq.fsf@gmail.com \
--to=tjolitz@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).