Tesla seem to be out to sue everyone who doesn't give a *positive* review of their car. I wouldn't even consider reviewing it - since I might not find it perfect, and if I published anything other than a glowing review, I could find myself facing a suit.
Choosing to name yourself something that doesn't use modern characters (in both cases) is your own fault.
But what if you didn't choose your own name? How is it 'your own fault'?
In many cultures, people don't chose their own names. It's not uncommon, for instance, for a child's name (or part thereof) to be chosen by the parents/shamen/elder/etc. Some people call these "fore-" or "Christian" names, but as we live in an ever-shrinking world, we have realised that there are cultures in which neither of these is an accurate description, so the term "given name" has become commonplace. "Given" is the clue here - it's the namer that's at fault, not the named.
Similarly, there are many cultures where part (or all) of a name is a 'family/clan/tribe/province/etc' name, which is passed by generation to generation. If your family has been around for a long time, then your family name is also likely to be old. As GP mentions, there are archaic characters from some ideographic scripts which do not have Unicode mappings. So again, it's not the named that's at fault. In this case, if there is 'fault' to be assigned (and I don't believe there is), then it's someone many generations in the past.
You have that the wrong way around: Emacs is very much alive and kicking ass.
vi, on the other hand is pretty much dead. Killed not so much by Emacs, as by its own clones (vim, nvi et. al.)
I honestly can't remember the last time I saw a machine that actually had vi installed. On the other hand, I see a lot of boxes where the command vi starts a vim session.
It does take a while - around two million microseconds on my laptop.
but once it's running, you don't close it for ages.
Typically, the only reason I close Emacs is because something else requires me to end my login session; I've had single sessions run for over a year in the past.
You run a bash shell *inside* Emacs (M-x shell) - I do this all the time (and by all the time, I mean literally 24/7)
It's bash on steroids - all the power of bash, with the added bonus that Emacs sees your bash session as "just another buffer", so you can search it, copy and paste from it, save it to disk, etc, etc, etc. - anything you can do with an 'ordinary' editing buffer. Plus you get all of the window/frame management that comes with Emacs (screen and tmux are great - but neither of them can match Emacs in that respect).
Slashdot Mirror
Tesla seem to be out to sue everyone who doesn't give a *positive* review of their car. I wouldn't even consider reviewing it - since I might not find it perfect, and if I published anything other than a glowing review, I could find myself facing a suit.
That should shut them up.
Sadly, they're religious zealots, so you can't shut them up.
Which is rather a pity - just think how much less CO2 we'd have to deal with if they'd all just stop exhaling.
I do. It's a lot more fun than whining on /. all day.
syncing at 18.2Mbs down and 1.3Mbs up, via Be Unlimited
Make the most of it. Now that Murdoch's got his sticky paws on Be, I expect things to go downhill rather rapidly...
Choosing to name yourself something that doesn't use modern characters (in both cases) is your own fault.
But what if you didn't choose your own name? How is it 'your own fault'?
In many cultures, people don't chose their own names. It's not uncommon, for instance, for a child's name (or part thereof) to be chosen by the parents/shamen/elder/etc. Some people call these "fore-" or "Christian" names, but as we live in an ever-shrinking world, we have realised that there are cultures in which neither of these is an accurate description, so the term "given name" has become commonplace. "Given" is the clue here - it's the namer that's at fault, not the named.
Similarly, there are many cultures where part (or all) of a name is a 'family/clan/tribe/province/etc' name, which is passed by generation to generation. If your family has been around for a long time, then your family name is also likely to be old. As GP mentions, there are archaic characters from some ideographic scripts which do not have Unicode mappings. So again, it's not the named that's at fault. In this case, if there is 'fault' to be assigned (and I don't believe there is), then it's someone many generations in the past.
Ahem. Missed the trailing ;).
You know what they say about little things? s/little/nano/
Do, or do not. There is no try.
In fairness, MC does have an "edit" function (on F4, iirc) - but I'd be hard pressed to keep a straight face while calling it an "editor".
What's wrong with cat - >filename?
You have that the wrong way around: Emacs is very much alive and kicking ass.
vi, on the other hand is pretty much dead. Killed not so much by Emacs, as by its own clones (vim, nvi et. al.)
I honestly can't remember the last time I saw a machine that actually had vi installed. On the other hand, I see a lot of boxes where the command vi starts a vim session.
I will admit to using Aquamacs on OS-X.
+1
And yes, for you vi girls, Emacs does have emulation modes. *sigh*
(defalias 'lobotomize-my-editor 'viper-mode)
We accept you - one of us!
(Damn you /. - where's "+1 Freaks reference" when I need it :-)
They're more like "Support Groups".
Shocking, but I have no need to google org-mode
Does emacs have a built in web browser?
You mean w3? (Although it's probably fair to say that it's somewhat limited when compared with the likes fo Chrome/Firefox/etc)
Have an RSS reader as well
Yep, Gnus RSS handles this.
Once all this is there, one can browse /. from a good ole vt100 terminal
In a pinch, you can curl http://slashdot.org/ | less. I assume this is how Vim users do it ;-)
Newsflash - most shells have had vi and emacs style line editing commands built in for decades.
Only for the input line - you can't use them on the scrollback.
Emacs allows you to use *all* of your editing commands on the *entire* of your bash history (both your input and the output)
Possible because forking is commonly followed by spawning.
Emacs takes a long time to start up
It does take a while - around two million microseconds on my laptop.
but once it's running, you don't close it for ages.
Typically, the only reason I close Emacs is because something else requires me to end my login session; I've had single sessions run for over a year in the past.
You run a bash shell *inside* Emacs (M-x shell) - I do this all the time (and by all the time, I mean literally 24/7)
It's bash on steroids - all the power of bash, with the added bonus that Emacs sees your bash session as "just another buffer", so you can search it, copy and paste from it, save it to disk, etc, etc, etc. - anything you can do with an 'ordinary' editing buffer. Plus you get all of the window/frame management that comes with Emacs (screen and tmux are great - but neither of them can match Emacs in that respect).
Control u 20 Control f
Or, with fewer keystrokes:
C-2 C-0 C-f
(Press control once, and then hold if while you hit 2,0,f)
That matches vi for number of characters transmitted (3), and you're already in insert mode when you get there
It's not really object oriented until it can do true multiple inheritance
... and with that, Java weenies all over the world are crying into their milk.
+1
re.match('^[a-z]',inputline)
Yes, I see how much overhead there is for 'building and using a regex object'.
My Perl solution returned results twice as fast (averaging 22ms/query) as any other in the class, most of which were C or C++
That doesn't mean Perl is fast - it means your classmates were idiots.
And it took me half the time to write.
See above.
You haven't addressed the thrust of my post which was "how does Objective-C not introduce new notations".
When you do a malloc in C you are getting memory assigned to you differently than it is with a C++ new
When you do a malloc in C you are getting memory assigned to you differently than it is with an Objective-C new.