Bastien writes:
> Hi Christopher,
>
> Christopher Allan Webber writes:
>
>> Just store the property on the item itself
>
> But this solution is task-based, not agenda-based.
>
> The "Sorting" property you describe would be useful in one
> agenda and not in one other -- so this does not really fit
>
> You can now use M- and M- to move agenda lines around.
> This is for quick use only. It is not persistent and the agenda
> will be reordered on next refresh.
>
That's nice, thanks.
Hi Daniel,
You can now use M- and M- to move agenda lines around.
This is for quick use only. It is not persistent and the agenda
will be reordered on next refresh.
--
Bastien
>
> ** TODO This task second
>:PROPERTIES:
>:Sorting: 5029662198291
>:END:
>
As others said, this should be view-based, because the order in one agenda
can be different to the order in other agenda.
Each agenda view has some identifier (e.g. the letter you use to open it:
"a"
Hi Christopher,
Christopher Allan Webber writes:
> Just store the property on the item itself
But this solution is task-based, not agenda-based.
The "Sorting" property you describe would be useful in one
agenda and not in one other -- so this does not really fit
for the OP use-case I guess.
-
Bastien writes:
> Hi Christopher,
>
> Christopher Allan Webber writes:
>
>> I wonder if we had a property that was basically sorting on very large
>> numbers? When you add something to the agenda and there aren't any
>> sorted items, it creates a property with some median-ish very large
>> numbe
Hi Michael
On Wed, Apr 10, 2013 at 2:35 PM, Michael Heinrich
wrote:
> I came from planner-mode and use kind of GTD also in org-mode. One
> thing I still miss in org-mode is the flexibility of moving tasks up and
> down on the today page.
Two years ago I wrote down my thoughts about using Org pr
Hi,
Bastien writes:
>> How do you decide what to do next?
>
> I bind `=' to a custom agenda command that will find out what to do
> next depending on the Emacs context.
>
> For example, when reading emails, C-c a = will find next emails to
> process; when in *.el C-c a = will find next Emacs/Or
Bastien writes:
> For example, when reading emails, C-c a = will find next emails to
> process
PS: I use Gnus and the lovely "dormant" mark '?' so that I can get
the impression I don't have many emails. Of course, many dormant
emails (or blog-entries from gwene.org) are bound to a task.
--
B
Hi Daniel,
Daniel Bausch writes:
> Just do not touch the IDs of items not currently visible or add the name
> of the agenda to which this applies and have an AGENDA_BEFORE per agenda.
Mhh... looks like overengineering to me.
>> I think we should start thinking from the existing functionalities
Hi Bastien,
Am 11.04.2013 09:04, schrieb Bastien:
> Hi Daniel,
>
> Daniel Bausch writes:
>
>> I have got another idea: all we need for sorting (from a technical POV)
>> is a partial order. Why not store exactly that as a property? Assume
>> every TODO entry has an ID (if it has none and it is
Hi Daniel,
Daniel Bausch writes:
> I have got another idea: all we need for sorting (from a technical POV)
> is a partial order. Why not store exactly that as a property? Assume
> every TODO entry has an ID (if it has none and it is required to store
> the order, just create one automatically)
Hi,
Am 11.04.2013 01:32, schrieb Bastien:
> Hi Christopher,
>
> Christopher Allan Webber writes:
>
>> I wonder if we had a property that was basically sorting on very large
>> numbers? When you add something to the agenda and there aren't any
>> sorted items, it creates a property with some me
Hi Christopher,
Christopher Allan Webber writes:
> I wonder if we had a property that was basically sorting on very large
> numbers? When you add something to the agenda and there aren't any
> sorted items, it creates a property with some median-ish very large
> number. As you move things up a
Bastien writes:
> "John Wiegley" writes:
>
>> You'll have to change the positions of the items within the Org file itself.
>> It would be great if there was a single key to do this and then very quickly
>> update the agenda view.
>
> This is tempting in imagination but I think the real implementa
"John Wiegley" writes:
> You'll have to change the positions of the items within the Org file itself.
> It would be great if there was a single key to do this and then very quickly
> update the agenda view.
This is tempting in imagination but I think the real implementation
would be limited and
Yes, it is possible.
I use priorities locally. That is, they sort in the outline and do
not have global semantics. Therefore, they have no meaning in the
agenda. Perhaps someday I will figure out how to remove the cookies
from the agenda.
You can do the opposite from me, using priorities only
> Michael Heinrich writes:
> I came from planner-mode and use kind of GTD also in org-mode. One
> thing I still miss in org-mode is the flexibility of moving tasks up and
> down on the today page.
Hi Michael, planner author here and now org-mode user too. :)
You'll have to change the posit
Hi everyone,
I came from planner-mode and use kind of GTD also in org-mode. One
thing I still miss in org-mode is the flexibility of moving tasks up and
down on the today page.
Typically I schedule the next actions for today which I want to do today
so that they appear in my agenda buffer. The
19 matches
Mail list logo
