Pieter Praet wrote: > Maybe we could wrap something like: Eh, this is rather extreme. My approach is to educate users and empower them, not to decide what's dangerous for them; maybe print a diagnostic warning that can be turned off after the user has gone in to see it?
We must also look into incorporating the repository state in the modeline. My prompt looks like (available from contrib/ in git.git): artagnon|master<>*+:~/src/git$ I immediately know that my worktree is dirty (red asterisk), I have some staged changes (green plus), and that I've diverged from upstream (white <>). After a commit and push: artagnon|master=:~/src/git$ In sync with upstream; clean worktree and index. -- --- You received this message because you are subscribed to the Google Groups "magit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
