Indeed. I will try to work on it in my spare time, it will take maybe up to
a year, but as soon as I have it, I will let the maillist know in case it's
of interest.
Again, thanks for all your help.
GM
El mié., 18 nov. 2020 a las 7:37, Ihor Radchenko ()
escribió:
> > So from now on, all the DONE t
> So from now on, all the DONE tasks would be archived straight away on the
> day they are DONE.
Not all the tasks, but all the tasks with repeater.
> Is there a way to do the same with all the logged items under the :LOGBOOK:
> that have been DONE before?
It is certainly possible, but require m
Thank you! Ok, now it works. I had to restart my Emacs, probably that was
the problem.
So from now on, all the DONE tasks would be archived straight away on the
day they are DONE. What about the previously LOGGED tasks?
Is there a way to do the same with all the logged items under the :LOGBOOK:
th
> Now I get the error: "wrong number of arguments..." :D
It does not happen in my Emacs. It would be helpful if you shared the
whole error message.
I used the following code for testing:
(defun my/org-archive-without-delete ()
"Archive item at point, but do not actually delete it."
(cl-letf
Now I get the error: "wrong number of arguments..." :D
El mar., 17 nov. 2020 a las 15:13, Ihor Radchenko ()
escribió:
> > I tried this but I get: "symbol's function definition is void:
> > org-trigger-doing"
>
> Oops. That's the old function name. Should be
>
> (add-hook 'org-trigger-hook #'org-
> I tried this but I get: "symbol's function definition is void:
> org-trigger-doing"
Oops. That's the old function name. Should be
(add-hook 'org-trigger-hook #'org-archive-repeated-task)
Best,
Ihor
Gerardo Moro writes:
> Thanks for the prompt reply!
> I tried this but I get: "symbol's fun
Thanks for the prompt reply!
I tried this but I get: "symbol's function definition is void:
org-trigger-doing"
El mar., 17 nov. 2020 a las 14:32, Ihor Radchenko ()
escribió:
> > Thanks, I don't know how to go about doing that, so I would have to rely
> on
> > others wanting to help me if they co
> Thanks, I don't know how to go about doing that, so I would have to rely on
> others wanting to help me if they consider this to be also useful to them
> (which I definitely think it is!).
Try the following code. It should archive any repeated task once it is
marked DONE.
(defun org-archive-rep
Thanks, I don't know how to go about doing that, so I would have to rely on
others wanting to help me if they consider this to be also useful to them
(which I definitely think it is!).
El mar., 17 nov. 2020 a las 11:32, Ihor Radchenko ()
escribió:
> > I actually now realized that your function wi
> I actually now realized that your function will not unfortunately archive
> each logged item (those located in the logbook) in its corresponding date
> (!).
> What it will do is to archive the whole tree under today's date without
> deleting it from the original org file.
You are right. It is ex
Hi again,
I actually now realized that your function will not unfortunately archive
each logged item (those located in the logbook) in its corresponding date
(!).
What it will do is to archive the whole tree under today's date without
deleting it from the original org file.
For instance,
* TODO
Wow, I’m impressed by your help, you are very kind!
I am also impressed by your researching skills, I gave a long go at trying
to find some code online unsuccessfully.
Yes, I agree that the agenda is a nice way to go to visualize my past
events (with v A).
My idea of not relying on the agenda inte
> Hope it is clear now, thanks so much for any help!
Sorry for not making my previous email more clear. I actually understood
what you want to achieve. My suggestion was rather an alternative
approach to "revisit the past" - you can always build agenda view for a
specific date (or range of dates)
Thanks, Ihor.
Indeed, that is an excellent feature of agenda. I use it sometimes to
visualize what I have DONE during the week on the sopt.
What I aim to accomplish however is a more systematic log of all the DONE
tasks, this is, to have an archive file where to archive all tasks.
This file is in
> It would be great if each of these individual "task
> happenings" were archived under the date and time they were completed
> individually, and not just all as one block. This way I could get weekly
> reviews that take those into account.
What about trying to do your weekly review using org-agen
Hi Gerardo,
I am by far no expert, but I think with the kind of setup you currently
use your goal cannot be reached: The repeating task you use is one
single task, and it will be archived as that one single task.
There's a different way to approach repeating tasks though that might
meet your req
Dear all,
I am resending this as I believe it's a useful concept to implement,
especially by those who track their tasks and do weekly/monthly reviews.
When I archive a repeated task (let's say, a learning project of 15 minutes
every Wednesday day for 2 months), the task gets archived in a date t
Dear all,
When I archive a repeated task (let's say, a learning project of 15 minutes
every Wednesday day for 2 months), the task gets archived in a date tree
all under the day it was closed (cancelled) as a whole. This means that all
the LOGGED individual instances of repetition are archived on t
18 matches
Mail list logo
