emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Alexander Gerds <tag@biostat.ku.dk>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: org agenda extensions
Date: Fri, 11 Jan 2013 21:50:35 +0100	[thread overview]
Message-ID: <86vcb3xx44.fsf@biostat.ku.dk> (raw)
In-Reply-To: <87zk0f1yas.fsf@bzg.ath.cx> (Bastien's message of "Fri, 11 Jan 2013 17:26:03 +0100")

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]


sure, here it comes (attached to this mail). to try my example you need
to evaluate the file test.el (also attached) and the following
expression:

(test-overriding-format "~/saved-attachments/test.org")

after saving test.org (also attached) in folder ~/saved-attachments/

does this work for you?


Bastien <bzg@altern.org> writes:

> Hi Thomas,
>
> Thomas Alexander Gerds <tag@biostat.ku.dk> writes:
>
>> with the aim to show properties in custom match views, I have been
>> experimenting with new variables:
>>
>> org-agenda-overriding-agenda-format
>> org-agenda-property-list
>>
>> then, tweaking the function org-scan-tags this enables custom format for
>> the agenda lines, optionally showing properties (without invoking
>> org-columns).
>>
>> you can test this here
>
> Thanks for experimenting with this -- could you send your code as a
> patch against current maint or master branch?
>
> That's easier for me to read/check/test... otherwise I'll have a look
> later on next week at best.
>
> Thanks,
--
Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics
University of Copenhagen, Øster Farimagsgade 5, 1014 Copenhagen, Denmark
Office: CSS-15.2.07 (Gamle Kommunehospital)
tel: 35327914 (sec: 35327901) 


[-- Attachment #2: patch-agenda-overriding-format-org.el --]
[-- Type: application/emacs-lisp, Size: 2162 bytes --]

[-- Attachment #3: test.el --]
[-- Type: application/emacs-lisp, Size: 1547 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #4: test.org --]
[-- Type: text/x-org, Size: 208 bytes --]

** a test entry
   :PROPERTIES:
   :filename: [[bla.txt]]
   :birthday: <2013-01-11 Fri>
   :END:
** another test entry
   :PROPERTIES:
   :filename: [[blub.txt]]
   :birthday: <2013-01-11 Fri 8:38>
   :END:

  reply	other threads:[~2013-01-11 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 10:47 org agenda extensions Thomas Alexander Gerds
2013-01-11 16:26 ` Bastien
2013-01-11 20:50   ` Thomas Alexander Gerds [this message]
2013-01-12  7:26     ` Bastien
2013-01-12  7:43       ` Thomas Alexander Gerds
2013-01-12  8:43         ` Bastien
2013-01-12  9:03           ` Thomas Alexander Gerds
2013-01-12  9:25             ` Bastien
2013-01-12  9:36               ` Thomas Alexander Gerds
  -- strict thread matches above, loose matches on Subject: below --
2013-01-11 13:35 Thomas Alexander Gerds

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=86vcb3xx44.fsf@biostat.ku.dk \
    --to=tag@biostat.ku.dk \
    --cc=bzg@altern.org \
    --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).