Re: cygpath -m behaviour change

2013-09-19 Thread Robert Klemme
On Thu, Sep 19, 2013 at 3:23 PM, David Griffiths wrote: >> But why are you even using cygpath to try and determine the containing >> directory? 'dirname' does that task, in a much more portable manner, >> and without having to worry about whether 'file/..' can be abused in >> spite of POSIX seman

Re: About ssh

2013-09-21 Thread Robert Klemme
On Fri, Sep 20, 2013 at 11:36 PM, Javier Vasquez wrote: > Hi, > > I'm able to perform: > > % ssh localhost > > From cygwing. But I'm unable to perform: > > % ssh > > I always get: > > -- > ssh: connect to host 192.168.2.103 port 22: Connection timed out > -- > > The client works well hooking to

Re: 1.7.25: problem with the cd command in ksh

2013-10-05 Thread Robert Klemme
On Sat, Oct 5, 2013 at 8:33 AM, Francis ANDRE wrote: > Hi Cygwin List > > I have a problem with the cd command in a ksh script. In the log below, > there is this error: > /make/scripts/webrev.ksh[2899]: cd: > /cygdrive/z/DEV/OpenJDK_7u40/hotspot/Z:/DEV/OpenJDK_7u40/hotspo > t/make/windows/makefile

Re: 1.7.25: problem with the cd command in ksh

2013-10-06 Thread Robert Klemme
On Sun, Oct 6, 2013 at 10:49 AM, Francis ANDRE wrote: > Hi Robert > > The problem here is that the string of the target directory is computed by > another tool -- Mercurial in this case -- and that Mercurial returns a > absolute windows style path as > > Z:/DEV/OpenJDK_7u40/hotspot > > which seems

Re: 1.7.25: problem with the cd command in ksh

2013-10-07 Thread Robert Klemme
On Mon, Oct 7, 2013 at 7:00 PM, Christopher Faylor wrote: > On Mon, Oct 07, 2013 at 06:44:56PM +0200, Francis ANDRE wrote: >>Le 07/10/2013 11:54, Andrey Repin a ?crit : Can I have a official statement from Cygwin about this? ie that bash is supporting MS-DOX path by accident and ksh wo

Re: transfering cygwin configuration from win XP to win 7

2013-10-09 Thread Robert Klemme
On Tue, Oct 8, 2013 at 11:33 PM, Chris Olin wrote: > I recently did this at work by backing up the C:\cygwin directory, my > Windows user profile directory and manually creating the directory > path C:\cygwin\etc\setup, then copying > C:\cygwin\etc\setup\installed.db to the new computer, running t

Re: Telnet in latest Cygwin

2013-10-28 Thread Robert Klemme
On Sun, Oct 27, 2013 at 7:15 PM, Ralph Siegler wrote: > Corinna Vinschen writes: > > I'd suggest to use ssh instead. >> Telnet is inherently unsecure and ssh is a wonderful replacement. > but telnet is an invaluable tool for command line troubleshooting tcp > network connectivity issues to SMTP,

Win 7 claims setup-x86_64.exe doesn't work any more - but it does

2013-11-28 Thread Robert Klemme
Folks, since the last update of my cygwin 64 installer during the execution I get a Windows pop up indicating that the program does not work any more. Funny thing is: it does. I just click "cancel" and the installation proceeds normally. It even happens if I start the program and click cancel on

Re: Win 7 claims setup-x86_64.exe doesn't work any more - but it does

2013-11-28 Thread Robert Klemme
Hi Corinna, On Thu, Nov 28, 2013 at 2:09 PM, Corinna Vinschen wrote: > On Nov 28 10:24, Robert Klemme wrote: >> since the last update of my cygwin 64 installer during the execution I >> get a Windows pop up indicating that the program does not work any >> more. Funny thin

Re: getting windows ntfs file info

2014-01-01 Thread Robert Klemme
On Mon, Dec 30, 2013 at 9:22 AM, Jon Retting wrote: > Hello, > Typed up this one liner function for getting a files actual windows > details/properties information. I needed a tertiary way to compare > executable/drivers, so a version number from windows seemed like a viable > option. Hope

Re: Clearing the buffer after quitting LESS, MAN, VIM etc.

2014-01-05 Thread Robert Klemme
On Sat, Jan 4, 2014 at 4:58 AM, Dawid Ferenczy wrote: > Christopher Faylor cygwin.com> writes: > >> Problems like that interfere with my sleep so it's best to get them out >> of the way before I go to bed. > that's the difference between real programmers and other coders. Real > programmer can't

$PATH contains dot but unclear where it comes from

2014-02-06 Thread Robert Klemme
Hi, in cygwin64 on Win 7 64 bit I find "." in $PATH: $ echo "$PATH" | tr : \\n | egrep '^\.$' . However, I was not able to detect where this came from. It's neither in the Windows system environment variables nor in the user environment variables - as you can also see on a cmd prompt: C:\Users

Re: $PATH contains dot but unclear where it comes from

2014-02-06 Thread Robert Klemme
On Thu, Feb 6, 2014 at 10:14 AM, Csaba Raduly wrote: > Hi Robert, > > On Thu, Feb 6, 2014 at 10:01 AM, Robert Klemme wrote: >> Hi, >> >> in cygwin64 on Win 7 64 bit I find "." in $PATH: >> >> $ echo "$PATH" | tr : \\n | egrep '^\

Re: $PATH contains dot but unclear where it comes from

2014-02-06 Thread Robert Klemme
On Thu, Feb 6, 2014 at 12:56 PM, Andrey Repin wrote: > Greetings, Robert Klemme! Hello Andrey! >> I should have mentioned that I did just that - to no avail. > >> $ echo exit | bash --login -i -x 2>|log >> $ egrep -n 'PATH=(.:|.*:\.($|:))' log | head >>

Re: $PATH contains dot but unclear where it comes from

2014-02-18 Thread Robert Klemme
On Thu, Feb 6, 2014 at 4:32 PM, Robert Klemme wrote: > Can anybody make sense of that? I can share the complete log with > individuals if it helps. Nobody? Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- Problem r

Re: $PATH contains dot but unclear where it comes from

2014-02-19 Thread Robert Klemme
On Tue, Feb 18, 2014 at 7:32 PM, David Boyce wrote: >> On Thu, Feb 6, 2014 at 4:32 PM, Robert Klemme >> wrote: >> >>> Can anybody make sense of that? I can share the complete log with >>> individuals if it helps. >> >> Nobody? > > I haven&#

Re: $PATH contains dot but unclear where it comes from

2014-02-19 Thread Robert Klemme
On Wed, Feb 19, 2014 at 5:06 PM, Eliot Moss wrote: > As others have said, cygwin does not add . to the path > itself. It must be something in your .bash_profile, > .bashrc, or other script sourced from them. > > Going through the output of your login with tracing > enabled, as previously describe

Re: $PATH contains dot but unclear where it comes from

2014-02-19 Thread Robert Klemme
On Wed, Feb 19, 2014 at 6:23 PM, Larry Hall (Cygwin) wrote: > On 2/19/2014 12:16 PM, Robert Klemme wrote: >> The dot is already in the variable before bash even modifies it. > > So that means you need to look in your Windows environment to understand > where this comes fr

Re: $PATH contains dot but unclear where it comes from

2014-02-20 Thread Robert Klemme
Thanks to all who helped so far! On Wed, Feb 19, 2014 at 11:23 PM, Andrey Repin wrote: > So far, I'm not convinced that issue is Cygwin-specific. The fact that it > doesn't manifest in Windows is actually because of it's (windows) native > ignorance for this matter. I sent a lengthy email with

bash adds dot to $PATH (was: Re: $PATH contains dot but unclear where it comes from)

2014-03-06 Thread Robert Klemme
Folks, sorry for the delay, I was sick in the meantime. Now, I try to summarize all my finding in the hopes that bash package maintainer can pick up from here. When starting a terminal on my Windows 7 64 bit system $PATH contains a dot at the end. The dot is not present in my Windows environment

Re: bash adds dot to $PATH (was: Re: $PATH contains dot but unclear where it comes from)

2014-03-13 Thread Robert Klemme
Hi, Matthew Blakley pointed out to me that he noticed that under Windows 7 several processes have the dot added - not only Cygwin processes. I checked with ProcessExplorer and indeed PATH of chrome.exe ends with ";.;". So it could be an OS "feature" but I could not find any documentation about th

Re: bash adds dot to $PATH

2014-03-25 Thread Robert Klemme
On Tue, Mar 25, 2014 at 3:14 AM, Linda Walsh wrote: > Robert Klemme wrote: > So it could be an OS "feature" but I could not find any >> >> documentation about this. And it is still totally unclear to me what >> the criterion might be as bash suffers from this bu

Problem getting flock with timeout to work

2009-03-12 Thread Robert Klemme
Hi, I searched the archives but could not find any related issue. My problem is this: I use flock with a timeout but apparently the timeout does not work, i.e. flock waits longer than specified. Script is attached. Output is here: This is ok, timeout is longer than needed: 15:34:27 tmp$ ./fl-

Re: Problem getting flock with timeout to work

2009-03-12 Thread Robert Klemme
Hi again, 2009/3/12 Corinna Vinschen : > On Mar 12 15:40, Robert Klemme wrote: >> Any ideas?  Am I doing something wrong? > > On second thought, maybe I don't understand what you're expecting. > Running the testcase on a Linux box I get this: > > Linux calimer

Re: Problem getting flock with timeout to work

2009-03-12 Thread Robert Klemme
2009/3/12 Corinna Vinschen : > On second thought, maybe I don't understand what you're expecting. > Running the testcase on a Linux box I get this: > > Linux calimero 2.6.[etc] > -rw-r--r-- 1 corinna vinschen 0 Mar 12 16:48 lock > timeout 10 > started 1 > 3644 Thu Mar 12 16:48:48 CET 2009 > starte

Re: Problem getting flock with timeout to work

2009-03-13 Thread Robert Klemme
Corinna, thanks for your feedback! 2009/3/12 Corinna Vinschen : > On Mar 12 17:44, Robert Klemme wrote: >> The second flock does not start the command as I expect it to be. >> >> I am referring to the man page of flock which says this about option -w: >> >> Fail

dash vs. ash?

2009-07-10 Thread Robert Klemme
All, I just notice that there is dash in cygwin 1.7 but there is also ash. What would be the reason to switch from ash to dash? From what I am finding on the web it seems, dash was basically ash code modernized. So it seems when on 1.7 dash would be the preferred one. Any insight? Kind regards

ruby-1.8.6-p114-1: IRB cannot use readline any more

2008-05-21 Thread Robert Klemme
Hi, after upgrading to this new version of Ruby readline does not seem to work in IRB any more. I tried using parameter --readline as well as various combinations of packages readline, libreadline5 and libreadline6 but to no avail. Switching back to the previous version (ruby 1.8.6 (2007-03-13 p

Re: ruby-1.8.6-p114-1: IRB cannot use readline any more

2008-05-21 Thread Robert Klemme
2008/5/21 Corinna Vinschen <[EMAIL PROTECTED]>: > On May 21 09:51, Robert Klemme wrote: >> after upgrading to this new version of Ruby readline does not seem to >> work in IRB any more. I tried using parameter --readline as well as >> various combinations of packages

Re: Ruby and OpenSSL: no such file to load -- openssl (RuntimeError)

2008-10-19 Thread Robert Klemme
2008/10/18 Redd Vinylene <[EMAIL PROTECTED]>: > I'm getting this error on Cygwin when trying to run this tiny little Rails > app: > > ./script/../config/../vendor/rails/railties/lib/initializer.rb:253:in > `require_frameworks': no such file to load -- openssl (RuntimeError) > > I have both the ope

gem command broken on Cygwin 64 with Ruby 2.0.0p481

2014-09-05 Thread Robert Klemme
Hi folks, did someone of you experience this as well? $ uname -a CYGWIN_NT-6.1 arnie 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 Cygwin $ ruby --version ruby 2.0.0p481 (2014-05-08) [x86_64-cygwin] $ gem --version 2.4.1 $ gem list -l *** LOCAL GEMS *** io-console (0.4.2) json (1.8.1) minitest (4.7

Re: gem command broken on Cygwin 64 with Ruby 2.0.0p481

2014-09-05 Thread Robert Klemme
On Fri, Sep 5, 2014 at 9:54 AM, Robert Klemme wrote: > Hi folks, > > did someone of you experience this as well? > > $ uname -a > CYGWIN_NT-6.1 arnie 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 Cygwin > $ ruby --version > ruby 2.0.0p481 (2014-05-08) [x86_64-cygwin] > $ ge

Re: Updated: bash-4.1.14-7

2014-09-30 Thread Robert Klemme
On Mon, Sep 29, 2014 at 11:22 PM, Eric Blake (cygwin) wrote: > A new release of bash, 4.1.14-7, has been uploaded and will soon reach a > mirror near you; leaving the previous version at 4.1.13-6. ... Thank you Eric for the fast updates and staying on top of all the security warnings coming in! K

Re: cygwin bash script suddenly can't find ls, grep

2014-10-15 Thread Robert Klemme
On Tue, Oct 14, 2014 at 10:54 PM, LMH wrote: > Thorsten Kampe wrote: >> * LMH (Sat, 11 Oct 2014 20:30:07 -0400) >>> Good Lord, I guess I wasn't thinking very clearly trying to use >>> PATH as >>> a variable for something else. I changed to, >>> >>> FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal

Pin package version

2014-11-18 Thread Robert Klemme
Hi, I could not find an answer to this: is it possible to pin a package version with the Cygwin installer? Switching manually to "keep" on every update is error prone. Kind regards robert -- [guy, jim].each {|him| remember.him do |as, often| as.you_can - without end} http://blog.rubybestpract

1.7.7: Postinstall issue with boxes.sh

2011-01-03 Thread Robert Klemme
Hi, there seems to be a small glitch with the grep pattern. I have attached the error log and a patch for file /etc/postinstall/boxes.sh. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ setup.log.full Description: Binary data

Re: Newline missing in csh

2015-11-17 Thread Robert Klemme
On Tue, Nov 17, 2015 at 2:28 AM, Andrey Repin wrote: > > Greetings, Gluszczak, Glenn! > > > cat "/proc/registry/HKEY_CURRENT_USER/Control > > Panel/International/sLanguage" works fine in bash > > but if I switch to csh I fail to get a newline when reading the registry. > > > $ cat -v "/proc/regist

svn 1.7.10-1 on x86_64 does not work

2013-08-27 Thread Robert Klemme
Hi folks, even obtaining the version fails with this: $ svn --version /usr/bin/svn.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory I have a pretty fresh installation (only selected the older version of svn) and am not aware of anything I mi

Re: svn 1.7.10-1 on x86_64 does not work

2013-08-28 Thread Robert Klemme
On Tue, Aug 27, 2013 at 6:14 PM, David Rothenberger wrote: > On 8/27/2013 9:04 AM, Robert Klemme wrote: >> $ svn --version >> /usr/bin/svn.exe: error while loading shared libraries: ?: cannot open >> shared object file: No such file or directory > > Check that you have

Re: cygpath -m behaviour change

2013-09-17 Thread Robert Klemme
On Mon, Sep 16, 2013 at 11:56 AM, David Griffiths wrote: >> Yes, that's exactly right, assuming that 'boo' doesn't exist. > > Hi, it happens even if boo does exist. To put it in context, the > script in question was attempting to determine the current directory: > > CURRENT_DIR=$(cygpath -ma "${0}