Background: we have 2 separate installs of jedit tailored for 2 different workfows
(multi-user). Attempting to merge them using '-settings=/some/where/else' command-line
switch:
dmaziuk@stingray:~$ java -Xmx96m -Xms24m -jar /share/java/jEdit/5.0.0/jedit.jar -noserver
-settings=/share/java/jEdit/mrannotator/
12:56:25 PM \[main\] \[error\] main: java.io.FileNotFoundException: /share/java/jEdit/mrannotator/activity.log
(Permission denied)
After making that a+w:
PluginJAR: java.io.FileNotFoundException: /share/java/jEdit/mrannotator/jars-cache/QuickNotepad.jar.summary
(No such file or directory)
and
IOUtilities: Error moving file: java.io.FileNotFoundException: /share/java/jEdit/mrannotator/properties
(Is a directory) : /share/java/jEdit/mrannotator/properties (Is a directory)
12:57:18 PM \[AWT-EventQueue-0\] \[error\] jEdit: Failed to rename "/share/java/jEdit/mrannotator/#properties#save#"
to the user properties file "/share/java/jEdit/mrannotator/properties"
So clearly '-settings' overrides "user.home/.jedit" -- why have it in the first place
when I can just 'java -Duser.home=/some/place/else' ?
Or should I file a feature request for (e.g.) '-global-settings=' switch instead ?
Submitted | dmaziuk - 2013-01-07 19:14:45 | Assigned | |
---|---|---|---|
Priority | 2 | Labels | |
Status | open | Group | none |
Resolution | None |
2013-01-07 19:33:55 ezust |
You are getting permission denied messages because of permissions problems, and you're
trying to use a shared area for settings that are used by multiple users at the same
time?
|
---|---|
2013-01-07 19:58:10 dmaziuk |
What I'd like is to share a set of modes, macros, and plugins between different \*users\*.
Specifically, a user working on file type X today will have the macros and modes for
X. Tomorrow they'll work on file type Y and have the plugins and modes for that. |
2013-01-07 21:09:52 ezust |
There is a shared set of modes, macros and plugins in jEdit's home directory. You
can customize different jEdit installations that way. What is the harm of having jedit.jar
and documentation there too?
|
2013-01-07 22:22:04 dmaziuk |
So the two currently available options is to have 2 separate jEdit installs & remeber
to upgrade it ttwwiiccee, or have all plugins, macros, and modes available to everyone
through the menus -- but use custom '-settings' to turn on and off the relevant UI
elements. |
2013-12-09 19:03:15.464000 ezust |
- **summary**: sharable common user settings directory --> site-wide folder for modes,
macros and plugins that is not clobbered by upgrades |
2013-12-10 18:12:23.849000 dmaziuk |
Well, in "mode 1" I use plugin X with 2 windows docked to the bottom and left, and
in "mode 2" I use plugin Y with 2 windows docked to the bottom and right. The issue
is I don't want X and Y's windows there at the same time. So at teh very least you'd
have to package buffer properties like window docking in addition modes and macros
to make it a complete solution.
|
2013-12-10 18:18:17.979000 ezust |
Another option is to use the JVM argument,
|
2013-12-10 18:22:49.077000 ezust |
Also, your trick of overriding user.home might work fine on Linux but it won't work
well on other platforms or in future versions of jEdit.
|