Bunch not launching apps that have been closed but not quit. #181
-
|
Hi! Thanks for the great app! Launching apps with Bunch works for me when 1) the app is completely closed and 2) when the app was hidden (cmd-h). But when apps are still open but have had their window closed via cmd-w or clicking on the app's red close button (for app's that don't quit the app in that case) Bunch doesn't launch that app. (Bunch doesn't replicate what would happen if I click on an open app that has been closed but not quit.) Is there a way for Bunch to handle this? Or does this functionality require applescript or something else? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
|
That's activating, not launching. The app is already launched, so
sending a launch command has no reaction. Try adding a caret (^) at the
end of the app name and see if that does what you want. Let me know if
it doesn't work.
https://bunchapp.co/docs/bunch-files/apps/#activatingapps
…-Brett
On 4 Jan 2022, at 23:46, Evan Harmon wrote:
Hi! Thanks for the great app!
Launching apps with Bunch works for me when 1) the app is completely
closed and 2) when the app was hidden (cmd-h). But when apps are still
open but have had their window closed via cmd-w or clicking on the
app's red close button (for app's that don't quit the app in that
case) Bunch doesn't launch that app. (Bunch doesn't replicate what
would happen if I click on an open app that has been closed but not
quit.)
Is there a way for Bunch to handle this? Or does this functionality
require applescript or something else?
--
Reply to this email directly or view it on GitHub:
#181
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks - activating, not launching is my problem. And I should've specified that yes I've tried the caret. I have tried again and it is consistently not activating my apps (they are not visible if the apps have been "closed" with cmd-w or clicking the red close button). If they are hidden or if the app is completely closed (cmd-q), Bunch works like I expect. I'm just trying something like this so far: |
Beta Was this translation helpful? Give feedback.
-
|
This is an edge request for me, personally, as I never use apps in this
way. I either hide or quit. That said, there's a specific behavior in
macOS that presents the default window when an app is brought to
foreground by clicking the dock icon which I would have to simulate to
make this work. I'm adding it to the todo list.
In the meantime, you might have luck using:
* tell app "Safari" to activate
(but I haven't tested that, either)
…-Brett
On 5 Jan 2022, at 20:09, Evan Harmon wrote:
Thanks - activating, not launching is my problem. And I should've
specified that yes I've tried the caret. I have tried again and it is
consistently not activating my apps (they are not visible if the apps
have been "closed" with cmd-w or clicking the red close button). If
they are hidden or if the app is completely closed (cmd-q), Bunch
works like I expect. I'm just trying something like this so far:
```
---
title: Work - Browse
---
%Safari^
%Firefox^
%Obsidian^
%TaskPaper^
```
--
Reply to this email directly or view it on GitHub:
#181 (reply in thread)
You are receiving this because you commented.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'll try that and see if it works ok. Thanks for the help and the app!
Evan
… On Jan 6, 2022, at 12:14 PM, Brett Terpstra ***@***.***> wrote:
This is an edge request for me, personally, as I never use apps in this
way. I either hide or quit. That said, there's a specific behavior in
macOS that presents the default window when an app is brought to
foreground by clicking the dock icon which I would have to simulate to
make this work. I'm adding it to the todo list.
In the meantime, you might have luck using:
* tell app "Safari" to activate
(but I haven't tested that, either)
-Brett
On 5 Jan 2022, at 20:09, Evan Harmon wrote:
> Thanks - activating, not launching is my problem. And I should've
> specified that yes I've tried the caret. I have tried again and it is
> consistently not activating my apps (they are not visible if the apps
> have been "closed" with cmd-w or clicking the red close button). If
> they are hidden or if the app is completely closed (cmd-q), Bunch
> works like I expect. I'm just trying something like this so far:
> ```
> ---
> title: Work - Browse
> ---
>
> %Safari^
> %Firefox^
>
> %Obsidian^
> %TaskPaper^
> ```
>
> --
> Reply to this email directly or view it on GitHub:
> #181 (reply in thread)
> You are receiving this because you commented.
>
> Message ID:
> ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
I found a solution that works perfectly so far: I'm using this in a variety of ways now and has been 100% reliable for what I was wanting (which is to make the app visible/launched/active from whatever state it may have been in (quit, minimized, hidden). Bunch working great now, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thanks for the update!
…-Brett
________________________________
From: Evan Harmon ***@***.***>
Sent: Saturday, January 8, 2022 10:52:25 AM
To: ttscoff/bunch ***@***.***>
Cc: Brett Terpstra ***@***.***>; Comment ***@***.***>
Subject: Re: [ttscoff/bunch] Bunch not launching apps that have been closed but not quit. (Discussion #181)
I found a solution that works perfectly so far:
%Obsidian^
$ open /Applications/Obsidian.app
I'm using this in a variety of ways now and has been 100% reliable for what I was wanting (which is to make the app visible/launched/active from whatever state it may have been in (quit, minimized, hidden). Bunch working great now, thanks!
—
Reply to this email directly, view it on GitHub<#181 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAALVWO7EDB5SM5B4IOOBLTUVBTUTANCNFSM5LJCK57Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
I found a solution that works perfectly so far:
I'm using this in a variety of ways now and has been 100% reliable for what I was wanting (which is to make the app visible/launched/active from whatever state it may have been in (quit, minimized, hidden). Bunch working great now, thanks!