seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

No support for dvorak (or supposedly others) keyboard layout #451

New Issue
Open
opened 2018-05-12 18:27:17 +02:00 by casperravenhorst · 18 comments
casperravenhorst commented 2018-05-12 18:27:17 +02:00 (Migrated from github.com)
Copy Link

On macOS, this app takes its inputs from scancodes, not letting the OS translate them to the (ascii?) codes as usual for other apps. Not sure if supporting multiple keyboard layouts is doable, but a lot of countries probably use (if only slightly, see france germany etc) different layouts.

On macOS, this app takes its inputs from scancodes, not letting the OS translate them to the (ascii?) codes as usual for other apps. Not sure if supporting multiple keyboard layouts is doable, but a lot of countries probably use (if only slightly, see france germany etc) different layouts.
👍 14 🎉 1
whyboris commented 2018-06-28 13:47:17 +02:00 (Migrated from github.com)
Copy Link

Confirming that I can't use Dvorak on macOS -- cool-retro-term disregards my current keyboard layout (switching back and forth the layout setting doesn't affect the terminal).

Confirming that I can't use _Dvorak_ on _macOS_ -- _cool-retro-term_ disregards my current keyboard layout (switching back and forth the layout setting doesn't affect the terminal).
whyboris commented 2018-07-05 13:18:51 +02:00 (Migrated from github.com)
Copy Link

Looks like the situation is a bit worse -- I'm on macOS with Dvorak layout turned on:
When I use the keyboard's asdf keys it types asdf characters in the terminal (sort-of expected since cool-retro-term can't use Dvorak yet),
but when I press the comma or a period (, or . ) keys, w, and v appear (the characters I'd expect if Dvorak was working).
Unsure if it's partially good news -- but it also means I can't access , or . in cool-retro-term 😕
When I switch to the standard QWERTY layout on the Mac, I can successfully type in the , and . characters using the default keyboard keys.

I wonder if it's getting fixed with this PR: https://github.com/Swordfish90/cool-retro-term/pull/446 (see line 1027 and 1033)

Looks like the situation is a bit worse -- I'm on _macOS_ with _Dvorak_ layout turned on: When I use the keyboard's `asdf` keys it types `asdf` characters in the terminal (sort-of expected since _cool-retro-term_ can't use _Dvorak_ yet), but when I press the comma or a period (`,` or `.` ) keys, `w`, and `v` appear (the characters I'd expect if _Dvorak_ was working). Unsure if it's partially good news -- but it also means I can't access `,` or `.` in _cool-retro-term_ 😕 When I switch to the standard _QWERTY_ layout on the Mac, I can successfully type in the `,` and `.` characters using the default keyboard keys. I wonder if it's getting fixed with this PR: https://github.com/Swordfish90/cool-retro-term/pull/446 (see line _1027_ and _1033_)
whyboris commented 2018-07-05 13:28:19 +02:00 (Migrated from github.com)
Copy Link

Is getting the Dvorak keyboard layout just a matter of adding some file here: https://github.com/Swordfish90/qmltermwidget/tree/master/lib/kb-layouts ?
If that's all it takes, I'm willing to create a file (provided I get a little guidance about how things work)

Is getting the _Dvorak_ keyboard layout just a matter of adding some file here: https://github.com/Swordfish90/qmltermwidget/tree/master/lib/kb-layouts ? If that's all it takes, I'm willing to create a file (provided I get a little guidance about how things work)
whyboris commented 2018-08-29 18:23:56 +02:00 (Migrated from github.com)
Copy Link

Unbelievably -- today I launched the app by accident and it is working with Dvorak!!! 🎉
No idea why this difference. But very exciting!

Unbelievably -- today I launched the app by accident and it is working with _Dvorak_!!! 🎉 No idea why this difference. But _very_ exciting!
cascassette commented 2018-08-31 22:38:41 +02:00 (Migrated from github.com)
Copy Link

Not here. What did you do?

Not here. What did you do?
whyboris commented 2018-08-31 22:41:50 +02:00 (Migrated from github.com)
Copy Link

The app hasn't been updated, so it might be some weird combination of settings.
I now suspect it might have something to do with the login screen on Mac:
Mac has a bug that when you are on Dvorak, the login screen might still be on QWERTY and vice versa -- they are independent. I'll play around and if I figure something out -- I'll share here. As of now I'm unsure.

The app hasn't been updated, so it might be some weird combination of settings. I now suspect it might have something to do with the login screen on Mac: Mac has a bug that when you are on _Dvorak_, the login screen might still be on _QWERTY_ and vice versa -- they are independent. I'll play around and if I figure something out -- I'll share here. As of now I'm unsure.
bayabyum commented 2019-01-15 01:29:08 +01:00 (Migrated from github.com)
Copy Link

Even weirder... I'm using Programmer Dvorak (also on Mac), and I get QWERTY with all the letter keys, but it uses Programmer Dvorak for the number keys. And it can use Hangul (the Korean alphabet) just fine if I switch the layout to Korean. It never did anything like this on Linux.

Even weirder... I'm using Programmer Dvorak (also on Mac), and I get QWERTY with all the letter keys, but it uses Programmer Dvorak for the number keys. And it can use Hangul (the Korean alphabet) just fine if I switch the layout to Korean. It never did anything like this on Linux.
dessalines commented 2019-01-15 04:05:59 +01:00 (Migrated from github.com)
Copy Link

I can verify that dvorak is working fine on linux.

I can verify that dvorak is working fine on linux.
whyboris commented 2019-01-31 20:09:14 +01:00 (Migrated from github.com)
Copy Link

I'm on cool-retro-term version 1.1.1 and even though my Mac is set to Dvorak the home keys are asdf and jkls (QWERTY layout except for the : which ends up as s ⚠️ ).

Similarly the <, >, and ? get mapped to w, v, and z (as a Dvorak layout would).

So I get neither QWERTY nor DVORAK. The problem goes away and I get full QWERTY when I switch the computer setting to the QWERTY layout, but I can't get Dvorak support 😢

I would love for Dvorak to be supported.

Is it straight-forward to add the support? I'm willing to open a PR if someone could point me in the direction of how to fix things.

I'm on _cool-retro-term_ version `1.1.1` and even though my Mac is set to _Dvorak_ the home keys are `asdf` and `jkls` (QWERTY layout except for the `:` which ends up as `s` ⚠️ ). Similarly the `<`, `>`, and `?` get mapped to `w`, `v`, and `z` (as a _Dvorak_ layout would). So I get neither _QWERTY_ nor _DVORAK_. The problem goes away and I get full _QWERTY_ when I switch the computer setting to the _QWERTY_ layout, but I can't get _Dvorak_ support 😢 I would love for _Dvorak_ to be supported. Is it straight-forward to add the support? I'm willing to open a PR if someone could point me in the direction of how to fix things.
wasp604 commented 2019-02-26 23:52:52 +01:00 (Migrated from github.com)
Copy Link

What bothers me the most is that a previous version of CRT did support Dvorak, but since I updated to 1.1.1 it forces me to use QWERTY. If an update broke Dvorak, it should be easy enough to undo it, no?

I am on an iMac, by the way.

Confirmed: version 1.0.1 has full Dvorak support, and 1.1.0 does not.

What bothers me the most is that a previous version of CRT _did_ support Dvorak, but since I updated to 1.1.1 it forces me to use QWERTY. If an update broke Dvorak, it should be easy enough to undo it, no? I am on an iMac, by the way. Confirmed: version 1.0.1 has full Dvorak support, and 1.1.0 does not.
👍 2
lraulin commented 2019-03-05 16:45:29 +01:00 (Migrated from github.com)
Copy Link

Programmer Dvorak works on 1.0.1 too!

Programmer Dvorak works on 1.0.1 too!
justinmayer commented 2019-04-23 10:15:24 +02:00 (Migrated from github.com)
Copy Link

I can confirm that using cool-retro-term 1.1.1 with the Colemak keyboard layout setting (System Preferences > Keyboard > Input Sources > Colemak) on macOS 10.13.6 yields the incorrect behavior described in this issue — QWERTY appears to be used instead. Downgrading to cool-retro-term 1.0.1 restores the correct behavior, with the Colemak layout yielding the correct characters.

I can confirm that using _cool-retro-term_ 1.1.1 with the Colemak keyboard layout setting (System Preferences > Keyboard > Input Sources > Colemak) on macOS 10.13.6 yields the incorrect behavior described in this issue — QWERTY appears to be used instead. Downgrading to _cool-retro-term_ 1.0.1 restores the correct behavior, with the Colemak layout yielding the correct characters.
mblarsen commented 2019-04-30 08:22:59 +02:00 (Migrated from github.com)
Copy Link

Ditto everything with Colemak 1.0.1 is working 1.1.1 isn't

Ditto everything with Colemak 1.0.1 is working 1.1.1 isn't
Swordfish90 commented 2019-05-04 16:55:01 +02:00 (Migrated from github.com)
Copy Link

Are you able to reproduce this issue with the latest upstream version? I'm trying to figure out if it's a regression CRT side.
https://github.com/lxqt/qtermwidget

Are you able to reproduce this issue with the latest upstream version? I'm trying to figure out if it's a regression CRT side. https://github.com/lxqt/qtermwidget
justinmayer commented 2019-05-04 23:36:52 +02:00 (Migrated from github.com)
Copy Link

@Swordfish90: I visited the repo link you posted but have no idea what it is or how exactly I would use it on macOS to reproduce the issue.

@Swordfish90: I visited the repo link you posted but have no idea what it is or how exactly I would use it on macOS to reproduce the issue.
TheGrandmother commented 2019-09-02 11:35:20 +02:00 (Migrated from github.com)
Copy Link

I'm having this issue as well with a custom keyboard layout enabled via setxkbmap.
Although for me it works if i run setxkbmap in cool-retro-terminal

I'm having this issue as well with a custom keyboard layout enabled via `setxkbmap`. Although for me it works if i run `setxkbmap` in cool-retro-terminal
find1dream commented 2019-12-24 06:16:23 +01:00 (Migrated from github.com)
Copy Link

Temporary solutions for using programmer dvorak (or others) on Mac os:

  1. Choose your keyboard input source as Australian (Depending on your keyboard, you should try another one if the result is not desired. )
  2. Install Karabiner-elements
  3. Import programmer dvorak from https://pqrs.org/osx/karabiner/complex_modifications/?q=programmer
  4. Enjoy
Temporary solutions for using programmer dvorak (or others) on Mac os: 1. Choose your keyboard input source as Australian (Depending on your keyboard, you should try another one if the result is not desired. ) 2. Install Karabiner-elements 3. Import programmer dvorak from https://pqrs.org/osx/karabiner/complex_modifications/?q=programmer 4. Enjoy
g012 commented 2020-05-14 01:30:01 +02:00 (Migrated from github.com)
Copy Link

Well I'm using karabiner and an uncommon layout. The keys of the layout work fine, but I have some combinations, such as fn + ijkl mapped to arrows, and for ijkl keys it does input ijkl instead of the expected cstn in my layout. Weird (and unusable). Same for my keys which have a secondary mapping with right cmd + key (asdf, etc.).

Well I'm using karabiner and an uncommon layout. The keys of the layout work fine, but I have some combinations, such as fn + ijkl mapped to arrows, and for ijkl keys it does input ijkl instead of the expected cstn in my layout. Weird (and unusable). Same for my keys which have a secondary mapping with right cmd + key (asdf, etc.).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#451
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?