Earlier quoted context omitted.
> It sounds like your most of your complaints are with the .Net platform, library layout, and the compiler. Only about half-so. The first paragraph was all about VS exclusively, minus "too many warnings". But due to the issues in .NET, you essentially must use Visual Studio, which makes it at least bearable due to intellisense. But I crash VS fairly often, it eats up a half-gig or more of memory fairly often, it thra…
FWIW I'm the author of the Zeus programmer's editor and it can import VS solutions files and once imported you can build and compile all from inside the editor. Zeus also does a limited amount of intellisensing, but naturally the intellisensing is nowhere near good as that found in VS. But the code navigation is not too back. Zeus also has full MSDN integration and it can actually do context sensitive queries of the…
One with Vim
91–100 of 129 posts
Re: One with Vim
#92Earlier quoted context omitted.
It sounds like your most of your complaints are with the .Net platform, library layout, and the compiler. For what it's worth, I've always found Microsoft APIs to vary profoundly in terms of usability and (especially) documentation. And MSDN hasn't been directly useful to me since the VS 6.0 days. Can you give me an example of an editor with better text column editing? I'm not entirely sure what you mean.
> It sounds like your most of your complaints are with the .Net platform, library layout, and the compiler. Only about half-so. The first paragraph was all about VS exclusively, minus "too many warnings". But due to the issues in .NET, you essentially must use Visual Studio, which makes it at least bearable due to intellisense. But I crash VS fairly often, it eats up a half-gig or more of memory fairly often, it thra…
I recommend giving 2010 a go. If I recall correctly, 2010 was the version where they drastically reworked Intellisense. In previous versions, even my moderately-sized projects would break Intellisense upon reaching x lines of code. I don't think the multi-monitor support is any better, though. You can drag documents to their own window on any screen, but I can't seem to group them into sets of tabs.
Re: One with Vim
#93Vim is my primary editor but I think the only really good part of vim is the keyboard navigation. The rest could be much better. For example, to this day I haven't figured out an easy, built-in way to copy from one vim window to another. I'd love to have some features of other editors have but the key bindings always hold me back.
You're not really supposed to run vim in multiple windows. Use your system pasteboard if you need to copy between them. There's probably some plugin that would make it work with yank registers though.
Also, the + register has similar intended uses.
Re: One with Vim
#94selfish question here: Does anybody know how to setup vim so that :! recognises aliases? something like... set shellcmdflag=-O\ expand_aliases\ -c
Not sure why it wouldn't for you.
Re: One with Vim
#95Earlier quoted context omitted.
> It sounds like your most of your complaints are with the .Net platform, library layout, and the compiler. Only about half-so. The first paragraph was all about VS exclusively, minus "too many warnings". But due to the issues in .NET, you essentially must use Visual Studio, which makes it at least bearable due to intellisense. But I crash VS fairly often, it eats up a half-gig or more of memory fairly often, it thra…
That's all very interesting. I'm primarily a desktop C++ developer, so I don't run into the headaches of things like VS's database connectivity. I recommend giving 2010 a go. If I recall correctly, 2010 was the version where they drastically reworked Intellisense. In previous versions, even my moderately-sized projects would break Intellisense upon reaching x lines of code. I don't think the multi-monitor support is…
Oddly, Intellisense is generally keeping up with me, despite the site being at least a few hundred thousand lines of code (light on the abstraction, though, so it's mostly flat .NET code. Probably not too taxing on intellisense). There are times I just break out Notepad++ and finish up stuff VS was breaking, but it generally catches up any time I build the relevant projects.
And I should be clearer, because it's so weird: the designer-view was actually instantiating the entire window control, as it's init contained the database connecting code, and firing events on the combo box controls that queried the database. At no point was the database actually connected to VS, which you can do; and I'll never even consider trying it, after seeing that happen.
Re: One with Vim
#96"been around since 1991"?! while that's probably correct for vim proper, that ignores the much longer history of vi...
you are absolutely right - fixing this now. Vi has been around since the 70s, but I used the date for vim on the post - which was dumb of me.
Re: One with Vim
#97Re: One with Vim
#98Earlier quoted context omitted.
Visual Studio? Sure, as long as you're only going to be coding on Windows . I'm curious, does anyone use Visual Studio for non-code editing? For example, I'm typing this in Vim right now. I use Vim for lots of meant-for-human-readers text.
> as long as you're only going to be coding on Windows. In the past, I've used VS for editing PHP, which I then deployed to the server using a keyboard shortcut. I understand what you're saying, but I want to point out that VS can be used as an editor even when the target platform isn't MS.
What I'm curious about, is it so good an editor that people commonly use it for general text editing for non-code text? I know Vim and Emacs gets used like that a lot, maybe Notepad too.
Re: One with Vim
#99Am I foolish for not believing the vi/vim hype? I understand that it's been around for as long as rocks, and that it's quite handy since it's available everywhere. I use it daily, in fact, but rarely for more than basic editing. I'll just come out and say it: my favorite editor is Visual Studio. Sure, it's slow to load and rather fat now, but I'm talking solely about the editing functionality. With vim, I have to cli…
Re: One with Vim
#100Earlier quoted context omitted.
> It sounds like your most of your complaints are with the .Net platform, library layout, and the compiler. Only about half-so. The first paragraph was all about VS exclusively, minus "too many warnings". But due to the issues in .NET, you essentially must use Visual Studio, which makes it at least bearable due to intellisense. But I crash VS fairly often, it eats up a half-gig or more of memory fairly often, it thra…
That's all very interesting. I'm primarily a desktop C++ developer, so I don't run into the headaches of things like VS's database connectivity. I recommend giving 2010 a go. If I recall correctly, 2010 was the version where they drastically reworked Intellisense. In previous versions, even my moderately-sized projects would break Intellisense upon reaching x lines of code. I don't think the multi-monitor support is…
Also, VS10's WPF-based UI is a nightmare, but that's another discussion...