I've pushed a fix that uses the same path for taskwarrior database as the one you have set in your
.taskrcfile (unless you have set
TASK_DATA, which overrides the
I assume you have resolved the issue and it was on your end?
I had the "defcustom" idea in mind tbh: I don't think overengineering this is useful, simply because it's just "timeboxing" a session - if you finish the flashcards in one org-fc session, just start another if you are in the mood to do more.
Also, doing this enables us to programmatically set different limits for reviewing special files or directories using dir-local variables or the method I talked about here (https://lists.sr.ht/~l3kn/org-fc-devel/%3CX7dhfZInJUs7aD4oNpt8-8fZQImyFzCwj-Bt0UItFtSpW_HpfxifiQ9SYCPH5cqiFAz4i7tdvnJXo1IbOxgW75erwZCizZwl6S6MMArtdP8%3D%40protonmail.com%3E).
If you have better ideas, please go forward with them - I'm just telling you seems most convenient for me.
Limiting cards in a session is an easy way to avoid overwhelm during days when a huge number of cards are scheduled.
From a conversation with supersrdjan:
"Intervals for incremental writing should be wave-like. At first they grow as you elaborate. Then they compress as you consolidate. And when it hits bottom you either publish the article, or if you're not there yet, another cycle of increasing interval for further elaboration starts.
The problem with ever-increasing intervals is that it encourages you to start elaborating on new ideas at the expense of consolidating old ones. I know Naess recommends manual intervals but that's just, you know, a solution for lack of a better one.
You know, I think it's applicable for tasks to. It reminds me of Sebastian Marshall's Terminator mode. The more a task nears completion, the more resistance you feel toward actually completing it. So, wave-like increments could help there too.
Well, after a certain inflection point, the increments start getting shorter, to encourage you to wrap things up.
Ah okay. Well the equivalent of my idea would be that, at first, making progress on a task decreases its priority. This leaves room for you to step back and evaluate a little bit. Try other things. And then after a certain point it starts increasing the priority, to either conclude or dismiss the task. I guess this would only make sense for a particular type of task."
If aerc has keybinds set like
rr = reply rq = reply -q
it doesn't forward the common prefix to the underlying term
Steps to reproduce:
- Open an email
- Press "/" ( assuming less as pager)
- Type "r". Nothing comes up on the screen.
- Type "r" again. Now aerc takes this as the "rr" command and opens a tab for you to reply.
- Close compose tab, goto step 2. Next, type "rq" in the search box. Now aerc takes this as the "rq" command and opens a tab to reply, with quoted text.
If I try
org-fc-review-bufferon a non-org-roam file, the title is shown after the "Flip (X)" on the header line, while this doesn't occur with org-roam files (or when reviewing the entire directory).