-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update tmux-sessioner extension #16218
Conversation
- chore: lint & format - chore: update dependencies - feat: specify directory - Initial commit
Thank you for your contribution! 🎉 🔔 @louishuyng @sxn @jasonshanks you might want to have a look. You can use this guide to learn how to check out the Pull Request locally in order to test it. Due to our current reduced availability, the initial review may take up to 10-15 business days 🎄 |
I like this extension is getting some renewed attention right now! Not mine to say and I haven't downloaded the fork to check out yet but I think this is great, as long as the directory option can be left blank and not prompted for. Not how I personally use tmux: every session has a different directory and navigating to one is far superior in the actual terminal (like I immediately reach for Zoxide). What do you think @louishuyng ? |
I think the idea of setting up a new directory when starting a new tmux session is cool. To be honest, i not usually create new session as i always defined my session using But if i have a chance to setup directory for each new session i would like to follow the way
The reason is we usually focus on some main default directory (for me is For example:
@guidefari @jasonshanks what do you guys think if we follow above? |
Yeah that suits me fine! For the most part I create a lot of website repos in a main Sites folder. Then a bunch of other repos in a GitHub projects ones. But switching directories once I'm in is trivial. Great for this to meet as many needs as possible 😄
p.s. @guidefari just being listening to some DnB on Goosebumps. nice curation 👍 |
@jasonshanks @louishuyng yeah I have a similar workflow. Please check my latest commit to confirm if it's what you have in mind? @jasonshanks thanks for checking out goosebumps! I'm also listening to mixes from there now😄 & RE the checking out my fork, here's what I ran, let me know if it works? BRANCH="ext/tmux-sessioner"
FORK_URL="https://github.com/guidefari/raycast-extensions.git"
EXTENSION_NAME="tmux-sessioner"
git clone -n --depth=1 --filter=tree:0 -b ${BRANCH} ${FORK_URL}
cd raycast-extensions
git sparse-checkout set --no-cone "extensions/${EXTENSION_NAME}"
git checkout
cd "extensions/${EXTENSION_NAME}"
npm install && npm run dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi 👋
Looks good to me, approved 🔥
Published to the Raycast Store: |
🎉 🎉 🎉 We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag. |
Description
Screencast
Checklist
npm run build
and tested this distribution build in Raycastassets
folder are used by the extension itselfREADME
are placed outside of themetadata
folder