Kent Borg wrote: > Andreas Roehler wrote: >> no need for that, emacs -q or emacs -Q is the right thing then >> > > "emacs -q" does not work, "emacs -Q" does work. (The toggling of > highlighting while opening and closing a multi-line comment is like > before,
seems normal, seems the way it proceeds but inside a correct multi-line comment, a new ' is happily > ignored.) reads like ok now. > >> Patch attached - not polished yet, but works here some weeks now. >> > > Copied it to my /usr/share/emacs/site-lisp/python-mode > > Tried: > > # patch python-mode.el tqs-all-python-mode.patch > > It seemed to work. To check: > > # diff python-mode.el python-mode.el-351 > > ...seems to look like the patch file. > > New emacs doesn't work better, but do I need to open the new > python-mode.el and meta-X byte-compile-file or something? Just make sure it's loaded. For example put (load "PATH-TO-NEW-python-mode.el") into your .emacs Comment out old python-mode loads if any. BTW byte-compile is very seldom needed, only if speed matters. Usually you'll not remark a difference. The only common use for me while playing with single files - compiling displays possible errors. > python-mode.elc has a new time stamp, does that mean I did it correctly? > > > Thanks, > > -kb, the Kent who has never gotten into emacs internals and doesn't know > the difference between a -q and -Q launch. > After reading "An Introduction to Programming in Emacs Lisp" you'll enjoy Emacs much more probably: M-x info RET m emacs lisp TAB > _______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
