Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-13 Thread Triza UK 
 --- Yadin Y Goldschmidt <[EMAIL PROTECTED]> wrote: > The
recent snapshot from 10/10/03 seems to have
> solved the XEmacs problem
> for me. Thank
> you Chris for an excellent job. It was clear from
> the start that you were
> the right person to solve this problem.
> 

Yes indeed. I can concur that. It works for me, too.

Many thanks

Triza


Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-12 Thread Yadin Y Goldschmidt 
The recent snapshot from 10/10/03 seems to have solved the XEmacs problem
for me. Thank
you Chris for an excellent job. It was clear from the start that you were
the right person to solve this problem.




--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-12 Thread Henry S. Thompson 
I don't think any of those environment differences account for the
problem.  On my own setup almost all of those are _not_ there, and in
particular the PATH is the same, since I don't have X installed.

Note it's important for at least some of us that Cygwin/XEmacs works
_without_ X.

Thanks _very_ much for taking on the XEmacs<->Cygwin liaison task.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
  Half-time member of W3C Team
 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
 URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-11 Thread Christopher Faylor 
On Sat, Oct 11, 2003 at 03:13:13PM -0500, Jerry James wrote:
>I wandered over here to see what was up with the bug report that started
>this thread.  Igor's solution works for me.  Thanks, Igor!
>
>Christopher Faylor wrote:
>>But seriously, if anyone would like to be an official Xemacs liason and
>>officially test snapshots when they happen that would certainly be
>>welcome.  I will not be running Xemacs to test things, unfortunately.
>>I would be glad to work with someone who was willing to test debug
>>versions of the Cygwin DLL and provide intelligent feedback on
>>problems.
>
>I'll do that.  I'm one of the XEmacs developers, by the way.

Ok.  You're subscribed to cygwin-developers.  Please try out Xemacs when
you see discussion there about changes to a new snapshot and pay
particular attention when a pending release is mentioned.

If you are interested in XEmacs bug reports you should be subscribed to
the cygwin mailing list too.  You have my condolences, if you're really
willing to do that.

>Also, if I take on this role, it is with the caveat that I'm a
>professor, so I reserve the right to be pedantic at the drop of a hat.
>Er, no, what I meant to say is that my schedule is somewhat
>unpredictable, except for around finals time, when I can confidently
>predict that I will be extremely busy.  If you're willing to work with
>a guy who might take 2 or 3 days to answer your email, I'm your man.

