Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: keyboard shortcut to select conversation #3154

Closed
sidawson opened this issue Feb 17, 2019 · 7 comments
Closed

Feature Request: keyboard shortcut to select conversation #3154

sidawson opened this issue Feb 17, 2019 · 7 comments

Comments

@sidawson
Copy link

sidawson commented Feb 17, 2019

(I'll speak for OSX, but these standards are common on all platforms).

A common pattern is Cmd (⌘)-1 will give you the first (eg tab in a browser), ⌘-2 the second, and so on. ⌘-9 is reserved for the 9th (or if more than 9 tabs, the last one).

It would be extraordinarily helpful if Desktop Signal had the same pattern. ⌘-1 for the first conversation (ie, topmost), ⌘-2 for the second etc, ⌘-9 for the 9th/bottom one.

Signal currently becomes unnecessarily cumbersome as soon as you're talking to more than one person at a time (constant mouse moving and clicking).

From memory, on Windows/Linux it's Ctrl-1 (to 8) for first 8 conversations, Ctrl-9 takes you to the last/bottom one. Ie, exactly the same muscle memory, just Ctrl key instead of Cmd.

• Keyboard shortcuts have been on the roadmap (with zero specifics) since Mar 22, 2017
• Using Ctrl+arrows or tabs is discussed here, in Dec 14, 2015
• There's a PR allowing ctrl+arrows to cycle through conversations - although I couldn't get this to work (with any possible combo - ctrl, opt, fn or cmd + arrows). Also, ctrl+arrows conflicts with OSX default Mission Control/Spaces shortcuts.

For reference, on OSX, both Firefox & Chrome have opt+cmd+left/right arrows to cycle through tabs.

Hyask added a commit to Hyask/Signal-Desktop that referenced this issue Jul 26, 2019
This is related to some issues: signalapp#512, signalapp#1104, signalapp#3154.
This work is based on an existing closed PR (signalapp#2042) by @colefranz.
@NateEag
Copy link

NateEag commented Dec 6, 2019

There is a closed PR with an attempt to add this feature here:

#2042

Why did that PR never go anywhere?

If it had technical or quality issues, would it be reconsidered for merging if they were improved?

@scottnonnenberg-signal
Copy link
Contributor

Option/Alt+Down/Up are currently in place to switch between conversations. Please let us know if you're having any difficulty with it!

@NateEag
Copy link

NateEag commented Dec 6, 2019

Oh. So it does.

I guess I should read the docs more. I assumed since this PR was open that no keyboard shortcuts ever landed. I remember they weren't when I first starting using Desktop Signal.

Should've checked.

Thanks!

(What I really want in desktop is a keyboard shortcut to select by searching contact names, similar to Slack's Cmd-K shortcut, but that's probably its own feature request.)

@scottnonnenberg-signal
Copy link
Contributor

scottnonnenberg-signal commented Dec 6, 2019

@NateEag You could type Ctrl+F to search, then that contact will show up, and you can very easily tab to it. That's usually what I do.

@NateEag
Copy link

NateEag commented Dec 6, 2019

That's great. I was literally just thinking that the search interface might do what I want.

Thanks for the quick response!

@jrozelle
Copy link

Oh. So it does.

I guess I should read the docs more. I assumed since this PR was open that no keyboard shortcuts ever landed. I remember they weren't when I first starting using Desktop Signal.

Should've checked.

Thanks!

(What I really want in desktop is a keyboard shortcut to select by searching contact names, similar to Slack's Cmd-K shortcut, but that's probably its own feature request.)

+1 to cmd+K, (and arrow up/down :-) )
Telegram behavior is a must IMHO

@NateEag You could type Ctrl+F to search, then that contact will show up, and you can very easily tab to it. That's usually what I do.

It's better than nothing, but not as efficient as it could be :-)

@stale
Copy link

stale bot commented Sep 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

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

No branches or pull requests

5 participants