How do I install a plugin for gEdit v3?
up vote
43
down vote
favorite
I just installed the ubuntu 11.10, and I want to install a plugin for gEdit.
I unpacked the plugin to the following folder: ~/.gnome2/gedit/plugins
but in the gedit doesn't show up the plugin.
gedit plugins
add a comment |
up vote
43
down vote
favorite
I just installed the ubuntu 11.10, and I want to install a plugin for gEdit.
I unpacked the plugin to the following folder: ~/.gnome2/gedit/plugins
but in the gedit doesn't show up the plugin.
gedit plugins
add a comment |
up vote
43
down vote
favorite
up vote
43
down vote
favorite
I just installed the ubuntu 11.10, and I want to install a plugin for gEdit.
I unpacked the plugin to the following folder: ~/.gnome2/gedit/plugins
but in the gedit doesn't show up the plugin.
gedit plugins
I just installed the ubuntu 11.10, and I want to install a plugin for gEdit.
I unpacked the plugin to the following folder: ~/.gnome2/gedit/plugins
but in the gedit doesn't show up the plugin.
gedit plugins
gedit plugins
edited Jun 6 '12 at 17:09
fossfreedom♦
148k36326371
148k36326371
asked Sep 17 '11 at 10:33
OHLÁLÁ
2,12772748
2,12772748
add a comment |
add a comment |
6 Answers
6
active
oldest
votes
up vote
43
down vote
accepted
gEdit 3
The version of gEdit in Oneiric & above is v3 built using gtk+3 libraries. The plugin folder locations are slightly different than from gEdit v2.
Every plugin needs at least two files.
One file (pluginname.plugin) is to tell gedit
:
- where the plugin can be found,
- what it's called,
- a short description,
- who is the author, etc.
This file is in the .desktop
format.
The second file is the actual code.
Both of these files need to be placed in either:
- the system-wide plugins directory
/usr/lib/gedit/plugins/
, or - in the user plugins directory, which may have to be manually created -
~/.local/share/gedit/plugins/
.
Installing Plugins
First create the plugin folder:
mkdir -p ~/.local/share/gedit/plugins
Now create a .plugin
file using gedit N.B. these files have the format:
[Plugin]
Loader=python
Module=examplepy
IAge=3
Name=Example py
Description=A Python plugin example
Authors=Jesse van den Kieboom <jesse@icecrew.nl>
Copyright=Copyright © 2006 Jesse van den Kieboom <jesse@icecrew.nl>
Website=http://www.gedit.org
source
For your v2 plugin you already have a file called project-manager.gedit-plugin
so you can rename it:
mv project-manager.gedit-plugin project-manager.plugin
Then edit the plugin file and change the section header to "[Plugin]"
You will now see this in your gedit plugin list.
However for me it threw errors about "import gedit, gtk, gtk.glade".
You need to change the source code to import the gtk+3 variants - called python introspection.
An excellent tutorial for converting from gtk+2 to gtk+3 see
- http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a.plugin
extension. If it has a.gedit-plugin
extension then it is an old version.
– icc97
Jun 22 '13 at 8:42
add a comment |
up vote
6
down vote
2016 Update
To install all the gedit plugins, try:
sudo apt-get install gedit-plugins
This worked great on Ubuntu 14.04. I'm currently using gedit version 3.10.4.
You will need to activate them by navigating to Edit - Preferences - Plugins. Then select the desired plugins to activate.
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
add a comment |
up vote
5
down vote
I finally found where the gEdit plugins are stored. Try putting the two files to whatever plugin here: /usr/lib/gedit/plugins
.
add a comment |
up vote
2
down vote
I have a 64-bit Ubuntu 14.04 LTS and the folder with the plugins is /usr/lib/x86_64-linux-gnu/gedit/plugins/
Copying inside it the *.plugin
and *.py
files made the trick for me
add a comment |
up vote
0
down vote
For Auto install, try the following
sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases
sudo apt-get update
sudo apt-get install gedit-plugins
sudo apt-get install gedit-projects-plugin
add a comment |
up vote
0
down vote
For easy installation of additional 3rd party plugins there is a plugin installer plugin
https://github.com/lwindolf/gedit-plugininstaller
which might simplify discovering and installing plugins.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f61785%2fhow-do-i-install-a-plugin-for-gedit-v3%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
43
down vote
accepted
gEdit 3
The version of gEdit in Oneiric & above is v3 built using gtk+3 libraries. The plugin folder locations are slightly different than from gEdit v2.
Every plugin needs at least two files.
One file (pluginname.plugin) is to tell gedit
:
- where the plugin can be found,
- what it's called,
- a short description,
- who is the author, etc.
This file is in the .desktop
format.
The second file is the actual code.
Both of these files need to be placed in either:
- the system-wide plugins directory
/usr/lib/gedit/plugins/
, or - in the user plugins directory, which may have to be manually created -
~/.local/share/gedit/plugins/
.
Installing Plugins
First create the plugin folder:
mkdir -p ~/.local/share/gedit/plugins
Now create a .plugin
file using gedit N.B. these files have the format:
[Plugin]
Loader=python
Module=examplepy
IAge=3
Name=Example py
Description=A Python plugin example
Authors=Jesse van den Kieboom <jesse@icecrew.nl>
Copyright=Copyright © 2006 Jesse van den Kieboom <jesse@icecrew.nl>
Website=http://www.gedit.org
source
For your v2 plugin you already have a file called project-manager.gedit-plugin
so you can rename it:
mv project-manager.gedit-plugin project-manager.plugin
Then edit the plugin file and change the section header to "[Plugin]"
You will now see this in your gedit plugin list.
However for me it threw errors about "import gedit, gtk, gtk.glade".
You need to change the source code to import the gtk+3 variants - called python introspection.
An excellent tutorial for converting from gtk+2 to gtk+3 see
- http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a.plugin
extension. If it has a.gedit-plugin
extension then it is an old version.
– icc97
Jun 22 '13 at 8:42
add a comment |
up vote
43
down vote
accepted
gEdit 3
The version of gEdit in Oneiric & above is v3 built using gtk+3 libraries. The plugin folder locations are slightly different than from gEdit v2.
Every plugin needs at least two files.
One file (pluginname.plugin) is to tell gedit
:
- where the plugin can be found,
- what it's called,
- a short description,
- who is the author, etc.
This file is in the .desktop
format.
The second file is the actual code.
Both of these files need to be placed in either:
- the system-wide plugins directory
/usr/lib/gedit/plugins/
, or - in the user plugins directory, which may have to be manually created -
~/.local/share/gedit/plugins/
.
Installing Plugins
First create the plugin folder:
mkdir -p ~/.local/share/gedit/plugins
Now create a .plugin
file using gedit N.B. these files have the format:
[Plugin]
Loader=python
Module=examplepy
IAge=3
Name=Example py
Description=A Python plugin example
Authors=Jesse van den Kieboom <jesse@icecrew.nl>
Copyright=Copyright © 2006 Jesse van den Kieboom <jesse@icecrew.nl>
Website=http://www.gedit.org
source
For your v2 plugin you already have a file called project-manager.gedit-plugin
so you can rename it:
mv project-manager.gedit-plugin project-manager.plugin
Then edit the plugin file and change the section header to "[Plugin]"
You will now see this in your gedit plugin list.
However for me it threw errors about "import gedit, gtk, gtk.glade".
You need to change the source code to import the gtk+3 variants - called python introspection.
An excellent tutorial for converting from gtk+2 to gtk+3 see
- http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a.plugin
extension. If it has a.gedit-plugin
extension then it is an old version.
– icc97
Jun 22 '13 at 8:42
add a comment |
up vote
43
down vote
accepted
up vote
43
down vote
accepted
gEdit 3
The version of gEdit in Oneiric & above is v3 built using gtk+3 libraries. The plugin folder locations are slightly different than from gEdit v2.
Every plugin needs at least two files.
One file (pluginname.plugin) is to tell gedit
:
- where the plugin can be found,
- what it's called,
- a short description,
- who is the author, etc.
This file is in the .desktop
format.
The second file is the actual code.
Both of these files need to be placed in either:
- the system-wide plugins directory
/usr/lib/gedit/plugins/
, or - in the user plugins directory, which may have to be manually created -
~/.local/share/gedit/plugins/
.
Installing Plugins
First create the plugin folder:
mkdir -p ~/.local/share/gedit/plugins
Now create a .plugin
file using gedit N.B. these files have the format:
[Plugin]
Loader=python
Module=examplepy
IAge=3
Name=Example py
Description=A Python plugin example
Authors=Jesse van den Kieboom <jesse@icecrew.nl>
Copyright=Copyright © 2006 Jesse van den Kieboom <jesse@icecrew.nl>
Website=http://www.gedit.org
source
For your v2 plugin you already have a file called project-manager.gedit-plugin
so you can rename it:
mv project-manager.gedit-plugin project-manager.plugin
Then edit the plugin file and change the section header to "[Plugin]"
You will now see this in your gedit plugin list.
However for me it threw errors about "import gedit, gtk, gtk.glade".
You need to change the source code to import the gtk+3 variants - called python introspection.
An excellent tutorial for converting from gtk+2 to gtk+3 see
- http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
gEdit 3
The version of gEdit in Oneiric & above is v3 built using gtk+3 libraries. The plugin folder locations are slightly different than from gEdit v2.
Every plugin needs at least two files.
One file (pluginname.plugin) is to tell gedit
:
- where the plugin can be found,
- what it's called,
- a short description,
- who is the author, etc.
This file is in the .desktop
format.
The second file is the actual code.
Both of these files need to be placed in either:
- the system-wide plugins directory
/usr/lib/gedit/plugins/
, or - in the user plugins directory, which may have to be manually created -
~/.local/share/gedit/plugins/
.
Installing Plugins
First create the plugin folder:
mkdir -p ~/.local/share/gedit/plugins
Now create a .plugin
file using gedit N.B. these files have the format:
[Plugin]
Loader=python
Module=examplepy
IAge=3
Name=Example py
Description=A Python plugin example
Authors=Jesse van den Kieboom <jesse@icecrew.nl>
Copyright=Copyright © 2006 Jesse van den Kieboom <jesse@icecrew.nl>
Website=http://www.gedit.org
source
For your v2 plugin you already have a file called project-manager.gedit-plugin
so you can rename it:
mv project-manager.gedit-plugin project-manager.plugin
Then edit the plugin file and change the section header to "[Plugin]"
You will now see this in your gedit plugin list.
However for me it threw errors about "import gedit, gtk, gtk.glade".
You need to change the source code to import the gtk+3 variants - called python introspection.
An excellent tutorial for converting from gtk+2 to gtk+3 see
- http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
edited Sep 2 '12 at 18:32
answered Sep 17 '11 at 10:40
fossfreedom♦
148k36326371
148k36326371
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a.plugin
extension. If it has a.gedit-plugin
extension then it is an old version.
– icc97
Jun 22 '13 at 8:42
add a comment |
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a.plugin
extension. If it has a.gedit-plugin
extension then it is an old version.
– icc97
Jun 22 '13 at 8:42
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a
.plugin
extension. If it has a .gedit-plugin
extension then it is an old version.– icc97
Jun 22 '13 at 8:42
Note that there is a good library of third party plugins for gedit 3 here: live.gnome.org/Gedit/Plugins#third_party. For those that missed it in the section above the critical bit for a plugin being found by gedit 3 is that the plugin has a
.plugin
extension. If it has a .gedit-plugin
extension then it is an old version.– icc97
Jun 22 '13 at 8:42
add a comment |
up vote
6
down vote
2016 Update
To install all the gedit plugins, try:
sudo apt-get install gedit-plugins
This worked great on Ubuntu 14.04. I'm currently using gedit version 3.10.4.
You will need to activate them by navigating to Edit - Preferences - Plugins. Then select the desired plugins to activate.
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
add a comment |
up vote
6
down vote
2016 Update
To install all the gedit plugins, try:
sudo apt-get install gedit-plugins
This worked great on Ubuntu 14.04. I'm currently using gedit version 3.10.4.
You will need to activate them by navigating to Edit - Preferences - Plugins. Then select the desired plugins to activate.
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
add a comment |
up vote
6
down vote
up vote
6
down vote
2016 Update
To install all the gedit plugins, try:
sudo apt-get install gedit-plugins
This worked great on Ubuntu 14.04. I'm currently using gedit version 3.10.4.
You will need to activate them by navigating to Edit - Preferences - Plugins. Then select the desired plugins to activate.
2016 Update
To install all the gedit plugins, try:
sudo apt-get install gedit-plugins
This worked great on Ubuntu 14.04. I'm currently using gedit version 3.10.4.
You will need to activate them by navigating to Edit - Preferences - Plugins. Then select the desired plugins to activate.
answered Feb 11 '16 at 19:26
Heather92065
1931412
1931412
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
add a comment |
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
To be more precise (as installing a third-party plugin made me crazy), this are the steps to go (from terminal): 1) sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases; 2) sudo apt-get update; 3) sudo apt-get install <plugin-name> (e.g. sudo apt-get install gedit-classbrowser3g-plugin). Cheers!
– umbe1987
Mar 14 '16 at 18:23
add a comment |
up vote
5
down vote
I finally found where the gEdit plugins are stored. Try putting the two files to whatever plugin here: /usr/lib/gedit/plugins
.
add a comment |
up vote
5
down vote
I finally found where the gEdit plugins are stored. Try putting the two files to whatever plugin here: /usr/lib/gedit/plugins
.
add a comment |
up vote
5
down vote
up vote
5
down vote
I finally found where the gEdit plugins are stored. Try putting the two files to whatever plugin here: /usr/lib/gedit/plugins
.
I finally found where the gEdit plugins are stored. Try putting the two files to whatever plugin here: /usr/lib/gedit/plugins
.
edited Oct 19 '11 at 17:08
Kris Harper
9,559114670
9,559114670
answered Oct 19 '11 at 16:21
Michael
511
511
add a comment |
add a comment |
up vote
2
down vote
I have a 64-bit Ubuntu 14.04 LTS and the folder with the plugins is /usr/lib/x86_64-linux-gnu/gedit/plugins/
Copying inside it the *.plugin
and *.py
files made the trick for me
add a comment |
up vote
2
down vote
I have a 64-bit Ubuntu 14.04 LTS and the folder with the plugins is /usr/lib/x86_64-linux-gnu/gedit/plugins/
Copying inside it the *.plugin
and *.py
files made the trick for me
add a comment |
up vote
2
down vote
up vote
2
down vote
I have a 64-bit Ubuntu 14.04 LTS and the folder with the plugins is /usr/lib/x86_64-linux-gnu/gedit/plugins/
Copying inside it the *.plugin
and *.py
files made the trick for me
I have a 64-bit Ubuntu 14.04 LTS and the folder with the plugins is /usr/lib/x86_64-linux-gnu/gedit/plugins/
Copying inside it the *.plugin
and *.py
files made the trick for me
answered Feb 17 '16 at 13:49
Fernando Mlró Mlró
645
645
add a comment |
add a comment |
up vote
0
down vote
For Auto install, try the following
sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases
sudo apt-get update
sudo apt-get install gedit-plugins
sudo apt-get install gedit-projects-plugin
add a comment |
up vote
0
down vote
For Auto install, try the following
sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases
sudo apt-get update
sudo apt-get install gedit-plugins
sudo apt-get install gedit-projects-plugin
add a comment |
up vote
0
down vote
up vote
0
down vote
For Auto install, try the following
sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases
sudo apt-get update
sudo apt-get install gedit-plugins
sudo apt-get install gedit-projects-plugin
For Auto install, try the following
sudo add-apt-repository ppa:gedit-bc-dev-plugins/releases
sudo apt-get update
sudo apt-get install gedit-plugins
sudo apt-get install gedit-projects-plugin
answered Dec 11 '16 at 14:26
aashish
11615
11615
add a comment |
add a comment |
up vote
0
down vote
For easy installation of additional 3rd party plugins there is a plugin installer plugin
https://github.com/lwindolf/gedit-plugininstaller
which might simplify discovering and installing plugins.
add a comment |
up vote
0
down vote
For easy installation of additional 3rd party plugins there is a plugin installer plugin
https://github.com/lwindolf/gedit-plugininstaller
which might simplify discovering and installing plugins.
add a comment |
up vote
0
down vote
up vote
0
down vote
For easy installation of additional 3rd party plugins there is a plugin installer plugin
https://github.com/lwindolf/gedit-plugininstaller
which might simplify discovering and installing plugins.
For easy installation of additional 3rd party plugins there is a plugin installer plugin
https://github.com/lwindolf/gedit-plugininstaller
which might simplify discovering and installing plugins.
answered Dec 6 at 15:56
lwindolf
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f61785%2fhow-do-i-install-a-plugin-for-gedit-v3%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown