"Paul Moore" <[EMAIL PROTECTED]> wrote: > On 9/14/06, Josiah Carlson <[EMAIL PROTECTED]> wrote: > > So don't save it with a BOM and add a Python coding: directive to the > > second line. Python and bash comments just happen to have the same # > > delimiter, and if your editor doesn't suck, then it should understand > > such a directive. > > However, vim and emacs use *different* coding directive formats. > Python understands both, but (AFAIK) they don't understand each > other's. So which editor sucks? :-) :-) :-) (3 smileys is a > get-out-of-flamewar-free card :-))
Single users will be choosing a single tool. Multiple users will likely use a source repository. Good source repositories will allow for pre or post processing. Or heck, I'm sure that Emacs or Vim can even be tweaked to understand the others encoding declarations. If not, there are more than a dozen source editors that support both, and even some that offer the features I describe. - Josiah _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
