[
    {
        "role": "user",
        "content": "neomutt%20showing%20this%20error%20on%20start%3A%20Changing%20threaded%20display%20should%20prefer%20%24use_threads%20over%20%24sort"
    },
    {
        "role": "assistant",
        "content": "That error message:\n\n> `\"Changing threaded display should prefer $use_threads over $sort\"`\n\nis NeoMutt\u2019s way of warning that you\u2019re trying to enable threaded display (usually via the `$sort` configuration) in a setup where `$use_threads` should be used instead. It\u2019s not a fatal error, but rather a reminder to use the newer `$use_threads` variable to control threading, and to reserve `$sort` for sorting order\u2014even in threaded views. ([neomutt.org](https://neomutt.org/feature/use-threads?utm_source=openai))\n\nHere\u2019s how to understand and fix this in your `~/.neomuttrc` or `.muttrc`:\n\n---\n\n### What changed & why you\u2019re seeing this\n\n- **Old behavior**: Before a newer feature was added (around 2021), people used `set sort=threads` (or variants like `reverse-threads`) to both enable threading *and* define ordering.  \n- **New behavior**: The `use_threads` variable was introduced. With it:\n\n  - `$use_threads` defines *whether* messages are threaded, and *how* (flat, threads, or reverse).  \n  - `$sort` defines the *order* in which things are displayed (e.g. date, last-date-received, etc.).  \n  - `$sort_aux` defines a secondary sort\u2014especially relevant in threaded views (how children are ordered under each thread root). ([neomutt.org](https://neomutt.org/feature/use-threads?utm_source=openai))\n\n- If you try to use `$sort=threads`, NeoMutt will issue your error/warning, because `$use_threads` should be handling the thread-viewing logic now. ([neomutt.org](https://neomutt.org/guide/reference?utm_source=openai))\n\n---\n\n### How to fix your configuration\n\nModify your config to use `$use_threads`. Here are sample settings:\n\n```muttrc\n# Enable regular threaded view (roots above children)\nset use_threads = yes  \nset sort = last-date-received    # how threads are ordered\nset sort_aux = date               # how messages within a thread are ordered\n\n# If you want reverse-threaded view (children above roots)\nset use_threads = reverse\nset sort = last-date-received\nset sort_aux = date\n```\n\nIf you want no threading (a \u201cflat\u201d view):\n\n```muttrc\nset use_threads = no\nset sort = date or reverse-date or however you want\n```\n\nAvoid doing:\n\n```muttrc\nset sort = threads  # or reverse-threads\n```\n\nbecause that triggers the warning, and is now considered deprecated. ([neomutt.org](https://neomutt.org/guide/reference?utm_source=openai))\n\n---\n\n### Example scenarios\n\n| What you want                     | `use_threads` setting | `sort` example               | `sort_aux` example   |\n|-----------------------------------|------------------------|-------------------------------|------------------------|\n| Regular threading (recent threads at top/bottom) | `yes` or `threads`         | `last-date-received` or `date` | `date`                |\n| Reverse thumbnail (roots below children)         | `reverse`                 | `last-date-received`           | `date`                |\n| Flat list, newest first                        | `no`                     | `reverse-date-received`        | N/A or fallback        |\n\n---\n\nIf you post your current `.neomuttrc` settings around `$sort` and `$use_threads`, I can help you translate them precisely and eliminate the warning."
    }
]