--- "Karr, David" <[EMAIL PROTECTED]> wrote:
> At end.
> 
> > -----Original Message-----
> > From: Rick Rankin [mailto:[EMAIL PROTECTED] 
> > 
> > --- "David M. Karr" <[EMAIL PROTECTED]> wrote:
> > > >>>>> "Larry" == Larry Hall <[EMAIL PROTECTED]> writes:
> > > 
> > >     Larry> At 08:30 PM 10/9/2003, Karr, David you wrote:
> > >     >> I have version 1.3.22 installed on another box.  On 
> > a new box, I
> > > decided
> > >     >> to go for broke and install 1.5.5.  Unfortunately, 
> > as others have
> > >     >> described, Xemacs doesn't work in this Cygwin 
> > version.  I need to
> > 
> > What specific problem are you having with XEmacs? I use 
> > XEmacs 21.4.14 on
> > Cygwin 1.5.x constantly, and the only problem I have is that 
> > cut-n-paste from
> > external sources stops working after running a subshell. This 
> > is annoying, but
> > for me, at least, not a show-stopper. Supposedly, you can 
> > work around this by
> > adding
> > 
> > (setq process-connection-type nil) ;; use pipes instead of ptys
> > 
> > to your .emacs file, but I haven't tried it. I'm hoping to 
> > have a go at
> > debugging the problem when ptys are used, but I just haven't 
> > had time yet.
> > 
> > I've seen postings about a font problem, but I haven't 
> > experienced the problem
> > myself.
> 
> When I start up Xemacs, the window appears, and it starts to show the
> packages it's loading.  After a while, however, the display of the
> window gets corrupted.  The window decorations and border disappear, and
> text doesn't show up.  The toolbar icons look fine, however.  If I type
> in the opening buffer, it just prints a red block cursor for each
> character.  It's not "hung", as I can press the key to exit, and it
> exits fine.
> 

Interesting... What version of XEmacs? Do you build your own or download a
binary?

--Rick

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to