[Top][All Lists]

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

Re: [O] how to group together fields

From: Michael Brand
Subject: Re: [O] how to group together fields
Date: Sun, 23 Feb 2014 08:32:39 +0100

Hi Stefan

On Sun, Feb 23, 2014 at 2:12 AM, Stefan Huchler <address@hidden> wrote:
> that works great, sadly I have to type in the name of the shop
> redundantly but I can live with that, with a good org-capture template I
> could tab-complete them so it would not be that problem.
> I dont want to bother you endlessly but just if you happen to know that
> randomly:
> can you somehow define a template that autocompletes to all other values
> like that:
> %^{Shop|shop 1|shop 2|**all-knows-old-choices**}

Although there are many completion tools I doubt that there is one
which knows in which Org table column you are.

But [...]_ALL to predefine Org property values to be selected easily
in the column view as described here
knows in which column you are. To make benefit of this you could use a
flat tree with an entry for each purchase and a property for product,
shop and rating and capture the column view with
into the known table "#+NAME: data" to be processed further.

> A second question for me in trying to understand your code:
>  @I$4..@>$4
> I get @> stands for something like first line or is it a * wildcard? I
> should find that somewhere in doku but what does @I stand for?

@> is the last row, @I is the first hline to exclude the table header
that could have more than one line. For both and more see


reply via email to

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