Nicolas Goaziou writes:
Hello,
> You may want to read my answer again. There is no "write this, write
> that" in it. I'm pointing out what is missing or flawed and _suggesting_
> alternative approaches.
I appreciate your comments and input, but unfortunately I gave up on the
original idea becau
Hello,
Thorsten Jolitz writes:
> Thanks for the review and the comments. But this looks like an entirely
> different function to me
I think you're confused between `org-element-at-point' and
`org-entry-properties'. As I pointed out, there are properties that
ought to stay specific to the former
Hi,
Thorsten Jolitz writes:
> Nicolas Goaziou writes:
>
>> Thorsten Jolitz writes:
>>
>>> here is my first take of rewriting `org-entry-properties'.
>>
>> Interesting. A first round of comments follows.
> [...]
> But this looks like an entirely different function to me, and IMO it
> does not m
Nicolas Goaziou writes:
> Hello,
>
> Thorsten Jolitz writes:
>
>> here is my first take of rewriting `org-entry-properties'.
>
> Interesting. A first round of comments follows.
Thanks for the review and the comments. But this looks like an entirely
different function to me, and IMO it does not
At Mon, 04 Aug 2014 00:07:46 -0400,
Aaron Ecay wrote:
>
> Hi Erik,
>
> 2014ko abuztuak 3an, Erik Hetzner-ek idatzi zuen:
> >
> > […]
> >
> > This allows me to search with subject={Bar}, which is very helpful.
> > But it would be nice if org supported multi-valued properties.
>
> It does, at le
Hi Erik,
2014ko abuztuak 3an, Erik Hetzner-ek idatzi zuen:
>
> Hi John,
>
> Thanks for the tips! I have been using this:
>
> * Foo
> :PROPERTIES:
> :subject: Bar; Baz
> :END:
>
> This allows me to search with subject={Bar}, which is very helpful.
> But it would be nice if org supported
Hi John,
Thanks for the tips! I have been using this:
* Foo
:PROPERTIES:
:subject: Bar; Baz
:END:
This allows me to search with subject={Bar}, which is very helpful.
But it would be nice if org supported multi-valued properties. Again,
though, I don’t know how hard this would be.
best, E
I have used the following approaches in the past:
Lisp lists, and use read later to get them.
* Some heading
:PROPERTIES:
:SUBJECT: '(subject1 subject2 subject3)
:END:
#+BEGIN_SRC emacs-lisp
(read (org-entry-get (point) "SUBJECT"))
#+END_SRC
#+RESULTS:
| quote | (subject1 subject2 subjec
At Fri, 01 Aug 2014 01:21:47 +0200,
Thorsten Jolitz wrote:
>
> Hi List,
>
> here is my first take of rewriting `org-entry-properties'.
>
> The existing function predates the new parser and some Org variables,
> and thus does the parsing and the property classification itself. The
> new version l
Hello,
Thorsten Jolitz writes:
> here is my first take of rewriting `org-entry-properties'.
Interesting. A first round of comments follows.
> Implementation goals were:
>
> 1. (almost) full backward-compability. The parser upcases user
>properties, thus case-sensitivity is lost after pars
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> here is my first take of rewriting `org-entry-properties'.
>
> I didn't take the time to closely look at the change, but thanks
> for working on this.
>
> My main concern with anything that touches `org-entry-properties'
> is whether ag
Hi Thorsten,
Thorsten Jolitz writes:
> here is my first take of rewriting `org-entry-properties'.
I didn't take the time to closely look at the change, but thanks
for working on this.
My main concern with anything that touches `org-entry-properties'
is whether agenda generation is affected in
Hi List,
here is my first take of rewriting `org-entry-properties'.
The existing function predates the new parser and some Org variables,
and thus does the parsing and the property classification itself. The
new version leaves parsing to the parser and property classification
(mostly) to existin
13 matches
Mail list logo
