Searching in Task View (and others)

[pdgBC]

Not sure if I am doing something wrong. But when I search for the task name in the task list view, it does not work. I noticed if I do it in other base views it works. Am I doing something wrong or is this an issue? Thanks
.

.

.

.

[ther12k]

You're not doing anything wrong — search is opt-in on tasknotesTaskList and defaults to false. I just checked the source: in src/bases/TaskListView.ts the constructor reads

// Read enableSearch toggle (default: false for backward compatibility)
const enableSearchValue = this.config.get("enableSearch");
this.enableSearch = (enableSearchValue as boolean) ?? false;

That's why agenda / calendar / other base views behave differently — they don't gate their search UI behind the same flag.

The fix is to add enableSearch: true to the view options: block in your .base file (the same place hideTopLevelSubtasks, defaultCollapsedState, etc. live). For the default tasks-default.base shipped with TaskNotes, that block currently looks like:

views:
  - type: tasknotesTaskList
    name: Tasks
    order:
      - status
      - priority
      - due
      # ...
    options:
      showScheduled: true
      showDue: true
      showRecurring: true
      # ...other options
      enableSearch: true   # <-- add this line

After saving the file and reopening the view, the search box should appear and the in-view filter will work the same way as your agenda/calendar views.

Two side notes since this came up:

1. This toggle isn't in the published docs/views/task-list.md options table yet (it documents order, sort, groupBy, hideTopLevelSubtasks, filters, etc., but not enableSearch). Worth a small docs PR.
2. If you'd rather have it on by default, the comment in the source ("default: false for backward compatibility") suggests the maintainer wanted to avoid behaviour changes for existing users — but if a tracking issue exists for "Task List search doesn't work" complaints, flipping the default once the option has had a release cycle in opt-in mode would be the natural next step.

Happy to file a docs PR for the missing enableSearch row if useful.