emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: SAKURAI Masashi <m.sakurai@kiwanami.net>
To: bzg@altern.org
Cc: emacs-orgmode@gnu.org
Subject: Re: New backend for org-agenda: (Was Calendar-like view of	the org-agenda)
Date: Wed, 20 Jul 2011 16:50:46 +0900	[thread overview]
Message-ID: <20110720075047.13A8013C4EB@vps1.kiwanami.net> (raw)
In-Reply-To: <87d3h7w5nd.fsf@gnu.org>

Hi Bastien,

At Tue, 19 Jul 2011 01:06:14 +0200,
Bastien wrote:
> :
> > I'm sure that the caching mechanism is useful, but I'm not sure that
> > we should do it with paying the large cost of rewrite whole codes.
> 
> FWIW, this is a two separate steps process: 1) write a usable cache, 
> then 2) re-implement (parts of) the agenda by using it.
> 
> I think (1) could be interesting /per-se/ and if it helps calfw, then
> it's even more interesting.

What does '/per-se/' mean ?
Excuse me for asking a trivial word.

I'm also think about cache in the calfw side, such as an alist:
(date . [a list of contents]). Then, uses can refresh the cache
explicitly. It is easy to implement.

Is the plan(1) the same idea?


Regards,
--
SAKURAI, Masashi (family, given)
m.sakurai@kiwanami.net

  parent reply	other threads:[~2011-07-20  7:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10 15:41 New backend for org-agenda: (Was Calendar-like view of the org-agenda) SAKURAI Masashi
2011-07-12  7:37 ` Bastien
2011-07-16 16:22   ` SAKURAI Masashi
2011-07-18 23:06     ` Bastien
2011-07-18 23:20       ` Matthew Sauer
2011-07-18 23:54         ` Bastien
2011-07-20  7:50       ` SAKURAI Masashi [this message]
2011-07-20 12:43         ` Rasmus
2011-07-20 13:31         ` New backend for org-agenda: Giovanni Ridolfi
2011-07-21  4:38           ` New backend for org-agenda: (Was Calendar-like view of the org-agenda) SAKURAI Masashi
2011-07-21  9:52         ` Bastien
2011-07-23  2:35           ` SAKURAI Masashi

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=20110720075047.13A8013C4EB@vps1.kiwanami.net \
    --to=m.sakurai@kiwanami.net \
    --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).