emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] Re: Multiple column views for one file


From: Matt Lundin
Subject: [Orgmode] Re: Multiple column views for one file
Date: Thu, 31 Dec 2009 12:39:03 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)

Thomas Leitner <address@hidden> writes:

> I don't know if org-mode supports having multiple column views for one
> file currently but I did not find a way to do the following.
>
> What I have is a journal file in org-mode in which I record, for
> example, films I have seen, books I have read and kilometres I have
> run. All of these entries have properties based on their type, for
> example, films have the properties Genre, Year and Director. Now I
> would like to get a sparse tree for all entries tagged with `film` and
> use a special column view for the films. However, when I define the
> #+COLUMNS variable at the top, this procedure only works for films, and
> not for books or other entry types which have different properties.
>
> Therefore it would be nice to be able to define several column views
> and the possibility to switch between them. It is currently possible to
> disable column view by pressing `q` when the cursor is on a head line
> in column view. It should probably be no problem to add another hotkey
> like `s` for switching to a different column view. The different column
> views could be defined like this:
>
> #+COLUMNS: films %70ITEM(Details) %TAGS(Context) %Genre %Year %Director
> #+COLUMNS: books %70ITEM(Details) %TAGS(Context) %Author %Year %Pages
>
> It seems that org-mode currently ignores the column view names ("films"
> and "books") so this would be backwards compatible.
>
> I'm still at the beginning of learning Elisp, so I'm not able to
> implement this myself and would like to know if others find this
> proposal useful and if it could be implemented?  

AFAIK, it is not possible to switch between multiple column overlays for
the same subtree. One immediate solution, however, would be to keep all
your film entries in a subtree and to define a local column view for the
subtree. E.g.,

--8<---------------cut here---------------start------------->8---
* Films
  :PROPERTIES:
  :COLUMNS: %70ITEM(Details) %TAGS(Context) %Genre %Year %Director
  :END:
** Citizen Kane
--8<---------------cut here---------------end--------------->8---

The same method could be used for books, running, etc.

Another 

Best,
Matt




reply via email to

[Prev in Thread] Current Thread [Next in Thread]