Emaces 23.2 for Windows and App-V 4.5

At first, this looked like apiece of cake. I made a virtual package, deployed it, it worked. Yay! But now, it's looking like the customer is going to want it to be deployed customized. Emacs keeps all customizations in a .emacs file and "plugins" in a .emacs.d directory. I don't know if it's reasonable for a virtual app to lay down these files if they don't exist, but not if they don't. Obviously, each user could have a completely different config that they'd want to persist across sessions and possibly workstations.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Is it possible to configure where the files live? It may be possible to locate them on a network share and have a pre-launch script to create/modify them..
Answered 12/03/2010 by: DannyC
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity