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

Command vs. Alt vs. Win - trouble running non-GS applications #445

Open
mbert opened this issue Nov 25, 2024 · 1 comment
Open

Command vs. Alt vs. Win - trouble running non-GS applications #445

mbert opened this issue Nov 25, 2024 · 1 comment

Comments

@mbert
Copy link

mbert commented Nov 25, 2024

I am using an old thinkpad carbon for running NEXTSpace which I am currently still evaluating.
It looks I my Alt key is mapped to Command. So far so good. However it does not look like I can map Alt to any other phyiscal key.
I use tabbed terminal emulators (like tilda) which are all configured to use the "same" shortcuts I use on my Mac (hence: Alt-t for new tab, Alt-{} for navigating between tabs etc.). I can't get any of this to work. They don't know what "Command" is, hence I cannot map anything to "Command". I have played around a bit with the modifier key preference, but that was to no avail either.

I guess that a way to freely map Alt and Command to any physical keys, so that one could use Alt and Command alongside each other.

@trunkmaster
Copy link
Owner

@mbert you're right at current state of window manager implementation Alt (or Command) is mapped to app menu actions. App menu for non-GNUstep applications created by Workspace. I'm close to the where it would be better to drop this idea and move such menu to titlebar right-click menu. I'll look at this later.

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

No branches or pull requests

2 participants