Skip to content

Better feedback for longer operations triggered by the user #1170

Description

@t3mujin

My example is related with "commit-and-sync and then close", but I guess this could be extrapolated to any potentially longer operation, although in commit-sync-close is where this is more obvious.

Because of the conversation in #13 what I started doing in all my vaults is using "commit-and-sync and then close" to close Obsidian, I even added a button to the ribbon just for that. What happen is every time I do that, and because this is a long operation the immediate feeling I have is nothing has happened (but I know it is, I just wait for it to close).

I'm not a design nor a UX expert, so don't want to jump straight into solutions (could be that small feedback message or other), but for potentially longer operations, or even any, having some kind of feedback to the user that something is running, is helpful.

Activity

  1. Vinzent03 commented on Sep 19, 2026

    @Vinzent03
    Owner

    Do you have the status bar enabled in the plugin settings and not hidden via a plugin or theme? It shows what it is currently doing (e.g. fetch/push/commit) and if supported progress status as well. This is relatively new so please verify you are using the latest version.

    Image

    The download icon in this example indicates a fetch.

    Is that enough for you use case or would you prefer something more dominant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions