GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Too much repetition in tab name · Issue #77 · squirrel-sql-client/squirrel-sql-code

Too much repetition in tab name #77

New issue
Copy link
New issue
Copy link
Open
Open
Too much repetition in tab name#77
Copy link

Description

@xpusostomos
xpusostomos
opened on Nov 9, 2025
Issue body actions

When creating Aliases, I tend to name them including the database name, and user login name, because... well... what else would I name them?

So I might name an alias:
localhost foo as foo

But then when I connect using that alias, the tab becomes called:
localhost foo as foo (foo) as foo. That's a bit too foobar for me!

It seems to me there are 2 rational options:
Either:
(a) You let the user name the alias, and respect it in the tab bar title without adding to it.
or
(b) If you think dbname and user name is critical for display, ok, then also append it to the user alias in the Aliases sidebar, ... in which case I won't put that in my alias name.

Either way, I'll see the information only once, not twice.
And since I'm using the option to name the X-window after this string, this is bothering me double.

I believe you can make a TreeTable in Java Swing, so one option would be the alias list has columns database and user. You could also add columns host name, and then I don't think I'd even feel the need to name my aliases at all. That could get overly complicated though.

Activity

  1. fml2 commented on Nov 22, 2025

    @fml2
    fml2
    on Nov 22, 2025
    More actions

    Could a custom string with placeholders be a solution to this? I.e. we could have a setting for the window / tab title which could have a "well known" placeholders that would be replaced upon connection.

    E.g. {db-host}, {user-name}, {alias-name} etc.

    There would be a default title of course.

  2. t603 commented on Nov 22, 2025

    @t603
    t603
    on Nov 22, 2025
    More actions

    Could a custom string with placeholders be a solution to this? I.e. we could have a setting for the window / tab title which could have a "well known" placeholders that would be replaced upon connection.

    E.g. {db-host}, {user-name}, {alias-name} etc.

    There would be a default title of course.

    There is already such functionality for the main window title in Global Preferences, see attached screenshot. So [xpusostomos] is asking for similar functionality for Tabs, I guess

    Image
  3. gerdwagner commented on Dec 5, 2025

    @gerdwagner
    gerdwagner
    on Dec 5, 2025
    Member
    More actions

    You may try out the following: menu File --> Global Preferences --> tab General --> on the left hand side about in the middle there's a check box "Use short Session tab title ...".

  4. xpusostomos commented on Dec 6, 2025

    @xpusostomos
    xpusostomos
    on Dec 6, 2025
    Author
    More actions

    Ah... I guess use short session title is the answer. I don't get why this isn't the default, if people find that differentiation interesting, they would already have it in the alias. And if they don't find it interesting, why would they want to see it in the tab?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.