|
A good while ago I worked in a department where we did software development on both MSDos and Unix boxes. On the Dos boxes we used a realy good text editor called MultiEdit. One developer asked if I could get him MultiEdit for Unix - I replied no, but said that I couod get him vi for Dos - he nearly punched me!
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
VsVim[^] might be useful for you. It adds Vim commands to VS.
Getting information off the Internet is like taking a drink from a fire hydrant.
- Mitchell Kapor
|
|
|
|
|
Teach me to comment before reading the whole thread
|
|
|
|
|
Heh. I am not all that used to Vi(m), but this extension seems to be quite powerful.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
|
|
|
|
|
I have a vi plugin for visual studio. It's called vsvim, and as far as I remember I installed it in the extension manager gui.
|
|
|
|
|
If you are programmer with not enough background with the language i don't thing that the best practice is to disable the coloring of the text. I think that the language itself it is not so easy to do such practice. And beside that coloring can save you hours of debugging in some cases like this for example.
A enough experienced c++ / colorblind programmer can disable the coloring without lowering his or hers productivity.
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
When you become practised in the art then you simply hold your hands above the keyboard in supplication and the code writes itself out of fear of reprisals. 
speramus in juniperus
|
|
|
|
|
I can only dream of achieving such heights. 
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
Yes, we do know PMs have a quite twisted perception of the software development process. 
Veni, vidi, vici.
|
|
|
|
|
Hey man, hats off to vi: it provides syntax colouring as well.
And you can rely on colourization. Well, unless you write something like
for (n=0; n<100; ++n);
{
doSomething();
}
Veni, vidi, vici.
|
|
|
|
|
The compilers I've used give a warning in cases like this.
JM2B,
Pablo.
"Accident: An inevitable occurrence due to the action of immutable natural laws." (Ambrose Bierce, circa 1899).
"You are to act in the light of experience as guided by intelligence" (Rex Stout, "In the Best Families", 1950).
|
|
|
|
|
Who looks at warnings? nobody that works with me, sadly 
|
|
|
|
|
I don't - I have "treat warnings as errors" set on my projects to prevent compilation succeeding! 
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
People here don't read error messages, so even if i set that they would just ignore
|
|
|
|
|
That's the whole point: if you set "treat warnings as errors" then compilation fails until the warning is fixed. You can't run or test you app until you do.
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
My old boss once jokingly said that he was still waiting for the "treat errors as warnings" flag. 
The good thing about pessimism is, that you are always either right or pleasently surprised.
|
|
|
|
|
Many programmers use "treat errors as warnings" flag.
|
|
|
|
|
I just make sure my code compiles without warnings.
If I really cannot avoid a warning, I use a pragma to disable a specific warning, with an explanatory comment.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
|
Lol.
Getting information off the Internet is like taking a drink from a fire hydrant.
- Mitchell Kapor
|
|
|
|
|
Priceless. He sure got a lot of down votes for that one!
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
Here was my version: how to write a program[^]
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
haha hilarious, what happened in the end? Did he come clean to his tutor?
|
|
|
|
|
No idea.
I gave him 25 hours to be kind, and then sent the email. He hasn't been back since... 
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
