Re: [PATCHv3 1/2] wt-status.*: better advices for git status added

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: May 31, 2012, 06:47 UTC
Message-ID: <vpqmx4orgnm.fsf@bauges.imag.fr>
In-Reply-To: <20120530130914.Horde.CK7IZHwdC4BPxf-ak9fkbPA@webmail.minatec.grenoble-inp.fr>

konglu@minatec.inpg.fr writes:

> Yes, we first thought that we could use statusHints to protect the
> new messages warnings. But users that disabled statusHints and still
> wished to know what to do during am/rebase/bisect etc.

I don't think you should worry too much about people who already set statusHints. By definition, they are people who read the documentation, which already disqualifies them as "newbies". If you show the state unconditionally, and just hide the commands, then at worse, they will have to read the doc again.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.