User Ratings

★★★★★
★★★★
★★★
★★
3
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • This is an outstanding plugin. However, this plugin uses Python 2. To get it to work under later gedit versions on systems with Python 3, the following changed instructions apply: Installation ------------ Extract the tarball in the ~/.local/share/gedit/plugins directory. Configuration ------------- If you want to use dconf-editor to change the settings and you want to see the schema with its default settings you will have to add to XDG_DATA_DIRS the plugin dir e.g. XDG_DATA_DIRS=$XDG_DATA_DIRS:~/.local/share/gedit/plugins/builder dconf-editor Logging ------- To turn on logging you need a Python logging.conf file in the current working directory from which gedit is run. An example of this has been placed in the builder plugin directory so the easiest way to switch on full logging is to cd to the builder plugin directory and run gedit. 1. Find the builder.plugin file – edit this file and change the line that reads “Loader=python” and change it to read “Loader=python3″. What this does is force builder to recognize that it is a python3 plugin. 2. Convert the plugin to python3: Within the builder plugin folder, run the following: $ 2to3 -w *.py What this does is run through all the code looking for common python2 incompatibilities and converts them to python3 equivalents. The project does not appear to be maintaining the plugin for changes like this. The plugin will show as broken in gedit Plugin Manager until the above conversion to Python 3 is completed.
  • Does was it says. Give the same functionality as you get with emacs "compile" but you can save different commands for different directories. Cool.
  • Nice