Midnight Commander screen corruption w/ built-in editor

I'm having a problem with mc's editor (4.6.0-4, also tried mc-4.6.0a-20030721 with same issue). (cygwin 1.5.9-1 on 98se) If you are editing a file wider than the screen, sometimes the display becomes corrupted, with odd parts of lines appearing at the left screen edge and the display seems to

"which" with path $HOME/bin vs ~/bin

I recently switched my path from containing "$HOME/bin" to "~/bin" (by updating to a more recent skeleton of .bash_profile and removing stuff from my own .bashrc). Now a bash script of mine that uses "which " to see if a program exists started failing on programs contained in my ~/bin directory.

Re: How to force Setup.exe to behave?

"Lex Ein" <[EMAIL PROTECTED]> wrote: >Please help me figure out how to get Setup.exe to STOP TRYING TO INSTALL >X. >Setup.exe won't stop trying to snag unnecessary components. >What file(s) to I have to edit manually to make this happen? >What can I manually delete? >It's a remote system, so I ca

Re: "Broken pipe" warning from bash.

At 05:53 PM 28/09/2004, Bas van Gompel wrote: Following little (bash) shell-script many times causes a "Broken pipe" (SIGPIPE) warning to be emitted by bash. Is this expected behaviour? An example of the message: ./tc-pipe.sh: line 5: 3541109 Broken pipe seq 1 2 The message is generated

RE: "which" command does not expand "~" in path

At 09:23 PM 26/09/2004, "Hannu E K Nevalainen" wrote: FWIW; 'man bash' has a section on Tilde Expansion - I take it as; bash does this expansion for you, not which.exe -> use $HOME when not typing at the prompt. This is all fine & good, but it doesn't change the fact that the cygwin-supplied "whi

Re: "which" command does not expand "~" in path (base-files update needed)

At 01:31 AM 29/09/2004, Christopher Faylor wrote: > # Set MANPATH so it includes users' private man if it exists > # if [ -d ~/man ]; then >-# MANPATH="~/man:${MANPATH}" >+# MANPATH="${HOME}/man:${MANPATH}" > # fi > > # Set INFOPATH so it includes users' private info if it exists > # if [ -d ~/

Re: "which" command does not expand "~" in path (base-files update needed)

At 03:27 AM 29/09/2004, Igor wrote: > Agreed, but aren't we talking about .bash_profile here ;-)? Ugh. Yes. FWIW, /etc/profile does use '~' (in lines 191-195), so the above point is valid anyway (though by chance, rather than by intention)... I notice that it's also full of carriage returns! :-)

Re: "which" command does not expand "~" in path (base-files update needed)

At 05:43 AM 29/09/2004, Brian Ford wrote: > export PATH=~/bin:$PATH How 'bout using a temp, or just plain $HOME as suggested before? Good question, I'd like to know what was wrong with my (first ever cygwin) patch! ;-) Seriously though, is there any advantage to using ~ over $HOME? the bash man

Re: 'which' command does not expand '~' in path (base-files update needed)

At 06:40 AM 29/09/2004, John Morrison wrote: Just my two penny worth; I've just pulled, ./configure[d] and make[d] the GNU which application (it built OOTB). It correctly checks ~/bin. See my original post (http://www.cygwin.com/ml/cygwin/2004-09/msg01383.html) Would it be worth considering using

Donations Page

Christopher Faylor wrote: >>>I am willing to pay 100 USD into that account. Knowing that my machine >>>has cost about Euro 1000 I believe it should take a real short time to >>>provide cfg with a machine to test / debug the hyperthreading issue . >> >>http://www.cygwin.com/ml/cygwin/2004-09/msg000

1.5.11 win9x instability

I have been experiencing intermittent instability on win98se, but tried the same tests on another 98 box with similar problems, so I am confident that cygwin is the culprit. (my machine is solid outside of cygwin). I use the call to "find" below in one of my projects (webpack), and every once in

Re: cygwin1.dll problem with Hyperthreaded machines (reprise)

Christopher Faylor wrote: >For the record I have never doubted that people were reporting real >problems. I doubt that Corinna has either. > >No more "me toos" are required here. So, as Larry implied, either >debugging of the problem or the donation of a system is necessary. FYI, the win98 testc

Re: cygwin1.dll problem with Hyperthreaded machines (reprise)

Christopher Faylor wrote: >FYI, the win98 testcase that I reported >(http://cygwin.com/ml/cygwin/2004-07/msg01120.html) locks up in the >same way (as the testcase in this thread) on my hyperthreaded machine >at work (P4, XPPro), but runs fine fine with HT disabled in BIOS. >Maybe seeing what the tw

"which" command does not expand "~" in path

If your PATH contains the tilde character (eg. "~/bin:...") the cygwin version of "which" seems to fail to expand the "~" and will then not locate any commands in ~/bin (or any other directory on the path containing "~" presumably). I'm 99% sure it's cygwin's version of "which" causing th

Re: "which" command does not expand "~" in path

From: Sven Köhler Subject: Re: "which" command does not expand "~" in path Date: Sat, 25 Sep 2004 20:32:31 +0200 Message-ID: <[EMAIL PROTECTED]> Set PATH so it includes user's private bin if it exists if [ -d ~/bin ] ; then PATH="~/bin:${PATH}" fi Hmm, i'm not 100% percent sure, but is this supp