Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When I start lazygit inside terminal, most of time I need to jump into a specific layout such git status or git log directly, right now, the default layout is all the panes/windows are displayed, and default focused pane is Files (git status), I have to manually switch to other panes using 1-5, tig provides subcommand such tig status or tig log to display git status or git log directly.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Provide subcommands such as status, log, stash or flags like tig to start lazygit with a specific pane, the startup layout would be like, switch to the specific pane using 1-5 and then +(next screen mode)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When I start lazygit inside terminal, most of time I need to jump into a specific layout such
git statusorgit logdirectly, right now, the default layout is all the panes/windows are displayed, and default focused pane isFiles(git status), I have to manually switch to other panes using1-5,tigprovides subcommand suchtig statusortig logto displaygit statusorgit logdirectly.Describe the solution you'd like
A clear and concise description of what you want to happen.
Provide subcommands such as
status,log,stashor flags like tig to start lazygit with a specific pane, the startup layout would be like, switch to the specific pane using1-5and then+(next screen mode)Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: