Yesterday I put up a page for PyStump, a web-based announcements display system. I started PyStump as a pet project a couple years ago, but only in recent months have I put in the work to make it an actual usable piece of software. I thought it might be time to highlight it a little. (more…)
Joining a GNU/Linux machine to a Microsoft Active Directory has been possible for years, but it’s always been a bit of a science project that involved touching half-a-dozen obscure config files and usually resulted in me getting completely locked out of the machine. Various commercial packages such as Likewise and Centrify aimed to smooth out the process, but they weren’t universally accessible across distros, and often produced inconsistent results.
After upgrading a system to Debian 8, I noticed a new option for joining the domain, courtesy of the folks at RedHat: realmd. Realmd puports to make joining an Active Directory domain dead simple. How does it do?
As of tonight, WCGBrowser is available from the Arch User repository! Arch Linux users can install “wcgbrowser-git” using their favorite AUR front-end, or by downloading the PKGBUILD directly from the AUR.
At some point in my Linux-user career, I realized that my “perfect distro” setup (currently Arch with Awesome WM) – while great for me – was about as far removed from “average user” territory as you can get. So from time to time, I like to check out distributions that might be good to recommend to new users who want to find out what this Linux thing is all about.
With all the hubbub this month about Windows XP’s end-of-life, I thought I’d do a review of a relatively new distribution that has caught my eye as a possible contender for both users and hardware accustomed to the newly-legacied OS. (more…)
I’d like to announce the availability of a new program that I’ve been writing, Omega Hymnal. Omega Hymnal is a lyrics display program for informal worship settings.
In the previous article of this series, I covered a variety of “remix” distributions of Linux aimed at older computers, and posed the question “why not build our own”? In this article, we’ll look at doing exactly that.
Our goal will be to set up a basic desktop system, using only the necessary components, such that it will run reasonably well on a roughly ten-year-old computer.
When you mention Emacs on the Internet – be it on a blog, forum, mailing list, IRC channel, reddit thread, or tweet – certain responses must inevitably follow.
You were just sharing a bit of news, or asking a question about a feature, or plugging your new
webkit-buffers.el library that allows Emacs to really browse the web (somebody write this, please?); but it doesn’t matter. The same responses must always follow:
- Someone must say “Emacs is a great OS. It just needs a good text editor.”
- Someone must post a link to the XKCD comic about Emacs. You know, the “M-x butterflies” one. No, I’m not giving you a link to it.
- Some obviously lost and confused person who has been raised on Visual Studio / Eclipse / XCode or some other bloated IDE wonders incredulously that people still use “those old text editors” for serious development.
And then, of course, the Vi(m) users descend. I don’t know why. I have never, as an Emacs user/fan, butted into a discussion of Vi(m) stuff with my sanctified opinions about it, but like turkey vultures to a possum carcass, Vi(m) fanboys descend on every mention of Emacs with predictable regularity. Their comments vary:
- Some post lengthy walls of text about how they once tried Emacs and it gave them boils which were only cured by switching to Vim.
- Some just say pointless junk like “Vim is better” or “Vim FTW!”
- Some just type “Vim” or “Vi”. Nothing else, no explanation, just that. I don’t get this; it’s as if balance can only be achieved if every mention of Emacs is countered with a mention of Vim. Or maybe it’s some kind of insect-brained knee-jerk response: “I see word Emacs. Must type word ‘Vim'”
If anyone takes the bait (and someone usually does), flame wars ensue that span the gamut from Richard Stallman’s personal hygiene issues to RSI horror stories to “the year of the Linux desktop”.
Then some clever person comes along and posts a link to that rant about “ed”, at which point the thread is locked, comments are disabled, or everyone just agrees they’ve got better things to do.
Some time back, I wrote a little utility at work using CherryPy called EasyLIFT. The idea was to reduce the number of large files that were being sent as email attachments without having to resort to the tedium of setting up FTP accounts or a big complex CMS system.
EasyLIFT allowed users to login through their LDAP credentials, upload a file to a public-facing web server, and dispatch an email with the download location to recipients. The interface was minimal and quick to use, and was a real success at work.
Recently, I was looking for an open source project to keep my coding skills sharp, so I decided to do a clean re-implementation of the EasyLIFT idea using Flask instead of CherryPy. I dubbed the project LIFTS for “Large Internet File Transfer System”. No, we aren’t transferring “Large Internet Files”, or transferring Files over the “Large Internet”, but ILFTS is kind of goofy and not memorable, so there you have it.
The project is fairly young and not fully functional yet, but if you’re interested in pitching in or just checking it out, head on over to github and grab it from the repo: https://github.com/alandmoore/lifts.
More news to come, hopefully!
I’ve been coding Python in Emacs for years now, and for the most part it’s been a satisfactory experience. After experimenting with various python modes and utilities, I’ve had a pretty good environment that marries Emacs editing to syntax highlighting, real-time error highlighting, the ipython shell, linting tools like pylint and pep8, and various other goodies. But the one hole, the one sore spot in the whole works, was code completion. Something even idle can do out-of-the-box was simply beyond my ability to get functional in Emacs.
I’d tried just about every solution the internet could offer: PyMacs, company-mode, anything-mode, ipython completion, standard autocomplete-mode. Everything I tried either gave unacceptable results (like autocomplete-mode, which just scans the current buffer for completion information), or just flat-out didn’t work no matter how many tutorials I followed.
Here lately I’ve been trying to work a lot more on my Pythoning, so I decided to see if the state of the art has caught up with this need. Echo base, I’ve found it. Repeat: I’ve found it.
Emacs’ window-splitting functionality is an ergonomic way to view multiple files at once without having to deal with shuffling around floating windows or clicking between tabs. Anyone who does much with Emacs probably knows already that they can use C-x 2 or C-x 3 to split the window vertically or horizontally.
What always bothered me about this feature was that the newly-created window defaulted to the current buffer, which in layspeak means you had the same file or content open in both your new window and the old. The was almost (but not quite) never the behavior I wanted, since usually you split the window to have multiple buffers on screen at once. Typically, I would do this right after opening a new file or buffer to compare with whatever I already had open, so that I would have the old buffer in one window and the new buffer in another.
This is where having an extensible editor rocks; because in Emacs, if you get tired enough of a behavior, you start hacking elisp and fix it…