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.

Sign up for GitHub

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

Jump to bottom

Do not use persistent status sections for status messages #5

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

Do not use persistent status sections for status messages #5

wants to merge 2 commits into from

Commits on Mar 1, 2024

  1. Do not use persistent status sections for status messages 

    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
    kaste committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    73c0384 View commit details
    Browse the repository at this point in the history

  2. Fix typo

    @kaste
    kaste committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    9b7f384 View commit details
    Browse the repository at this point in the history