Re: Portable shell code between Cygwin and Linux

2011-08-07 Thread Eliot Moss
On 8/7/2011 9:16 PM, Sven Köhler wrote: Am 30.07.2011 14:14, schrieb Andrey Repin: Greetings, Corinna Vinschen! For every shell code that I write, I'd like it to be portable both to Cygwin on Windows, and to Ubuntu Linux for example. It's kinda possible, but am blocked with such a use case:

Re: Portable shell code between Cygwin and Linux

2011-08-07 Thread Sven Köhler
Am 02.08.2011 14:24, schrieb Sebastien Vauban: > I don't like copy/pasting things, and just changing bits of the code, if I can > avoid it. if you detect cygwin: pathconvert() { // do cygwin specific path conversion of $1 } if you don't detect cygwin pathconvert() { echo "$1" } Use the pa

Re: Portable shell code between Cygwin and Linux

2011-08-07 Thread Sven Köhler
Am 30.07.2011 14:14, schrieb Andrey Repin: > Greetings, Corinna Vinschen! > >>> For every shell code that I write, I'd like it to be portable both to Cygwin >>> on Windows, and to Ubuntu Linux for example. >>> >>> It's kinda possible, but am blocked with such a use case: >>> >>> alias vpnup='exec

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Ken Brown
On 8/7/2011 4:02 PM, Corinna Vinschen wrote: On Aug 7 12:18, Ken Brown wrote: On 8/7/2011 10:43 AM, Ken Brown wrote: On 8/7/2011 7:50 AM, Corinna Vinschen wrote: I did set breakpoints to all functions returning malloc information, but emacs doesn't call one of them. Is there a chance that em

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Ken Brown
On 8/7/2011 4:02 PM, Corinna Vinschen wrote: On Aug 7 12:18, Ken Brown wrote: On 8/7/2011 10:43 AM, Ken Brown wrote: On 8/7/2011 7:50 AM, Corinna Vinschen wrote: I did set breakpoints to all functions returning malloc information, but emacs doesn't call one of them. Is there a chance that em

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Corinna Vinschen
On Aug 7 12:18, Ken Brown wrote: > On 8/7/2011 10:43 AM, Ken Brown wrote: > >On 8/7/2011 7:50 AM, Corinna Vinschen wrote: > >>>I did set breakpoints to all functions returning malloc information, > >>>but emacs doesn't call one of them. Is there a chance that emacs > >>>does some invalid 32 bit p

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Ken Brown
On 8/7/2011 10:43 AM, Ken Brown wrote: On 8/7/2011 7:50 AM, Corinna Vinschen wrote: On Aug 7 13:33, Corinna Vinschen wrote: On Aug 5 19:16, Ken Brown wrote: Starting with the 2011-07-21 snapshot, emacs doesn't work well with the large-address-awareness flag set (under 64-bit Win7). As soon

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Ken Brown
On 8/7/2011 7:50 AM, Corinna Vinschen wrote: On Aug 7 13:33, Corinna Vinschen wrote: On Aug 5 19:16, Ken Brown wrote: Starting with the 2011-07-21 snapshot, emacs doesn't work well with the large-address-awareness flag set (under 64-bit Win7). As soon as emacs is started, a *Warning* buffer

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Corinna Vinschen
On Aug 7 13:33, Corinna Vinschen wrote: > On Aug 5 19:16, Ken Brown wrote: > > Starting with the 2011-07-21 snapshot, emacs doesn't work well with > > the large-address-awareness flag set (under 64-bit Win7). As soon > > as emacs is started, a *Warning* buffer is created with the > > following m

Re: pb w/ cygpath -w /dev/sdXY (was Re: Device names in /proc/mounts)

2011-08-07 Thread Corinna Vinschen
On Aug 7 01:53, Cyrille Lefevre wrote: > some times ago, someone (you?) modifies cygpath to handle /dev/sdXY paths. > > however, it seems there is a problem somewhere ? > > v2$ uname -a > CYGWIN_NT-6.0 pcvista 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin > > v2$ /usr/sbin/blkid > /dev/sda1: LA

Re: emacs and large-address awareness under recent snapshots

2011-08-07 Thread Corinna Vinschen
On Aug 5 19:16, Ken Brown wrote: > Starting with the 2011-07-21 snapshot, emacs doesn't work well with > the large-address-awareness flag set (under 64-bit Win7). As soon > as emacs is started, a *Warning* buffer is created with the > following message: > > Emergency (alloc): Warning: past 95%

Re: mintty --log overwrites existing logfile in place

2011-08-07 Thread Csaba Raduly
On Sat, Aug 6, 2011 at 12:37 PM, Christian Franke wrote: > Agree, e.g. "--log +FILE" appends to FILE: > > client.c: >  // Open log file if any >  if (*cfg.log) { >    if (cfg.log[0] == '+' && cfg.log[1]) >      log_fd = open(cfg.log+1, O_WRONLY | O_CREAT | O_APPEND, 0600); >    else >      log_fd

Re: New problem with 20110803

2011-08-07 Thread Corinna Vinschen
On Aug 7 03:51, Yaakov (Cygwin/X) wrote: > There's another problem with the 20110803 snapshot. When a fork fails > with the following message: > >0 [main] cmake 5088 child_info_fork::abort: address space > needed by 'cyggcc_s-1.dll' (E20A) is already occupied > > ALL user processes

New problem with 20110803

2011-08-07 Thread Yaakov (Cygwin/X)
There's another problem with the 20110803 snapshot. When a fork fails with the following message: 0 [main] cmake 5088 child_info_fork::abort: address space needed by 'cyggcc_s-1.dll' (E20A) is already occupied ALL user processes except for mintty, even those in other terminal windows,