Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write memos and tasks in chronological order #77

Open
mjbain10 opened this issue May 4, 2021 · 1 comment
Open

Write memos and tasks in chronological order #77

mjbain10 opened this issue May 4, 2021 · 1 comment
Milestone

Comments

@mjbain10
Copy link

mjbain10 commented May 4, 2021

When adding a new memo/task, the new item is inserted directly under the heading (or whatever is configured for the "after" template pattern) and above any previous items. So the items end up in reverse chronological order (newest first).

It would be great if there was a way to configure memos/tasks to be appended to the end of a section so that the order is chronological.

I'm loving this extension btw, it's pretty much exactly what I've been looking for. Thanks!

@pajoma
Copy link
Owner

pajoma commented Jun 28, 2021

It is certainly possible, but kind of tricky

Let us consider the following example

# Tasks
- [] task 1
- [x] task2
>> 1
- [x] manually added task 3
>> 2

## next subsection
- [x] my other manually added task 4

# next section 

Where should we place the new task?

  • after configured header and before the next free line (>> 1)
  • after configured header and before next section (>> 2)

Maybe we could trim the tasks list before adding new tasks, e.g. removing all empty lines, move all completed tasks to the top

pajoma added a commit that referenced this issue Jul 6, 2021
@pajoma pajoma added this to the 0.12 milestone Jul 6, 2021
@pajoma pajoma mentioned this issue Apr 10, 2022
9 tasks
@pajoma pajoma modified the milestones: 0.12, 0.13 Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants