On Sat, Feb 28, 2004 at 10:29:01AM -0800, linda w [EMAIL PROTECTED] wrote:
I still haven't figured out how to get Tk to build from cpan
w/o the x param. It builds when I drop into the build
dir view Tk from in cpan, and build it w/the x, but
to install, I finally just ignore the makefile
The same problem keeps coming up in new and different
ways that keep running into. My background also has user
interface design, usability in it and I keep running into
problems as I try to use things from the perspective of
a user like my mom -- or just a windows users not famililar
with linux
On Sat, Feb 28, 2004 at 10:29:01AM -0800, linda w wrote:
[long, rambling off-topic email deleted]
Ok.
As mentioned here:
http://cygwin.com/ml/cygwin/2003-12/msg00186.html
you're now blocked from this mailing list.
--
Please use the resources at cygwin.com rather than sending personal email.
Tried this...some scripts ran. One that didn't wanted lanman.pm located in
Win32::lanman.
Queerly enough, doing a i /lanman comes up zip even though it is in
CPAN at
/CPAN/sources/authors/id/J/JH/JHELBERG/lanman.1.0.10.0.zip.
Obviously I'm still a bit too new for this stuff, get, make and
Do all the win32 libraries have to have a special port to work on cygwin
even though
cygwin was supposed to aid in allowing posix type apps (like perl) to
run under
win either from the bash or cjmd.exe shell?
Definitely the win32 lib is a step in the right direction...but why does
cygwin
On Thu, Feb 19, 2004 at 01:46:05AM -0800, linda w [EMAIL PROTECTED] wrote:
Tried this...some scripts ran. One that didn't wanted lanman.pm located in
Win32::lanman.
Queerly enough, doing a i /lanman comes up zip even though it is in
CPAN at
On Thu, Feb 19, 2004 at 07:48:48AM -0800, Yitzchak Scott-Thoennes [EMAIL PROTECTED]
wrote:
On Thu, Feb 19, 2004 at 01:46:05AM -0800, linda w [EMAIL PROTECTED] wrote:
Tried this...some scripts ran. One that didn't wanted lanman.pm located in
Win32::lanman.
Queerly enough, doing a i
What features does one get with a unix perl over a perl built where
WinNT is
defined as true or false? Many (most? all?) of the Win32 calls are
available
in the Cygwin environment, why not compile the perl as a mixed breed
perl that
defines WinNT?
What is lost by allowing Perl to make
On Thu, Feb 19, 2004 at 11:27:29AM -0800, linda w wrote:
What features does one get with a unix perl over a perl built where
WinNT is
defined as true or false? Many (most? all?) of the Win32 calls are
available
in the Cygwin environment, why not compile the perl as a mixed breed
perl
On Thu, Feb 19, 2004 at 11:27:29AM -0800, linda w wrote:
What features does one get with a unix perl over a perl built where
WinNT is defined as true or false? Many (most? all?) of the Win32
calls are available in the Cygwin environment, why not compile the perl
as a mixed breed perl that
It seems cyg_win_ was designed to add POSIX and unix compatibility
and functionality to the _Win_ environment with the intent of making
things _easier_ (Easy is good -- not everyone can be a master of
every technology). So why not make things easier for perl scripters
as well by starting
Is that a new package? I thought I had installed all the perl related
cygwin packages?
Could just be my failing eyesite, though as well...
I, of course, had tried the old fashion way of downloading the win32 modules
from CPAN, and tried installing them which was when I got the you aren't
WinNT
I'm on an NT compatible (Windows XP) release trying to run the reg utils
but I
get an error message that IsWinNT is not defined, so they the reg utils
fail to
install. Presumably IsWinNT is to differentiate between Protected and
DOS-based versions of Windows but presumably wouldn't be defined
On Thu, 12 Feb 2004, linda w wrote:
[snip]
Speaking of compatibility -- there is only 1 application I know of that
uses / in keynames -- Cygwin. Since it's already been noted that this
makes it very awkward to access these keys in /proc, perhaps cygwin
could op for better windows
On Thu, Feb 12, 2004 at 01:44:24PM -0500, Igor Pechtchanski wrote:
The only mechanism I can think of that is adversely affected by this
convention is /proc/registry, because of its attempt to map the
registry onto a filesystem. Because the registry doesn't have the same
set of invalid characters
On Thu, 12 Feb 2004, Christopher Faylor wrote:
On Thu, Feb 12, 2004 at 01:44:24PM -0500, Igor Pechtchanski wrote:
The only mechanism I can think of that is adversely affected by this
convention is /proc/registry, because of its attempt to map the
registry onto a filesystem. Because the
: Bug: Perl:IsWinNT undefined RFE, only use / in reg values,
not names..?]
I'm on an NT compatible (Windows XP) release trying to run the reg utils
but I
get an error message that IsWinNT is not defined, so they the reg utils
fail to
install. Presumably IsWinNT is to differentiate between Protected
17 matches
Mail list logo
