On 12.4.2011, at 22:00, Memnon Anon wrote:
> Hi,
> Christopher Allan Webber writes:
>
>> I was once one of the many people who apparently originally
>> misunderstood what "SCHEDULED" meant, and used to set it to like, an
>> appointment time.
>
> Well, you can use it that way.
> The point is: S
Michael Brand writes:
> On Wed, Apr 13, 2011 at 16:43, Christopher Allan Webber
> Are your concerns concrete?
>
> I have thought about and tested this already before: The three example
> items above show up in the agenda, and are still correct even after
> changing with `S->'. So this "newer/futu
On Wed, Apr 13, 2011 at 16:43, Christopher Allan Webber
wrote:
> Michael Brand writes:
>> * _appointment_ that _occurs_ at bike shop (keyword inside drawer)
>> :PROPERTIES:
>> :TIMESTAMP: <2011-04-12 Tue 19:00>
>> :END:
>> * _appointment_ that _occurs_ at bike shop (keyword outside drawer)
>>
Michael Brand writes:
> Yes, I suggest to remove this limitation and would prefer TIMESTAMP
> much over OCCURANCE, APPOINTMENT (not every occurrance is an
> appointment) or any other name to avoid a second name for the same
> behavior of the existing special property TIMESTAMP and to avoid
> conf
On Wed, Apr 13, 2011 at 15:08, Christopher Allan Webber
wrote:
> Michael Brand writes:
>
>> The name could be critical. To avoid any confusions/collisions I would
>> recommend to use just that name TIMESTAMP for easy get/set access:
>>
>> * _appointment_ that _occurs_ at bike shop
>> :PROPERTIE
Michael Brand writes:
> The name could be critical. To avoid any confusions/collisions I would
> recommend to use just that name TIMESTAMP for easy get/set access:
>
> * _appointment_ that _occurs_ at bike shop
> :PROPERTIES:
> :TIMESTAMP: <2011-04-12 Tue 19:00>
> :END:
>
Maybe you're alre
Matt Lundin writes:
> O.K. I wasn't clear what you meant by property in the original post.
> What about :APPOINTMENT:?
"Appointment" makes a lot of sense. +1. Better than "occurance" I
think. :)
--
The bottom line.
On Tue, Apr 12, 2011 at 22:52, Christopher Allan Webber
wrote:
> ** Pick up bike from the shop
> :PROPERTIES:
> :OCCURANCE: <2011-04-12 Tue 19:00>
> :END:
>
> etc.
>
> It's nice to know there's a meta-property for TIMESTAMP, but I'm
> specifically looking for a nice place to put that timesta
Matt Lundin writes:
> There is a special property name for active timestamps: TIMESTAMP. You
> can access the first active timestamp in an entry (either with column
> view or org-entry-get) via the special property TIMESTAMP. Inactive
> timestamps = TIMESTAMP_IA.
>
Hm, that's interesting. But I
Memnon Anon writes:
> Hi,
> Christopher Allan Webber writes:
>
>> I was once one of the many people who apparently originally
>> misunderstood what "SCHEDULED" meant, and used to set it to like, an
>> appointment time.
>
> Well, you can use it that way.
> The point is: Scheduled items behave dif
Christopher Allan Webber writes:
> Matt Lundin writes:
>
>> There is a special property name for active timestamps: TIMESTAMP. You
>> can access the first active timestamp in an entry (either with column
>> view or org-entry-get) via the special property TIMESTAMP. Inactive
>> timestamps = TIMES
Hi,
Christopher Allan Webber writes:
> I was once one of the many people who apparently originally
> misunderstood what "SCHEDULED" meant, and used to set it to like, an
> appointment time.
Well, you can use it that way.
The point is: Scheduled items behave differently to timestamped items.
If y
Christopher Allan Webber writes:
> theo writes:
>
>> Hello,
>>
>> On 12/04/2011 00:42, Christopher Allan Webber wrote:
>>> I was once one of the many people who apparently originally
>>> misunderstood what "SCHEDULED" meant, and used to set it to like, an
>>> appointment time.
>>
>> That's what
Christopher Allan Webber writes:
> I was once one of the many people who apparently originally
> misunderstood what "SCHEDULED" meant, and used to set it to like, an
> appointment time.
>
> It seems the appropriate thing for what I actually meant was to just
> put a timestamp anywhere in the entr
theo writes:
> Hello,
>
> On 12/04/2011 00:42, Christopher Allan Webber wrote:
>> I was once one of the many people who apparently originally
>> misunderstood what "SCHEDULED" meant, and used to set it to like, an
>> appointment time.
>
> That's what I do.
>
> Maybe I lack background, but why do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On 12/04/2011 00:42, Christopher Allan Webber wrote:
> I was once one of the many people who apparently originally
> misunderstood what "SCHEDULED" meant, and used to set it to like, an
> appointment time.
That's what I do.
Maybe I lack backg
I was once one of the many people who apparently originally
misunderstood what "SCHEDULED" meant, and used to set it to like, an
appointment time.
It seems the appropriate thing for what I actually meant was to just
put a timestamp anywhere in the entry and that works out well. A lot of
people pu
17 matches
Mail list logo