From: "Ehud Karni" <ehud@unix.mvs.co.il>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org,
jbuehler@spirentcom.com, cygwin@cygwin.com
Subject: Re: is there a cygwin maintainer for gnu emacs?
Date: Mon, 8 Aug 2005 13:31:45 +0300 [thread overview]
Message-ID: <200508081031.j78AVjjE008727@beta.mvs.co.il> (raw)
In-Reply-To: <BAY107-F8B4D21670F6A0DE5980E3F8B80@phx.gbl> (message from emacs user on Mon, 08 Aug 2005 02:21:53 -0400)
On Mon, 08 Aug 2005 02:21:53 -0400, emacs user wrote:
>
> Hello, I find emacs to be very unstable under cygwin, crashing every couple
> of minures (both emacs 21.X and cvs emacs with and without gtk). I
> submitted a few bug reports but received no reply. I was hoping to find the
> maintainer and interact directly with her/ him. any advice? EU
AFAIK Joe Buehler is maintaining Cygwin Emacs. But may be he is not
subscribed to emacs-devel@gnu.org.
Cygwin specific Emacs problems should be discussed on cygwin@cygwin.com,
not on emacs-devel@gnu.org.
What are your problems ?
May be you did rebasing (especially rebase all) - it is known to
have a negative effect on Emacs.
I work with both Emacs 21.2 (distributed with Cygwin, prepared by
Joe Buehler) and Emacs 22.0.50 (updated from CVS and compiled on
2005-08-01), both in terminal mode and on X, and they work fine.
Ehud.
--
Ehud Karni Tel: +972-3-7966-561 /"\
Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign
Insurance agencies (USA) voice mail and X Against HTML Mail
http://www.mvs.co.il FAX: 1-815-5509341 / \
GnuPG: 98EA398D <http://www.keyserver.net/> Better Safe Than Sorry
next prev parent reply other threads:[~2005-08-08 10:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 6:21 is there a cygwin maintainer for gnu emacs? emacs user
2005-08-08 10:31 ` Ehud Karni [this message]
2005-08-08 11:36 ` Joe Buehler
2005-08-09 5:08 ` emacs user
2005-08-09 18:05 ` Ehud Karni
2005-08-09 18:15 ` Joe Buehler
2005-08-10 10:47 ` emacs user
2005-08-10 11:37 ` Joe Buehler
2005-08-10 17:56 ` Eli Zaretskii
2005-08-10 20:18 ` emacs user
2005-08-11 3:37 ` Eli Zaretskii
2005-08-11 14:27 ` Richard M. Stallman
2005-08-11 15:12 ` Joe Buehler
2005-08-12 14:59 ` Richard M. Stallman
2005-08-12 17:02 ` Eli Zaretskii
2005-08-11 17:17 ` emacs user
2005-08-16 8:47 ` stackdump on cygwin (was: is there a cygwin maintainer for gnu emacs?) emacs user
2005-08-16 9:05 ` Brian Dessent
2005-08-17 4:09 ` Eli Zaretskii
2005-08-18 6:45 ` is there a cygwin maintainer for gnu emacs? emacs user
2005-08-19 8:38 ` Eli Zaretskii
2005-08-28 20:57 ` emacs user
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 18:15 David Masterson
2005-08-09 18:27 ` Joe Buehler
2005-08-09 21:02 ` emacs user
2005-08-09 18:31 David Masterson
2005-08-09 18:43 ` Joe Buehler
[not found] <42F9E5E8.7010908@spirentcom.com>
2005-08-10 13:36 ` emacs user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508081031.j78AVjjE008727@beta.mvs.co.il \
--to=ehud@unix.mvs.co.il \
--cc=cygwin@cygwin.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=jbuehler@spirentcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).