Re: R: Emacs silence

[Ken Brown]

On 10/31/2010 1:46 PM, Nigel Hardy wrote:

Thank you Eliot for the mail attachment suggestion. I attach the output
here.
Thank you Ken for the "cygcheck /usr/bin/emacs-X11.exe" suggestion - the
output seems good to me and is attached. Starting from mintty did not work.

 bash-3.2$ echo $DISPLAY
 127.0.0.1:0.0
 bash-3.2$ emacs
 bash-3.2$ emacs-X11.exe
 bash-3.2$ cygcheck -s -v -r>  cygcheck.out
 bash-3.2$ cygcheck /usr/bin/emacs-X11.exe>  cygcheck_emacs.out

I have also tried running the Xming server in place of Cygwin/X. This
displays "xterm" ok. but emacs-X11.exe fails silently in the same way.


[Please don't top-post.]

Your output from cygcheck /usr/bin/emacs-X11.exe is different from mine. 
 I get C:\cygwin\bin\cyggthread-2.0-0.dll right below 
C:\cygwin\bin\cyggobject-2.0-0.dll.  Did you by any chance edit the 
output and accidentally delete that line?  Otherwise, I don't understand 
why there's a difference.


Also, your cygcheck.out shows that you still have some remnants of an 
obsolete X server on your system.  For example, you have /usr/X11R6/bin 
in your path, and you have the following obsolete packages installed:


xorg-x11-base   7.4-1
xorg-x11-bin7.4-1
xorg-x11-bin-dlls   7.4-1
xorg-x11-bin-lndir  7.4-1
xorg-x11-etc7.4-1
xorg-x11-fenc   7.4-1
xorg-x11-fnts   7.4-1
xorg-x11-libs-data  7.4-1
xorg-x11-xwin   7.4-1

I don't know whether that's your problem or not, but you should 
uninstall them and get rid of /usr/X11R6/bin.  Also, you haven't said 
how you're starting the X server.  Are you by any chance using the 
obsolete startxwin.bat?


Ken

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

Re: SSH - Can't Login

[Brian Wilson]

> On 31 October 2010 17:12, Brian Wilson wrote:
> > In my case the context was that suddenly ssh stopped working and would only
> > give the usage message no matter what I tried.  I ran the "cygcheck -svr" 
and
> > noted that I did not have the latest Cygwin (1.7.7) installed even though
> > running setup said there was nothing needed.
> 
> Which probably means that you'd tried to update the cygwin package
> while a Cygwin process was running, told it to skip it when setup.exe
> complained about it, and forgot to reboot to trigger the delayed
> update. There have been reports of the delayed update not working
> under some circumstances, but nothing definitive.

I did leave processes running when I did the update; good guess, but nope I did 
not skip the restart.  I choose the continue option and whenever I got the 
restart message, I did a restart.  I believe I have the latest setup as well, 
but am going to get a new one just in case.  Hopefully this won't happen in 
future.


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

Re: SSH - Can't Login

[Andy Koppe]

On 31 October 2010 17:39, Andy Koppe wrote:
> On 31 October 2010 17:12, Brian Wilson wrote:
>> In my case the context was that suddenly ssh stopped working and would only
>> give the usage message no matter what I tried.  I ran the "cygcheck -svr" and
>> noted that I did not have the latest Cygwin (1.7.7) installed even though
>> running setup said there was nothing needed.
>
> Which probably means that you'd tried to update the cygwin package
> while a Cygwin process was running, told it to skip it when setup.exe
> complained about it, and forgot to reboot to trigger the delayed
> update. There have been reports of the delayed update not working
> under some circumstances, but nothing definitive.

Also, make sure you're using the latest setup.exe. A problem with the
handling of in-use packages was fixed earlier this year.

Andy

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

Re: SSH - Can't Login

[Andy Koppe]

On 31 October 2010 17:12, Brian Wilson wrote:
> In my case the context was that suddenly ssh stopped working and would only
> give the usage message no matter what I tried.  I ran the "cygcheck -svr" and
> noted that I did not have the latest Cygwin (1.7.7) installed even though
> running setup said there was nothing needed.

Which probably means that you'd tried to update the cygwin package
while a Cygwin process was running, told it to skip it when setup.exe
complained about it, and forgot to reboot to trigger the delayed
update. There have been reports of the delayed update not working
under some circumstances, but nothing definitive.

Andy

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

Re: SSH - Can't Login

[Andy Koppe]

On 31 October 2010 17:02, James Broadhead wrote:
> On 31 October 2010 16:51, Andy Koppe wrote:
>> On 31 October 2010 16:45, James Broadhead wrote:
>>> I also have this problem;
>>
>> Context?
>
> The 10 or so messages in the archive with the same subject line.

Might have been a good idea then to reply to one of those messages and
quote the relevant bits rather than start a new thread.

Also: http://www.cygwin.com/acronyms/#PCYMTNQREAIYR. (I thought those
were getting blocked these days?)

Andy

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

Re: SSH - Can't Login

[Brian Wilson]

> On 31 October 2010 16:45, James Broadhead wrote:
> > I also have this problem;
> 
> Context?
> 
> >>> ssh ja...@192.168.1.15
> > usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
> >           [-D [bind_address:]port] [-e escape_char] [-F configfile]
> >           [-I pkcs11] [-i identity_file]
> >           [-L [bind_address:]port:host:hostport]
> >           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
> >           [-R [bind_address:]port:host:hostport] [-S ctl_path]
> >           [-W host:port] [-w local_tun[:remote_tun]]
> >           [u...@]hostname [command]
> >
> >>> ssh -p 1022 ja...@localhost
[UTF-8?]> > Bad port '�y"a'
> >
> > Here are strace output for:
> > - OpenSSH_5.6p1, OpenSSL 0.9.8l 5 Nov 2009  -
> > http://obviouslies.net/share/strace-new-ssh
> > and
> > - OpenSSH_5.5p1, OpenSSL 0.9.8o 01 Jun 2010  -
> > http://obviouslies.net/share/strace-old-ssh
> >
> > SFVs of my cygwin1.dll for the old and new environments:
> > cygwin1-new.dll B6328143
> > cygwin1-old.dll   DFB07A25
> >
> > Anything else that I can add that would be useful?
> 
> http://cygwin.com/problems.html

In my case the context was that suddenly ssh stopped working and would only 
give the usage message no matter what I tried.  I ran the "cygcheck -svr" and 
noted that I did not have the latest Cygwin (1.7.7) installed even though 
running setup said there was nothing needed.  I confirmed this by opening a 
bash shell and running "uname -a" command.

I rebooted my PC in safe mode with networking and ran setup with cygwin and 
cygserver set to reinstall.  I rebooted and opened a bash shell again and 
reran the uname -a command to confirm the update was working.  I then ran the 
ssh  and got the expected login prompts.

Hope this helped.

Brian S. Wilson

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

Re: SSH - Can't Login

[James Broadhead]

On 31 October 2010 16:51, Andy Koppe  wrote:
> On 31 October 2010 16:45, James Broadhead wrote:
>> I also have this problem;
>
> Context?

The 10 or so messages in the archive with the same subject line.

On 31 October 2010 13:28, Brian Wilson  wrote:
> Looks like the "gummed up" diagnosis was the correct one.  I restarted my
> system in safe mode with networking and ran setup.  It reported nothing needed
> to be updated (looks like setup has an issue with detecting differences
> between what is actually running, and what should be installed; but that is a
> different debate).

I'll try this + will report back.

JB

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

Re: SSH - Can't Login

[Andy Koppe]

On 31 October 2010 16:45, James Broadhead wrote:
> I also have this problem;

Context?

>>> ssh ja...@192.168.1.15
> usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
>           [-D [bind_address:]port] [-e escape_char] [-F configfile]
>           [-I pkcs11] [-i identity_file]
>           [-L [bind_address:]port:host:hostport]
>           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
>           [-R [bind_address:]port:host:hostport] [-S ctl_path]
>           [-W host:port] [-w local_tun[:remote_tun]]
>           [u...@]hostname [command]
>
>>> ssh -p 1022 ja...@localhost
> Bad port '�y"a'
>
> Here are strace output for:
> - OpenSSH_5.6p1, OpenSSL 0.9.8l 5 Nov 2009  -
> http://obviouslies.net/share/strace-new-ssh
> and
> - OpenSSH_5.5p1, OpenSSL 0.9.8o 01 Jun 2010  -
> http://obviouslies.net/share/strace-old-ssh
>
> SFVs of my cygwin1.dll for the old and new environments:
> cygwin1-new.dll B6328143
> cygwin1-old.dll   DFB07A25
>
> Anything else that I can add that would be useful?

