From: Kyle Machulis <kyle@nonpolynomial.com>
To: Michael Welle <mwe012008@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: calfw, get rid of file names
Date: Tue, 12 Jun 2012 12:14:29 -0700 [thread overview]
Message-ID: <CAF1EFcej0gsBAFvCDNw1VrL=bW73UhcAvhGM2P103VGMyx=R+g@mail.gmail.com> (raw)
In-Reply-To: <0sbja9xkjk.ln2@news.c0t0d0s0.de>
On Tue, Jun 12, 2012 at 1:40 AM, Michael Welle <mwe012008@gmx.net> wrote:
> The thing Kyle wanted to point out is that you can customise
> the item in the above advice. (message item) just prints the item to the
> status line.
>
> Since I'm a bit short on time at the moment I cheated a little bit and
> manipulated the function cfw:org-summary-format (calfw-org.el). At the
> end of this function I excluded the buffer name from the concatenation.
Hah, wow, ok, I actually completely was not paying attention when I
copy/pasted that, just thought "Oh I remember fixing that" and didn't
realize I never actually /finished/ the function, and hadn't used
calfw much since. Oops. :)
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.
Also
next prev parent reply other threads:[~2012-06-12 19:14 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 [this message]
2012-06-13 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='CAF1EFcej0gsBAFvCDNw1VrL=bW73UhcAvhGM2P103VGMyx=R+g@mail.gmail.com' \
--to=kyle@nonpolynomial.com \
--cc=emacs-orgmode@gnu.org \
--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).