I use GVim myself, with syntastic for checking for errors when I hit save.

On Fri, Sep 13, 2013 at 02:35:07PM -0700, Walter Bright wrote:
> On 9/13/2013 1:58 PM, H. S. Teoh wrote:
> >Syntax highlighting hurts my eyes. I've been using vim in black-on-white for more than a decade now. (Well, more accurately, black on an almost fully saturated off-white, but that's irrelevant.)
> 
> I tend to agree. I think syntax highlighting looks better if it's a subtle color change, not a glaring one. Unfortunately, in text mode, color palette is very limited.

Xterm has a 256-color mode that can be used for subtler highlighting, I suppose. But still, syntax highlighting to me is merely something peripheral, and I'm a minimalist. Besides, 256-color mode isn't always supported when you're working over ssh.

Not to mention, syntax highlighting falls down upon encountering q{} blocks.  (It *can* be made to highlight those as well, I suppose, but it leads to the awkward situation where you can't tell whether that's code or a string literal.)


T

-- 
If you look at a thing nine hundred and ninety-nine times, you are perfectly safe; if you look at it the thousandth time, you are in frightful danger of seeing it for the first time. -- G. K. Chesterton

On Friday, 13 September 2013 at 19:48:18 UTC, Namespace wrote:
> Just out of interest.
>
> I use Sublime 2, Notepad++ and as IDE currently Mono-D. But I will try this evening VisualD.

Mostly stock vim (NerdTree is only absolutely mandatory plugin) + grep + gdb

Sometimes I poke Mono-D but more out of curiosity than real necessity.

On Fri, 13 Sep 2013 14:29:02 -0700, H. S. Teoh wrote:

> On Fri, Sep 13, 2013 at 11:00:49PM +0200, monarch_dodra wrote:
> vim (and all vi-derived editors) is... shall we say, a unique beast all
> its own. It requires a different *mode* of thinking (har har) than your
> usual GUI-based editors.  In most other editors, you think in terms of
> "move cursor here, type some characters, move cursor there, hit delete a
> few times", etc..  But in vi(m), you operate on a different level of
> abstraction. Rather than thinking in terms of individual cursor
> movements and single-character operations, you're thinking in terms of
> abstract editing operations: "go to the word that begins with 'vo',
> replace the word with 'int', go back to the start of the paragraph, open
> a new line of text above it", etc..

I've introduced a few young developers to Vim and the major hole that they tend to fall into is printing out a list of vim "keyboard shortcuts", because that's how other editors work: you memorize a bunch of arbitrary key combinations.  So the thing that I emphasize is learning Vim's *language*.  Say you already know that "d" means delete--whenever you learn a new noun such as "e" (end of word), you can combine the two: "de" (delete to end of the word).  The same applies when you learn a new verb, e.g. "y" for "yank" (copy): "ye" copies from the cursor to the end of the word.  Then mix it up with adjectives like counts ("d5e", delete to five word endings) or "i" and "a" (inside and around, "di{" for "delete inside this block").

On 9/13/13, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
> Not to mention, syntax highlighting falls down upon encountering q{} blocks.

Works on Scite.

>  (It *can* be made to highlight those as well, I suppose, but it
> leads to the awkward situation where you can't tell whether that's code
> or a string literal.)

Well that's kind of the point of q{} IMO, to make it appear like code. Otherwise you can use backticks or r"". E.g.:

http://imgur.com/UGUuUGU

(and lol at the generated imgur name)

On Fri, Sep 13, 2013 at 05:42:18PM -0400, Jonathan M Davis wrote:
> On Friday, September 13, 2013 21:48:15 Namespace wrote:
> > Just out of interest.
> > 
> > I use Sublime 2, Notepad++ and as IDE currently Mono-D. But I will try this evening VisualD.
> 
> I use gvim regardless of the language that I'm writing in. I even use it for word processing, because if I have to write a document that requires that, I use LaTex.
[...]

+1.

I use vim (bare text mode, no GUI, so no gvim for me) for literally *everything*. Everything from system config files to coding to LaTeX for word-processing to scripted graphics processing (thanks to imagemagick) to povray scene files, there's almost nothing in my world that can't be accomplished by vim. :)

Sometimes I wonder how the GUI-encumbered people get any work done at all, what with needing to constantly switch their hands between the keyboard and the rodent, wait for a 600MB application to load up 200MB of eye-candy and paint the screen with 50 toolbar controls, 45 of which that they never actually use, click through endless layers of nested menus just to perform a single operation, etc.. ;-)

