Microsoft Office 2010 shortcutting

Auteur Réponses
SirLouen Dimanche 16 Décembre 2012 à 21:37

I've found an strange issue: Everytime I open a microsoft office file (docx, pptx or xlsx) with my Office 2010 tools instaled on PlayOnLinux, the system automatically creates a new .Ink shortcut in the folder where the file exists.

I can't understand why is this happening, I've been googling around but found anything regarding this issue, any ideas?
SirLouen Mardi 18 Décembre 2012 à 1:49

Here is an example of what is happening :(
This happens everytime I basically, save the DOCX file

Edité par SirLouen

SirLouen Mercredi 2 Janvier 2013 à 17:44

I have not found any solution to this problem.
I've discovered that it creates an .ink shortcut in the same dir as the document itself, everytime i Save it, no matter if it is a Powerpoint Word or Excel document.
Why this happens?
SirLouen Dimanche 13 Janvier 2013 à 18:07

Ok, I've found the solution to this problem: The issue is due to a "Recent" docs feature that Office for windows offer. Under the drive_c/users/wine_user_whatever/ directory, there should be a dir called "Recent"
We can create it for example
mkdir ~/.PlayOnLinux/wineprefix/Office2010/drive_c/users/myuser/Recent
And everytime we save the document the Ink will be created strictly there, instead of being created in the home dir, or in the dir where the doc exists.
If we dont want to store thousands of 1kb .Ink files, we can run a cron job to delete them every hour for example
This is not a super-solution, should be solved inside the Microsoft Office 2010 script instead but it can leave things cleaner (specially because I was editing Word docs based on a Dropbox directory, and the shortcuts tend to sync in everyother PC of mine :))

Edité par SirLouen

petch Dimanche 13 Janvier 2013 à 20:54

It seems the normal situation is rather that Wine creates this directory as needed, and manages what it contains. Something must have gone wrong with your virtual drive.
SirLouen Dimanche 13 Janvier 2013 à 20:58

I'm not sure about that. I'm sure that hasn't been anything wrong because I've redone the installation multiple times due to other issues (not this), but this has been a permanent issue.