emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: A new module for Org-mode: Org-X
Date: Tue, 16 Aug 2011 15:27:21 -0400	[thread overview]
Message-ID: <m262lxrwbq.fsf@140-182-243-14.dhcp-bl.indiana.edu> (raw)
In-Reply-To: <87sjp1mgui.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 16 Aug 2011 19:00:37 +0200")

Achim Gratz <Stromeko@nexgo.ed> writes:

> I can easily see how this works with bug/issue trackers.  What I'm not so
> sure is how you imagine it to work with files.  For my part I'm hoping that
> it might be able to get some interface to the various bits and pieces I've
> bookmarked and sometimes put into local versions with the ScrapBook Firefox
> extension.

The backend gets to define what the parts of an entry are.  Some backends will
import actual content into the related Org entry, while others will only
import a link back to the original content.  This is what I would do for a
backend that monitors files within an "Inbox" directory, for example.

> I'd check source code for FIXME, not TODO.

Sure, this would be configurable through both a customization variable (for
setting default behavior), and through an inherited property (as part of the
backend context).

> If org-x-states is backend specific, why not let the backend define it?

It is defined, by the ox-org backend. :)  I imagine that very soon now, I'll
pay attention to SEQ_TODO and the usual Org variable, rather than having my
own custom variable for this.

> LZW: is there really nothing in Emacs that already does this? In any case it
> seems to belong into an own library and should probably be unbundled from
> org before long.

There's really not!  I wrote it because I imagine at some point wanting to
take a snapshot of the "state" of an entry, for the purpose of accelerating
certain backends, but I haven't yet found that use.  For now, it's just living
in ox-lzw so that it's under version control.  If it becomes useful, I'll
submit it to Emacs separately and ahead of Org-X.

John

  reply	other threads:[~2011-08-16 19:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14  7:41 A new module for Org-mode: Org-X John Wiegley
2011-08-14 17:32 ` Karl Voit
2011-08-14 22:19   ` John Wiegley
2011-08-15 10:25     ` Karl Voit
2011-08-15 13:23       ` John Wiegley
2011-08-15 12:06     ` Sebastien Vauban
2011-08-15 13:25       ` John Wiegley
2011-08-15 21:29         ` Sebastien Vauban
2011-08-16 17:00 ` Achim Gratz
2011-08-16 19:27   ` John Wiegley [this message]
2011-08-16 19:42     ` Achim Gratz

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=m262lxrwbq.fsf@140-182-243-14.dhcp-bl.indiana.edu \
    --to=jwiegley@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).