From mikets at frontline-pcb.com  Sun Sep  7 09:22:28 2008
From: mikets at frontline-pcb.com (Michael Tseitlin)
Date: Sun, 7 Sep 2008 09:22:28 +0300
Subject: Tcsh Digest, Vol 51, Issue 3
In-Reply-To: <mailman.1.1220691603.11160.tcsh@mx.gw.com>
References: <mailman.1.1220691603.11160.tcsh@mx.gw.com>
Message-ID: <830C82B0B852B9488F0A944853D4D012051D3FBB@uganda.FRONTLINE-PCB.COM>

Guys,

When running tcsh-6.15-amd64.exe (6.15.01) on Windows XP 64 bit I see
the same "No more processes" when running backquote commands, as I
reported few days ago for Windows 32.

Michael

-----Original Message-----
From: tcsh-bounces at mx.gw.com [mailto:tcsh-bounces at mx.gw.com] On Behalf
Of tcsh-request at mx.gw.com
Sent: Saturday, September 06, 2008 12:00 PM
To: tcsh at mx.gw.com
Subject: Tcsh Digest, Vol 51, Issue 3

Send Tcsh mailing list submissions to
	tcsh at mx.gw.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://mx.gw.com/mailman/listinfo/tcsh
or, via email, send a message with subject or body 'help' to
	tcsh-request at mx.gw.com

You can reach the person managing the list at
	tcsh-owner at mx.gw.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tcsh digest..."


Today's Topics:

   1. Re: Vista x64 (James Burgess)


----------------------------------------------------------------------

Message: 1
Date: Fri, 05 Sep 2008 13:56:30 -0700
From: James Burgess <jamesrburgess at mac.com>
Subject: Re: Vista x64
To: tcsh at mx.gw.com
Message-ID: <BE552E8A-4824-4F0D-8022-CA8A5A297619 at mac.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed


>
> Date: Sun, 24 Aug 2008 16:37:08 -0700
> From: "Amol Deshpande" <amol.vinayak.deshpande at gmail.com>
> Subject: Re: Vista x64
> To: "Tcsh development team" <tcsh at mx.gw.com>
> Cc: jamesrburgess at mac.com
>
> I've updated the binaries on ftp.astron.com with fixes for these
> issues. Unfortunately, I no longer have XP to test on, but I think the
> changes are not specific to the Windows version.
>
> Please let me know if there are any problems.
>
> thanks,
> -amol
>

Hi Amol,
	I been using the amd64 binary for a week now (on Vista 64) and
it  
seems solid except I have found a couple of my own apps that are  
launched in the foreground even though they are gui apps. I seem to  
recall tcsh pokes about in the PE header to determine what to do, I  
can't send you my binaries but I could chop out the header if you are  
interested. I'm using the icc10.1 compiler if that makes any  
difference. I guess I could also download source and step through  
with a debugger.

Thanks,

- James



------------------------------

_______________________________________________
Tcsh mailing list
Tcsh at mx.gw.com
http://mx.gw.com/mailman/listinfo/tcsh


End of Tcsh Digest, Vol 51, Issue 3
***********************************


From methfessel at ihp-microelectronics.com  Wed Sep 24 15:36:42 2008
From: methfessel at ihp-microelectronics.com (Michael Methfessel)
Date: Wed, 24 Sep 2008 14:36:42 +0200
Subject: tcsh 6.15 closes xterm windows unexpectedly
Message-ID: <002801c91e42$33102260$191e10ac@w2k.ihpffo.de>


Hello,

recently I upgraded from tcsh 6.14 to 6.15 under cygwin.
As a result, xterm windows running tcsh close at strange moments,
which is quite unsettling for the user!

Examples are:
 - killing Latex with Ctl-C when it waits for input
 - suspending emacs when it was invoked over a shellscript
 - changing to a non-existing directory when done via source and eval.

Here is the simplest example I could construct, based on the last point.
I made a shellscript called "bla" with the following lines:

#!/bin/tcsh -f
set cmd = "cd ~/bla"
echo cmd = $cmd
eval $cmd
echo "Here after eval"

Hereby directory ~/bla does not exist. 

Now, in an xterm running tcsh-6.15:
 - When I just type "bla", I get the expected message from cd that
   bla does not exist, but I don't see the echo on the last line.
 - When I type "source bla", my xterm window closes.

Under cygwin, I went back to tcsh-6.14 and the problems went away.
Also, no such strange behavior was ever seen under Linux or Solaris,
using various older tcsh versions. That is why I think this is 
a problem with tcsh, and not cygwin. 
 
Hopefully this report is useful in your maintenance of the 
otherwise splendid tcsh. 

Best wishes, 
Michael Methfessel