@Just this guy, you know: That's what I thought when I saw "progs" too.
Considering that I'm primarily a Linux user, it would be hard to list every free app I use and am thankful for; it would be easier to just look at a package list for Debian or Ubuntu. Basically, I just want to thank everyone developing open source projects. I like seeing open source projects thrive, even the ones I…
@soulfinger: I'll bite, since I was helping a family member with iTunes recently and was left with a bad taste in my mouth over it.
@TheWhisper: I don't know whether I'm happy or sad
@robertwan: You should give geany a try, it's a Gtk app with the same kind of coding-oriented features as Kate (e.g. function listings and tracking) along with some things Kate actually lacks. It's definitely worth a try if you do any kind of coding at all. If not for KDE's IOslaves, I'd probably use it more than…
@jackalopette: Don't take this wrong, but part of the problem here sounds like your own usage habits, so you'll want to either find a solution that works around that or modify your own usage slightly. If they're able to do dangerous things on your system then you haven't been treating it as a multi-user system and…
@MrCobaltBlue: It's hard to have religious zeal for a text editor, in my opinion; I use different tools for different needs (or moods). I use pico or nano for quick editing, vi (or LyX) for situations where I want to focus on the content, and kate (KDE's code-oriented editor) for HTML and coding, with an honourable…
@Avedis: Thanks for mentioning this, I never knew you could set up vi-style editing in bash. I'll be using it, and probably suggesting it to anyone that's interested in learning vi.
@Whitson Gordon: Same here - I don't think anyone's immune - though I try to be open about things.
@Whitson Gordon: If I remember correctly, Microsoft vs. Apple is basically pragmatism vs. aesthetic in regard to font rendering. Microsoft aims for screen readability at the cost of appearance, while Apple's approach to font rendering focuses on being print-correct. (Note: not sure if this is still accurate, but…
@Whitson Gordon: Yeah, that's something I wasn't aware you could do, and one of the advantages of keeping config files easily editable: you can put a GUI on 90% of the features, but there will be that obscure 10% that someone, somewhere will end up needing.
@Whitson Gordon: The niche tips are often the best, since they're the things that can be the hardest to find on your own.
@Whitson Gordon: Right next to anti-aliasing is a "configure..." button that has extra settings related to AA. Hinting, sub-pixel rendering, and font size limits.
As a long-time Linux user, this is probably blasphemy for me to admit but you can also change the hinting without mucking about with config files.
@SpudDude: Haha, works for me! ;)
@Rob Oakes: Thanks for the dock idea, I might have to try it. The left/right panes thing sounds a lot like what I do with screen (for vim or other console programs) and how I use KDE's vertical maximise.
@Vogie: I like your shorter version of the article quote better than the actual quote. :D
@Rob Oakes: I know what you mean about the width. Widescreen monitors suck for putting writing programs into fullscreen, since you either waste a ton of space or you end up with something uncomfortable to work with. Portrait mode would help a lot but it's not always an option. :\
@SpudDude: Yeah, that sums it up pretty well for me, too. I'd do it if I actually used Facebook, but I don't and I don't plan to start. ;)