From: Carsten Dominik <c.dominik@uva.nl>
To: Adam Spiers <orgmode@adamspiers.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: ITEM in column view in the agenda
Date: Thu, 29 May 2008 00:09:31 +0200 [thread overview]
Message-ID: <4E49CF17-EFC8-4A22-B048-6469CDB8C93A@uva.nl> (raw)
In-Reply-To: <20080528152659.GH20846@atlantic.linksys.moosehall>
[-- Attachment #1.1: Type: text/plain, Size: 1884 bytes --]
Hi Adam,
no, this is not too much to ask, in particular since I am doing
this kind of compaction (not duplicating info that is shown in
other columns) already in the normal column view (i.e. in
an Org buffer as opposed to the agenda buffer. In fact, the
function doing the compaction is already called, only it does
not do anything because it is trying to match a headline.
This can be easily fixed....... DONE.
This should now also work in agenda buffers, using the latest
GIT version. There is a new variable
`org-agenda-columns-remove-prefix-from-item' which can be used
to decide it the prefex should be removed. The default
it to remove it in column view, on order to optimize the use
of the window width.
HTH
- Carsten
On May 28, 2008, at 5:26 PM, Adam Spiers wrote:
> I'm trying to get a good COLUMN format for viewing the agenda in
> column view mode. Am I right in thinking that ITEM is the only
> property available for showing the actual "meat" of a given headline?
> The problem with ITEM is that it includes any leaders, plus the TODO
> keyword and priority, which leads to duplication if any of these are
> displayed in separate columns, e.g.:
>
> TODO | PRI | Task
> [snip]
> NEXT | A | personal:In 1d: NEXT [#A] book MOT | ....
> WAITING | B | personal:Sched.109x: WAITING [#B] boo | ....
>
> Of course it is very wasteful of window width to have this
> duplication, so I would like to at least be able to exclude the TODO
> keyword and priority from the ITEM column, and preferably the leaders
> too (although I would like to keep them for normal non-column agenda
> view). Asking too much as usual? ;-)
>
> Thanks!
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[-- Attachment #1.2: Type: text/html, Size: 2581 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2008-05-28 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 15:26 ITEM in column view in the agenda Adam Spiers
2008-05-28 22:09 ` Carsten Dominik [this message]
2008-05-28 23:09 ` Adam Spiers
2008-05-28 23:11 ` Adam Spiers
2008-05-29 5:49 ` Carsten Dominik
2008-05-29 5:49 ` Carsten Dominik
2008-05-29 17:11 ` Adam Spiers
2008-05-30 4:06 ` Carsten Dominik
2008-05-30 14:01 ` Adam Spiers
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=4E49CF17-EFC8-4A22-B048-6469CDB8C93A@uva.nl \
--to=c.dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@adamspiers.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).