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

Result of Scripts depends to kind of shortcut #2174

Closed
meisterleise opened this issue Jan 3, 2016 · 4 comments
Closed

Result of Scripts depends to kind of shortcut #2174

meisterleise opened this issue Jan 3, 2016 · 4 comments

Comments

@meisterleise
Copy link

That's really strange! I want to set the date by using a script and quicksilver trigger shortcut.
The normal output without quicksilver is:

03.01.2016

According to the kind of shortcut I set to the script, Quicksilver makes different outputs:
ctrl + alt + d
03…01…2016

ctrl + shift + t
03012016

ctr + alt + shift + h
03÷01÷2016

@skurfer
Copy link
Member

skurfer commented Jan 4, 2016

What kind of script? My guess is that the modifiers are still being pressed as the script runs.

Try editing the trigger and change it to activate “On Release” instead of “On Press”.

@meisterleise
Copy link
Author

Sorry, suggestion didn't work.

This is one of the Scripts:

set h to do shell script "date "+%d.%m.%Y""

tell application "System Events"
set k to name of every application process whose frontmost is true
end tell
set k to k as text

tell application k
activate
tell application "System Events"
keystroke h
end tell
end tell

@tiennou
Copy link
Member

tiennou commented Feb 5, 2016

Actually, it's not a Quicksilver issue per se, as Rob told above, the modifiers that caused the script to run are still pressed, so you'll get various garbage out of ., depending on which shortcut you use.

You might have better luck by storing your script's result in the clipboard and keystroke "v" using command down instead.

@stale
Copy link

stale bot commented Apr 4, 2022

This issue hasn't been updated in over 2 years. It has been marked as 'stale' and will be closed in 30 days. Please check whether this is still an issue with the latest version of Quicksilver. If so, update or comment on this issue to keep it open.

@stale stale bot added the noactivity label Apr 4, 2022
@stale stale bot closed this as completed May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants