Buchbinder, Barry (NIH/NIAID) [E] niaid.nih.gov> writes:
>
> # Only set ThisTerm if not set.
> if [ -z "${ThisTerm}" ]
> then
> if [ ${PPID} = 1 ]
> then
> ThisTerm=cmd
> else
> if [ "$(cat /proc/${PPID}/exename)" = '/usr/bin/mintty' ]
> then
> ThisTerm=mintty
> else
>
I have a 32-bit XP Pro machine with an old cygwin installation (DLL
version 1.5.25). In the past, started Setup on a machine on which
cygwin was already installed an created a package directory on CD with
the same packages as the installation. I can then install the same
packages on another 32-bi
On Wed, Jun 22, 2011 at 12:55 AM, Andrew Hancock wrote:
>
> I have a 32-bit XP Pro machine with an old cygwin installation (DLL
> version 1.5.25). In the past, started Setup on a machine on which
> cygwin was already installed an created a package directory on CD with
> the same
After some web surfing about how to clear the screen in cygwin, I
installed ncurses. /bin/clear.exe is not there, but /bin/clearw.exe
is. Nothing comes up on a search for clearw either in the mailing
list archives or google. Just wondering if this was a filenaming
typo.
--
Problem reports:
I am seeing two different versions of a file depending on how I access
it. Specifically, the file "C:\Program Files (x86)\Vim\_vimrc" uses
plain text to provide startup specifications for the text editor gvim.
This is the standalone installation for Windows, not the one the one
that comes with Cy
I am seeing two different versions of a file depending on how I access
it. Specifically, the file "C:\Program Files (x86)\Vim\_vimrc" uses
plain text to provide startup specifications for the text editor gvim.
This is the standalone installation for Windows, not the one the one
that comes with Cy
2011 at 10:40 AM, Andrew Hancock wrote:
> I am seeing two different versions of a file depending on how I access
> it. Specifically, the file "C:\Program Files (x86)\Vim\_vimrc" uses
> plain text to provide startup specifications for the text editor gvim.
> This is the sta
On a Windows XP system, I was using an administrator account to take
ownership of file trees belonging to deleted accounts, with the aim of
deleting those file trees. Unfortunately, I issued a recursive chown
from "c:\Documents and Settings" rather than "c:\Documents and
Settings\DeletedUser". No
I notice a thread on cygwin's inability to create folders/files on a network
drive (http://cygwin.com/ml/cygwin/2011-08/msg00136.html). Corinna's advice to
use to snapshot worked for me. However, I found that when I upgraded cygwin
some time afterward, the problem recurred. I had to re-do the ad
According to http://savannah.gnu.org/bugs/?func=detailitem&item_id=30309 , a bug
with octave's wavread function was fixed in octave 3.2.3. My "cygcheck -cvs"
shows an octave of 3.4.2, but I still get the bug. I was wondering if it is
wise to assume that the app version number from cygcheck is the
marco atzeri gmail.com> writes:
> On 12/3/2011 5:26 AM, Andrew Hancock wrote:
>> According to
>> http://savannah.gnu.org/bugs/?func=detailitem&item_id=30309 , a bug
>> with octave's wavread function was fixed in octave 3.2.3. My
>> "cygcheck -cvs&qu
Christopher Faylor cygwin.com> writes:
>
> On Sat, Dec 03, 2011 at 03:26:38PM +0000, Andrew Hancock wrote:
>>
>>Thanks, Marco. I posted on another thread asking whether it was
>>wise to update Octave without updating the cygwin DLL. Updating the
>>cygwin DLL us
marco atzeri gmail.com> writes:
|
| On 12/3/2011 4:26 PM, Andrew Hancock wrote:
|| marco atzeri gmail.com> writes:
||| On 12/3/2011 5:26 AM, Andrew Hancock wrote:
According to
http://savannah.gnu.org/bugs/?func=detailitem&item_id=30309 , a
bug with octave's wavre
I installed cygwin's gvim on Windows 7. I found that pasting from the
Windows clipboard into gvim doesn't work by clicking the middle mouse
button unless I go through a weird ritual that I discovered by
accident. If I don't do this, I get "E353: Nothing in register *".
First, I have to highlight
14 matches
Mail list logo
