feature: persistence / save to file

[Noneangel]

Did you check the docs?

• I have read all the trouble.nvim docs

Is your feature request related to a problem? Please describe.

When I close Neovim, the view is lost. I often edit a view using delete (dd), or trouble_add

trouble.nvim/lua/trouble/sources/snacks.lua

Line 110 in 85bedb7

trouble_add = { action = M.wrap({ type = "smart", add = true }), desc = "smart-add-to-trouble" },

The view act as my to-do list. But noevim crash some time, so the editions made to the view are lost.

Describe the solution you'd like

An API like require("trouble").save(filename, opts) to save a view to a file.

Describe alternatives you've considered

Use quickfix list with romainl/vim-qf plugin. But it is hard to keep it in sync with trouble.

Additional context

No response

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[Noneangel]

not stale

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[rmunn]

I actually want the "opposite" feature, which would be the ability to load from an arbitrary file. The other day I ran eslint . > lint-results.txt at the commandline, outside of neovim, and wanted to load the lint-results.txt into the trouble window later on. I couldn't find an obvious way to do that.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[rmunn]

Not stale. It's a feature request! Feature requests should never be marked as stale, IMHO.

Edit: Correction. Feature requests should never be automatically marked as stale due to lack of comments. The nature of feature requests is that they are made, then they sit there until the author has time to look at them. A lack of comment activity does not correlate to a lack of interest in the feature; rather, it means that people don't want to spam the issue comments. Having a bot auto-mark feature requests as stale just results in more useless, bordering-on-spam comments being made because the system forces users to do that.

In other words, this comment of mine adds NO value to the discussion of the feature, and borders on being spam. Yet I'm forced to add it so that the feature request won't be closed. This is silly, causes everyone subscribed to the feature to get unnecessary email/notifications, and should not be needed.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.