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

Keybinding for Moving Finder to Current Workspace in AeroSpace Beta #441

Closed
LockeAG opened this issue Aug 22, 2024 · 1 comment
Closed
Labels
issue-template-ignored The issue will be ignored. The issue is most likely a duplicate or covered in docs

Comments

@LockeAG
Copy link

LockeAG commented Aug 22, 2024

I found that persisting a floating window across workspaces is not supported (as noted in Issue #2).

I use Finder a lot and I've been trying to create a custom solution to move it to the current workspace with a keybinding. I've managed to make it work, but the process still feels a bit clunky. I could really use a smoother solution.

cmd-shift-alt-down = "exec-and-forget ~/.dotfiles/.aerospace/finder_move.sh"

#!/usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail

current_workspace=$(aerospace list-workspaces --focused)

osascript -e "
tell application \"Finder\"
    activate
end tell
" && aerospace move-node-to-workspace "$current_workspace" && aerospace workspace "$current_workspace"

Is there a more efficient way to achieve this? Any improvements or guidance would be appreciated.

aerospace CLI client version: 0.14.1-Beta 5861e85b65cb7dc914a0a68027c56e2bc90510fd                                                
AeroSpace.app server version: 0.14.1-Beta 5861e85b65cb7dc914a0a68027c56e2bc90510fd 
@nikitabobko
Copy link
Owner

Please don't ignore the checklist

@nikitabobko nikitabobko added the issue-template-ignored The issue will be ignored. The issue is most likely a duplicate or covered in docs label Aug 22, 2024
Repository owner locked and limited conversation to collaborators Aug 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue-template-ignored The issue will be ignored. The issue is most likely a duplicate or covered in docs
Projects
None yet
Development

No branches or pull requests

2 participants