jenndhemus / editra-plugins

Automatically exported from code.google.com/p/editra-plugins
0 stars 0 forks source link

Support user config directory at runtime #103

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I am developing on Eclipse and that one allows only one svn branch in the
project, thus I need to have one project for Editra, and the other project
for my plugins. Editra will not load my plugins from the second project, as
it is not under plugins, nor inside the .Editra

I was thinking how to best solve it, so that it can be useful for
everybody, and I think that an elegant way is to change config_dir at
runtime. Many other editors have such options.

- developers can have different test instances with different settings
- people can create different distributions
- and this patch also helps this TODO (Editra.py line: 930)
# TODO: make output file configurable via commandline
prof = hotshot.Profile("editra.prof")

Because with the patch, the options passed on commandline are turned into
dictionary and therefore it is possible to supply commandline settings for
profiling

The patch adds one config option, and turn options into dictionary.

Original issue reported on code.google.com by roman.ch...@gmail.com on 3 May 2009 at 11:41

Attachments:

GoogleCodeExporter commented 8 years ago
ahh, sorry, here it is already with the TODO solved

Original comment by roman.ch...@gmail.com on 3 May 2009 at 11:57

Attachments:

GoogleCodeExporter commented 8 years ago
wrong bug tracker?

On a quick glance it looks fine. Will look into applying it sometime today.

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 6 May 2009 at 12:32

GoogleCodeExporter commented 8 years ago
Applied with a number of modifications.

There was a bug in writing the errors to the console in ProcessCommandLine, 
write()
needs a string not an exception object.

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 7 May 2009 at 3:48