Let’s Install Nano (With Some Bonus Information)

This site mentions Nano quite a few times but never tells you how to install Nano. Today, this changes! Today, we make sure you have Nano available! Not all distros have Nano installed by default, but in pretty much all distros Nano would be a useful tool to have.

The Nano text editor (GNU nano) has been around since 1991, 21 years at the time of writing. I’ve written about it a few times, but nothing major. I think the most I’ve written about it was in an article about My Three Favorite Text Editors. If it’s not obvious from all of this, Nano is one of my favorite editors.

Rather than gush, I think I’ll just explain why I like Nano. It’s simple. When making quick edits to text from the terminal, I don’t need to know things like :q! just to exit the program, I can see how to exit the program because it’s written at the bottom. Nano has plenty of features, even a viable, albeit not great, find-and-replace function.

In Nano, you can do the obvious text manipulation tasks – like cut and paste, of course. You can jump to line numbers and all that stuff. At the end of the day, it’s a great terminal text editor that just works and is simple to use. If you’re new to Linux and think Nano looks daunting, you should introduce yourself to Vim or Emacs!

I like simplicity and effectiveness. For the things I do in that situation, quick file creation or editing, it works just fine. I don’t need anything more robust – or more complex.

Install Nano:

Sadly, Nano doesn’t come installed by default on all distros. It’s a tiny application that just works, so I’d be happy to see it as the default (or available by default) on more distros. Until that time, we’re stuck installing it ourselves.

Fortunately, there’s not much trouble installing Nano in the major distros. You just need to start with an open terminal. You can open one with your keyboard. Just pressing CTRL + ALT + T should open up your default terminal. Pick the appropriate command below and it should install nano for you.

Arch/derivatives:

RHEL/Fedora/derivatives:

OpenSUSE/derivatives:

Debian/Ubuntu/derivatives:

For everyone else, hunt around or download and compile it from source

Once you have Nano installed, you’ll need to know how to use it. Fortunately, for most users and most uses, there are a few shortcuts to learn and that’s it. For most people, you don’t need to know a whole lot for basic functionality. As you’re making basic edits, that works. It’s pretty easy.

My usual blurb (that I cut and paste) to tell people how to save a file in Nano is just this little snippet:

(Which, when formatted properly, comes out looking like “press CTRL + X, then Y, and then ENTER“.)

And, that’s it. That’s pretty much all you need to know when making quick text edits in Nano. However, there’s so much more to Nano than you might be expecting.

Bonus Nano Info:

While Nano is simple, it is deceptively simple. If you type nano into the terminal, you’ll see just a few options on the bottom. And, like I said, that too is a bit deceptive. With your terminal still open, type the following:

As you can see, there are a whole lot more options. There are far too many options for me to even begin to touch on them, and you won’t need any/most of them for the basic text editing for which we usually rely on Nano.

You can open a file with Nano like this:

You can also just open an instance of Nano and name the file when you’re closing it. If you want to create the title when you’re starting, you can just use:

That’ll auto-populate the name field when you’re saving the file. So, you can use Nano to create a new text file easily enough.

While you’re in there, you can use CTRL + W to search. If you then use ALT + W to go to the next instance of the text you searched for. Searching is even kind enough to support regex, case-sensitive searches, and can even be used to replace text.

At the bottom of the output, you’ll see directions that tell you how to use Nano. The ^ means you use the CTRL as the modifier. The M (such as M-A to undo) means you use the ALT as the modifier. So, to cut, you’d use CTRL + K and to undo something you’d use the previously mentioned ALT + M.

You’ll get used to it, I promise. You’ll learn it much faster than you’ll learn Vim or Emacs – but those too have their place. I wouldn’t want to spend hours in Nano, but it’s great for a few minutes when you need to make a quick edit.

Like I said, this is just touching on the surface. Look at the man page ( man nano) for more information. There’s a lot to this little editor and the advanced features are there if you need them. For example, I often open files with the -l flag so that it will show line numbers.

Closure:

Yup… There’s another article. This one tells you how to install Nano and has some bonus information about how to use Nano. I didn’t have time (and this isn’t that kind of site) to tell you about all the other nano options. Those options are just a man nano command away, should you want to use them.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To Install Krita In Ubuntu

Krita is an image authoring application. Some people compare Krita with GIMP. While the two programs have overlaps, the two programs are not the same and really shouldn’t be compared. Where GIMP is meant for image manipulation, Krita is more aimed at people who want to create images from scratch.

GIMP and Krita probably shouldn’t even be compared with each other. In fact, to save some time, you can read an article from the good folks at GIMP Tutorials for a good description of the benefits from either as well as why the two applications, GIMP and Krita, should not be compared with each other.

