From: Boyan Penkov <firstname.lastname@example.org>
To: Carsten Dominik <email@example.com>
Subject: Re: Remove filename from agenda view?
Date: Fri, 4 Jan 2013 08:52:44 -0500 [thread overview]
Message-ID: <5226E697-474E-4052-93AF-E9334F566444@gmail.com> (raw)
On Jan 4, 2013, at 2:02 AM, Carsten Dominik <firstname.lastname@example.org> wrote:
> On 4.1.2013, at 06:28, Nick Dokos <email@example.com> wrote:
>> Boyan Penkov <firstname.lastname@example.org> wrote:
>>> In the default agenda view (C-c a), the leftmost column is the org-mode file name from which the given item stems. However, I use a single file for all my actionables, and would like to eliminate this column, as it wastes 12 or so characters worth of space on the left of the agenda.
>> Not quite: it is the "category" of the item which, if absent, is
>> defaulted to the filename. Check section 10.4.1, "Categories", of
>> the org manual for more information - evaluate the following:
>> (info "(org) Categories")
>>> Can anyone point me in the right direction with a .emacs file snippet?
>> AFAIK, you cannot eliminate it in any simple way.
> Well, you can customize org-agenda-prefix-format and remove the "%-12:c" from each of the strings where you do not want the category to be shown. Note that the two leading space characters in these formats are necessary IIRC, for technical reasons.
> (setq org-agenda-prefix-format
> '((agenda . " %i %?-12t% s")
> (timeline . " % s")
> (todo . " %i ")
> (tags . " %i ")
> (search . " %i "))
I can confirm that this works pretty brilliantly.
> - Carsten
next prev parent reply other threads:[~2013-01-04 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 3:23 Remove filename from agenda view? Boyan Penkov
2013-01-04 5:28 ` Nick Dokos
2013-01-04 7:02 ` Carsten Dominik
2013-01-04 13:52 ` Boyan Penkov [this message]
2013-01-04 15:27 ` Nick Dokos
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).