2 or 3 days would be heaven as long as you are providing accurate
feedback.  Just to be clear: I'm not going to be driving this.  I'm
expecting good bug reports (see http://cygwin.com/bugs.html).

To summarize bugs.html, a good bug report will entail detailed
descriptions of the problem.  It will not contain phrases like "and then
it went all to hell" or "and then it just fizzled out".  It will not
editorialize on how important the problem is to you or how angry you are
that the problem occurred to you or how much the documentation sucks.  It
won't go into great detail about what you had for breakfast on a given
day and it won't contain a treatise on the way you think software projects
should be run.  If you look at code, it won't contain shock, anger, or
amazement at the way the code was organized, commented, or indented.

I'm not going to get involved in discussions on how to set up your
environment or what packages to install via setup.exe.  The mailing
list can help with that.

Oh, and no personal email, please.  The discussions belong on the
appropriate mailing lists.

I'm not saying that you will do any of these things.  I'm giving you
care and feeding of cgf (and pretty much any developer) instructions
here.

>> If someone is interested in doing this perhaps they might also be
>> interested in providing an Xemacs package for the cygwin distribution.
>> This would be automatically preapproved.
>
>Sure thing.  Do you want X with that?  (I prefer fries.)

That would be up to you.  Check out the information at
http://cygwin.com/setup.html for what is entailed.

>Also, FWIW, I compared the environments of an XEmacs started from the
>shell (working) and an XEmacs started from an icon (not working).  The
>one started from the shell had these environment settings that were not
>present in the nonworking version:
>
>"!::=::\\"
>"!C:=C:\\cygwin\\bin"
>"MAKE_MODE=unix"
>"MANPATH=:/usr/ssl/man"
>"OLDPWD=/cygdrive/f/build-21.5"
>"PKG_CONFIG_PATH=:/usr/X11R6/lib/pkgconfig"
>"PROMPT=$P$G"
>"PS1=\\[\\033]0;[EMAIL PROTECTED] \\[\\033[33m\\w\\033[0m\\]\n$ "
>"PWD=/cygdrive/f"
>"SHLVL=1"
>"TEXMF={/usr/share/lilypond/2.0.1,/usr/share/texmf}"
>"USER=[censored by Jerry]"
>"_=/usr/local/test/bin/xemacs-21.5-b16.exe"

Those look like variables that came from the command shell.

>The PATH variables are different for the two versions, also.  The
>difference is that the one started from the shell starts with
>"/usr/local/bin:/usr/bin:/bin:", and ends with ":/usr/X11R6/bin", both
>of which are missing in the nonworking version.  If I'm reading the FAQ
>correctly (http://cygwin.com/faq/faq_4.html#SEC35), this could be the
>source of the problem.
>
>Are we doing something wrong, or should the PATH have been magically
>modified somehow?

The only thing that the Cygwin DLL does explicitly is convert the PATH
from windows to unix format.  It doesn't add or delete directories from
the PATH.

The PATH that a non-console-started version of Xemacs sees would come
from the standard windows location.  The PATH that an Xemacs-from-shell
sees would depend on what the shell has set.

Btw, there is a new cygwin snapshot available that has been reported
to solve the cut/paste problems:  http://cygwin.com/snapshot.html .
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to [EMAIL PROTECTED]
and be permanently blocked from mailing lists at sources.redhat.com

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.htm

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-11 Thread Jerry James 
I wandered over here to see what was up with the bug report that started
this thread.  Igor's solution works for me.  Thanks, Igor!

Christopher Faylor wrote:
> But seriously, if anyone would like to be an official Xemacs liason and
> officially test snapshots when they happen that would certainly be
> welcome.  I will not be running Xemacs to test things, unfortunately.  I
> would be glad to work with someone who was willing to test debug
> versions of the Cygwin DLL and provide intelligent feedback on problems.

I'll do that.  I'm one of the XEmacs developers, by the way.  Also, if I
take on this role, it is with the caveat that I'm a professor, so I
reserve the right to be pedantic at the drop of a hat.  Er, no, what I
meant to say is that my schedule is somewhat unpredictable, except for
around finals time, when I can confidently predict that I will be
extremely busy.  If you're willing to work with a guy who might take 2
or 3 days to answer your email, I'm your man.

> I'll even give an automatic subscription to cygwin-developers to anyone
> who is willing to perform this service to the community.  I do this
> because I know that Xemacs is a popular package and, despite what I said
> above, I would like to ensure that it works correctly.

So would we XEmacs developers. :-)  It sounds good to me.  What other
lists should I subscribe to?  (I'm not subscribed to any Cygwin lists at
the moment.)

> If someone is interested in doing this perhaps they might also be
> interested in providing an Xemacs package for the cygwin distribution.
> This would be automatically preapproved.

Sure thing.  Do you want X with that?  (I prefer fries.)

Also, FWIW, I compared the environments of an XEmacs started from the
shell (working) and an XEmacs started from an icon (not working).  The
one started from the shell had these environment settings that were not
present in the nonworking version:

"!::=::\\"
"!C:=C:\\cygwin\\bin"
"MAKE_MODE=unix"
"MANPATH=:/usr/ssl/man"
"OLDPWD=/cygdrive/f/build-21.5"
"PKG_CONFIG_PATH=:/usr/X11R6/lib/pkgconfig"
"PROMPT=$P$G"
"PS1=\\[\\033]0;[EMAIL PROTECTED] \\[\\033[33m\\w\\033[0m\\]\n$ "
"PWD=/cygdrive/f"
"SHLVL=1"
"TEXMF={/usr/share/lilypond/2.0.1,/usr/share/texmf}"
"USER=[censored by Jerry]"
"_=/usr/local/test/bin/xemacs-21.5-b16.exe"

The PATH variables are different for the two versions, also.  The
difference is that the one started from the shell starts with
"/usr/local/bin:/usr/bin:/bin:", and ends with ":/usr/X11R6/bin", both
of which are missing in the nonworking version.  If I'm reading the FAQ
correctly (http://cygwin.com/faq/faq_4.html#SEC35), this could be the
source of the problem.

Are we doing something wrong, or should the PATH have been magically
modified somehow?
-- 
Jerry James
http://www.ittc.ku.edu/~james/

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-11 Thread David Rothenberger 
Triza UK wrote:

I have same experience with Cygwin 1.5.5
 
I updated my Cygwin to 1.5.5 and XEmacs became
unusable. Cygwin 1.3.20 works OK. XEmacs I am using is
21.5.5, but this must be a Cygwin bug because I only
ungraded Cygwin. 
 
The problem starts when I run a subprocess from
XEmacs. Good example is gnuserv. This is not a gnuserv
related bug because clearcase.el also wrecks XEmacs,
which also runs subprocesses.
Having run a subprocess, XEmacs screen failed to get
updated,
characters dissappear.
 
I use XEmacs 21.4, not 21.5, and do not have the reported problem with 
fonts.  But, I did have a possibly related problem. When I started a 
subprocess in XEmacs, copy/paste to the Windows clipboard would stop 
working.  The work-arounds described for the fonts problem (starting 
from rxvt) also worked for my problem, which is why I think they are 
related.

Anyway, FWIW, the latest changes to fhandler_tty.cc in the latest cygwin 
snapshot fixed my XEmacs problems.  You might want to try it.

If they don't solve your problem, I may have time to take a stab at 
reproducing and debugging your problem with XEmacs 21.5 in a couple of 
weeks.

David



--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-09 Thread Christopher Faylor 
On Thu, Oct 09, 2003 at 07:00:56PM +0100, Triza UK wrote:
>I have same experience with Cygwin 1.5.5
> 
>I updated my Cygwin to 1.5.5 and XEmacs became unusable.  Cygwin 1.3.20
>works OK.  XEmacs I am using is 21.5.5, but this must be a Cygwin bug
>because I only ungraded Cygwin.
>
>The problem starts when I run a subprocess from XEmacs.  Good example
>is gnuserv.  This is not a gnuserv related bug because clearcase.el
>also wrecks XEmacs, which also runs subprocesses.  Having run a
>subprocess, XEmacs screen failed to get updated, characters dissappear.
> 
>I found a thread on an XEmacs mailing list which describes the same
>problem.  There is a hint on this thread about the root cause:
>
>http://list-archive.xemacs.org/xemacs-beta/200309/msg00312.html

This message has already been sent here.  It is, predictably, the usual
vague type of musings that we get from the XEmacs camp.

>I tried and recompiled the very same XEmacs version I mentioned above,
>but it did not help.  I compiled some more recent beta and normal
>XEmacs versions, but they all suffer from this problem.
>
>Many thanks to the good soul who could fix this bug.  I am happy assist
>you in testing it.

I will repeat my original offer to help anyone who wants to debug this
program but (and I think I'm being consistent here) I'm not going to
be downloading XEmacs to try to figure out what's going on.  I simply
don't care enough to do that.  I have other things which interest me
more.

Sorry to be blunt, but having been subjected to the insinuations of the
above archive message twice now, my already limited ability to be
tactful has worn a bit thin.

cgf

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-09 Thread Triza UK 
I have same experience with Cygwin 1.5.5
 
I updated my Cygwin to 1.5.5 and XEmacs became
unusable. Cygwin 1.3.20 works OK. XEmacs I am using is
21.5.5, but this must be a Cygwin bug because I only
ungraded Cygwin. 
 
The problem starts when I run a subprocess from
XEmacs. Good example is gnuserv. This is not a gnuserv
related bug because clearcase.el also wrecks XEmacs,
which also runs subprocesses.
Having run a subprocess, XEmacs screen failed to get
updated,
characters dissappear.
 
I found a thread on an XEmacs mailing list which
describes the same
problem. There is a hint on this thread about the root
cause:
 
http://list-archive.xemacs.org/xemacs-beta/200309/msg00312.html

I tried and recompiled the very same XEmacs version I
mentioned above,
but it did not help. I compiled some more recent beta
and normal XEmacs versions, but they all suffer from
this problem.
 
Many thanks to the good soul who could fix this bug. I
am happy assist you in testing it. 

Triza



Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-08 Thread Henry S. Thompson 
Igor Pechtchanski <[EMAIL PROTECTED]> writes:



> Hmm.  I was going to point you to
> , but it
> seems the page is temporarily unavailable.  You can still take a
> look at the Google cache version at
> 
> or the one in the Internet Archive at
> ,
> though.

Yeah, that's where I got the idea for the code I posted -- since it
was a) not obviously still available from the author and b) much more
sophisticated than I required, I posted the simplified version.  For
the full deal, it's certainly the right thing.

As another poster pointed out, this is just a workaround, the main
goal is figuring out how to help the xemacs developers fix this in
their cygwin build . . .

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
  Half-time member of W3C Team
 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
 URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-07 Thread David Rothenberger 
Yadin Y. Goldschmidt wrote:

It is true that making a xemacs.bat file which contains
c:\cygwin\usr\X11R6\bin\run.exe /bin/bash -c
"/usr/local/bin/i686-pc-cygwin/xemacs" makes XEmacs run correctly
under cygwin 1.5.5. (Actually one needs to add a line 'set
cygwin=tty ' before that line if one does not already have it in
the windows' environment). Alternatively one can run it from rxvt.
By running correctly I mean nvoking secondary processes like
opening a shell or compiling a program.  However the bigger
question is why XEmacs ran correctly before from its icon on the
desk and it does not run correctly now? It must be something that
has changed going from cygwin 1.3.22 to 1.5 that prevents runnung
this application from the dos command line when it was compiled
with cygwin.  In 1.3.22 it ran flawlessly.  It seems that this
change affects also some other applications. 
Right, it was a change in the 1.5.x series related to tty management 
code.  I think the changes made to help services run without pop-up 
windows broke XEmacs

> I wonder also if once XEmacs is compiled with 1.5.5 it will also
> run from the dos prompt or icon or not.
I compile my own XEmacs and it does not make a difference.  It also 
doesn't matter if XEmacs is compiled with X support or not.

I have not experienced the problem with fonts, but I do have a problem 
with copy/paste; it stops interacting with the Windows clipboard once a 
subshell is started, unless XEmacs is started from rxvt.  One 
interesting bit of information is that if XEmacs is configured to use 
pipes instead of ttys for subprocesses (setq process-connection-type 
nil), copy/paste works fine.

I've taken several stabs at debugging this problem, but the tty 
management in the Cygwin kernel is over my head.

"Henry S. Thompson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Igor Pechtchanski <[EMAIL PROTECTED]> writes:


On Mon, 6 Oct 2003, Henry S. Thompson wrote:


Igor Pechtchanski <[EMAIL PROTECTED]> writes:



If you're _really_ obsessive (like me :-( about launching from an
icon, compile the following and point the icon at it.
Hope this helps,
ht
[code snipped]
  if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c
\"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs,
NULL, TRUE, 0,
 NULL, NULL, &start, &child))
Ouch!  Why not simply point the shortcut at
'c:\cygwin\bin\bash --login -c

"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
 Igor
Because that produces an unsightly command window as well as the
desired xemacs window.  That's what all the WinMain etc. stuff is
there to defeat.
ht
Umm, yeah, ok, make that 'c:\cygwin\usr\X11R6\bin\run.exe /bin/bash
--login -c "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"',
then.

:-D
Igor
Ah, but I don't run X, just vanilla cygwin.

See you and raise you again :-)

ht
--
 Henry S. Thompson, HCRC Language Technology Group, University of
Edinburgh

 Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
   Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged
spam]





--
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/


--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-07 Thread Igor Pechtchanski 
On Tue, 7 Oct 2003, Henry S. Thompson wrote:

> Igor Pechtchanski <[EMAIL PROTECTED]> writes:
>
> > On Mon, 6 Oct 2003, Henry S. Thompson wrote:
> >
> >> Igor Pechtchanski <[EMAIL PROTECTED]> writes:
> >>
> >> 
> >>
> >> >> If you're _really_ obsessive (like me :-( about launching from an
> >> >> icon, compile the following and point the icon at it.
> >> >>
> >> >> Hope this helps,
> >> >> ht
> >> >> [code snipped]
> >> >>if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c 
> >> >> \"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs, NULL, 
> >> >> TRUE, 0,
> >> >>   NULL, NULL, &start, &child))
> >> >
> >> > Ouch!  Why not simply point the shortcut at 'c:\cygwin\bin\bash --login -c
> >> > "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
> >> >   Igor
> >>
> >> Because that produces an unsightly command window as well as the
> >> desired xemacs window.  That's what all the WinMain etc. stuff is
> >> there to defeat.
> >>
> >> ht
> >
> > Umm, yeah, ok, make that 'c:\cygwin\usr\X11R6\bin\run.exe /bin/bash
> > --login -c "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"', then.
> > :-D
> >   Igor
>
> Ah, but I don't run X, just vanilla cygwin.
>
> See you and raise you again :-)
> ht

Hmm.  I was going to point you to
, but it seems
the page is temporarily unavailable.  You can still take a look at the
Google cache version at 

or the one in the Internet Archive at
,
though.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-07 Thread Yadin Y. Goldschmidt 
It is true that making a xemacs.bat file which contains
c:\cygwin\usr\X11R6\bin\run.exe /bin/bash  -c
"/usr/local/bin/i686-pc-cygwin/xemacs"
makes XEmacs run correctly under cygwin 1.5.5. (Actually one needs to add a
line 'set cygwin=tty '
before that line if one does not already have it in the windows'
environment). Alternatively one can run it from rxvt.
By running correctly I mean nvoking secondary processes like opening a shell
or compiling a program.
However the bigger question is why XEmacs ran correctly before from its icon
on the desk and it does not run correctly now? It must be something that has
changed going from
cygwin 1.3.22 to 1.5 that prevents runnung this application from the dos
command line when it was compiled with cygwin. In 1.3.22 it ran flawlessly.
It seems that this change affects also some other applications. I wonder
also if once XEmacs is compiled with 1.5.5 it will also run from the dos
prompt or icon or not.
"Henry S. Thompson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Igor Pechtchanski <[EMAIL PROTECTED]> writes:
>
> > On Mon, 6 Oct 2003, Henry S. Thompson wrote:
> >
> >> Igor Pechtchanski <[EMAIL PROTECTED]> writes:
> >>
> >> 
> >>
> >> >> If you're _really_ obsessive (like me :-( about launching from an
> >> >> icon, compile the following and point the icon at it.
> >> >>
> >> >> Hope this helps,
> >> >> ht
> >> >> [code snipped]
> >> >>if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c
\"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs,
NULL, TRUE, 0,
> >> >>   NULL, NULL, &start, &child))
> >> >
> >> > Ouch!  Why not simply point the shortcut at
'c:\cygwin\bin\bash --login -c
> >> > "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
> >> >   Igor
> >>
> >> Because that produces an unsightly command window as well as the
> >> desired xemacs window.  That's what all the WinMain etc. stuff is
> >> there to defeat.
> >>
> >> ht
> >
> > Umm, yeah, ok, make that 'c:\cygwin\usr\X11R6\bin\run.exe /bin/bash
> > --login -c "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"',
then.
> > :-D
> > Igor
>
> Ah, but I don't run X, just vanilla cygwin.
>
> See you and raise you again :-)
>
> ht
> -- 
>   Henry S. Thompson, HCRC Language Technology Group, University of
Edinburgh
>   Half-time member of W3C Team
>  2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
> Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
>  URL: http://www.ltg.ed.ac.uk/~ht/
>  [mail really from me _always_ has this .sig -- mail without it is forged
spam]
>




