Nick Roberts schrieb:
>  > >  > Unfortunately, I have only a dial-up connection and can't give
>  > >  > immediate feedback on new Emacs versions.
>  > > 
>  > > One advantage of using CVS over tarballs is that you only need to 
> download
>  > > the (compressed) _changes_.  Even with a dial-up connection that 
> shouldn't
>  > > take a long time.
>  > 
>  > Thanks for the hint.  I am already familiar with rcs, actually.  But I
>  > didn't set up a proper environment for compiling Emacs by myself yet.
>  > There just wasn't much use in that so far. :)
> 
> While it helps to just report bugs and with due respect, it's not reasonable 
> to
> claim that the Emacs developers don't give the Window port a high priority,

If you could cite from a message where I _claimed_ that, it would be
much easier for me to respond to that.

After rereading my message, I think I didn't claim anything about Emacs
development, but only wrote up some personal experiences I've made with
Emacs on Windows during the last years.

In fact, in

>>> Personally, I'd categorize this bug as a show-stopper for a
>>> stable release.  On the other hand, I don't know if Windows is an
>>> officially supported platform.  Could someone please clarify
>>> that?  And what user base does Emacs target to?

I finally asked about the relevance of the Windows port, but couldn't
see an answer or a pointer to some manifest or such so far.  Honestly,
it's not clear to me how Emacs and Windows relate.


> if you're not in a position to even test the patches which are
> provided.

Even if I were able to compile and test patches I don't think that
brought me into a position to claim anything about Emacs development.

I'll try my best to make my points more clear in the future, but
honestly, I can't see yours.  Currently, I tend to guess you're trying
to say: "You'd better shut up as long as you're not an active
developer!"  I could agree that this is not the right list.


> Some developers work hard on that very issue,

Sorry, for bothering you (all).  I didn't notice that.  To my defence,
not being a developer, I don't see how I could have got aware of what's
going on behind the scenes other than testing pre-built binaries from
time to time and reading several Emacs related mailing lists (watching
just this item).

Best regards,
Stephan Hennig



_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Reply via email to