Bastien writes:
> Jason Dunsmore writes:
>
>> Carsten Dominik writes:
>>
>> Yes, that was my original reason. But your suggestion of adding a
>> special keyword for events is another good reason. Also, as recently
>> discussed, consistent formatting conventions and clarifying the
>> frequent
Hi Jason,
Jason Dunsmore writes:
> Carsten Dominik writes:
>
>> Why do you want this special interface for setting an event date.
>> How is that better than `C-c .'? Is it that you don't need to
>> position the cursor?
>
> Yes, that was my original reason. But your suggestion of adding a
> sp
Carsten Dominik writes:
> Why do you want this special interface for setting an event date.
> How is that better than `C-c .'? Is it that you don't need to
> position the cursor?
Yes, that was my original reason. But your suggestion of adding a
special keyword for events is another good reason
Hi Jason,
Jason Dunsmore wrote:
> "Sebastien Vauban" writes:
>> suvayu ali wrote:
>>> Yes, this would be a nice addition. I always find it difficult to decide
>>> how to put regular timestamps too.
>>
>> By regular timestamps, you mean: inactive timestamps?
>
> I think he means active timestamps
Hi Suvayu,
suvayu ali wrote:
> On Sat, Aug 6, 2011 at 8:59 PM, Sebastien Vauban wrote:
>> suvayu ali wrote:
>>> On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban wrote:
> Another idea would be to introduce another keyword like APPT an place
> these time stamps also into the second line. Tha
"Sebastien Vauban" writes:
> Hi Suvayu,
>
> suvayu ali wrote:
>> On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
>> wrote:
Another idea would be to introduce another keyword like APPT an place
these time stamps also into the second line. That might be more easy to
implement.
>>>
Hi Seb,
On Sat, Aug 6, 2011 at 8:59 PM, Sebastien Vauban
wrote:
> Hi Suvayu,
>
> suvayu ali wrote:
>> On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
>> wrote:
Another idea would be to introduce another keyword like APPT an place
these time stamps also into the second line. That might
"Sebastien Vauban" writes:
>> Another idea would be to introduce another keyword like APPT an place these
>> time stamps also into the second line. That might be more easy to implement.
>
> FWIW, my instinctive reaction would be: yes, great! Maybe that clarifies the
> bits around dates: all acti
Hi Suvayu,
suvayu ali wrote:
> On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
> wrote:
>>> Another idea would be to introduce another keyword like APPT an place
>>> these time stamps also into the second line. That might be more easy to
>>> implement.
>>
>> FWIW, my instinctive reaction would b
On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
wrote:
>> Another idea would be to introduce another keyword like APPT an place these
>> time stamps also into the second line. That might be more easy to implement.
>
> FWIW, my instinctive reaction would be: yes, great! Maybe that clarifies the
>
Hi Carsten,
Carsten Dominik wrote:
> On 5.8.2011, at 19:05, Jason Dunsmore wrote:
>> In the Org manual, a distinction is made between items that have a
>> timestamp with the "SCHEDULED" keyword and items that have a plain
>> timestamp:
>>
>> "Scheduling an item in Org-mode should not be understo
On 5.8.2011, at 19:05, Jason Dunsmore wrote:
> In the Org manual, a distinction is made between items that have a
> timestamp with the "SCHEDULED" keyword and items that have a plain
> timestamp:
>
> "Scheduling an item in Org-mode should not be understood in the same way
> that we understand
12 matches
Mail list logo
