How To: Install ‘gedit’ With All The Bells and Whistles2 min read

There are many text editors out there, but gedit is a perennial favorite. There are also many plugins to extend gedit, and this is an easy way to install a bunch at once.

gedit, the default editor for the Gnome desktop environment, is a part of the GNOME Core Applications and is available in pretty much every distro. It also doesn’t actually need a lot of additional dependencies, which helps make it useful for most any popular desktop environment.

You can use gedit for anything, from programming to writing markup for your website. You can use it as a plain text editor and there are many ways to extend it, to add functionality not included by default. There are plugins to highlight syntax, to auto-complete words, to auto-close brackets, etc. You can make it do all sorts of things you’d not expect from a plain text editor.

Given that disk space is absurdly cheap these days, I don’t see any reason to not just go ahead and install as many plugins at once as I can. I may not use them all, but I’ll use most of them and I can just not enable those that I don’t want to use. So, how to install it all at once?

Crack open your terminal with CTRL + ALT + T and enter the following:

So, what’s going on there? You can string together applications with aptitude and this is installing gedit first, a pack of common plugins, and then every other plugin that uses the ‘gedit-plugin-*’ format and is in the repositories.

If you don’t already know, the asterisk is known as a wildcard. A wildcard basically means, “any character.” So, foo* is anything from fool to foolish and foob* is anything from foobar to foob-gibberish183742 or whatever. It’s unlike the question mark, which only matches one character, in that it means any and all characters.

It should be noted that this only installs the plugins. You still can’t use them until you enable them. To select them, you need to first open ‘gedit’ (which will almost certainly be called “Text Editor” in your application menu) and click on preferences where you can navigate to the right-most tab and enable them. It looks like this:

gedit preferences
Select plugins ’til you’re satisfied!

If you did this properly,  you should now have a bunch of plugins enabled and not have to hunt them down, one by one, trying to find and install them manually. Is this a bit of overkill? Perhaps, but disk space is cheap and the entire thing takes up less than 19 additional MB on my system.

Like always, thanks for reading. Scroll up and look right. Toss your name and email address in there and you’ll get notified of new articles. I promise, I won’t spam you. You ain’t even gotta use your real name!

 

Smash a Button
[Total: 1 Average: 5]
Get PDFPrint This
About Me: I'm just some retired dude with a little bit more free time on my hands. If you want to support the site, why not help yourself out too by ordering some inexpensive web hosting so that you can start your own site?


Author: Admin

I'm a retired mathematician that has a fondness for Linux and many (not all) things tech. I'm an old-school geek that just enjoys the life he has. I live in a very, very rural area of Maine. View all posts by Admin

5 thoughts on “How To: Install ‘gedit’ With All The Bells and Whistles2 min read

  1. i normally use geany for writing both php and html by hand. Its great but i have not yet seen a spell checker that can be used with geany, that checks spelling of html documents whilst ignoring the html tags. So what i usually do is complete and save a whole html file and then use aspell from the command line with appropriate flags so it checks spelling but ignores the tags.

    Can not remember when i last used gedit, but can it do spelling checking whilst working on a html document with it ignoring html tags?

    1. Not that I’m aware of. I just checked and it happily marks ‘href’ as a typo. I also just decided to check Bluefish and even it highlights ‘href’ as a typo.

      With enough work with the ‘ignore’ option in manual spellcheck, that could be mostly eliminated. If I get a chance, I’ll check a few more editors. If I find one, I’ll both reply here and write an article about it.

      Thanks for reading.

  2. its an issue for those that actually manually write code in text editors . Here is one solution. Say you save your html document to your home directory as index.html . using aspell from command line you use:

    aspell –lang=en –encoding=utf-8 –mode=sgml –add-sgml-check=ch check index.html

    Aspell is in Slackware default install; other OS users can install it .

    An interactive simple dialogue/gui comes up thats intuitive to use

Leave a Reply

Your email address will not be published. Required fields are marked *