emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: jmcbray@carcosa.net (Jason F. McBrayer)
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Idea: Agenda Search publish?
Date: Tue, 24 Apr 2007 13:51:31 -0400	[thread overview]
Message-ID: <m1y7khu0d8.fsf@bertrand.carcosa.net> (raw)
In-Reply-To: <4bbea17378fe63d761a2ce6a80eddb04@science.uva.nl> (Carsten Dominik's message of "Mon\, 23 Apr 2007 22\:39\:49 +0200")

Carsten Dominik <dominik@science.uva.nl> writes:

> On Apr 2, 2007, at 16:06, Tim O'Callaghan wrote:
>> What about adding the generated searches as a publishable source?
>> possibly  by adding to
>> org-agenda-custom-commands.
>
> Would htmlize be enough to publish this, or do people have more fancy
> ideas about how this should work?

I'm a bit of mixed minds on this topic.

Unrealistic wishful thinking that I should implement my damn-self:

    Tag searches are always contexts for me.  If I want to export the
    results of a tag search, it's probably because I want to print a
    context that is not @Computer and put it in my planner.  The
    output ought to be something that eventually yields a PDF file
    that looks like a DIY Planner (http://www.diyplanner.com/) context
    page.

    Likewise, daily/weekly agenda views ought to yield DIY Planner-ish
    calendar pages.

    This is a totally non-serious proposal, because I expect anyone to
    have completely different preferences for from me, and it's not
    worth anyone else's time to implement exactly what I want :)

 Totally realistic, requires little work for anyone:

    Provide a utility function for calling htmlize on the agenda
    buffer and saving the results; doesn't need to be more integrated
    than that.  You can then generate somewhat naff PDFs which are at
    least the right paper size and so forth by printing from a web
    browser.

Alternative idea:

    Many people seem to be using scripts (orgna.pl, for example) to do
    this kind of thing, which seems to be perfectly reasonable.  Maybe
    a good idea would be to make it easier for scripts by letting
    org-mode handle the logic of selecting things, then just feeding
    the data to the script in a sensible format?

    org-batch-agenda /very nearly/ does this.  I think it could be
    improved as an adjunct to external script-writing by providing two
    things:

    1. An unambiguously parseable output format with some semantic
       content.  An XML microformat would do dandy for this, but
       something like adequately-escaped comma-separated text with
       defined columns for category, status, title, and tags would
       also do well enough.

    2. Support for arbitrary tag/keyword searches, though continued
       support for cmd-keys from org-agenda-custom-commands would
       still be conveient.

Anyone else's thoughts?

-- 
+-----------------------------------------------------------+
| Jason F. McBrayer                    jmcbray@carcosa.net  |
| If someone conquers a thousand times a thousand others in |
| battle, and someone else conquers himself, the latter one |
| is the greatest of all conquerors.  --- The Dhammapada    |

  reply	other threads:[~2007-04-24 17:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 14:06 Idea: Agenda Search publish? Tim O'Callaghan
2007-04-05  9:23 ` Bastien
2007-04-05 10:03   ` Leo
2007-04-05 16:56     ` Carsten Dominik
2007-04-05 18:25       ` David O'Toole
2007-04-05 18:40         ` Leo
     [not found]           ` <3d6808890704051213i1a3bc737wfa715f4b7f2f0c25@mail.gmail.com>
2007-04-05 19:29             ` Tim O'Callaghan
2007-04-05 20:56         ` Jason F. McBrayer
2007-04-11  9:09           ` chris
2007-04-11 11:01             ` Bastien
2007-04-11 12:38               ` chris
2007-04-11 20:26                 ` publish archives François Lagarde
2007-04-11 14:00             ` Idea: Agenda Search publish? Leo
2007-04-05 18:37       ` Leo
2007-04-23 20:39 ` Carsten Dominik
2007-04-24 17:51   ` Jason F. McBrayer [this message]
2007-04-25 21:21   ` Leo

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=m1y7khu0d8.fsf@bertrand.carcosa.net \
    --to=jmcbray@carcosa.net \
    --cc=dominik@science.uva.nl \
    --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).