How to not show completed items?

[duckunix]

So, I have syncing working between Foreground 1.5.4 which is good, but how I do I only display items which are not completed?

Thanks!

[bgregos]

Foreground by default will only display tasks that are not completed - currently there's no way to show completed tasks.

[duckunix]

I am using now 1.5.5, and have syncing enabled. It is showing me only completed tasks. What am I doing wrong?

[bradyt]

I wonder if their last message is related to how inthe.am web UI can have different data from what inthe.am's Taskserver will provide to clients. Maybe @duckunix could check with another client outside of inthe.am's web UI, such as CLI Taskwarrior, and compare result.

@duckunix, can you clarify if you're mostly comparing Foreground's list view to the list view from inthe.am's web UI?

@bgregos, is Foreground's default report basically filter=status:pending? And what is the sorting in Foreground most similar to from CLI Taskwarrior? Approximately by id+ or entry+ date? Maybe @duckunix could check task oldest limit:10 at a PC.

[duckunix]

I am syncing to a private server using taskd.

When I run task oldest limit:10 on my laptop, I get my 10 oldest uncompleted tasks.

[bgregos]

Once a task is completed Foreground will save that info to be sent on the next sync and then delete the task internally, so this is pretty perplexing to me. @bradyt - Correct, Foreground's default report shows only pending tasks. The default (and only) sort is by due date.

…

On Thu, Dec 29, 2022, 9:06 PM Brady Trainor ***@***.***> wrote: I wonder if their last message is related to how inthe.am web UI can have different data from what inthe.am's Taskserver will provide to clients. Maybe @duckunix <https://github.com/duckunix> could check with another client outside of inthe.am's web UI, such as CLI Taskwarrior, and compare result. @duckunix <https://github.com/duckunix>, can you clarify if you're mostly comparing Foreground's list view to the list view from inthe.am's web UI? @bgregos <https://github.com/bgregos>, is Foreground's default report basically filter=status:pending? And what is the sorting in Foreground most similar to from CLI Taskwarrior? Approximately by id+ or entry+ date? Maybe @duckunix <https://github.com/duckunix> could check task oldest limit:10 at a PC. — Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABM2MFLS5J2A336A3ZMBIYLWPY7RBANCNFSM5XL5QLNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bradyt]

Okay, so I would wonder if Foreground has some implicit sort, to handle when tasks do not have a due date to compare by. I would guess that that would be the order by which they arrive from the server, which is approximately what id+ will be on each client (clients need not agree on map from uuid to id), which may often roughly correlate with entry+ date, ignoring that some tasks may be moved to completed and back again to pending, which would put them back at the end of id+ sort.

But this all makes assumptions about how you handle responses from Taskserver, and how you store the responses (tasks) on device. If I understand correctly, Taskwarrior simply appends tasks as a newline, to a plain text file, or modifies a preexisting line by uuid. And that contributes to the pseudo-stable id. Which actually I think goes back to its todo.txt roots. I'm not sure what implicit sort your app might be using, after due date. For example, if I query task like task all rc.report.all.sort='' , removing all's default sort, I would wager that it sorts tasks by line number, first from pending.data, then from complete.data. The first group has ids so we can say it's sorted by id. But the completed tasks will have the special id "0", so I think the most precise claim there is that it sorts by line number.

[bgregos]

@bradyt the implicit order appears to be by when the task was added to Foreground. Specifically this is when Foreground first saw the task, either by sync or by the user adding the task locally. This is different from the "created" timestamp. I'm not sure how sort order would affect completed task visibility however.

…

On Thu, Dec 29, 2022, 9:36 PM Brady Trainor ***@***.***> wrote: Okay, so I would wonder if Foreground has some implicit sort, to handle when tasks do not have a due date to compare by. I would guess that that would be the order by which they arrive from the server, which is approximately what id+ will be on each client (clients need not agree on map from uuid to id), which may often roughly correlate with entry+ date, ignoring that some tasks may be moved to completed and back again to pending, which would put them back at the end of id+ sort. But this all makes assumptions about how you handle responses from Taskserver, and how you store the responses (tasks) on device. If I understand correctly, Taskwarrior simply appends tasks as a newline, to a plain text file, or modifies a preexisting line by uuid. And that contributes to the pseudo-stable id. Which actually I think goes back to its todo.txt roots. I'm not sure what implicit sort your app might be using, after due date. For example, if I query task like task all rc.report.all.sort='' , removing all's default sort, I would wager that it sorts tasks by line number, first from pending.data, then from complete.data. The first group has ids so we can say it's sorted by id. But the completed tasks will have the special id "0", so I think the most precise claim there is that it sorts by line number. — Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABM2MFPVGZFAQIFP7T7CHJ3WPZDEXANCNFSM5XL5QLNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bradyt]

I'm not sure how sort order would affect completed task visibility however.

If I'm trying to figure out a disparity between two lists, I'll sometimes try to put them into a common sort order.

[duckunix]

In checking which tasks are listed in Foreground, all are tasks which have due dates, even if they are done.

[bgregos]

My best guess is there's some attribute about the tasks that's causing them to get detected as pending and not completed. Could you post a few lines of `task all`, specifically some of the pending tasks and some of the completed ones? Redacting personal information is fine, I'm just interested in the attributes.

…

On Thu, Dec 29, 2022, 10:01 PM Don Harper ***@***.***> wrote: In checking which tasks are listed in Foreground, all are tasks which have due dates, even if they are done. — Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABM2MFI634SW2LD2GRPLMJ3WPZGBFANCNFSM5XL5QLNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[duckunix]

Below are 4 tasks. The first two are two pending tasks near the top of my priority list. The other two are the first two showing up in Foreground for me even though they have been completed for a while:

Name          Value
------------- --------------------------------------------------------------------------
ID            30
Description   PhotoPrism: Browse your life in pictures
                2020-07-27 07:38:01 https://photoprism.org/
Status        Pending
Project       selfhosted.media
Entered       2020-07-27 07:38:01 (2.4y)
Due           2022-12-31 23:59:59
Last modified 2022-11-20 22:57:13 (5w)
Virtual tags  ANNOTATED DUE MONTH PENDING PROJECT QUARTER READY UDA UNBLOCKED WEEK YEAR
UUID          4824b485-73e5-4bea-8d10-b3e3b5240353
Urgency       11.67
Reviewed      2022-11-20 22:57:13

--------------- ------ - ---- - ------
    project          1 *    1 =      1
    annotations    0.8 *    1 =    0.8
    due          0.656 *   12 =   7.87
    age              1 *    2 =      2
                                ------
                                 11.67


Name          Value
------------- ---------------------------------------------
ID            174
Description   Change nozzle on 3d printer
Status        Pending
Project       3dprint
Entered       2022-07-23 09:34:38 (5mo)
Last modified 2022-10-02 21:58:03 (12w)
Virtual tags  PENDING PRIORITY PROJECT READY UDA UNBLOCKED
UUID          306aa2e3-408f-4ee9-8c53-0bb4ab515297
Urgency       6.871
Priority      H
Reviewed      2022-10-02 21:58:03

------------------ ------ - ---- - ------
    project             1 *    1 =      1
    age             0.436 *    2 =  0.871
    UDA priority.H      1 *    5 =      5
                                   ------
                                    6.871


Name          Value
------------- ---------------------------------------------
ID            -
Description   add officers to post on website
                2020-01-13 06:23:07 Nobody wants
Status        Completed
Project       club
Entered       2018-12-16 04:55:07 (4.0y)
Due           2019-12-31 23:59:59
End           2020-01-13 06:23:07
Last modified 2020-01-13 06:23:07 (3.0y)
Tags          computer
Virtual tags  ANNOTATED COMPLETED PROJECT TAGGED UNBLOCKED
UUID          780e510e-06e3-49ae-aa10-a12b0dd8e6b6
Urgency       16.6

--------------- ------ - ---- - ------
    project          1 *    1 =      1
    annotations    0.8 *    1 =    0.8
    tags           0.8 *    1 =    0.8
    due              1 *   12 =     12
    age              1 *    2 =      2
                                ------
                                  16.6


Name          Value
------------- ------------------------------------------------------
ID            -
Description   Look @ https://github.com/AmruthPillai/Reactive-Resume
                2020-04-22 07:29:45 Not going to do
Status        Completed
Project       job
Entered       2020-03-29 09:14:48 (2.8y)
Due           2020-04-08 09:14:48
End           2020-04-22 07:29:45
Last modified 2020-04-22 07:29:45 (2.7y)
Virtual tags  ANNOTATED COMPLETED PRIORITY PROJECT UDA UNBLOCKED
UUID          67ca4207-8fc6-432b-b33e-7e14221b04b4
Urgency       26.7
Priority      M

------------------ ------ - ---- - ------
    project             1 *    1 =      1
    annotations       0.8 *    1 =    0.8
    due                 1 *   12 =     12
    age                 1 *    2 =      2
    UDA priority.M      1 *  3.9 =    3.9
    PROJECT job         1 *    7 =      7
                                   ------
                                     26.7

For completeness, the output of task diag:

task 2.6.2
   Platform: Linux

Compiler
    Version: 11.3.0
       Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64
 Compliance: C++17

Build Features
      CMake: 3.24.3
    libuuid: libuuid + uuid_unparse_lower
  libgnutls: 3.7.8
 Build type: Release

Configuration
       File: /home/don/.config/task/taskrc (found), 6485 bytes, mode 100660
       Data: /home/don/.task (found), dir, mode 40755
    Locking: Enabled
         GC: Enabled
    $EDITOR: nvim
     Server: my.task.host:12345
         CA: /home/don/.task/ca.cert.pem, readable, 3700 bytes
Certificate: /home/don/.task/don_harper.cert.pem, readable, 3710 bytes
        Key: /home/don/.task/don_harper.key.pem, readable, 27025 bytes
      Trust: strict
    Ciphers: NORMAL
      Creds: duckland/Don Harper/************************************

Hooks
     System: Enabled
   Location: /home/don/.task/hooks
     Active: on-add-onenote-manage-notes-annotation.py                                          (executable)
             on-add.blocks_attr.py                                                              (executable) (symlink)
             on-launch.blocks_attr.py                                                           (executable) (symlink)
             on-modify-onenote-manage-notes-annotation.py                                       (executable)
             on-modify-onenote-manage-notes-annotation.sync-conflict-20220701-034511-JJJTD33.py (executable)
             on-modify.blocks_attr.py                                                           (executable)
             on-modify.timewarrior                                                              (executable)
   Inactive: on-exit                                                                            (not executable)
             on-exit_dashboard                                                                  (not executable)
             on-modify                                                                          (not executable)

Tests
   Terminal: 214x30
       Dups: Scanned 11096 tasks for duplicate UUIDs:
             No duplicates found
 Broken ref: Scanned 11096 tasks for broken references:
             No broken references found