You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2023. It is now read-only.
This may feel a bit presumptuous, but I believe a tig-like user experience would not be overly dumb: I'm using verco as it is the only maintained TUI for mercurial that I know of, and what I like about tig is the fact that with four keystrokes (1. t 2. i 3. g 4. enter), one may visualise the whole tree of commits after a git fetch or git pull. I'm looking for a similar experience with hg. verco is the only thing that comes close, but it requires more keystrokes to get to the relevant screen.
I thus, humbly, or presumptuously, suggest making that user experience as the default. Because:
One can always get back to the other functionalities of verco with some keystrokes anyway.
That may ease the uptake of verco for the kind of niche that I represent.
The text was updated successfully, but these errors were encountered:
You mean just putting the log screen as the default?
So like as you first open verco, it starts in the log history screen?
Would a cli option that lets you choose the first screen be enough?
Something like verco --screen log and then you would be able to create an alias to it.
Yes. I mean putting the log screen as the default.
No. I do not mean adding a cli option: I can live with the current situation.
I believe it's a design choice you have to make.
I will adapt either way.
It seems you'd rather have it the current way. I'm just saying that I believe users of your tool (which is the only tig alternative for mercurial that I know of) would perhaps like having the log screen pop up first. That's what I was after, and what I believe most users will be after.
The design choice is up to. I believe a --screen log is a workaround that's akin to splitting the apple in half. Or akin to saying that the earth is half flat half round, like a bowl, just to satisfy "everyone", here ending up with a "theory" that's even less credible than Flat Earth. I thus wouldn't endorse a --screen log option from a UX point of view. But it's up to you.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This may feel a bit presumptuous, but I believe a tig-like user experience would not be overly dumb: I'm using verco as it is the only maintained TUI for mercurial that I know of, and what I like about tig is the fact that with four keystrokes (1. t 2. i 3. g 4. enter), one may visualise the whole tree of commits after a git fetch or git pull. I'm looking for a similar experience with hg. verco is the only thing that comes close, but it requires more keystrokes to get to the relevant screen.
I thus, humbly, or presumptuously, suggest making that user experience as the default. Because:
The text was updated successfully, but these errors were encountered: