Re: Several %(expression) in org-agenda-prefix-format

[laurent.jucquois@posteo.de]

Hi Christophe,

Thanks for the pointer!

I had already tried this solution but I wasn't entirely satisfied 
because of alignment reasons.

Not all my properties have the same length, so my agenda now looks like 
this:

DUPOND 12/RG/569 (10) : My task
DURAND 16/1689/A (05; 10-12; 14) : My task

So it's better than not knowing to which case my todos relate but it 
isn't ideal for readability.

Do you know if, like org-agenda-prefix-format, I could align the result 
of concat or define the number of character the first string can occupy?

Thanks in advance,

Laurent

Am 15.04.2016 00:37 schrieb Christophe Schockaert:
> laurent.jucquois@posteo.de writes:
> 
>> Hi list,
>> 
>> I'm trying to setup some custom agenda views that would be useful for 
>> my
>> work but i'm unable to define a custom org-agenda-prefix-format with
>> several %expression successfully.
>> 
> [...]
>> I've come up with the following (mal-functionning)
>> org-agenda-prefix-format:
>> 
>> %(org-get-entry (point) "Case" t) %(org-entry-get (point) "CaseNum" t)
>> %(org-entry-get (point) "FiscalYear" t)
> 
> Hi Laurent,
> 
> I encountered the same limitation when I tried something alike.
> 
> I finally solved it using 'concat' in one unique %expression :
> 
> (org-agenda-prefix-format
>   "%((concat (or (org-entry-get (point) \"Case\" t) \"\") \" \"
>              (or (org-entry-get (point) \"CaseNum\" t) \"\") \" \"
>              (or (org-entry-get (point) \"FiscalYear\" t) \"\") \" 
> \"))")
> 
> For better readability in the agenda, or more complex expressions, I
> thought I could write an entire function for handling them, but I never
> dit.
> 
>> I would really appreciate that someone points me into the right
>> direction.
>> 
>> Thanks,
>> 
>> Laurent
> Well, I hope you'll be able to get something from this direction :-)
> 
> Christophe