on Wed Nov 09 2011, Jason Dunsmore wrote:
> Giovanni Ridolfi writes:
>
>> Jason Dunsmore writes:
>>
>> Hi, _Jason,
>>
>>> After reading http://orgmode.org/org.html#Tracking-TODO-state-changes,
>>> I expected the "@!" TODO syntax, eg. TODO(t@!), to do the following:
>>>
>>> - Log timestamp w
Hi Jason,
On Wed, Nov 9, 2011 at 15:56, Jason Dunsmore wrote:
> After reading http://orgmode.org/org.html#Tracking-TODO-state-changes, I
> expected the "@!" TODO syntax, eg. TODO(t@!), to do the following:
>
> - Log timestamp when entering state
> - Add note when entering state
>
> This syntax ap
Giovanni Ridolfi writes:
> Jason Dunsmore writes:
>
> Hi, _Jason,
>
>> After reading http://orgmode.org/org.html#Tracking-TODO-state-changes,
>> I expected the "@!" TODO syntax, eg. TODO(t@!), to do the following:
>>
>> - Log timestamp when entering state
>> - Add note when entering state
>
>
Jason Dunsmore writes:
Hi, _Jason,
> After reading http://orgmode.org/org.html#Tracking-TODO-state-changes,
> I expected the "@!" TODO syntax, eg. TODO(t@!), to do the following:
>
> - Log timestamp when entering state
> - Add note when entering state
Well the TODO(t@!) syntax seems not to
After reading http://orgmode.org/org.html#Tracking-TODO-state-changes, I
expected the "@!" TODO syntax, eg. TODO(t@!), to do the following:
- Log timestamp when entering state
- Add note when entering state
This syntax appears to break the functionality, because it does neither.
The state is chan