(OK, OK, so I'm a fossilized relic from the last ice age of '75, I'll stop the GUI-bashing now. :-P  You may carry on.)


T

-- 
Skill without imagination is craftsmanship and gives us many useful objects such as wickerwork picnic baskets.  Imagination without skill gives us modern art. -- Tom Stoppard

On Friday, 13 September 2013 at 19:48:18 UTC, Namespace wrote:
> Just out of interest.
>
> I use Sublime 2, Notepad++ and as IDE currently Mono-D. But I will try this evening VisualD.

Vim, VisualD and some Mono-D (when on GNU/Linux).

When using Mono-D, I have a shortcut to open the file at the current location in vim as MonoDevelop/Xamarin Studio sucks at vi emulation.

For Visual Studio, ViEmu works very well, but it's not free. Worth the $100 though.

Vim for all smaller things, and otherwise when I need it.

On Fri, Sep 13, 2013 at 11:50:53PM +0200, Andrej Mitrovic wrote:
> On 9/13/13, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
> > Not to mention, syntax highlighting falls down upon encountering q{} blocks.
> 
> Works on Scite.
> 
> >  (It *can* be made to highlight those as well, I suppose, but it
> > leads to the awkward situation where you can't tell whether that's code
> > or a string literal.)
> 
> Well that's kind of the point of q{} IMO, to make it appear like code. Otherwise you can use backticks or r"". E.g.:

True, you have a point there. :)


> http://imgur.com/UGUuUGU
> 
> (and lol at the generated imgur name)

Heh. Reminds of "point-and-grunt". ;-)


T

-- 
The two rules of success: 1. Don't tell everything you know. -- YHL

On Friday, September 13, 2013 14:58:48 H. S. Teoh wrote:
> On Fri, Sep 13, 2013 at 05:42:18PM -0400, Jonathan M Davis wrote:
> > On Friday, September 13, 2013 21:48:15 Namespace wrote:
> > > Just out of interest.
> > > 
> > > I use Sublime 2, Notepad++ and as IDE currently Mono-D. But I will try this evening VisualD.
> > 
> > I use gvim regardless of the language that I'm writing in. I even use it for word processing, because if I have to write a document that requires that, I use LaTex.
> 
> [...]
> 
> +1.
> 
> I use vim (bare text mode, no GUI, so no gvim for me)

I don't actually use any of the GUI controls. It's just useful to have vim in a window that I can resize (you also get better color choices than in the shell).

> for literally
> *everything*. Everything from system config files to coding to LaTeX for
> word-processing to scripted graphics processing (thanks to imagemagick)
> to povray scene files, there's almost nothing in my world that can't be
> accomplished by vim. :)
> 
> Sometimes I wonder how the GUI-encumbered people get any work done at all, what with needing to constantly switch their hands between the keyboard and the rodent, wait for a 600MB application to load up 200MB of eye-candy and paint the screen with 50 toolbar controls, 45 of which that they never actually use, click through endless layers of nested menus just to perform a single operation, etc.. ;-)
> 
> (OK, OK, so I'm a fossilized relic from the last ice age of '75, I'll stop the GUI-bashing now. :-P You may carry on.)

LOL. Yeah, the main reason that I don't use IDEs is the fact that they're essentially a glorified version of notepad as far as editing goes. They _do_ usually have better editing capabilities then the ever-so-pathetic notepad, but they can't do much of anything in comparison to the likes of vim or emacs. So, I end up using (g)vim for everything. The features that an IDE has that vim doesn't typically just aren't worth it. e.g. if I'm stuck doing Windows programming, about the most that I even do with VS is use the debugger. I even build from the command line rather than open the IDE.

Vim's learning curve is quite nasty, but I definitely think that it was worth it.

- Jonathan M Davis

On Friday, 13 September 2013 at 21:45:06 UTC, H. S. Teoh wrote:
> Xterm has a 256-color mode that can be used for subtler

You can do a palette swap in hardware text mode too (fiddling the vga palette registers, I think it is the same as in mode 13h but it's been a looooong time since I've played with that), the linux console in vga text mode (see man console_codes(4)), and in Windows console:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms686039%28v=vs.85%29.aspx


Perhaps bad practice to change that stuff, at least not without changing it back when you're done, but it is doable.


Actually, my biggest problem with linux is how terrible the operating system is compared to DOS and Windows. I'm not even kidding, the unix terminal debacle sucks (maybe good when you had various hardware, but it is weak next to what the PC hardware offers), the available system facilities suck (Win32 is plenty usable and reliably there! Even on linux, using a Windows .exe tends to work better than using a linux binary - exe's just work there thanks to wine, whereas linux binaries always have some incompatibility).

Eh I'm getting off topic.