Didier Verna <didier(a)xemacs.org&gt; writes: I'll try covering the GNU Emacs angle. This is made considerably easier since you have a copyright assignment on file, so at least from the licensing situation, you need not differentiate your contributions. If your changes would cleanly apply as patch to the version in GNU Emacs, you can (assuming you don't have developer access yourself) post the patch (in context diff format, not unified diff) to the developer list, explain the changes (and to what degree you tested them on Emacs) and write "could somebody apply this?". That would usually work. You could add your changes yourself to XEmacs then, or wait until the next synchronization. Since you very likely prefer to see them sooner rather than in a few years, you'd likely want to apply them yourself. They would probably not complicate a later synchronization. If the situation is such that you can't figure out whether your stuff would still apply to the GNU Emacs version or work there, the situation would be somewhat different. You'd probably have to propose the changes, argue for them and post the patch you did for the XEmacs version (the patch will contain context taken from XEmacs, but the _content_ of the _changes_ that are going to end up in Emacs will have originated just with you). There is also the possibility of posting just code fragments and explanations. In any case, the more straightforward the work for the other developers is, the more likely is an unproblematic inclusion. You might want to wait until the Emacs 22 release excitement is over (the release should be any year now: I actually just blew my cork at RMS putting in another prerelease-requiring change without which it might have happened tomorrow), though. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

Didier Verna <didier(a)xemacs.org&gt; writes: Putting yourself in as the maintainer at the top of the file considerably helps usually. But you won't have "control" in any manner: that is pretty much the point of the copyright assignment: passing the control. I don't think that it is a good idea to suggest in a multiperson free software project that every contributor retains individual control. While there are projects (like the Linux kernel) where this is factually the case, having every contributor able to throw a monkey wrench into further development is calling for trouble in the long run. Alienation _does_ happen in personal and professional relationships. Hopefully not forever. But then that's the same worry I have about Emacs 22. I hope I'll be able to see it, too. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

Didier Verna <didier(a)xemacs.org&gt; writes: You are an author of some files in Emacs and have a copyright assignment for it on file. I have no idea why you should _not_ get CVS access for it on Savannah unless you manage to ask for it in a manner rubbing people in the wrong way very badly. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

Stephen> ... whitespace cleanup has been an issue on Python lists the Stephen> last couple of days, and they might be interested. Just an FYI (haven't posted this to python-dev yet), my problems with dangling whitespace are caused by hitting RET or LF (py-newline-and-indent) which indents according to the current environment, then moving away from that indentation using a command python-mode doesn't know about (e.g. previous-line), so it doesn't have the opportunity to delete the whitespace. The whitespace module might help here, though I've never used it. I think the best place for it would be as a write-file-hook though I worry about it not being aware of Python's triple-quoted strings which can extend over multiple lines and which might presumably contain legitimate trailing whitespace. (It might be interesting to have a list of cursor-motion-hooks which would get called just before point moves, but that's another story altogether.) Skip _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

skip(a)pobox.com writes: I note that Tim Peters thinks that (as with MIME quoted printable) the last character of trailing whitespace should be written \x20 or \x09. It would be rude to disagree with sweet ol' Uncle Timmy.<wink> _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

So I've just upgraded CVS with my improvements on whitespace.el. The documentation at the top of the file is also clearer and more complete than before (I hope). I'm currently wondering why this library is in text-modes. Wouldn't it be better placed in edit-utils ? -- Read the Jazz Blog !! http://jazzblog.didierverna.com Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier(a)xemacs.org _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

Didier> So I've just upgraded CVS with my improvements on whitespace.el. Didier> The documentation at the top of the file is also clearer and Didier> more complete than before (I hope). I haven't run from CVS in like forever. Does your change add a whitespace-describe function? (I reported a bug about it just after your first post on the subject.) Skip _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta