Something that that Linux desktop isn't lacking is tools for working with plain text. That's especially true for text editors. I should know — I've tried more than a few in my time.
A while back, I was having a spot of bother with an editor called Gedit. That bother had to do with the editor's search function — I don't recall the details, to be honest. To get around that problem, I turned to another editor called FeatherPad.
I found FeatherPad to be a more-than-adequate editor, one with several useful functions. Even though I looked at it briefly in another post, I've been meaning to take a closer look at FeatherPad. So why don't we do that now?
When you think of the word wiki, examples like MediaWiki or DokuWiki probably come to mind. They're open source, useful, powerful, and flexible. They can be great tools for collaborating, working on your own, or just organizing the piles of information in your life.
On the other hand, those wikis are also big. They need quite a bit of additional digital plumbing to run. For many of us, this is overkill, especially if we only want to use wikis on our desktops.
If you want to get that wiki feeling on your desktop without dealing with all of that plumbing, you easily can. There are a number of solid lightweight wikis that can help you organize your information, keep track of your task, manage your notes, and more.
Let's take a look at three lightweight, desktop wikis.
As you may or may not know, I publish an email letter called Weekly Musings. To celebrate the letter's first year, I recently decided to collect the first 52 essays into an ebook.
With the last few ebooks I've published (at least ones in EPUB format), I've written them in a desktop application called Sigil. This time 'round, things were a bit different.
The 52 essays that I wanted to collect in the book were individual files formatted with Markdown. Converting them to HTML (which is file format in which Sigil stores chapter files) and importing them into Sigil would have been a bit of a chore. Instead, I turned to Pandoc to quickly do the deed.
Pandoc, if you're not familiar with it, is something of a Swiss Army Knife for converting between markup languages. Pandoc can also create EPUB files.
When I mention that I contribute to free/open source projects, and that I do it for free, the question that I invariably hear is If you're doing it for free, then what do you get out of it?
That's the wrong question. Why? Because I've already gotten something from the projects that I support. That might be the software I'm using, a community I can turn to for help or take part in, or ideas that intrigue me.
Admittedly, I don't contribute as much as I want to or think I should. But I try to do as much as I can, not matter how little that actually is.
Just to spare you the pain, I won't go into my usual spiel about how useful the command line is. It is, even for the non techie.
In the terminal window, there are so many commands and so little time to learn them all. And there are so many little tips and tricks that can make life (or even just a visit) to the command line a bit easier.
Let's take a look at a few of my favourite tips. If you've been using the command line for any length of time, these tips will probably be old hat to you. But if you're still learning about the Linux command line, then you might find these tips useful.
If you've been reading my site The Plain Text Project, you know that I'm a heavy user of Markdown. I do a lot of writing with it. In fact, just about all of my writing is done with a text editor and Markdown. Mainly articles and blog posts, but also book chapters and editions of my weekly letter.
To be honest, I'm not one to use a dedicated Markdown editor. While I use a text editor called Emacs for my writing, I've also tried several dedicated Markdown editors. Most left me feeling cold. A few I found useful and worth taking a second or third look at.
One of those editors is ReText. While it's not the prettiest editor out there, ReText is a solid and capable tool with some useful features.