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.
(Note: This post was first published, in a slightly different form, at Opensource.com and appears here via a Creative Commons license.)
There are dozens, if not more, tools out there that can help you manage your ever-expanding task list. If you want to manage your tasks like a techie, or just feel like going back to basics, the best way to do that is to turn to the command line.
With the software that's available, there's no reason why you can't effectively manage your tasks from the command line. You don't need to worry about sacrificing features and functions, either. The three task management tools I look at in this post have something for everyone.
(Note: This post is based on a presentation I gave at the Opensource.com Lightning Talks on October 22, 2014)
There are many people out there who are interested in, and even eager to use, open source. Not just for one or two tasks, but for their entire computing experience. But, for a variety of reasons, they aren’t able or willing to make the leap from the closed, proprietary world to a more free and open one.
Even the more resolute ones hesitate. Why? A big part of it is change, which no one really likes. And they might not know a lot about open source.
It doesn’t have to be that way.
I’d like to share a few things I’ve learned that can help you ease people into open source.
Chances are, have a pile of ebooks in any number of formats — like PDF, EPUB, and even .mobi — on your computer. Chances are those ebooks are scattered across a directory or four. Which means finding an ebook at any given time can be a bit of a chore.
One way around that is to do some housekeeping. You can manually move your ebooks around into dedicated set of folders or subfolders. Instead of doing that, why not use calibre to manage your ebooks?
For most people (especially non-techies), the act of writing means tapping out words using LibreOffice Writer or another GUI word processing application. But there are many other options available to help anyone communicate their message in writing, especially for the growing number of writers embracing plain text.
There's also room in a GUI writer's world for command line tools that can help them write, check their writing, and more — regardless of whether they're banging out an article, blog post, or story; writing a README; or prepping technical documentation.
Here's a look at some command-line tools that any writer will find useful.
When I tell people I have 10 thumbs when it comes to anything technical, they don't believe me. In fact, they point to all the articles and blog posts I've written about using the command line to try to refute my claim.
I'm no expert or wizard with the command line. Far from that. And I'm not one of those people who believes that you absolutely must be fluent in command line/shell/terminal (or whatever you want to call it) to be able to use Linux. I know any number of folks who happily and productively use Linux. Not one of them have ever cracked open a terminal window.
So why do I write about the command line, especially in posts and articles aimed at those without many (or any) technical skills? Aimed at people like me? Two reasons.
Second, you don't need to be an expert to use the command line. You don't need to know how to script. You don't need to remember ever option for every tool that you use. You only need to remember the options that you need to remember, nothing more.
Yes, anyone can use the command line.
That said, being able to use the command line isn't a requirement for using Linux. But using it can expand what you can do with Linux.
I was surprised and saddened when I read this post earlier today. Yes, the venerable Linux Journal has ceased publication. For good this time.
Back in 2017, the magazine announced that it could no longer continue publishing. Shortly afterwards, the Linux Journal got a second lease on life. Sadly, the kind of resurrection doesn't seem to be in the cards this time 'round.
I've been reading the Linux Journal on and off since the 1990s. Even for someone with 10 thumbs when it comes to anything technical, the magazine was a great source of information about Linux and free/open source software.
And while it may sound a bit lame, one of my goals as a writer was to have something published in the Linux Journal. I have to balance the minor disappointment of not achieving a professional goal with the cold reality that the magazine's staff, a group of FOSS advocates who passionately kept the publication alive, are now out of work. I'm hoping they can bounce back.
A tip of the hat to the staff and writers, past and present, of the Linux Journal. You did fine work, and the forum that you provided for both writers and readers will be missed.
Over the years, I’ve heard (and I keep hearing) that you can’t do this or you can't do that or you can't do the other thing using Linux or using open source software. And guess what? Most of those things I’ll never do or rarely, if ever, need to do. As I’ve written and said in the past, I really don’t care what other people think or what they use their computers and devices for. None of that has any bearing on what I need and what to do.