--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-07 Thread Henry S. Thompson 
Igor Pechtchanski <[EMAIL PROTECTED]> writes:

> On Mon, 6 Oct 2003, Henry S. Thompson wrote:
>
>> Igor Pechtchanski <[EMAIL PROTECTED]> writes:
>>
>> 
>>
>> >> If you're _really_ obsessive (like me :-( about launching from an
>> >> icon, compile the following and point the icon at it.
>> >>
>> >> Hope this helps,
>> >> ht
>> >> [code snipped]
>> >>if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c 
>> >> \"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs, NULL, 
>> >> TRUE, 0,
>> >>   NULL, NULL, &start, &child))
>> >
>> > Ouch!  Why not simply point the shortcut at 'c:\cygwin\bin\bash --login -c
>> > "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
>> >   Igor
>>
>> Because that produces an unsightly command window as well as the
>> desired xemacs window.  That's what all the WinMain etc. stuff is
>> there to defeat.
>>
>> ht
>
> Umm, yeah, ok, make that 'c:\cygwin\usr\X11R6\bin\run.exe /bin/bash
> --login -c "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"', then.
> :-D
>   Igor

Ah, but I don't run X, just vanilla cygwin.

See you and raise you again :-)

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
  Half-time member of W3C Team
 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
 URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-06 Thread Igor Pechtchanski 
On Mon, 6 Oct 2003, Henry S. Thompson wrote:

> Igor Pechtchanski <[EMAIL PROTECTED]> writes:
>
> 
>
> >> If you're _really_ obsessive (like me :-( about launching from an
> >> icon, compile the following and point the icon at it.
> >>
> >> Hope this helps,
> >> ht
> >> [code snipped]
> >>if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c 
> >> \"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs, NULL, 
> >> TRUE, 0,
> >>   NULL, NULL, &start, &child))
> >
> > Ouch!  Why not simply point the shortcut at 'c:\cygwin\bin\bash --login -c
> > "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
> >   Igor
>
> Because that produces an unsightly command window as well as the
> desired xemacs window.  That's what all the WinMain etc. stuff is
> there to defeat.
>
> ht

Umm, yeah, ok, make that 'c:\cygwin\usr\X11R6\bin\run.exe /bin/bash
--login -c "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"', then.
:-D
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-06 Thread Henry S. Thompson 
Igor Pechtchanski <[EMAIL PROTECTED]> writes:



>> If you're _really_ obsessive (like me :-( about launching from an
>> icon, compile the following and point the icon at it.
>>
>> Hope this helps,
>> ht
>> [code snipped]
>>if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c 
>> \"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs, NULL, TRUE, 
>> 0,
>>   NULL, NULL, &start, &child))
>
> Ouch!  Why not simply point the shortcut at 'c:\cygwin\bin\bash --login -c
> "/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
>   Igor

Because that produces an unsightly command window as well as the
desired xemacs window.  That's what all the WinMain etc. stuff is
there to defeat.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
  Half-time member of W3C Team
 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
 URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-06 Thread Igor Pechtchanski 
On Mon, 6 Oct 2003, Henry S. Thompson wrote:

