Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not use persistent status sections for status messages #5

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

kaste
Copy link

@kaste kaste commented Mar 1, 2024

Initially the plugin used window.status_messages which disappear
after a few seconds. A persistent message like "sublack: reformatted"
which doesn't even go away when editing the file is not helpful.

Persistent messages for the daemon on the view are also a mistake
as they stick to the view although the daemon has been probably started
for the window. Make them non-sticky as well.

Initially the plugin used `window.status_message`s which disappear
after a few seconds.  A persistent message like "sublack: reformatted"
which doesn't even go away when editing the file is not helpful.

Persistent messages for the daemon *on the view* are also a mistake
as they stick to the view although the daemon has been probably started
for the window.  Make them non-sticky as well.
@kaste
Copy link
Author

kaste commented Mar 1, 2024

CI pipeline is broken; the startup code doesn't even run.

@kaste
Copy link
Author

kaste commented Mar 1, 2024

Sorry for that, you're not the maintainer of sublack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant