https://github.com/DreymaR/BigBagKbdTri … evdev#L605
As you can see, the model is named 'pc104angle'. You have an underscore there.
https://github.com/DreymaR/BigBagKbdTri … 14-L990C25
The layout name is 'tarmak2c_et', so that seems right.
setxkbmap -model "pc104_angle" -layout "us(tarmak2c_et)"
and it didn't seem to work (said "error loading new keyboard description.
]]>The options component (for Extend) should be okay, as long as you don't reset it. Setting model and layout doesn't affect the options.
]]>setxkbmap -v 9
, I can successfully set the angle mod by running
bash setkb.sh -m "pc104_angle"
" (although this doesn't change the layout as far as I can tell). However, running
bash setkb.sh -l "tarmak2c_et"
the script displays the readout at bottom and does not change the layout from cmk_ed_us as far as I can tell. Also, not even the angle mod seems to be set up when I added this to /etc/rc.local.
/Desktop/BigBagKbdTrixXKB-master/setkb.sh -m "pc104angle" -l "us(tarmak2c_et)" || exit 1
exit 0
Setting verbose level to 9
locale is C
Warning! Multiple definitions of keyboard model
Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
Using command line, ignoring X server
Trying to load rules file ./rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105awide
layout: tarmak2c_et
options: misc:extend,lv5:caps_switch_lock,grp:shifts_toggle,compose:menu
Trying to build keymap using the following components:
keycodes: evdev(pc105awide)+aliases(qwerty)
types: complete
compat: complete
symbols: pc+tarmak2c_et+inet(evdev)+group(shifts_toggle)+compose(menu)+level5(caps_switch_lock)+extend(basic)
geometry: pc(pc105awide)
Error loading new keyboard description
First, you have to use the install script to copy the BigBag files to the system X11/xkb directory. Then, the setkb.sh script activates a layout combo of your choice. To make it persistent, the setkb script can write its setxkbmap command to a file that gets sourced at startup, such as your user's .bashrc file.
If your distro uses Wayland, the procedure is different. I'm afraid you'll have to peruse the README and try to find the answers yourself.
The ANSI keyboard has model name pc104, and with the Angle mod that's pc104_angle (iirc). The setkb script has a shorthand notation where for instance 'a' means 'anglemod'; run `./setkb.sh -h` to see its help text.
]]>I'm a colemak and linux noob and trying to get the keyboard on my ubuntu dual boot to match my setup in epkl on windows. I'm using Tarmak 1 with the curlangle mod on ANSI -- QWJRTYUIOP ASDFGMNEL XCBVZKH. I am having trouble finding this option in the menu after installing the BBT XBB package on ubuntu. How would I go about installing it?
]]>I apologize for any inconvenience caused by not using the GitHub Issues, but I'll keep it in mind for future reference. I'm fairly new to this whole programming thing and it just somehow slipped my mind.
Much thanks :)
]]>Try updating to the latest commit. I had a wrong scan code for the <BKSP> key in the extend file (it was incorrectly called <BACK>, an artefact of me working cross-platform).
Here's the current Backspace mapping:
key <BKSP> { symbols[Group1]=[Any , Any , Any , Any , // BackSpace
Pause , Pause , // Pause/Break
Pause , Pause ] , // (<BRK> is special)
actions[Group1]=[NoAction(), NoAction(), NoAction(), NoAction(),
Redirect(key=<PAUS>,clearmods=LevelFive), Redirect(key=<PAUS>,clearmods=LevelFive) ,
NoAction() , NoAction() ] ,
repeat=yes }; // BackSpace
If instead you want to output Ctrl+Backspace, it's doable I think. You'd want to use this I suppose:
key <BKSP> { symbols[Group1]=[Any , Any , Any , Any , // BackSpace
BackSpace , BackSpace , // Ctrl+Backspace (by action)
BackSpace , BackSpace ] , //
actions[Group1]=[NoAction(), NoAction(), NoAction(), NoAction(),
Redirect(key=<BKSP>,mods=Control,clearmods=LevelFive), Redirect(key=<BKSP>,mods=Shift+Control,clearmods=LevelFive), // Ctrl+Back
Redirect(key=<BKSP>,mods=Control,clearmods=LevelFive), Redirect(key=<BKSP>,mods=Shift+Control,clearmods=LevelFive)], // Ctrl+Back
repeat=yes }; // BackSpace
Please let me know if that works!
]]>However, if you use Extend it should be possible to press Caps+T+O to delete words. Does that work for you?
]]>But of course this manual editing of the keyboard file is not optimal. How should I have done this?
Also, I was trying to figure out how to gain access to the extend locking behavior discussed in Dreymar's post so that I don't need to hold an awkward stretch for both extend and other modifiers.
Thanks for I sight you can provide. And also thanks for this awesome package! I have loved using the extend layer for the last few days!
]]>