Forum Discussion
Feature adjustment request: "Add tag" popup too small, sorting issues, allow drag-scrolling
Please make the Add tag popup larger and sort it alphabetically.
Apparently new to 1Password 8: Issues when I click on "Add tag" and the popup appears :
* It is only 4½ lines high which is only 12% of my vertical screen space. This is needlessly small requiring a lot of scrolling to get to the tag I want.
* It is not sorted intuitively--maybe it's by tag count? I would like this sorted alphabetically so I can quickly scroll to about the right place where my tag should appear, ex. halfway down for those starting with M.
* I cannot drag the "thumb" in the scrollbar to quickly scroll to a different place in the list. The thumb highlights when I mouse over it but clicking to grab it dismisses the whole popup.
I realize that I can start typing the name of a tag to filter the list.
Using 1Password versions:
* 8.9.10 on Windows 10
* 8.9.11 on macOS 12.6.2
1Password Version: 8.9.10
Extension Version: Not Provided
OS Version: Windows 10
Browser:_ Not Provided
Referrer: forum-search:add tag popup
- Jack_P_1P
1Password Team
Hi tamird:
I'm not entirely sure if this is an intentional choice or an oversight, but what I can tell you is that `op-ssh-sign` primarily exists to make commit signing a one click setup process.
Since the 1Password app has no good way of modifying your environment variables in a persistent manner, setting the `[gpg "ssh"].program` config option is the easiest way to ensure that git will use the ssh agent for signing operations, since git will use either the config value, or `SSH_AUTH_SOCK` in that order.
However, if `SSH_AUTH_SOCK` is set to point at the agent, like you've done in your example, there's no need to set the SSH program, and `ssh-keygen` should be able to use the agent normally.
Personally, I leave the SSH program unset in my gitconfig, and instead ensure that I have `SSH_AUTH_SOCK` set globally, which allows for everything to work as expected.
- tamirdNew Contributor
Hi Jack_P_1P, thanks for the detailed reply.
The problem with setting `SSH_AUTH_SOCK` globally is that it prevents you from using multiple agents which is common in corporate environments. In my case this is a show stopper.