Re: sftp progress showing ... 66% complete

Robert Body wrote: > ok it appears my problem is with my script, not sftp: > > specifically with using tee or > in the command: (time $mycommand) 2>&1 | > tee $tempFile The sftp program, like many others (e.g. scp) will only output status information if stdout is a tty. When you redirect to a f

Re: [ANNOUNCEMENT] Updated: zsh-4.2.6-1

On Thu, 8 Dec 2005 16:28:04 -0800 (PST), wrote: >On Thu, 8 Dec 2005, zzapper wrote: > >> On Thu, 8 Dec 2005 09:55:51 -0800 (PST), wrote: >> >>> Fresh from the oven, an updated version of zsh (zsh-4.2.6-1) has been >>> freshly baked and should be at a mirror near you real soon. >>> >> Hi Peter, >

Re: "type ahead" bug with cygwin

Robert Body, le Fri 09 Dec 2005 20:01:49 -0700, a écrit : > During an ftp session, when the shell was tied up for 15 minutes, I typed > something, and of course it was echoed, but when the ftp session completed, > the commands I typed were lost, no action was taken. Mmm, are you sure? There is

1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

Hi, On a Windows XP SP2 I have installed cygwin 1.5.18-1 (the latest as for now). When I launch cygwin.bat, I have: C:\cygwin\bin\bash.exe (3652): *** system shared memory version mismatch detected - 0x75BE0074/0x75BE0084. This problem is probably due to using incompatible versions of the cygw

Re: [ANNOUNCEMENT] Updated: zsh-4.2.6-1

On Sat, 10 Dec 2005, zzapper wrote: > As you suggested, an uninstalof zsh l followed by install cleared the > problem. > > I would guess that when one runs setup.exe and the shell itself is being > updated zsh bash etc it would be best to close all running shells? Yes, that would be good, since W

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

On Sat, 10 Dec 2005, JeDi wrote: > Hi, > > On a Windows XP SP2 I have installed cygwin 1.5.18-1 (the latest as > for now). When I launch cygwin.bat, I have: > > C:\cygwin\bin\bash.exe (3652): *** system shared memory version mismatch > detected - 0x75BE0074/0x75BE0084. > This problem is probably

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

> Please read and follow the Cygwin problem reporting > guidelines at > , especially the > part that asks you to > attach (as an uncompressed text attachment) the > output of "cygcheck -svr" > on your system. > Here is the output of 'cygcheck -svr'. I didn't attac

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

JeDi wrote: > Here is the output of 'cygcheck -svr'. I didn't > attached it in the first place because it produce > itself lot of those 'shared memory vesion mismatch'. Found: C:\Program Files\OpenSSH\bin\ls.exe Found: C:\Program Files\OpenSSH\bin\rm.exe Found: C:\Program Files\OpenSSH\bin\sh.exe

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

--- Brian Dessent <[EMAIL PROTECTED]> wrote: > Found: C:\Program Files\OpenSSH\bin\ls.exe > Found: C:\Program Files\OpenSSH\bin\rm.exe > Found: C:\Program Files\OpenSSH\bin\sh.exe > > That directory contains a bunch of unix like tools > and probably a > foreign, incompatible version of cygwin1.d

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

JeDi wrote: > Sure Brian, but bash.exe is present nowhere but in my > cygwin\bin directory, and bash doesn't work. I agree > with you that my computer is kind of a mess but I > don't think this is the root cause. Actually, i've set > up my environment variable with cygwin\bin in the > first positi

Re: gnuplot dependency in octave

> Chris Taylor writes: > How about having a gnuplot-nox package like debian, which satisfies > the dependancy, and having gnuplot-x-drivers available separately? > It could be referenced in the README easily enough, and wouldn't be > too hard to find.. Currently not only /usr/

Re: octave-forge dependency?

> James R Phillips writes: > BTW, the gnuplot version in Debian sarge behaves exactly the same way as the > cygwin version in response saving a file if kpsexpand is not present. And > Debian does not list tetex-bin as a dependency for gnuplot. Probably this > needs to be res

New gnuplot setup.hint file

Hi Until the problem with gnuplot calling kpsexpand unconditionally is sorted out here is a new setup.hint file for gnuplot: Please upload. --- cut here sdesc: "A command-line driven interactive function plotting utility." ldesc: "Gnuplot is a

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

On Sat, Dec 10, 2005 at 09:20:42AM -0800, Brian Dessent wrote: >JeDi wrote: >>Sure Brian, but bash.exe is present nowhere but in my cygwin\bin >>directory, and bash doesn't work. I agree with you that my computer is >>kind of a mess but I don't think this is the root cause. Actually, >>i've set u

Re: New gnuplot setup.hint file

On Sat, Dec 10, 2005 at 06:30:09PM +0100, Dr. Volker Zell wrote: >Hi > >Until the problem with gnuplot calling kpsexpand unconditionally is >sorted out here is a new setup.hint file for gnuplot: Done. I really think your ldesc is too long however. While there are a couple of other examples of pe

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

> It's irrelevent what the name of the .exe is. As > Igor already said, > even if a third party packages a cygwin1.dll that > has simply been > renamed, it will still have the same shared memory > name, so that if the > two DLLs are ever loaded at the same time they will > clash. This is > exactl

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

> > Maybe this has been mentioned already but it looks > like these recent > openssh problems may be due to this idiotic site: > > http://sshwindows.sourceforge.net/download/ > > Anyone want to take a stab at getting it taken down? > It hasn't been > updated in more than a year and it is obvio

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

> > Maybe this has been mentioned already but it looks > like these recent > openssh problems may be due to this idiotic site: > > http://sshwindows.sourceforge.net/download/ > > Anyone want to take a stab at getting it taken down? > It hasn't been > updated in more than a year and it is obvio

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

On Sat, 10 Dec 2005, JeDi wrote: > > It's irrelevent what the name of the .exe is. As Igor already said, > > even if a third party packages a cygwin1.dll that has simply been > > renamed, it will still have the same shared memory name, so that if > > the two DLLs are ever loaded at the same time

Re: Call for testing Cygwin snapshot

> Corinna Vinschen writes: > Since we're much too long on the way to the 1.5.19 release and there > are already way too many changes since 1.5.18, we would again like to > ask people for testing the latest snapshot, 2005-Nov-30, from > http://www.cygwin.com/snapshots/ >

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

> filename. Is there a way to > > know which dll is loaded in memory and which > filename or program it is > > loaded from ? > > Yes, you could try using ProcessExplorer or some > other tools (e.g., > "handle") from SysInternals.com (ProcessExplorer can > give you a list of > all loaded DLLs, for

Slow responsiveness on keypresses in Mutt

Hello. When I use the cygwin Bash Shell (the cmd.exe console) and use Mutt as my mail reader, sometimes hitting d for delete, or other keys works instantaneously. Other times, it takes up to a second to process the request, when it is normally instantaneous. What can I do to debug and/or fix thi

Re: sftp progress showing ... 66% complete

Thanks for the input, Brian, I was trying to have the script re-direct output to a file (well actually just the final command of _time_ command was what mattered), but I guess that meant the sftp progress % went to a file too, but strange thing is, the other Stdout messages like "Uploading..." a

Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected"

Igor Pechtchanski wrote: > Yes, you could try using ProcessExplorer or some other tools (e.g., > "handle") from SysInternals.com (ProcessExplorer can give you a list of > all loaded DLLs, for example). However, I don't think they will let you > search by the shared memory region name... You can

Re: sftp progress showing ... 66% complete

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ugh. Top-posting. http://cygwin.com/acronyms#TOFU >> From: Brian Dessent ^ Ugh. http://cygwin.com/acronyms/#PCYMTNQREAIYR According to Robert Body on 12/10/2005 2:01 PM: > I don't know how to handle X-

Re: sftp progress showing ... 66% complete

Robert Body wrote: > Thanks for the input, Brian, I was trying to have the script re-direct > output to a file (well actually just the final command of _time_ command was > what mattered), but I guess that meant the sftp progress % went to a file > too, but strange thing is, the other Stdout messa

[openjade] port incomplete - lacks default catalogs

Hello. I'm a part of PHP and PEAR documentation team and I'd like to switch from Jade to OpenJade in our documentation building process, which uses DSSSL stylesheets. It will be nice to have doc building system on windows completely installed from Cygwin environment. Unfortunately to successfully

Re: sftp progress showing ... 66% complete

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://cygwin.com/acronyms/#PPIOSPE Ugh - top-posted. Reformatted. http://cygwin.com/acronyms/#TOFU >> From: Eric Blake ^ Ugh - http://cygwin.com/acronyms/#PCYMTNQREAIYR > > If you use bash, $(( x - y )) does

Re: 'uptime' command producing incorrect uptime

On Sat, 10 Dec 2005, Jack wrote: > It appears to me that the uptime command is not producing the correct > uptime and, in fact, is running twice as fast as it should be. > [...] I've noticed a similar effect recently, and looked in the sources. If you take a look at the algorithm used by cygwin (

Re: d_ino deprecated in latest snapshot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 12/5/2005 2:26 PM: > I've deprecated dirent's d_ino field in the latest snapshot. I've taken > this step because in the majority of cases this field was different from > the inode field returned by stat() and this pr

Re: d_ino deprecated in latest snapshot

On Sat, Dec 10, 2005 at 04:09:16PM -0700, Eric Blake wrote: >According to Christopher Faylor on 12/5/2005 2:26 PM: >>I've deprecated dirent's d_ino field in the latest snapshot. I've >>taken this step because in the majority of cases this field was >>different from the inode field returned by stat

Re: [ANNOUNCEMENT] Updated: zsh-4.2.6-1

On Sat, 10 Dec 2005 10:40:49 -0500 (EST), wrote: >On Sat, 10 Dec 2005, zzapper wrote: > >> As you suggested, an uninstalof zsh l followed by install cleared the >> problem. >> >> I would guess that when one runs setup.exe and the shell itself is being >> updated zsh bash etc it would be best to c