--- Kevin Markle ha scritto:
> Hello,
>
> I'm attemping to use the expr variable and am
> having
> problems. when I
> type test=expr 1+1 or
> test=`expr 1+1` or
> test='expr 1 + 1' or
>
> with and without quotes?? I just want to create a
> variable based on and
> expression?
this is a bash qu
I'm using Cygwin 1.5.24 on Windows XP Pro SP2
I saw the announcement about the new bash package, so I used setup.exe
to upgrade my installed packages today. This bumped my mutt (and its
documentation) up to 1.4.2.2-1
When I do (with less 381-1)...
less /usr/share/doc/mutt-1.4.2.2/manual.txt
I
PACKAGE DESCRIPTION
===
BSFlite - A minimalist console AIM client
Homepage: http://bsflite.sourceforge.net/
Version : 0.82
License : BSD
BSFlite is a rather small and "minimalistic" client for AOL's Instant
Messenger service.
NOTE: New package built with cygport, no new upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 3/22/2007 11:26 PM:
> This happens about 50% of the time when I run some kind of fork from
> perl in cygwin:
>
> Executing: rsync -a --delete --delete-excluded --stats -v --progress
> '/cygdrive/d/coLinux' '/cygdrive/
[EMAIL PROTECTED] wrote:
This happens about 50% of the time when I run some kind of fork from
perl in cygwin:
Executing: rsync -a --delete --delete-excluded --stats -v --progress
'/cygdrive/d/coLinux' '/cygdrive/h/Backup/coLinux'
9648 [main] perl 4064 d:\cygwin\bin\perl.exe: *** fatal error -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mark S. Reglewski on 3/23/2007 3:20 AM:
> less /usr/share/doc/mutt-1.4.2.2/manual.txt
>
> I get a display like this:
> ESC[1mset-flag ESC[22m(default: w)
>
> Does anyone else observe this, or is this a me-only problem?
I'm guessing
On 3/23/07, Zak Johnson wrote:
I first blamed XFT, as it manifested itself most obviously when starting
XFT applications;
fc-cache helps?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cyg
I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
Installation went fine. After running /usr/sbin/libusb-install the test
program worked OK and also my own libusb based program worked fine.
The real problem started after the following reboot.
The /usr/sbin/libusb-install installs th
Hi,
Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit :
> I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
Just to make sure, does the old 0.1.10.1-3 work fine?
> My guess is that /usr/sbin/libusb-install omits some crucial step
> (registry? kernel service?) which make
Version 0.9.5.1a-3 of "python-pyrex" has been uploaded.
Pyrex lets you write code that mixes Python and C data types any way
you want, and compiles it into a C extension for Python.
If you have questions or comments, please send them to the Cygwin
mailing list at: cygwin@cygwin.com .
On 23 March 2007 06:38, Zak Johnson wrote:
> I recently installed Cygwin (1.5.24(0.156/4/2)) on a new (dual-core)
> machine, and am seeing much slower performance than a February install
> of Cygwin on an older machine (no longer available for comparison, I'm
> afraid).
>
> I suspect it is a prob
On Fri, 23 Mar 2007, Samuel Thibault wrote:
> Hi,
>
> Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit :
> > I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
>
> Just to make sure, does the old 0.1.10.1-3 work fine?
>
Yes, Installed 0.1.10.1-3 after removing 0.1.12.1-
Lev Bishop wrote:
> On 3/23/07, Zak Johnson wrote:
> >I first blamed XFT, as it manifested itself most obviously when starting
> >XFT applications;
>
> fc-cache helps?
fc-cache fails:
$ fc-cache
/usr/X11R6/lib/X11/fonts: failed to write cache
/usr/X11R6/lib/X11/fonts/75dpi: failed to
Dave Korn wrote:
> Do you have any of the following installed?
>
> - Sonic Solutions burning software containing DLA component (dlactrlw.exe)
> - Norton/MacAffee/Symantec antivirus or antispyware
These two; no others. I disabled DLA using Sysinternals autoruns, as
per the "Cygwin fork()" threa
Ton van Overbeek, le Fri 23 Mar 2007 16:56:48 +0100, a écrit :
> Yes, Installed 0.1.10.1-3 after removing 0.1.12.1-1 and it works fine.
Ok, so people can use that one instead for the few coming days until I
fix the issue.
> Also there is now an /usr/lib/libusb/install-filter.exe which did not
> e
On 23 March 2007 16:11, Zak Johnson wrote:
> Dave Korn wrote:
>> Do you have any of the following installed?
>>
>> - Sonic Solutions burning software containing DLA component (dlactrlw.exe)
>> - Norton/MacAffee/Symantec antivirus or antispyware
>
> These two; no others. I disabled DLA using S
Eric Blake wrote:
According to Mark S. Reglewski on 3/23/2007 3:20 AM:
less /usr/share/doc/mutt-1.4.2.2/manual.txt
I get a display like this:
ESC[1mset-flag ESC[22m(default: w)
Does anyone else observe this, or is this a me-only problem?
I'm guessing that you also upgraded man. There is
Dave Korn wrote:
> Suspect DLA then.
No such luck, I'm afriad. Uninstalled DLA (and all other Roxio
software, for good measure). Rebooted. Verified DLA is not running and
no DLA-related DLLs exist. No change in behavior.
In fact, I see similar behavior when booted into safe mode. What else
The colon (:) character appears to be being misinterpreted.
As an example:
$ > xxx:yyy
Rather than creating a file names xxx:yyy (as all other shells do, and
bash does on my Solaris and Linux boxes) it creates a file called xxx.
The colon appears to be being treated as a comment character r
Philip Peake vogon.net> writes:
>
> The colon (:) character appears to be being misinterpreted.
That's Windows for you!
>
> As an example:
>
>$ > xxx:yyy
On Windows 9x, that is an invalid file name. On NT class machines, that is a
command to create an alternate stream (google this li
[EMAIL PROTECTED] wrote:
Angelo Graziosi wrote:
As I wrote:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31039
Ah, okay. I failed to see that you'd posted the config.log there. (And
I mentioned gmp/mpfr as I have seen that cause the build to fail in
exactly the way you described, but it's
I believe I found the cause of the problem.
When running cygcheck on /usr/lib/libusb/libusb0.sys I get this:
$ cygcheck /usr/lib/libusb/libusb0.sys
c:/Cygwin/lib/libusb/libusb0.sys
Error: could not find usbd.sys <
C:\WINDOWS\system32\ntoskrnl.exe
C:\WINDOWS\system32\BOOTVID.dll
22 matches
Mail list logo