> Terrence Brannon <[EMAIL PROTECTED]> writes:
>
> >>I have just recently upgraded to the latest Cygwin and latest XEmacs.
> >>Now, whenever I invoke a subprocess in XEmacs, all text in the XEmacs
> >>frame goes blank. I am using zsh as my shell, but the problem always
> >>occurs whether I am invoking a subshell, compiling, grepping, or running
> >>gnu-serv. I am running Windows XP Pro SP1 and XEmacs 21.4.13.
>
> My experience was similar, and the work-around I found successful was
> to launch xemacs from rxvt/bash, rather than from the Task Bar or
> Start Menu.  I spent a fair amount of time attempting to discover
> whether there was an environment variable which accounted for this,
> but failed.
>
> If you're _really_ obsessive (like me :-( about launching from an
> icon, compile the following and point the icon at it.
>
> Hope this helps,
> ht
> [code snipped]
>if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c 
> \"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs, NULL, TRUE, 
> 0,
>   NULL, NULL, &start, &child))

Ouch!  Why not simply point the shortcut at 'c:\cygwin\bin\bash --login -c
"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start"'?
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-06 Thread Henry S. Thompson 
Terrence Brannon <[EMAIL PROTECTED]> writes:

>>I have just recently upgraded to the latest Cygwin and latest XEmacs.
>>Now, whenever I invoke a subprocess in XEmacs, all text in the XEmacs
>>frame goes blank. I am using zsh as my shell, but the problem always
>>occurs whether I am invoking a subshell, compiling, grepping, or running
>>gnu-serv. I am running Windows XP Pro SP1 and XEmacs 21.4.13.

My experience was similar, and the work-around I found successful was
to launch xemacs from rxvt/bash, rather than from the Task Bar or
Start Menu.  I spent a fair amount of time attempting to discover
whether there was an environment variable which accounted for this,
but failed.

If you're _really_ obsessive (like me :-( about launching from an
icon, compile the following and point the icon at it.

Hope this helps,

ht

#define WIN32

#include 
#include 
#include 
#include 
#include 
#include 

#include 

int WINAPI
WinMain (HINSTANCE hSelf, HINSTANCE hPrev, LPSTR cmdline, int nShow) {

   STARTUPINFO start;
   SECURITY_ATTRIBUTES sec_attrs;
   SECURITY_DESCRIPTOR sec_desc;
   PROCESS_INFORMATION child;
   int retval;

   memset (&start, 0, sizeof (start));
   start.cb = sizeof (start);
   start.dwFlags = STARTF_USESHOWWINDOW;
   start.wShowWindow = SW_HIDE;
  
   sec_attrs.nLength = sizeof (sec_attrs);
   sec_attrs.lpSecurityDescriptor = NULL;
   sec_attrs.bInheritHandle = FALSE;

   if (CreateProcess (NULL, "c:\\cygwin\\bin\\bash -c 
\"/usr/local/bin/i686-pc-cygwin/xemacs -f gnuserv-start\"", &sec_attrs, NULL, TRUE, 0,
  NULL, NULL, &start, &child))
   {
  CloseHandle (child.hThread);
  CloseHandle (child.hProcess);
   }
   else
 exit(1);
   return retval;

}

-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
  Half-time member of W3C Team
 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED]
 URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-04 Thread Christopher Faylor 
On Sat, Oct 04, 2003 at 07:45:44PM -0400, Yadin Y Goldschmidt wrote:
>No double slashes or backslashes for me.  After upgarding cygwin tp
>1.5.XXX Xemacs preview latex is no longer working, showing blank spaces
>where latex should be rendered.  In case you missed it I found this
>correspondence on the xemacs newsgroup:

I'm sorry.  I was reading on autopilot while doing something else and
responded to the wrong message.  Double backslashes should have nothing
to do with this.

We just like to break Xemacs from time to time, is all.  That's the only
reason why this stopped working.

But seriously, if anyone would like to be an official Xemacs liason and
officially test snapshots when they happen that would certainly be
welcome.  I will not be running Xemacs to test things, unfortunately.  I
would be glad to work with someone who was willing to test debug
versions of the Cygwin DLL and provide intelligent feedback on problems.

