No I didn't I said running and debugging on Android from the command line is not fun.
Eclipse and Netbeans do a lot of work for you on the debugging side that make the task a hell of a lot easier. You said you didn't want to use either, and with Android development using Java, that is a mistake.
Sorry I meant that I do not have much experience in working with Netbeans or Eclipse. So by using those programs I shouldn't have to much problems when debugging, correct?
I wish the answer was no, but...
Eclipse is the most stupidly over-engineered piece of @#$@#$ I have ever encountered in an IDE. The learning curve is stupidly high.
NetBeans is a great deal better, but at last look, Android support was a bit sketchy, because Google has ordained Eclipse as the one true way.
Granted, I am biased, I hate Eclipse with a passion, I think it's simply bloated and awful software that is incredibly inaccessible for new developers, a right pain in the ass for existing developers and one of the only tools that got in my way more often then it helped me. Other people absolutely swear by it though, so it may only be me.
IMHO, the very worst part about Android development is the toolchain, its far too fragile and frustrating.
Obviously learning Eclipse isn't insurmountable, but for an IDE, it is going to cause you a world of frustrations...