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

Keyboard shortcut conflict #3

Closed
cipo28 opened this Issue Jan 20, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@cipo28
Copy link

cipo28 commented Jan 20, 2016

The new 1.6 Brackets version has introduced the no-distraction view with ctrl+shift+2: now it's impossible to set the 2nd line bookmark. Can I suggest to implement a shortcut with ctr+ALT+x?

@cipo28 cipo28 changed the title keyboard shortcut conflict Keyboard shortcut conflict Jan 20, 2016

@robcaa

This comment has been minimized.

Copy link
Owner

robcaa commented Jan 21, 2016

In addition, the MAC does not work on the current combination (#2).
It seems that must to change the keyboard shortcuts, but I have a little trouble.

The proposed combination will be conflict by the Hungarian keyboard layout.
In the picture you can see:
hungarian layout
There are many special characters, the Hungarian keyboard can be reached with this combination.

It should be a combination that is good for everyone.
What do you think about this combination:
CMD + SHIFT + ALT + #

Or maybe we need a configuration option?
Discuss this and I will make the changes.

@cipo28

This comment has been minimized.

Copy link
Author

cipo28 commented Jan 21, 2016

I was thinking about the "insert" key, but it will change everytime the writing mode... so I think yours is the most generic applicable.
I've also noticed that the bookmarks were lost when saving the file, do I need to open another issue?

@robcaa

This comment has been minimized.

Copy link
Owner

robcaa commented Jan 25, 2016

OK I will make the necessary changes, as it becomes a little time. (maybe tomorrow)

Yes open a new issue, and please describe (detailed) how to reproducate the bug.
I can not reproducate the bug, but I don't installed the new version yet.

@robcaa robcaa closed this in 1a97bf0 Jan 26, 2016

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