-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bundle non-C/C++ plugins with the python core code #44
Comments
This is a good idea if a Python interpreter is already installed. However, installing a Python interpreter just to use a plugin seems like more of a hassle than installing the C core. I think this is a good idea for Gedit and Vim because it is implied that the user has a Python interpreter for use with those two plugins. I'm not sure about Emacs and jEdit plugins. |
On Mar 28, 2012, at 0:05, Trey Hunnerreply@reply.github.com wrote:
We just bundle the script, and the python script could be used if a python interpreter is present. But I believe we should use the C core (except vim and gedit) if the c executable is found. |
Just like this, we could find an external python interp for a editor that does not support a built-in one. If a C core is missing and a python interp is found, we could take advantage of the python version, so user would feel more comfortable about the installation, since most Linux users have python installed by default. |
That could work well. Maybe for now we should look for I don't think we should be too concerned with bundling the Python version with all of the plugins yet though. Our current solution works reasonably (even if it's not ideal) and for all I know there are currently no users of the jEdit or emacs plugins. |
Done for vim. |
By bundling non-C/C++ plugins with the python core code, users could avoid install the EditorConfig Core separately.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: