Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

Re: Re: Environments extended with embeded Perl: are they for real?

by stefp (Vicar)
on Mar 24, 2003 at 00:15 UTC ( #245343=note: print w/replies, xml ) Need Help??

in reply to Re: Environments extended with embeded Perl: are they for real? (vim+debugger)
in thread Environments extended with embeded Perl: are they for real?

About IDEs

First , an IDE does not to include a GUI contrary to Agide (which seems interesting anyway. thx for the ptr).

Second, it takes so long to learn an environment that you want it to do a lot with it. A text editor that cannot act as an IDE is not of much interest to me. Too bad, vim fall very short of that. Also "real IDEs" have a way to force things on you (define file for projects and so on) so sometimes it is interesting to have a best that is half-way between a full-fledged IDE and an text editor.

About the vim pager

Sometimes you get to display stuff that you can't scroll back to when you have gone thru. I don't have a interesting example out of hand. Anyway, say, you want to list all the options:
:se all
There is more than one pageful so you get a pager. But you can't scroll back or make a editable buffer out of what you got. At least, the new vim user I am don't know how to do it.

-- stefp

  • Comment on Re: Re: Environments extended with embeded Perl: are they for real?
  • Download Code

Replies are listed 'Best First'.
Re^3: Environments extended with embeded Perl: are they for real? (:redir)
by Aristotle (Chancellor) on Mar 24, 2003 at 00:50 UTC

    Ah, that pager - yeah, it does suck. You can redirect messages to a register or file though it is cumbersome. See help :redir. vi does indeed take a long time to get into and find your way around, but I find that once you've gotten into its way of getting things done, you can work with very little distraction. When in doubt, reach for :help - there's copious documentation.

    Personally, I think an editor is just an editor - period. Of course, while I read my mail with mutt, I do edit it with vim.

    $ grep vim .muttrc
    set editor="vim -c 'set textwidth=60 | normal }j'"

    Same goes for my Usenet perusal with slrn. It's also the editor midnight commander is set up to use (on the rare occasion I reach for that). And so on. Tools should do one job, not attempt to be everything under the sun. Where the tasks overlap (like needing an editor when dealing with mails), the tools should let the user tell them what other tools they want to use instead of providing their own rendition of it. I'm still peeved that Mozilla provides no way to use vim or another editor for text input areas on webpages - pasting to gvim and back just doesn't cut it.

    As always, though, different strokes for different people. I do think that most folks don't give vi a fair enough shot, but if they truly don't like it, far be it from me to force anything onto anyone.

    Makeshifts last the longest.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (3)
As of 2022-08-07 23:02 GMT
Find Nodes?
    Voting Booth?

    No recent polls found