If you want to create digital art, Krita may be the software you’re looking for. When you’ve got a pointing device and plan on using the software like you’re painting, then Krita is the kind of software you’re looking for. Should you plan on creating from the ground up, not modifying memes or photoshopping dicks on pictures of previous politicians, you probably want Krita.

As luck would have it, this article will teach you how to install Krita on your Ubuntu-based system. It should also work for Debian, the official Ubuntu flavors, and Ubuntu derivatives like Mint or ElementaryOS. However, I tested in exactly none of those other systems. If you it doesn’t work, don’t say I didn’t tell you.

This process will have you installing it through your package manager. If you don’t want to do so, then there are an AppImage and Snap package that you can grab by going here. The way we will be installing Krita is a bit more ‘traditional’, so to speak.

Install Krita:

This article requires an open terminal. If you don’t know how to open the terminal, you can do so with your keyboard. Press CTRL + ALT + T and your default terminal should open up like magic.

The first thing we need to do is add the PPA. That’s a Personal Package Archive that adds itself to your regular repositories. A PPA is meant for software that’s not in the default repos. It’s meant for personal use – but we’ve bastardized the use to make it a way to easily install 3rd party software. That’s not important right now. What is important is that you then use this command:

When asked, you can finish adding the repository by pressing ENTER. That should then trigger apt, making it check for new software. If it doesn’t, you can run:

After that finishes, you can go right ahead and just install Krita from the terminal. (It’d also appear in your software manager, but we’re in the terminal so we might as well just finish in the terminal.)

Krita is a pretty large and complicated bit of software, so it’s a sizable download. Once downloaded and installed, you can bring out your inner Leonardo da Vinci! It’s really as simple as that, and nothing more.

Installing Krita this way will keep Krita up to date as the repository is updates. You do have a Flatpak and an AppImage available if either of those is your preference. If not, you can go right ahead and install it the old fashioned way.

Closure:

DING! There’s another article done and done. This one just was a passing fancy, pulled more or less randomly from my notes. It’s a great way to install Krita, for those looking to do so. It’s pretty painless and it’s a solid piece of software.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Let’s Install ‘gedit’ With All The Fixin’s In Ubuntu

This article is going to tell you how to install gedit along with a bunch of plugins. There are many text editors out there, but gedit is a popular choice. Many plugins exist to extend gedit, and this is an easy way to install a bunch at once.

Notes: This will only install the plugins in the default repositories. This article covers just Ubuntu, but will likely work with derivatives and even Debian.

gedit, the default editor for the Gnome desktop environment, is a part of the GNOME Core Applications and is available in almost every distro, at least every major distro. The gedit text editor doesn’t need a lot of additional dependencies, which helps make it useful on almost any desktop environment.

You can use gedit for anything – from programming, to writing markup for your website. You can use it just like you would any other plain text editor. There are many ways to extend it, to add functionality not included by default, and that is with plugins.

There are plugins to highlight syntax, to auto-complete words, to auto-close brackets, etc. You can make gedit do all sorts of things you’d not expect from a plain text editor. 

Disk space is absurdly cheap these days, so I don’t see any reason to not install as many plugins as I can, and no reason to not do it all at once. I may not use them all, but I’ll use many of them and I can just not enable those that I don’t want to use. I may have a reason to use them later on. You never know!

Well, this article will help you install gedit and all the plugins your system can find!

Install gedit With Plugins:

Like always, you need an open terminal and you can do that with your keyboard by pressing CTRL + ALT + T and enter the following:

What’s going on with that command? You can string together requests with apt, and this is installing gedit first, then a pack of common plugins, and then every other plugin that uses the ‘gedit-plugin-*’ format. It checks for all software with that naming pattern and installs them if they’re not already installed and have satisfied dependencies.

By the way, 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-gibberish or whatever. 

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

gedit preferences
Select plugins ’til you’re satisfied!

Anyhow, if you did this properly,  you will now have a bunch of plugins enabled. 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. You might as well do it all at once. 

Closure:

And there you have it. You now have gedit installed along with a bunch of gedit plugins. It’s really not all that difficult and there’s no real huge hit on performance or resources. Heck, it doesn’t even take all that long!

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Let’s Install Ubuntu Restricted Extras

If you’re using Ubuntu and want to use some patent/license encumbered features, such as playback for certain media formats, you need to install Ubuntu Restricted Extras. This is fairly normal and is done because the software licenses prevent Ubuntu from releasing the distro with that software. In some cases, you also will need to agree to different user-agreements. This is unlike most other software you will use on Linux, as software should never ask you to agree to anything.

Because of the license Ubuntu is released under, and according to their legal council, they just don’t include these sort of things by default and you’ll need to install them later, on your own. On the other hand, if you don’t need to use patent-encumbered files, then you don’t need to install the ‘ubuntu-restricted-extras’ metapackage at all.

This shouldn’t be a very long article, though I’ll break it up a bit. If you’re new to Ubuntu (or an official Ubuntu flavor) then you might as well install the restricted extras. If you are morally opposed to software patents, restrictive software licenses, or binary blobs then you may wish to avoid installing it.

About Ubuntu Restricted Extras:

When you install the ubuntu-restricted-extras, you’re actually installing a metapackage. It’s one package but installing it will install multiple packages, all relatively related by license restrictions. In this case, they’re packages that wouldn’t be installed by default and may help with your computing experience. They’re not all multimedia codecs, but most of them are.

So, what’s in the metapackage? As I said, it’s a package with multiple things in it that will also download along the way. These are the contents of ubuntu-restricted-extras:

gstreamer0.10-ffmpeg
gstreamer0.10-fluendo-mp3
gstreamer0.10-pitfdll
gstreamer0.10-plugins-bad
gstreamer0.10-plugins-ugly
gstreamer0.10-plugins-bad-multiverse
gstreamer0.10-plugins-ugly-multiverse
icedtea6-plugin
libavcodec-extra-52
libmp4v2-0
ttf-mscorefonts-installer
unrar

As you can see, it’s some fonts, a bunch of codecs (so that you can play patent-encumbered media files), software that lets you open .rar compressed files, and use Java applets in the browser. It’s some pretty handy stuff, but because it’s all non-free/non-FLOSS Ubuntu doesn’t include it by default.

Install Ubuntu Restricted Extras:

For starters, you won’t even find the ‘ubuntu-restricted-extras’ unless you enable the ‘multiverse’ repository. An easy way to do so is to open the terminal (press CTRL + ALT + T) and enter the following:

Next, you need to make sure that your system knows about the new software choices. It might do this automatically, after adding the repository above, but it can be manually done with this:

With that done, you install the Ubuntu Restricted Extras with:

That downloads a bunch of stuff and shows a screen that trips up a lot of newer users. There’s no obvious way to use a mouse and, indeed, you have to use your keyboard to agree to the user agreement. Like this:

accept the eula
Yes, you have to agree to proceed. It’s pretty easy, but it is also mandatory.

You can use your TAB (or arrows) key to make selections and use the ENTER button to submit your answers. The same on the next screen.

more eula
Use the tab or the arrow keys and the enter to agree. You got this!

That one will download some files with fonts in them, so that it can extract them to the right directories – just so that you can use them. These things are free as in beer, but not free as in libre.

Closure:

There it is, another article in the books and this one is about installing Ubuntu Restricted Extras. Most folks do this so that they can play encumbered media files, and I have no issues with doing so. If your morality doesn’t let you watch encumbered media, then there’s really no reason for you to care about any of this.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Find Out Which Kernel Version You’re Using

The Linux kernel‘s progress is marked by versioning, and this article tells you how to find out which kernel version you’re using. There are all sorts of ways to do this, but this article is going to just cover a few of them.

You might want to know which kernel version you’re using for when you ask for support. It may be that your hardware is best (or only) supported after or before a certain kernel. It may be that you want to know which kernel you’re using because you want to upgrade or downgrade the kernel.

For example, I recently didn’t want to switch to the new kernel. I saw that there was a kernel update, learned which kernel version I was now using, and promptly decided to return to an older LTS kernel. Yes, different kernel versions will have different support lengths. I opted for a more stable and consistent kernel as none of my hardware required a newer kernel.

There are any number of reasons why you’d want to know which kernel version you’re using. And, as stated, there are any number of ways to get that information. This article only covers some of them.

Find Out Which Kernel Version You’re Using:

This article will only show you how to determine which kernel version you’re using with the terminal. Of course, this means you need an open terminal. You can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

With your terminal open, you can try:

The information is also contained in the output of ‘hostnamectl’, so working with grep you’d have this command:

You can also use cat on/proc/version in a command that looks like:

If you have screenfetch or neofetch installed, the output contains the kernel version that you’re using. An output from those would look kinda like this:

neofetch in action
Neofetch in action, showing the kernel version number. See? It’s all over the place!

So, there are any number of ways to find which kernel version you’re using. There are surely other ways to find the kernel version, so feel free to leave a comment letting us know how you find your kernel version.

By the way, if you’re having problem with your current kernel, your distro probably has at least the previous kernel installed and you can use that as a fallback. Even if it automatically deletes old kernels, it usually leaves at least one older kernel as a way to recover should the proverbial poop hit the aerator.

Closure:

See? That wasn’t so painful! It’s another article that’s said and done. We’re getting closer to the halfway point, but I’m legitimately having fun getting my notes online. I admit, I pretty gleefully monitor the increasing (or sometimes consistent) traffic. It makes me happy to know my notes are helping.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.