http://cygwin.com/problems.html

Andy

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

SSH - Can't Login

[James Broadhead]

I also have this problem;

>> ssh ja...@192.168.1.15
usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
          [-D [bind_address:]port] [-e escape_char] [-F configfile]
          [-I pkcs11] [-i identity_file]
          [-L [bind_address:]port:host:hostport]
          [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
          [-R [bind_address:]port:host:hostport] [-S ctl_path]
          [-W host:port] [-w local_tun[:remote_tun]]
          [u...@]hostname [command]

>> ssh -p 1022 ja...@localhost
Bad port '�y"a'

Here are strace output for:
- OpenSSH_5.6p1, OpenSSL 0.9.8l 5 Nov 2009  -
http://obviouslies.net/share/strace-new-ssh
and
- OpenSSH_5.5p1, OpenSSL 0.9.8o 01 Jun 2010  -
http://obviouslies.net/share/strace-old-ssh

SFVs of my cygwin1.dll for the old and new environments:
cygwin1-new.dll B6328143
cygwin1-old.dll   DFB07A25

Anything else that I can add that would be useful?

James Broadhead

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

Re: Cygwin c compiler and c99

[Andy Koppe]

On 31 October 2010 14:39, David wrote:
> By adding #include  it worked.
>
> Den 31-10-2010 14:45, Tim Prince skrev:
>>
>> On 10/31/2010 6:21 AM, David wrote:
>>>
>>> Does Cygwin c compiler not support c99?
>>> or does c99 not support?:
>>>
>>> #include 
>>> #include 
>
> #include 
>>>
>>> int main(void) {
>>> bool f=true;
>>> for(int i=0; i<10; i++) {
>>> if (f)
>>> printf("%d\n",i);
>>> }
>>> puts("Hello World!!!"); /* prints Hello World!!! */
>>> return EXIT_SUCCESS;
>>> }
>>>
>
>
> But why do I have to include ?

Because 'bool', 'true' and 'false' are not defined in the C99
language, but in the C99 library, as macros in the stdbool.h header.
The language only defines the type _Bool with vaues 0 and 1.

See also:
http://www.codinghorror.com/blog/2008/03/the-first-rule-of-programming-its-always-your-fault.html

Andy

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

Re: Cygwin c compiler and c99

[David]

By adding #include  it worked.

Den 31-10-2010 14:45, Tim Prince skrev:

On 10/31/2010 6:21 AM, David wrote:


Does Cygwin c compiler not support c99?
or does c99 not support?:

#include 
#include 

#include 


int main(void) {
bool f=true;
for(int i=0; i<10; i++) {
if (f)
printf("%d\n",i);
}
puts("Hello World!!!"); /* prints Hello World!!! */
return EXIT_SUCCESS;
}




But why do I have to include ?


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

Re: Cygwin c compiler and c99

[David]

Your result is right but I get

$ gcc -O -Wall -pedantic -std=c99 testC.c
testC.c: In function 'main':
testC.c:15: error: 'bool' undeclared (first use in this function)
testC.c:15: error: (Each undeclared identifier is reported only once
testC.c:15: error: for each function it appears in.)
testC.c:15: error: expected ';' before 'f'
testC.c:17: error: 'f' undeclared (first use in this function)


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

Re: Cygwin c compiler and c99

[Tim Prince]

On 10/31/2010 6:21 AM, David wrote:


Does Cygwin c compiler not support c99?
or does c99 not support?:

#include 
#include 

int main(void) {
bool f=true;
for(int i=0; i<10; i++) {
if (f)
printf("%d\n",i);
}
puts("Hello World!!!"); /* prints Hello World!!! */
return EXIT_SUCCESS;
}

Here the bool declaration fails and so do the for statement. The 
compiler doesn't like that I use the iteration variable inside the 
for-loop.


Neither I nor the compiler see a declaration of bool there.  Is this 
example what you intended?

After defining bool and true in terms of _Bool
gcc -O -Wall -pedantic -std=c99 djb.c
$ ./a
0
1
2
3
4
5
6
7
8
9
Hello World!!!

--
Tim Prince


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

Cygwin c compiler and c99

[David]

Does Cygwin c compiler not support c99?
or does c99 not support?:

#include 
#include 

int main(void) {
bool f=true;
for(int i=0; i<10; i++) {
if (f)
printf("%d\n",i);
}
puts("Hello World!!!"); /* prints Hello World!!! */
return EXIT_SUCCESS;
}

Here the bool declaration fails and so do the for statement. The 
compiler doesn't like that I use the iteration variable inside the for-loop.

What shall I do to fix it?

Cygwin 1.7.7, Eclipse Helios, Windows 7


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

Re: SSH - Can't Login (3rd Post)

[Brian Wilson]

> 
> No, if it's reporting 1.7.1, I expect that's the version you're running.
> And I expect that's coming into play here.  But go ahead and double check
> it in the Windows explorer.  I expect you'll find it reports 1.7.1 too.
> 
> This is a problem.  I expect you know that you need to stop all your
> services before an upgrade in order to get the new DLL moved into place
> immediately, right?  If you don't do this, it will queue up the move 
> for next reboot.  My guess is you've rebooted at least once since installing
> 
> 1.7.x > 1.7.1 but it's possible things have gotten gummed up if you didn't
> and have since done other upgrades (that's pure theory though).  What's
> not is that you have ZoneAlarm installed that is known to cause problems.
> I'd recommend unstalling it, stopping all Cygwin services (cron, 
> cygserver, httpd2, and sshd), reinstall the Cygwin package, and then 
> restart the services.  You should find this process gives you a 
> current cygwin1.dll in '/bin'.  If not, we need to look at the 
> results of the installation process (and/or for 
>  ).

Looks like the "gummed up" diagnosis was the correct one.  I restarted my 
system in safe mode with networking and ran setup.  It reported nothing needed 
to be updated (looks like setup has an issue with detecting differences 
between what is actually running, and what should be installed; but that is a 
different debate).

I opened a Cygwin bash shell and ran the "uname -a" command and it still 
reported release 1.7.1, not 1.7.7.  I reran the setup and reinstalled Cygwin 
and cygserver then rebooted the system back to its normal operations mode.  
Once the system was up and stable I restarted the bash shell and got a series 
of stack dumps with complaints about timing out waiting for a return from a 
long jump (another issue for another time).  I closed the window and did the 
insane thing (repeated opening of a bash shell hoping for a different result). 
and this time I got a working shell prompt.

I ran the "uname -a" command and this time it returned the 1.7.7 version.  
Next, I did an ssh to my own machine "ssh ncc-1701" and was able to get the 
expected prompts for a login.  Ssh appears to be working again.

Thank you all for your help and suggestions.  It is community support and 
cooperation, as well as support from the Dev team that keeps Cygwin one of the 
most popular *nix like environments for Windoze.

Sincerely,

Brian S. Wilson

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

Re: R: Emacs silence

[Eliot Moss]

In my first e-mail I failed to attached the Xwin log and the cygcheck output. I have just tried that 
and 209.132.180.131 bounced it as spam.


How should I make those available?

Nigel

The log files have an email address in them.
Look for the @ character.  Delete the email
or rewrite it to read "foo at bar" instead
of "f...@bar".  I have suggested that the logs
output the email that way, but that suggestion
has not been taken up yet ...

Eliot Moss

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

Re: R: Emacs silence

[Ken Brown]

On 10/31/2010 6:00 AM, Marco Atzeri wrote:

--- Dom 31/10/10, Nigel Hardy  ha scritto:


When I try to start my new emacs
under X from bash, I get complete silence. This happens with
"emacs" and directly with "emacs-X11.exe".
"emacs-nox.exe" starts up fine.

I have just upgraded to emacs 23.2-3 (from, I believe a 22
version - I have no record of what was replaced).

I am running cygwin 1.7.7 as follows:

bash-3.2$ uname -a
CYGWIN_NT-6.0 pcpnwh 1.7.7(0.230/5/3)
2010-08-31 09:58 i686 Cygwin
bash-3.2$

I am running Vista with all patches as far as I can tell.

I have tried returning to emacs 23.2-1 but that shows the
same (lack of) behaviour. I fear that I am guilty of
ignoring an earlier error. I was on an old version of emacs
because I had a problem a while back which I solved quickly
by returning to an earlier version. That earlier version is
now not available directly from set up so I have got
caught.

I don't even know where to start with diagnosing what is
happening. Any suggestions?



start here
Problem reports:   http://cygwin.com/problems.html

It seems a dll missing problem


Two further suggestions for the OP.  First, run 'cygcheck 
/usr/bin/emacs-X11.exe' to see if it reports a missing dll.  Second, try 
running emacs-X11 in a non-X terminal (like mintty).


Ken


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

Re: R: Emacs silence

[Nigel Hardy]

In my first e-mail I failed to attached the Xwin log and the cygcheck 
output. I have just tried that and 209.132.180.131 bounced it as spam.


How should I make those available?

Nigel

Marco Atzeri wrote:

--- Dom 31/10/10, Nigel Hardy  ha scritto:

  

When I try to start my new emacs
under X from bash, I get complete silence. This happens with
"emacs" and directly with "emacs-X11.exe".
"emacs-nox.exe" starts up fine.

I have just upgraded to emacs 23.2-3 (from, I believe a 22
version - I have no record of what was replaced).

I am running cygwin 1.7.7 as follows:

   bash-3.2$ uname -a
   CYGWIN_NT-6.0 pcpnwh 1.7.7(0.230/5/3)
2010-08-31 09:58 i686 Cygwin
   bash-3.2$

I am running Vista with all patches as far as I can tell.

I have tried returning to emacs 23.2-1 but that shows the
same (lack of) behaviour. I fear that I am guilty of
ignoring an earlier error. I was on an old version of emacs
because I had a problem a while back which I solved quickly
by returning to an earlier version. That earlier version is
now not available directly from set up so I have got
caught.

I don't even know where to start with diagnosing what is
happening. Any suggestions?




start here
Problem reports:   http://cygwin.com/problems.html

It seems a dll missing problem

  

Nigel







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

  



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

R: Emacs silence

[Marco Atzeri]

--- Dom 31/10/10, Nigel Hardy  ha scritto:

> When I try to start my new emacs
> under X from bash, I get complete silence. This happens with
> "emacs" and directly with "emacs-X11.exe".
> "emacs-nox.exe" starts up fine.
> 
> I have just upgraded to emacs 23.2-3 (from, I believe a 22
> version - I have no record of what was replaced).
> 
> I am running cygwin 1.7.7 as follows:
> 
>    bash-3.2$ uname -a
>    CYGWIN_NT-6.0 pcpnwh 1.7.7(0.230/5/3)
> 2010-08-31 09:58 i686 Cygwin
>    bash-3.2$
> 
> I am running Vista with all patches as far as I can tell.
> 
> I have tried returning to emacs 23.2-1 but that shows the
> same (lack of) behaviour. I fear that I am guilty of
> ignoring an earlier error. I was on an old version of emacs
> because I had a problem a while back which I solved quickly
> by returning to an earlier version. That earlier version is
> now not available directly from set up so I have got
> caught.
> 
> I don't even know where to start with diagnosing what is
> happening. Any suggestions?


start here
Problem reports:   http://cygwin.com/problems.html

It seems a dll missing problem

> Nigel
> 




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

Emacs silence

[Nigel Hardy]

When I try to start my new emacs under X from bash, I get complete 
silence. This happens with "emacs" and directly with "emacs-X11.exe".

"emacs-nox.exe" starts up fine.

I have just upgraded to emacs 23.2-3 (from, I believe a 22 version - I 
have no record of what was replaced).


I am running cygwin 1.7.7 as follows:

   bash-3.2$ uname -a
   CYGWIN_NT-6.0 pcpnwh 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin
   bash-3.2$

I am running Vista with all patches as far as I can tell.

I have tried returning to emacs 23.2-1 but that shows the same (lack of) 
behaviour. I fear that I am guilty of ignoring an earlier error. I was 
on an old version of emacs because I had a problem a while back which I 
solved quickly by returning to an earlier version. That earlier version 
is now not available directly from set up so I have got caught.


I don't even know where to start with diagnosing what is happening. Any 
suggestions?



Nigel


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