From: Marcelo de Moraes Serpa <firstname.lastname@example.org>
To: Marcelo de Moraes Serpa <email@example.com>,
Org Mode <firstname.lastname@example.org>,
Subject: Re: Frames and the agenda
Date: Tue, 28 Feb 2012 10:57:11 -0600 [thread overview]
Message-ID: <CACHMzOE1Gh4Biq4hzL+pUuWypKO52-hTAjkscbDwpYqWbhAJCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
Anyway, I can't emphasize enough how useful this feature is. Having
different agenda filtered views at the same time is a timesaver. This
should be in the main org branch!
Thanks for that, Max.
On Tue, Feb 28, 2012 at 10:55 AM, Marcelo de Moraes Serpa <
> Thanks guys, que quickfix worked. I'll see if I can rebase to org's HEAD
> myself, let's see if conflicts don't scare me away. Or perhaps just apply
> the fix manually.
> - Marcelo.
> On Tue, Feb 28, 2012 at 3:49 AM, Max Mikhanosha <email@example.com> wrote:
>> At Mon, 27 Feb 2012 18:52:09 -0600,
>> Marcelo de Moraes Serpa wrote:
>> > Although everything else is working great, I'm getting the following
>> > error message when trying to follow links to org files:
>> > "cond: Symbol's function definition is void: org-in-clocktable-p [11
>> My branch is probably a few weeks behind the master, so the fix that
>> Nick mentioned above is not there.
>> You can temporarily fix this by doing "M-x load-library RET
>> I'll rebase my branch to the latest origin/master soon, with the pace
>> of development in org-mode its hard to be completely synced up all the
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
next prev parent reply other threads:[~2012-02-28 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 18:38 Frames and the agenda Marcelo de Moraes Serpa
2012-02-24 20:48 ` Max Mikhanosha
2012-02-27 22:45 ` Marcelo de Moraes Serpa
2012-02-28 0:52 ` Marcelo de Moraes Serpa
2012-02-28 1:44 ` Nick Dokos
2012-02-28 9:49 ` Max Mikhanosha
2012-02-28 16:55 ` Marcelo de Moraes Serpa
2012-02-28 16:57 ` Marcelo de Moraes Serpa [this message]
2012-02-29 17:55 ` Rebased to the latest tip Max Mikhanosha
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).