I'll even give an automatic subscription to cygwin-developers to anyone
who is willing to perform this service to the community.  I do this
because I know that Xemacs is a popular package and, despite what I said
above, I would like to ensure that it works correctly.

If someone is interested in doing this perhaps they might also be
interested in providing an Xemacs package for the cygwin distribution.
This would be automatically preapproved.

cgf

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-04 Thread Yadin Y Goldschmidt 
No double slashes or backslashes for me. After upgarding cygwin tp 1.5.XXX
Xemacs
preview latex is no longer working, showing blank spaces where latex should
be rendered.
In case you missed it I found this correspondence on the xemacs newsgroup:
Jerry James wrote:

>This bug affects both 21.4 and 21.5.  There have been reports on
>comp.emacs.xemacs about shell mode being broken on Cygwin/XP.  I traced
>the problem through the Lisp code, down to this call into the internals:
>
>(start-process-internal "shell" (get-buffer-create "*shell*") "/bin/sh"
"-i")
>
>That call alone is enough to demonstrate the problem.  After it returns,
>all newly typed characters display as red rectangles, menus pull down,
>but the mouse doesn't highlight anything, and other weird display
>problems occur.  If anybody has any idea where I should look, I'd
>appreciate a clue.
>
>Thanks,
>
>
In case you missed this because it was on another thread, this is the
response that I got from Andy Piper (andy at xemacs dot org) when I
reported the bug. Don't know whether it helps...

>> This behaviour is new to this release. Previous releases (many) have
>> been fine. However, I confess that I updated both Cygwin and XEmacs at
>> the same time so I don't know which update caused the breakage.
>
>
>
>So, predictably, they have almost certainly broken it in cygwin. The
special
>select() handling in cygwin for /dev/mswindows is only used by XEmacs and I
>suspect they have no tests for it.
>
>
Andy

-- 
Andy Rushton, Research Fellow, ECS Department, Southampton University

"Christopher Faylor" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Sat, Oct 04, 2003 at 11:59:15AM -0700, Terrence Brannon wrote:
> >Robert Getter wrote:
> >>I have just recently upgraded to the latest Cygwin and latest XEmacs.
> >>Now, whenever I invoke a subprocess in XEmacs, all text in the XEmacs
> >>frame goes blank. I am using zsh as my shell, but the problem always
> >>occurs whether I am invoking a subshell, compiling, grepping, or running
> >>gnu-serv. I am running Windows XP Pro SP1 and XEmacs 21.4.13.
> >
> >This happens for me too under bash! How annoying!
>
> Check for double backslashes or slashes in your PATH environment
> variable or in your HOME environment variable.
>
> cgf
>




--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-04 Thread Christopher Faylor 
On Sat, Oct 04, 2003 at 11:59:15AM -0700, Terrence Brannon wrote:
>Robert Getter wrote:
>>I have just recently upgraded to the latest Cygwin and latest XEmacs.
>>Now, whenever I invoke a subprocess in XEmacs, all text in the XEmacs
>>frame goes blank. I am using zsh as my shell, but the problem always
>>occurs whether I am invoking a subshell, compiling, grepping, or running
>>gnu-serv. I am running Windows XP Pro SP1 and XEmacs 21.4.13.
>
>This happens for me too under bash! How annoying!

Check for double backslashes or slashes in your PATH environment
variable or in your HOME environment variable.

cgf

--
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/

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

2003-10-04 Thread Terrence Brannon 
Robert Getter wrote:

I have just recently upgraded to the latest Cygwin and latest XEmacs.
Now, whenever I invoke a subprocess in XEmacs, all text in the XEmacs
frame goes blank. I am using zsh as my shell, but the problem always
occurs whether I am invoking a subshell, compiling, grepping, or running
gnu-serv. I am running Windows XP Pro SP1 and XEmacs 21.4.13.
 

This happens for me too under bash! How annoying!



--
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/