Updating my config to TOML V1.1 #2148
Unanswered
iandol
asked this question in
questions-and-answers
Replies: 1 comment 2 replies
You’re absolutely right. I had to do the same thing. It’s beneficial to compare your configuration with the default configuration. Here’s part of my configuration# Config version for compatibility and deprecations
# See: https://nikitabobko.github.io/AeroSpace/guide#config-version
# Fallback value (if you omit the key): config-version = 1
config-version = 2
# Start AeroSpace at login
start-at-login = true
# Normalizations. See: https://nikitabobko.github.io/AeroSpace/guide#normalization
enable-normalization-flatten-containers = true
enable-normalization-opposite-orientation-for-nested-containers = true
# Windows arrangement per workspace
#
on-window-detected = [
# Floating windows - without workspace assigned
{
if = '''
test %{app-bundle-id} = com.apple.calculator \
|| test %{app-bundle-id} = com.apple.clock \
|| test %{app-bundle-id} = com.apple.systempreferences \
|| test %{app-bundle-id} = com.apple.mail
''',
run = ['layout floating'],
},
# Per workspace location
# See: https://nikitabobko.github.io/AeroSpace/commands#move-node-to-workspace
#
# Workspace 1 (Private)
{
if = '''
test %{app-bundle-id} = com.apple.mail \
|| test %{app-bundle-id} = com.apple.Music \
|| test %{app-bundle-id} = com.apple.MobileSMS \
|| test %{app-bundle-id} = com.apple.TV \
|| test %{app-bundle-id} = com.apple.Photos \
''',
run = ['move-node-to-workspace 1', 'layout floating'],
},
# Workspace 2 (Files and Directories, Finder)
{
if = 'test %{app-bundle-id} = com.apple.finder',
run = ['move-node-to-workspace 2'],
},
]
focus-follows-mouse.enabled = true
# 'main' binding mode declaration
# See: https://nikitabobko.github.io/AeroSpace/guide#binding-modes
# 'main' binding mode must be always presented
# Fallback value (if you omit the key): mode.main.binding = {}
[mode.main.binding]
# All possible keys:
# - Letters. a, b, c, ..., z
# - Numbers. 0, 1, 2, ..., 9
# - Keypad numbers. keypad0, keypad1, keypad2, ..., keypad9
# - F-keys. f1, f2, ..., f20
# - Special keys. minus, equal, period, comma, slash, backslash, quote, semicolon,
# backtick, leftSquareBracket, rightSquareBracket, space, enter, esc,
# backspace, tab, pageUp, pageDown, home, end, forwardDelete,
# sectionSign (ISO keyboards only, european keyboards only)
# - Keypad special. keypadClear, keypadDecimalMark, keypadDivide, keypadEnter, keypadEqual,
# keypadMinus, keypadMultiply, keypadPlus
# - Arrows. left, down, up, right
# All possible modifiers: cmd, alt, ctrl, shift
# All possible commands: https://nikitabobko.github.io/AeroSpace/commands
# See: https://nikitabobko.github.io/AeroSpace/commands#exec-and-forget
# You can uncomment the following lines to open up terminal with alt + enter shortcut
# (like in i3)
# alt-enter = '''exec-and-forget osascript -e '
# tell application "Terminal"
# do script
# activate
# end tell'
# '''
# See: https://nikitabobko.github.io/AeroSpace/commands#layout
alt-slash = 'layout tiles horizontal vertical'
alt-comma = 'layout accordion horizontal vertical'
# See: https://nikitabobko.github.io/AeroSpace/commands#focus
ctrl-h = 'focus --boundaries-action wrap-around-the-workspace left'
ctrl-j = 'focus --boundaries-action wrap-around-the-workspace down'
ctrl-k = 'focus --boundaries-action wrap-around-the-workspace up'
ctrl-l = 'focus --boundaries-action wrap-around-the-workspace right'
# See: https://nikitabobko.github.io/AeroSpace/commands#move
alt-ctrl-h = 'move left'
alt-ctrl-j = 'move down'
alt-ctrl-k = 'move up'
alt-ctrl-l = 'move right'
# ... |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
So the latest beta supports a better format for our
on-window-detectedblocks. But when I change to the inline table format aerospace gives me an error on the "previous" part:I now need to move my
on-window-detectedblock above any of the[block]sections. i'm sure this is some sort of TOML requirement; I thought the idea of TOML was that it was "obvious" 🫤 compared to YAML...By the way, one problem I encountered is that my VSCode TOML linter didn't support V1.1, so I had to remove it an install this one: https://tombi-toml.github.io/tombi/docs/editors/vscode-extension -- however it still defaults to V1.0 and you need to put a
#:tombi toml-version = "v1.1.0"at the beginning of the TOML file...All reactions