gitkraken / vscode-gitlens

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
http://gitkraken.com/gitlens
Other
9.05k stars 1.35k forks source link

Don't take up so much screen real estate #2467

Open tjayrush opened 1 year ago

tjayrush commented 1 year ago

Description

I love GitLens, I do, but why do you take up so much screen real estate in the terminal window?

Screen Shot 2023-01-24 at 5 55 59 AM

It should just say GitLen -- we don't need you taking up a third of the tab bar when you're only one of six tabs.

GitLens Version

12

VS Code Version

Version: 10

Git Version

git version 1.0

Logs, Screenshots, Screen Captures, etc

Thest

eamodio commented 1 year ago

Other than shortening the name of "Visual File History", which I am open to, alternatives will still be longer than desired (e.g. Visual Timeline or Visual History).

VS Code prepends the panel container name "GitLens" to the view name "Visual File History". It would be nice if VS Code only showed the full name or something when the tab was active -- whereas right now it adds the view name once it becomes active the first time.

@sbatten is there another way GitLens could deal with this?

tjayrush commented 1 year ago

I know I’m a total stranger and all, but I am a dispassionate user. Just pain old GitLens would be plenty.

On Jan 24, 2023, at 1:57 PM, Eric Amodio @.***> wrote:

Other than shortening the name of "Visual File History", which I am open to, alternatives will still be longer than desired (e.g. Visual Timeline or Visual History).

VS Code prepends the panel container name "GitLens" to the view name "Visual File History". It would be nice if VS Code only showed the full name or something when the tab was active -- whereas right now it adds the view name once it becomes active the first time.

@sbatten https://github.com/sbatten is there another way GitLens could deal with this?

— Reply to this email directly, view it on GitHub https://github.com/gitkraken/vscode-gitlens/issues/2467#issuecomment-1402439467, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJKXPWR3JKVKH3IDS7MO23WUAQ2VANCNFSM6AAAAAAUE53C7Q. You are receiving this because you authored the thread.