Jan Rychter wrote:
>>>>>"Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>>>"Reiner" == Reiner Steib <reinersteib+gmane(a)imap.cc>
writes:
>>>>>
>>>>>
Reiner> Can we expect _any_ reaction (yes, no, maybe) from the XEmacs
Reiner> board?
Stephen> Unfortunately, at this time we're very short-handed for
Stephen> reviewers and developers in general. If there was negative
Stephen> feeling, you'd get a "no", so the answer is "maybe"
until it
Stephen> turns into "yes". This is a shortcoming of our relatively
Stephen> decentralized process.
Reiner> Am I posting to the wrong list?
Stephen> No and yes. For what you posted that I'm responding to, this
Stephen> is the right place.
Stephen> If you want to help something to get done a lot faster, you
Stephen> can post a full patch (in the case of a new file, either a
Stephen> patch against /dev/null or the file as an attachment is OK),
Stephen> with appropriate XEmacs-format changelog, to XEmacs Patches
Stephen> <xemacs-patches(a)xemacs.org>.
[...]
I did just that about a year ago -- I posted a reasonably simple patch
that adds about 4 lines of code to the XEmacs code base. I brought the
issue up again about three weeks ago, and a couple of days ago, but it
seems continuous nagging doesn't get me anywhere.
The patch (mswindows window id property for XEmacs frames) is necessary,
because without it I cannot support people who want to use my vx-mode
package for dictation with XEmacs under Windows. As it is, my user base
is limited to people who use Linux and run Dragon NaturallySpeaking
under VMware, a rather rare combination.
I'm getting increasingly disappointed -- I initially switched to XEmacs
because I found the developer community to be more responsive and code
would change quicker. I hate sending those nagging E-mails, it annoys
the developers, it annoys me, and causes people to dislike me for no
good reason. Should I just give up, rework vx-mode to use properties
instead of extents and switch to FSF Emacs?
I understand "being short-handed for developers", but this attitude will
cause even more developers to go elsewhere.
hello Jan. i checked your feature to the latest CVS. i have to
personally apologize for not getting to this sooner; too much has been
going on lately. i changed it slightly so that the value of the
`window-id' property is a string, like in X windows. also, it is
currently only available through `frame-property'; i didn't implement
`mswindows-window-id'. (if we want something like this, it should be
called `frame-window-id'.)
please also note that david kastrup's views are not shared by the xemacs
developers as a whole. i for one am committed to having good ms windows
support in xemacs, and in fact do all my development under windows [with
lots of help from cygwin].
ben