[Twisted-Python] Re: [Twisted-commits] r16486 - Merge epytext-cleanups-1545
- zsh_extras = [":file to read from:action", ":file to write to:action"] + zsh_extras = [\":file to read from:action\", \":file to write to:action\"]
Why were changes like that made? Isn't it a no-op, since they were in triple-quoted strings anyhow? It would be nice if the docs were actually usable/readable by people viewing the source as well as people viewing the generated docs, where possible. James
On Mon, 2006-03-27 at 11:15 -0500, James Y Knight wrote:
Why were changes like that made? Isn't it a no-op, since they were in triple-quoted strings anyhow? It would be nice if the docs were actually usable/readable by people viewing the source as well as people viewing the generated docs, where possible.
Probably to work around python-mode emacs brokenness?
On Mon, 27 Mar 2006 11:31:16 -0500, Itamar Shtull-Trauring <itamar@itamarst.org> wrote:
On Mon, 2006-03-27 at 11:15 -0500, James Y Knight wrote:
Why were changes like that made? Isn't it a no-op, since they were in triple-quoted strings anyhow? It would be nice if the docs were actually usable/readable by people viewing the source as well as people viewing the generated docs, where possible.
Probably to work around python-mode emacs brokenness?
Yes. See <http://twistedmatrix.com/trac/browser/trunk/doc/core/howto/policy/coding-sta...> :) Jean-Paul
On Mon, Mar 27, 2006 at 11:40:54AM -0500, Jean-Paul Calderone wrote:
On Mon, 27 Mar 2006 11:31:16 -0500, Itamar Shtull-Trauring <itamar@itamarst.org> wrote:
On Mon, 2006-03-27 at 11:15 -0500, James Y Knight wrote:
Why were changes like that made? Isn't it a no-op, since they were in triple-quoted strings anyhow? It would be nice if the docs were actually usable/readable by people viewing the source as well as people viewing the generated docs, where possible.
Probably to work around python-mode emacs brokenness?
Yes. See <http://twistedmatrix.com/trac/browser/trunk/doc/core/howto/policy/coding-sta...> :)
Has anyone tried fixing this brokenness in python-mode? I'm no emacs hacker, but it seems like it's the sort of thing that ought to be, say, a 10-line fix in some chunk of parsing code somewhere. I could be massively wrong though :) If I've got a spare weekend, maybe I'll look at it sometime. - Colin
On Mon, 2006-03-27 at 11:52 -0500, Colin McMillen wrote:
Has anyone tried fixing this brokenness in python-mode? I'm no emacs hacker, but it seems like it's the sort of thing that ought to be, say, a 10-line fix in some chunk of parsing code somewhere. I could be massively wrong though :) If I've got a spare weekend, maybe I'll look at it sometime.
It's fixed as of GNU Emacs 22, which has a rewritten emacs-mode. Probably still broken in xemacs.
On Mon, 27 Mar 2006 11:52:01 -0500, Colin McMillen <mcmillen@cs.cmu.edu> wrote:
Has anyone tried fixing this brokenness in python-mode? I'm no emacs hacker, but it seems like it's the sort of thing that ought to be, say, a 10-line fix in some chunk of parsing code somewhere. I could be massively wrong though :) If I've got a spare weekend, maybe I'll look at it sometime.
There was an urban myth for quite some time that it was not possible to fix this problem given the way that Emacs does syntax highlighting. However, the new "python.el" that comes with CVS emacs (as opposed to the "python-mode.el" which comes with XEmacs and is distributed by python.org) does not have this problem. However, it has a few other issues, so it's a "six of one, half dozen of the other" sort of problem. I think that the new "python.el" is better, but no effort seems to have yet been made to integrate the two efforts.
participants (5)
-
glyph＠divmod.com -
Itamar Shtull-Trauring -
James Y Knight -
Jean-Paul Calderone -
mcmillen＠cs.cmu.edu