Menu
▾
▴
Re: [ jEdit-users ] Creating a customised jEdit OSX build.
|
From: Vampire (jEdit) <Vam...@gm...> - 2010-03-12 19:06:58
|
Hi Dennis, of course you can. Again there are multiple ways. The most important ones are maybe: - change the default location of the settings directory if you rebuild from source - use the startup parameter with which you can define a custom settings directory. I'm not sure if you can set this up in the plist but maybe this is possible. Regards Vampire Dennis Hotson schrieb: > Thanks Vampire, that really helps explain a lot. I'll give it a try. > > One thing I was wondering about is if I send my custom jEdit package > to someone who is already an existing jEdit user, can I make it avoid > messing with their existing settings directory? > > Regards, > Dennis > > On Fri, Mar 12, 2010 at 8:34 PM, Vampire (jEdit) <Vam...@gm... > <mailto:Vam...@gm...>> wrote: > > Hi Dennis, > > there are many ways to do that or something similar. Here some > options: > > - open the jEdit.app folder with "Show content" from the context > menu and copy the settings and plugins that you want to have > "pre-packaged" there, then send around the jEdit.app or build a > (internet enabled) DMG for it > > - use the plugin manager to install the plugins you want to have > "pre-packaged" not to the settings but to the jEdit directory, > then they should land automatically in the jEdit.app, then open > the jEdit.app folder with "Show content" from the context menu and > copy the settings that you want to have "pre-packaged" there, then > send around the jEdit.app or build a (internet enabled) DMG for it > > - export your plugin set via plugin manager as plugin set and > distribute that exported file and your settings file. With the > plugin set your friends can install that same set of plugins > automatically by importing the plugin set from within plugin > manager and the settings file has just to be placed inside the > settings directory > > - distribute your whole settings folder to your friends (take care > about what you distribute, some plugins store cache data there > that only would need space, some plugins store passwords there) > > - download or checkout the source and modify the build process so > that the settings and plugins you want are included, then call > "ant dist-mac" > > There are possibly a dozen other ways to do what you want to do, > it is a matter of taste how you want to do it. The simplest and > easiest way is maybe to export your plugin set and give them your > settings file. > > Regards > Vampire > > PS: To get your settings file, either just pick "properties" from > your settings folder (by default ~/.jedit) or use the macro > "Properties->jEdit Properties" to dump the settings to a new > buffer and save that buffer > > Dennis Hotson schrieb: >> Hi, >> >> I'm looking for some advice on creating my own pre-customised >> jEdit that I can >> give to friends who want to try out jEdit. >> >> Is there a way to package up my settings and plugins into a >> standalone jEdit.app ? >> >> Any ideas are welcome. :-) >> >> Regards, >> Dennis >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev > > |