ping Slack dev team
in [Slackware]
|
Prev: LewPitcher.ca tops Google Search!
Next: Xorg and Intel Integrated Graphics Chipset: low resolution
From: Lew Pitcher on 26 Nov 2009 16:02 Sylvain Robitaille <syl(a)alcor.concordia.ca> trolled: > > For day-to-day text editting, vim is hard to beat. You don't need to use > any of the "enhanced" features. In fact, vim has a mode of operation in > which it behaves like an ordinary vi. For emergency work, especially on > an unfamiliar system, a predictable "unenhanced" vi is far more desirable. And allow us to add that for "day-to-day" coding vim can't be beat. You can shove your typical IDEs where the sun don't shine. > That's a silly comparison. Vim is a far more powerful editor than > Nano (I'm not knocking Nano; it's less powerful by design). However, > I'd say the Slackware distribution agrees that Vim strays too far from > "real" vi (whose vi is the real one? UCB's? I don't believe the vi > on recent versions of Solaris is UCB's, so is it the "real" vi?) to > take it's place as the default editor. What I've found works best for > me is being aware that there are multiple vi-like editors out there, > so if I'm working with one that isn't behaving as I expect, it's fairly > easy for me to reconcile that, and fall back to "plain" editing commands. There is no reason to learn more than one editor. And vim (or gvim) fills all needs. But if, for some reason vim is not readily available then mc write, joe, and our long-time fave le, are the way to go. The only reason emacs is in a separate directory on the installation DVD is so that it does not have to be loaded at installation time. We are currently lobbying the Federal Government to make it legal to pulp the skulls, with a baseball bat, of all emacs "enthusiasts." LewPitcher(a)LewPitcher.ca -- Official Website -->> http://lewpitcher.ca/ Something to look at: -->> http://www.emusclemag.com/ Lonely in Brampton? -->> http://gaypros.meetup.com/cities/ca/on/brampton/ Peel HIV/AIDS Network -->> http://www.phan.ca/home.html
From: Joe on 26 Nov 2009 17:57 Sylvain Robitaille wrote on 11/26/09 12:31: > On Thu, 26 Nov 2009 12:06:29 -0800, Joe wrote: > >>> : charlotte[syl] ~; file Ethernet*.txt >>> Ethernet.txt: ASCII English text >>> Ethernet_dos.txt: ASCII English text, with CRLF line terminators >> But in that situation, you have to get the idea first that the line >> endings are the problem. We were troubleshooting the configuration, >> not the file it was in. > > Experience goes a long way, I think. If you're troubleshooting a > configuration, and you don't *see* anything that seems wrong, it's time > to look for anything wrong that you don't "see". file and od become > very valuable tools at that point. od was indeed what revealed the problem... > Also, in its default configuration, vim will identify the file as "DOS" > formatted, on the status line at the bottom, so you still could have > seen that before much of your time had been wasted: Not at that time, I guess (this was 10 years ago or so.) -Joe
From: Mike Jones on 26 Nov 2009 18:58 Responding to Joe: > Eef Hartman wrote on 11/26/09 04:37: > >> Lew Pitcher <lewpitcher(a)lewpitcher.ca> wrote: >>> If you want to think in a minimal, survivalist manner, you should >>> lookup the "ex" command. >> >> If you really wanna go minimal, look up "ed" (i.e. the stream editor, >> sed, is derived from THAT, nor from the EXtended editor ex). > > > sed is really powerful, with regex. I use it regularly in my scripts (I > have to write multiline documentation, though, to be able remember 6 > months later what the one-line regex does...) > > -Joe And never EVER allow the streams to get crossed... ;\ -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 26 Nov 2009 19:00 Rspndng t'ntbb: > Trim yer d Ok. -- sig
From: Mike Jones on 26 Nov 2009 19:04
Responding to Joe: > Mike Jones wrote on 11/26/09 08:46: > >> Responding to Sylvain Robitaille: >> >> [...] >>> For day-to-day text editting, vim is hard to beat. You don't need to >>> use any of the "enhanced" features. In fact, vim has a mode of >>> operation in which it behaves like an ordinary vi. For emergency >>> work, especially on an unfamiliar system, a predictable "unenhanced" >>> vi is far more desirable. >> >> >> If you've had your brain rewired, maybe. For us normal mortals with >> limited lifespans, its a "Raiders of the Lost Ark" puzzle game, and >> typically appears in the precise situation where we need a text editor >> that actually makes sense and works at least /something/ like all the >> other editors we've seen and\or used. This is NOT Vi(m). > > > Then you learn it. > When you have to fix somebody else's system, you don't have the time to > install another editor. You make do with what is there. And that always > is vi. > >> Crisis plus deadline plus Vi. Shudder! >:| > > That what you get. Live with it. > In a crisis, you don't have the time to install some other editor. So, > you better learn how to use vi, and be done with it. > > -Joe Or, alternatively, boot a different SNAFU disk, like "rescuecd". You missed the "free choice" lecture on the FOSS course, didn't you? ;) T'would have been nice to be able to just use the Slack disk, but... :\ -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs. |