This code snippet will modify your agenda buffer upon creation so that the
string [#A] is bolded, and [#C] is italicized. It keeps whatever color it
had, it's just now strong or weak based on priority.
This doesn't change the display all that much, but it's enough to help pick
out the important a
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> On 10/9/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
>> However, a different question pops up here. When rescheduling,
>> should the +Nd be relative to today, or relative to
>> the currently scheduled date?
>
> I don't have a preference. Would it
When I switch to a daily agenda view, I like to know that what I'm seeing is
everything there is to see. The current definition of org-fit-agenda-window
sets a maximum height for the agenda view to 3/4 the frame height. This
always leaves me wondering if maybe there's one more task, just beyond t
On 10/9/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
> However, a different question pops up here. When rescheduling,
> should the +Nd be relative to today, or relative to
> the currently scheduled date?
I don't have a preference. Would it be reasonable to have both?
+2d & now+2d
+=2 &
On Oct 9, 2007, at 22:27, Leo wrote:
On 2007-10-09 21:45 +0100, Bastien wrote:
Leo <[EMAIL PROTECTED]> writes:
What do you exactly mean by "include the LOCATION"?
I mean "in the exported .ics file".
The :LOCATION: property is exported as the LOCATION parameter in .ics
since Org 5.11. It
Leo <[EMAIL PROTECTED]> writes:
> However, in order to insert the LOCATION property, I need to first run
> org-insert-property-drawer and then `C-c C-c s' ...
>
> Is there a better way of setting LOCATION?
Well, no.
But property drawers are designed for this kind of additionnal
information, aren
Carsten Dominik <[EMAIL PROTECTED]> writes:
> - A good reason to make it relative to today is that you might not always
> know that the entry is already scheduled. Using today as reference would be
> safe
>
> - A good reason for doing it relative to the scheduled date is that you are
> *re*-sched
On 2007-10-09 21:45 +0100, Bastien wrote:
> Leo <[EMAIL PROTECTED]> writes:
>
>>> What do you exactly mean by "include the LOCATION"?
>>
>> I mean "in the exported .ics file".
>
> The :LOCATION: property is exported as the LOCATION parameter in .ics
> since Org 5.11. It complies normally with th
Bastien schrieb:
John Rakestraw <[EMAIL PROTECTED]> writes:
Perhaps this is personal preference, but somehow it seems more
reasonable to me to reschedule from today. This not only avoids
problems if (I don't know that) an event is already scheduled, but it
also fits in better with my thinking a
Austin Frank <[EMAIL PROTECTED]> writes:
> When I try to store a note using remember, I get the following error:
> "Symbol's value as variable is void: initial"
Right in the middle of org.el (line 12463) :
(v-i initial) ; defined in `remember-mode'
So I guess somehow remember-mode is
John Rakestraw <[EMAIL PROTECTED]> writes:
> Perhaps this is personal preference, but somehow it seems more
> reasonable to me to reschedule from today. This not only avoids
> problems if (I don't know that) an event is already scheduled, but it
> also fits in better with my thinking about tasks.
Max Mikhanosha <[EMAIL PROTECTED]> writes:
> Someone recently asked on a list for a command to unschedule a TODO, I
> would like to join this request.
As of Org 5.11, you can unschedule an item with C-u C-c C-s, either from
an Org buffer or from an agenda view.
--
Bastien
Leo <[EMAIL PROTECTED]> writes:
>> What do you exactly mean by "include the LOCATION"?
>
> I mean "in the exported .ics file".
The :LOCATION: property is exported as the LOCATION parameter in .ics
since Org 5.11. It complies normally with the RFC specs:
http://tools.ietf.org/rfc/rfc2445.txt
Hi Dominik,
Carsten Dominik wrote:
>
> In 5.12 there will be a new variable `org-agenda-scheduled-leaders' that
> determines the leading string of a scheduled item in the agenda display.
>
> If you customize
>
> (setq org-agenda-scheduled-leaders '("Start: " "Cont: "))
>
> then your INPRO
> However, a different question pops up here. When rescheduling,
> should the +Nd be relative to today, or relative to
> the currently scheduled date?
Perhaps this is personal preference, but somehow it seems more
reasonable to me to reschedule from today. This not only avoids
problems if (I don
On Oct 4, 2007, at 14:32, Richard G Riley wrote:
Should something +3d work when rescheduling a task? It would be nice if
it did and be a little more consistent IMO.
Yes, it would be more consistent so I will do this.
However, a different question pops up here. When rescheduling,
should the
I have to agree with the other posters that this seems to be the wrong
idea. First of all, the danger is reasonably large that you
mark an entry DONE by accident, and then you will loose all state info
in the subtree.
Even the other way round, marking a parent DONE when all children are
is not
On Oct 8, 2007, at 20:25, Richard G Riley wrote:
Carsten Dominik <[EMAIL PROTECTED]> writes:
Why do you think this is better?
Because if I am on a thursday and I go a week forward or backward it
makes more sense to still be on a thursday IMO. Just a gut feeling and
how it works on pretty mu
Hi Max,
after thinking this through, I believe it is more consistent not to
implement your patch, because for my feeling it changes the logic of
agenda and todo lists in a slightly confusing way.
Instead, I will try to invite you to keep your INPROGRESS items
scheduled, by implementing the foll
Hello!
I've been trying to implement a setup based on John Wiegley's day
planner tutorial. I have a file org-config.el that is loaded in my
.emacs. org-config.el looks like this:
(require 'org-install)
(require 'remember)
;; basic org-mode configuration
;; keys are set in ekeys.el
(add-to-list
On 10/9/07, Christian Egli <[EMAIL PROTECTED]> wrote:
> One of org-mode biggest strengths is its simplicity. I do not want it to turn
> into a feature ridden dinosaur that is impossible to maintain.
I was hoping for something more like perl, where the easy things are
easy and the hard things are p
On 10/9/07, Bastien <[EMAIL PROTECTED]> wrote:
> "Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> > It's more like, work can't even begin E until A, C & D are done. Work
> > can't start F until A & B are done.
>
> Would the TRIGGER/BLOCKER be okay for that (assuming we can use John's
> proposal of
On 10/9/07, Richard G Riley <[EMAIL PROTECTED]> wrote:
> I'm interested in this. Why would an Org file with permissions like 700
> be any more virus friendly than an .emacs with the same permissions? Een
> taking the windows case, a .emacs is executed each and every time, but
> the org file only wh
On 2007-10-09 03:45 +0100, Bastien wrote:
> Leo <[EMAIL PROTECTED]> writes:
>
>> I start to export org to icalendar and then to google calendar. I
>> wonder what's the best way to include the LOCATION.
>
> What do you exactly mean by "include the LOCATION"?
I mean "in the exported .ics file".
-
On Oct 8, 2007, at 22:12, Russell Adams wrote:
I don't use links often... If I could have a link to another TODO
item, but have the visible portion of the link display the status of
the target TODO item.
Ie:
* Things to do in reverse order
** TODO One
** TODO Two
** DONE Three
* Implementati
Richard G Riley <[EMAIL PROTECTED]> writes:
> e.g If I had a task called "Project 1" I would expect it to be
> automatically marked done when all sub tasks are marked as cancelled
> or done.
Okay, then a :BLOCKER: on "Project 1" wouldn't let you mark it DONE
until all sub-items are DONE.
--
Bas
Wanrong Lin <[EMAIL PROTECTED]> writes:
> When a TODO item is marked "DONE", all TODO items under that tree are
> automatically marked as "DONE". More generically, the user should be
> able to customize what states (for me, that is "DONE", "CANCELED",
> "SUSPENDED", "DELEGATED") will affect the wh
Christian Egli <[EMAIL PROTECTED]> writes:
> To that end my plea is to keep org mode simple. That's why John's
> proposal appeals to me. It is flexible and delegates the complexity to
> emacs lisp instead of inventing another micro language for dependency
> tracking.
Again, I fully agree with tha
Eddward DeVilla gmail.com> writes:
> I've been waiting to see if org might develop something like todo
> dependency ordering. Seems like one could use this with and estimated
> time to complete a todo item to generate a milestone table or more
> easily estimate how long a group of tasks will
Russell Adams <[EMAIL PROTECTED]> writes:
> As to Gantt, lets just dump trees into Graphviz!
Gantt charts could be achieved with TRIGGER/BLOCKER, trees would
requires GUID and labels. Am I right?
--
Bastien
___
Emacs-orgmode mailing list
Remember:
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> I'm not really trying to deal with linear C depends and B which
> depends on A type things. Those are easy. I don't really need org to
> change the states for me.
Okay, but this was Rainer initial request.
> It's more like, work can't even begin
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> This could be dangerous. Org file are (most) text. The more code you
> allow to be embedded, the more of a vector org-mode becomes for trojan
> horse attacks.
Well, thinking of org-mode as a vector of trojan horse attacks sounds
like science ficti
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> On 10/8/07, John Wiegley <[EMAIL PROTECTED]> wrote:
>> How about just having generalized Lisp triggers:
> [snip]
>
> This could be dangerous. Org file are (most) text. The more code you
> allow to be embedded, the more of a vector org-mode becomes
John Wiegley <[EMAIL PROTECTED]> writes:
> Bastien <[EMAIL PROTECTED]> writes:
>
>> We could use the TODO keywords instead of "SEND" as a way to say that
>> reaching a particular todo state should trigger some kind of action.
>
> How about just having generalized Lisp triggers:
>
> :PROPERTIES:
Wanrong Lin <[EMAIL PROTECTED]> writes:
> Hi,
>
> I have not followed very closely on the "dependency" thread that is
> hot now. But I guess my wish here probably relates to it. The feature
> I wish for is:
>
> When a TODO item is marked "DONE", all TODO items under that tree are
> automatically m
On Oct 8, 2007, at 20:03, Adam Spiers wrote:
Hi Carsten,
Another *really* easy feature request: when it says
# Insert note for state change, finish with C-c C-c, or cancel with
C-u C-c C-c.
could you change it so it says *which* state you're going to? Of
course, an intelligent user should
"William Henney" <[EMAIL PROTECTED]> writes:
>
> The trouble is, it is currently not possible to wrap a section in a
> when you _do_ need it. At least, I tried to do this with @
> ... @ and it produces incorrectly nested tags for the case when
> an org heading is mapped onto an html list item (e.
Mike Newman <[EMAIL PROTECTED]> writes:
> On Sat, 06 Oct 2007 11:25:00 +0300
> [EMAIL PROTECTED] wrote:
>
>> I have not yet used this feature, but I am working with html/css all
>> day, so here is my opinion:
>>
>> 1. You shouldn't use more divs than you need to, and you don't need
>> them.
>>
>
Wanrong Lin gmail.com> writes:
> When a TODO item is marked "DONE", all TODO items under that tree are
> automatically marked as "DONE". More generically, the user should be
> able to customize what states (for me, that is "DONE", "CANCELED",
> "SUSPENDED", "DELEGATED") will affect the whole s
39 matches
Mail list logo
