Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: I usually debug via...

by jonadab (Parson)
on Feb 20, 2005 at 18:28 UTC ( #432890=note: print w/ replies, xml ) Need Help??


in reply to Re^2: I usually debug via...
in thread I usually debug via...

then it is a thing that Vim can not do, but emacsers easily do; am I right?

There are a *lot* of such things.

vim users generally attempt to construe vim's smaller feature set *as* a feature, proclaiming that Emacs is "bloated" and "fat" and "slow", an example of "creeping featurism", mocking it for including the proverbial kitchen sink, which, in their view, is completely unnecessary. Why, they want to know, is it necessary for a text editor to come with a module for interfacing with ISO networked coffee makers? (Answer: because it's possible.) But there is not really any question as to which editor is the more featureful; if featurefulness is your standard for quality, then Emacs reigns completely supreme. Emacs has text editing features I miss in OpenOffice, navigation features I miss in Firefox, and customizeability out the royal wazootie -- among other things.

The difference is one of viewpoint. The vim users just want a text editor, pretty much. Emacs users aren't satisfied with that: they want everything. vim users see some of Emacs' more excessive features as "unnecessary" bloat. To the Emacs user, however, features are desirable even if not strictly necessary. If every feature had to be justified as strictly necessary, the Emacs user reasons, why do we even need computers, when typewriters were working just fine? The vim user doesn't see things this way; he views the ability to edit his stuff without retyping it as necessary, but he views the ability to transparently edit remote files (accessed via ssh perhaps) in the same editor as local files as unnecessary; for that he would just shell out, scp the file, edit it, and scp the changes back. (Which is basically what tramp does, behind the scenes; tramp is the Emacs thingydoo for editing remote files as if they were local.) The vim user does not consider decoding morse code to be something he would do in his text editor -- why would he? The Emacs user, OTOH, knows that, of *course* Emacs would have the ability to do that. (The command is called unmorse-region. Assuming you don't have it bound to a key, you'd access it via M-x.) To the vim user, playing Zork in a text editor buffer is a fundamentally preposterous notion -- but Emacs users have malyon.


"In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings."  — Pratico & Van Pelt, BBHG, p68


Comment on Re: I usually debug via...
Re^2: I usually debug via...
by Aristotle (Chancellor) on Feb 20, 2005 at 18:39 UTC

    You are behind the times. Vim has been able to embed Perl, Python and Ruby for a while. There's a Vim plugin using the Perl interpreter to turn Vim into an IRC client, f.ex. One of my pet projects uses the Perl interpreter and Gtk2 to add some minor IDE-ish features to gvim/gtk+.

    Makeshifts last the longest.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://432890]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (11)
As of 2014-10-23 20:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (128 votes), past polls