On Tuesday, December 24, 2013 8:53:19 PM UTC+4, Ishfaque Jahan Rafee wrote: > Its been a pleasure discussing with you. I learnt a lot from it. @MarcWeber > thanks a lot for your cordial response. I use some of your plugins & love > them. > > Some of you, I think got me wrong. I am not a Vim hater. If I was, I wouldn't > have come here at all. Actually every new system/IDE/editor I use, the first > thing I do is, setup plugins so that it behave like Vim itself. But what I > want, is not using anything else at all. Why use something like Visual > Studio/Eclipse when I have Vim. But whether you agree or not, Vim's debugging > support is not up to the mark. I tried PyClewn, Setting it up is a complete > mess, let alone using it. > > About embedded shell support, why are you thinking its the feature of OS? Let > me try a bit, lets say you have Screen.vim installed & put :IPython! in > command line. It opens a split, just like now & supports every operation like > now, but doesn't use something like Tmux. And by supporting it natively it > will not need copying the code to window. As much as I have seen, > "Vim-R-Plugin" managed to do it best. I am quite sure he had to manage a lot > of workaround to do that using screen. But if it was supported natively, it > would have been much easier on his part. And some of the problems in this > option are pointed by MarcWeber.
Wondering who said about OS here? I said about plugins. We need some things that will make embedding shell easier (mostly async support). I do not see how one needs direct support for such a specific task in vim. And do not talk about screen (it supports tmux BTW, if you are talking about http://www.vim.org/scripts/script.php?script_id=2711). Check out Conque_Shell: it is almost full vt100 terminal embedded in the vim buffer. Not perfect: last time I remember using it it suffered from color-related problems (using colors sometimes) and lagging updating (this requires some asynchronous features or at least recent settimeout/setinterval patch). If you have non-regex-based API for syntax coloring and threading support you can do much more then if you have just embedded shell support. Once you have threading it is much easier to write asynchronous :make/:grep/:vimgrep (preferably in the vim core, not in some plugin), but they do not require any kind of embedded shell support. > But nevertheless, it was a good experience. > with regards, > Rafee -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
