It's the interviewer's job to decide what they're testing for. Some developers need an IDE - that does not make them bad developers.

An interviewer should ask

    How can we help you show us why
    you'd be good for this job?

Stupid tricks don't help you determine if someone can do a job. Tiny, trivial programming tasks don't tell you if someone can do the job, but can (sometimes) tell you if someone can't do the job.

Interviewing is hard, there are no short cuts. You need someone who is smart, will get things done, can interact usefully with others, and adds value. Sometimes using an IDE is the best way to accomplish that - why ignore someone just because they don't work the way you do?