From: SAKURAI Masashi <m.sakurai@kiwanami.net>
To: kyle@nonpolynomial.com
Cc: emacs-orgmode@gnu.org, mwe012008@gmx.net
Subject: Re: calfw, get rid of file names
Date: Wed, 13 Jun 2012 11:35:41 +0900 [thread overview]
Message-ID: <20120613023555.E065C13C5B2@vps1.kiwanami.net> (raw)
In-Reply-To: <CAF1EFcej0gsBAFvCDNw1VrL=bW73UhcAvhGM2P103VGMyx=R+g@mail.gmail.com>
Hi,
I'm sorry for my late response.
At Tue, 12 Jun 2012 12:14:29 -0700,
Kyle Machulis wrote:
> :
> But yeah, that is definitely a way to change the output, but on
> further inspection it doesn't look like the right one. If you check
> out calfw-org.el, there's a useful defvar,
> cfw:org-schedule-summary-transformer. This allows you to write your
> own summary line transformer without even needing to advise, so you
> could just copy cfw:org-summary-format, chop it up to your hearts
> content, then set the variable without modifying the package at all.
> I'll probably do this myself.
Yes. That is my intent for customization.
However, I think calfw-org should be improved for better integration
between org-mode and calfw.
Because I'm not an user of the org-mode scheduling (I'm using howm
mainly), I have little idea for better summarizing the items and
calfw-org customization.
If you give me some idea or patches, I would include them.
(I may have to involve org-mode users for integration...)
Thank you,
--
SAKURAI, Masashi (family, given)
m.sakurai@kiwanami.net
prev parent reply other threads:[~2012-06-13 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a54ea9xa8e.ln2@news.c0t0d0s0.de>
2012-06-12 1:47 ` calfw, get rid of file names Kyle Machulis
2012-06-12 7:56 ` Ivan Vilata i Balaguer
[not found] ` <0sbja9xkjk.ln2@news.c0t0d0s0.de>
2012-06-12 10:30 ` Ivan Vilata i Balaguer
2012-06-12 19:14 ` Kyle Machulis
2012-06-13 2:35 ` SAKURAI Masashi [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=20120613023555.E065C13C5B2@vps1.kiwanami.net \
--to=m.sakurai@kiwanami.net \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@nonpolynomial.com \
--cc=mwe012008@gmx.net \
/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).