bug#50743: Emacsclient not tested vs. Local Variables prompt

[積丹尼 Dan Jacobson]

emacsclient -t makes even another (non-x) window.

Anyway, normally if we type abcefg... it goes right into the file, where
it belongs.

If we type M-x abcefg... we are still inputting and outputting to emacs'
minibuffer.

However if we boobytrap the file with  -*- foo: bar; -*-,
now suddenly emacs is asking us questions, but our answers are hijacked
elsewhere!

So we can type until we are blue in the face, but emacs will just sit
there with its question waiting for us to answer forever.

So the message should say "Please enter y, n... if nothing happens, then
next time use emacsclient -t."