We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Took me a while to work this out - but Quicksilver and Excel no longer live in harmony on my Mac.
Copy / Paste of cells using keyboard shortcuts... and general slowness result.
When I shut down Quicksilver and rebooted - the Excel problem went away.
Did a fair bit of testing on this... so I guess it's a thing. I told the Microsoft Support Network people about this too in case you need to know!
I have MS Office 2011 for Mac also on my computer - and it runs fine - always did! - This issue is with 365 on a MacBook Pro late 2015.
The text was updated successfully, but these errors were encountered:
If you disable Quicksilver’s Clipboard plug-in, does the problem go away?
Sorry, something went wrong.
It certainly does! - I just tested it! - Well done - and thanks for helping me.
Well, that’s not a fix, but it gives us an idea where the problem is. Something about the Excel data must be confusing the clipboard code.
A less extreme solution might be to list Excel under “Ignore Applications” in the Clipboard plug-in’s preferences.
Gotcha - thanks for the advice. I shall make the necessary alterations.
@spiketrain - what version of Excel are you using, and is this still an issue?
I am unable to reproduce here using Excel version 16.46
No branches or pull requests
Took me a while to work this out - but Quicksilver and Excel no longer live in harmony on my Mac.
Copy / Paste of cells using keyboard shortcuts... and general slowness result.
When I shut down Quicksilver and rebooted - the Excel problem went away.
Did a fair bit of testing on this... so I guess it's a thing. I told the Microsoft Support Network people about this too in case you need to know!
I have MS Office 2011 for Mac also on my computer - and it runs fine - always did! - This issue is with 365 on a MacBook Pro late 2015.
The text was updated successfully, but these errors were encountered: