Bastien b...@altern.org writes:
Jason Dunsmore emacs-orgm...@dunsmor.com writes:
Carsten Dominik domi...@uva.nl 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
Hi Jason,
Jason Dunsmore emacs-orgm...@dunsmor.com writes:
Carsten Dominik domi...@uva.nl 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
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. That might be more
Hi Jason,
Jason Dunsmore wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com 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
Carsten Dominik domi...@uva.nl 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
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
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 understood in the
On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
wxhgmqzgw...@spammotel.com 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
Hi Suvayu,
suvayu ali wrote:
On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
wxhgmqzgw...@spammotel.com 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
Sebastien Vauban wxhgmqzgw...@spammotel.com 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
Hi Seb,
On Sat, Aug 6, 2011 at 8:59 PM, Sebastien Vauban
wxhgmqzgw...@spammotel.com wrote:
Hi Suvayu,
suvayu ali wrote:
On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
wxhgmqzgw...@spammotel.com wrote:
Another idea would be to introduce another keyword like APPT an place
these time stamps
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Hi Suvayu,
suvayu ali wrote:
On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban
wxhgmqzgw...@spammotel.com wrote:
Another idea would be to introduce another keyword like APPT an place
these time stamps also into the second line. That might
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 scheduling a meeting. Setting a date for a meeting is
13 matches
Mail list logo
