org-recur icon indicating copy to clipboard operation
org-recur copied to clipboard

Published 20 hours ago • verified publisher icon mrcnski

Adding Timestamp instead of Scheduling

Open ugurbolat opened this issue 3 years ago • 5 comments

Hello,

Thanks for this package. I really like the simplicity.

Is there a way to add a timestamp to a task rather than scheduling? I would like to create repeating appointments/tasks. In this way, I don't see them in the next days of my agenda...

ugurbolat avatar Sep 27 '20 23:09 ugurbolat

We don't have support for timestamps or deadlines right now. Feel free to submit a proposal (e.g. do you want new commands? config variables?) and I may or may not pick it up 🙃

mrcnski avatar Sep 28 '20 17:09 mrcnski

Got it.

"org-recur-timestamp" function (similar to org-recur-schedule) would be nice :)

ugurbolat avatar Sep 28 '20 17:09 ugurbolat

I have a quick and dirty solution to this. I am really new to git and have little idea how to upload the code change. Can someone guide me on how I can share a suggested change?

lenient7 avatar Jan 06 '23 17:01 lenient7

Hi @lenient7! You'll want to:

  1. make a fork (copy of the repo)
  2. clone it (download it locally)
  3. make a commit (save your change with git)
  4. push the commit (upload it to GitHub)
  5. raise a "pull request" (contribution proposal)

If you do a web search for "github pull request tutorial", you should be able to find more detailed information.

Let me know if you have any questions! Excited to see your contribution.

mrcnski avatar Jan 06 '23 18:01 mrcnski

Dear Marcin:

First of all, thank you so much for writing this nice package!

I also appreciate your quick reply, which is very helpful. I followed your guide and created a pull request. As I mentioned, it is a (quick) and dirty hack, but it seems working fine for me.

Wish you have a great week!

Hojae

On Fri, Jan 6, 2023 at 1:14 PM Marcin S. @.***> wrote:

Hi @lenient7 https://github.com/lenient7! You'll want to:

  1. make a fork (copy of the repo)
  2. clone it (download it locally)
  3. make a commit (save your change with git)
  4. push the commit (upload it to GitHub)
  5. raise a "pull request" (contribution proposal)

If you do a web search for "github pull request tutorial", you should be able to find more detailed information.

Let me know if you have any questions! Excited to see your contribution.

— Reply to this email directly, view it on GitHub https://github.com/mrcnski/org-recur/issues/5#issuecomment-1373975225, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQMERG667A5B2OYAHUB5VDWRBOGTANCNFSM4R324FPQ . You are receiving this because you were mentioned.Message ID: @.***>

lenient7 avatar Jan 09 '23 01:01 lenient7