Re: what's the software for making slide under cygwin, please?
Hi, I think it's pretty unreasonable to rely on every individual posting to this list to obfuscate email addresses in their submissions. It's inherently error prone, will never be done anywhere near thoroughly enough and properly is a responsibility of the list software. IMO, of course. Randall Schulz On Monday 01 March 2004 22:14, Gregory Borota wrote: PLEASE, configure your email client not to show email addresses in reply!!! (or if you can't take this off list) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Java Thread Dump in Bash
Frank-Michael, At 07:37 2004-02-18, Frank-Michael Moser wrote: Larry Hall wrote: OK. Maybe now it's time for you to look at and follow: Problem reports: http://cygwin.com/problems.html Larry, what was wrong with my mails? Sorry, if..., but...? I'm reading the mailing list since a long time and thought I would follow these guidelines you just mentioned. What especially do you miss: -... - asked whether to send cygcheck - Randall said no. All I said was that cygcheck output would not help me. - ... Please be specific to me, too, tell me what I did wrong and I swear to pick it up for the future. Frank-Michael Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Java Thread Dump in Bash
Frank-Michael, I hesitate to continue this on the Cygwin list, but I will, for now. At 09:45 2004-02-18, Frank-Michael Moser wrote: Randall, does your Java application die after pressing Ctrl-Break or not? It appears it terminates. As you've had me trying this much more than I ever have in the past, I've found that the behavior is not really very uniform or predictable. When the program's standard input and output are not redirected, I see the thread dump and the program dies--usually, but not quite always. Sometimes the program just terminates. I had interpeted the termination as an indication of an end-of-file having been generated, but that may have been incorrect. When I run the program with standard input, output and error redirected to files and type CTRL-BREAK, the program terminates but the thread dump is nowhere to be seen in the file that received standard output, the file that received standard error nor the console / tty. I could hypothesize that the recent changes in Cygwin signal handling might have something to do with this. However, I know nothing of the details of this change, just that a change was mentioned in the Cygwin release notes. So this is really just blind speculation, especially since I really don't have much of a basis for comparison (in a before-and-after sense). Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Java Thread Dump in Bash
Frank-Michael, CTRL-BREAK produces a thread-dump using the latest Sun JVM on my system when launched from BASH. However, if the program is reading standard input from the unredirected console, it receives an end-of-file indication on that stream as well. Randall Schulz At 03:42 2004-02-17, Frank-Michael Moser wrote: Searching the mailing list archive I found that there is an old thread from Dec 2000 which exactly describes my problem: http://sources.redhat.com/ml/cygwin/2000-12/msg00490.html In short: Using Ctrl-Scroll does not cause a Java program to dump threads as it does in cmd.exe. Unfortunately the thread ended up with some personal strife. I understand that the signal problem could be by design. But now (3 years later) maybe there are news about this issue? Has someone a way to work around this problem? Frank-Michael -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Java Thread Dump in Bash
Frank-Michael, At 12:09 2004-02-17, Frank-Michael Moser wrote: Unfortunately neither Ctrl-Break nor Ctrl-Scroll produce a thread dump not in pure bash and not in RXVT for me. I'm using latest cygwin and tried JDK 1.4.2_02 and 1.5.0 beta. Also the java applications I tried do not read from standard input. What versions (cygwin/java) do you use. Cygwin: Latest kernel and latest version of all packages. Java: Latest (specifically, 1.4.2_03); If it might matter, I generally use the java and javac commands from the SDK bin, not the jre bin. That's the directory that includes the compiler and related development tools, where as the jre bin has only the JVM and other runtime resources. By pure BASH I take it you mean BASH in a console window, in contrast to an RXVT window. I do _not_ use the tty option in the CYGWIN environment variable. Do you? Is it worth to send my cygcheck output attached? Should I really expect Ctrl-Break to work - this would be great? I expect it to work because it does work for me... Cygcheck output isn't anything I can use for any purpose I can think of in resolving this discrepancy between how your system and mine behave. Frank-Michael Randall Schulz Randall R Schulz wrote: Frank-Michael, CTRL-BREAK produces a thread-dump using the latest Sun JVM on my system when launched from BASH. However, if the program is reading standard input from the unredirected console, it receives an end-of-file indication on that stream as well. Randall Schulz At 03:42 2004-02-17, Frank-Michael Moser wrote: Searching the mailing list archive I found that there is an old thread from Dec 2000 which exactly describes my problem: http://sources.redhat.com/ml/cygwin/2000-12/msg00490.html In short: Using Ctrl-Scroll does not cause a Java program to dump threads as it does in cmd.exe. Unfortunately the thread ended up with some personal strife. I understand that the signal problem could be by design. But now (3 years later) maybe there are news about this issue? Has someone a way to work around this problem? Frank-Michael -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gcj problem...
Jason,
You need to learn about the ways in which GCJ differs from the stock
Sun Java Tools. In particular, you need to use the --main= option to
nominate the class that bears the primary entry point. See
http://gcc.gnu.org/java/faq.html#4_1 for more.
In general, familiarize yourself with the information at
http://gcc.gnu.org/java/ if you want to use GCJ in place of or in
addition to the Sun tools (or Jikes, for that matter).
Randall Schulz
At 05:20 2004-02-16, Jason Fu wrote:
Any idea about it...
$ gcj HelloWorld.java
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a(libcmain.o)(.text+0
x7
c): undefined reference to [EMAIL PROTECTED]'
collect2: ld returned 1 exit status
=
public class HelloWorld
{
public static void main(String[] args)
{
System.out.println(Hello World!);
}
}
=
http://www.hkucs.org:8080/~tsfu/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
This Just In: Mozilla Releases Compiled Using Cygwin
Howdy, Folks, I installed the new Mozila (1.6) yesterday and was exploring the about:* pages via the new about:about master about page. Check out about:buildconfig: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- about:buildconfig Build platform target i586-pc-msvc Build tools Compiler Version Compiler flags $(CYGWIN_WRAPPER) cl 12.00.8804 for 80x86 -TC -nologo -W3 -nologo -Gy -Fd$(PDBFILE) $(CYGWIN_WRAPPER) cl 12.00.8804 for 80x86 -TP -nologo -W3 -nologo -Gy -Fd$(PDBFILE) Configure arguments --disable-debug --enable-optimize --enable-crypto --disable-auto-deps --with-extensions=all --without-system-jpg --without-system-zlib -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- Evidently they're using the MSVC compiler, but use Cygwin for their Windows-based build activities. Too bad we can't see what's in $(CYGWIN_WRAPPER). Randall Schulz Mountain View, CA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash $substitution in 2.05b.0-9
David, At 12:28 2003-08-05, David Selby wrote: I have hit a problem with bash ... as a sample program I have ... Your problem is that /bin/sh is ash, not BASH. To get BASH, use /bin/bash #!/bin/sh Dave Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Yes but I don't understand ...
Igor, At 13:29 2003-08-05, Igor Pechtchanski wrote: On Tue, 5 Aug 2003, David Selby wrote: You are dead right, I tried /bin/bash script and it worked perfectly, but I am afraid I do not understand why ... echo $BASH_VERSION Tells me I have bash Yes, because it's inherited from the parent shell environment, most likely (or you're running the above command from bash). You do have bash installed, but as /bin/bash, *not* /bin/sh. BASH_VERSION, as well as its counterpart BASH_VERINFO, are not exported by default. I think the explanation for what David is seeing is that his interactive shell is BASH, as is the default for interactive sessions under Cygwin. But his script used the shebang line #!/bin/sh, which as we all know is ash. It seems that he (David) was under the combined misapprehensions that the interactive shell was /bin/sh and that /bin/sh was BASH. ... Igor Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Yes but I don't understand ...
David, At 13:14 2003-08-05, David Selby wrote: You are dead right, I tried /bin/bash script and it worked perfectly, but I am afraid I do not understand why ... echo $BASH_VERSION Tells me I have bash I call cygwin with ... c:\cygwin\win\rxvt.exe -e \bin\bash --login -i ie bash Where did ash (a stripped down bash?) come in ? As I understand it, it all goes back to the big bang... I don't understand the question. Cygwin has for a long time used ash as it's /bin/sh. Ash is a POSIX compliant shell and is much lighter-weight than BASH. For purposes such as interpreting commands issuing from makefiles, it's faster start-up time makes it a better choice. You script assumed BASH--that is, it used BASH-specific features. Thus it should explicitly invoke bash in its #! line. The fact that most Linuxes use BASH as their /bin/sh probably falsely led you to believe that BASH was _the_ shell in POSIX-compliant systems. That's not true. In fact, for a long time, even /bin/bash was a version 1.2 BASH, and that was a far cry from what we now know as BASH. Dave Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: loading DLLs created with Cygwin into Sun JDK
Ville, At 10:33 2003-08-03, Ville Herva wrote: On Sun, Aug 03, 2003 at 12:24:33AM -0400, you [Norman Vine] wrote: Marcus G. Daniels writes: Incidentally, does anyone know of a Windows application that can be used to see the VM maps in a given process. (Like in Linux, with /proc/PID/maps?) May mot be 'exactly' what you had in mind but I find http://www.dependencywalker.com/ *very* helpful for these kind of things also lots of good stuff at http://www.sysinternals.com/ntw2k/utilities.shtml One commercial alternative is VM Validator: http://softwareverify.com/vmValidator/ It gives you a graphical view of dll layout (and memory maps in general.) Commercial as in closed, proprietary source, but available free of charge. Randall Schulz -- v -- [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: activating a dial-up connection from cygwin
Rob, At 07:01 2003-07-25, Rob wrote: Hello, I was wondering if there was any way to activate an existing windows 2000 dial-up connection from the cygwin command line. I don't know of an explicit command that will do this, and once upon a time before I received the blessing of DSL, I did look for such a thing. The best I could figure out is that if you configure Windows to dial on demand, then all you have to do is issue any old command that requires access to the Internet (nslookup, ping, etc.) to get a connection established. Auto-dial is controlled (on Windows 2000 and probably XP, too) in the Network and Dial-up Connections sub-folder of the Control Panels folder. When that folder is displayed in Windows Explorer, a menu called Advanced appears. Choose the Dial-up Preferences command and select the Enable autodial by location for the appropriate location(s). For shutting down, the only thing I know of is to set a suitable idle timeout. This option is controlled in the dial-up configuration's Properties dialog on the Options tab. One caveat: I have found that from time to time, for reasons I could never discern, Windows will activate the Disable autodial for the current session (until I log off) option in the Advanced / Dial-up Preference dialog. When I found that my system was not dialing on its own, I'd have to go there and de-select that option. Randall Schulz The reason I want to know is because I have a shell script that automatically backs up files to a remote computer (which is only accessible through a vpn connection). Since I don't want to maintain the VPN connection all the time, I need a way to start it up (and possibly shut it down) from the command line. Thanks in advance, Rob. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: activating a dial-up connection from cygwin
Hey, Sam, Where were you when I was looking for this way back when? That's two lacunae in as many days: rasdial mkshortcut Ignorance is _not_ bliss! Thanks to you and Luke Kendall for the enlightenment. RRS At 07:46 2003-07-25, Sam Edge wrote: Rob [EMAIL PROTECTED] wrote in [EMAIL PROTECTED] in gmane.os.cygwin on Fri, 25 Jul 2003 10:01:28 -0400: Hello, I was wondering if there was any way to activate an existing windows 2000 dial-up connection from the cygwin command line. The reason I want to know is because I have a shell script that automatically backs up files to a remote computer (which is only accessible through a vpn connection). Since I don't want to maintain the VPN connection all the time, I need a way to start it up (and possibly shut it down) from the command line. Try typing rasdial /help from a command line. It's a built-in in NT, 2k and (I think) XP and works fine for me from CMD.EXE or bash. There's a freeware (or perhaps shareware) version available for 9x/Me as well. You'll have to Google for that. Regards, -- Sam Edge -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: how to make cygwin run under shells other than bash
Damien, Here's the stock Cygwin.bat file: -==--==--==--==--==--==--==--==--==--==- @echo off D: chdir \cygwin\bin bash --login -i -==--==--==--==--==--==--==--==--==--==- All you have to do to substitute tcsh for BASH is change the last line. The options are slightly different, though (check the man page, of course): -==--==--==--==--==--==--==--==--==--==- @echo off D: chdir \cygwin\bin tcsh -l -==--==--==--==--==--==--==--==--==--==- However, I find it more straightforward to create a Windows shortcut that launches my shell directly without any BAT file. An easy way to do this is to use right-mouse drag on /cygwin/bin/tcsh.exe (which is probably C:\cygwin\bin\tcsh.exe or D:\cygwin\bin\tcsh.exe or something analogous) to create a copy on the desktop or in the QuickLaunch bar or in your Start menu. When you release the mouse, choose Create Shortcut(s) Here. Then open the newly created shortcut's Properties dialog and make any changes you like, such as window size and placement, font and cursor preferences, background and foreground colors, etc. (QuickEdit mode is usually a good idea). I like to give the shortcut the Cygwin icon, which is conveniently available in /Cygwin.ico. I recommend setting the Start in: field to you Cygwin home directory. In the Target: field be sure to add the -l (login shell) option. From now on, you can start a tcsh shell in a new console window by activating this shortcut. Good luck. Randall Schulz At 18:05 2003-07-24, Damien Suttle wrote: Hi, my favorite shell is tcsh, but cygwin always starts up in bash. I tried playing with the cygwin.bat file, but i couldn't get it to work. does anyone know how to reconfigure cygwin to start up in other shells? Thank you. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to diagnose Cygwin / Windows shutdown problem
Richard, You know, we heard you the first time... At 10:02 2003-07-23, Richard Anderson wrote: When I start Cygwin 1.3.22-1 and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. I tried using Start / Run / msconfig to disable the startup of all applications and rebooting, but the problem persists. I'm guessing that the next step would be to uninstall and reinstall Cygwin. Any suggestions? Where do people get this from? Maybe you should buy a brand new PC and start by formatting the drives, installing the OS, other applications and Cygwin. Cygwin apps don't know about and cannot respond to the system-generated messages that request that applications quit in preparation for the system to shut down or the user to log off. You just have to manually quit running Cygwin applications before shutting down Windows. If you prefer one-stop shopping, you can initiate shutdown from within Cygwin. If that works for you, do something like this: # Quit all Cygwin applications % shutdown -r now; exit There's no man page or info entry for shutdown, so you if you want information on its operation, use shutdown --help: % shutdown --help Usage: shutdown [OPTION]... time Bring the system down. -f, --force Forces the execution. -s, --shutdown The system will shutdown and power off (if supported) -r, --reboot The system will reboot. -h, --hibernate The system will suspend to disk (if supported) -p, --suspendThe system will suspend to RAM (if supported) --help Display this help and exit. --versionOutput version information and exit. `time' is either the time in seconds or `+' and the time in minutes or a timestamp in the format `hh:mm' or the word now for an immediate action. To reboot is the default if started as `reboot', to hibernate if started as `hibernate', to suspend if started as `suspend', to shutdown otherwise. Good luck. Randall Schulz Richard Anderson -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Skipping the /proc filesystem
At 13:59 2003-07-23, Chris January wrote: Randall R Schulz wrote: At 18:15 2003-07-22, David A. Cobb wrote: I would wish to tell find not to get involved with the /proc filesystem at all. Can that easily be done? Very easily: % find / -path '/proc' -prune -o -print Would it make sense to identify the inodes under /proc/registry as not regular files (type f), but, say, devices (or other such special files)? No. Chris, Just to clarify what may, due to quote trimming, appear to be a suggestion I made, the idea about using a special inode type for the /proc entries was not mine, it was David A. Cobb's. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin prevents normal Windows shutdown
Richard, For starters, you're sending two copies of your messges (some of them, anyway), both a To: copy and a CC: copy. Please try to avoid that. At 15:19 2003-07-23, Richard Anderson wrote: - Original Message - From: Igor Pechtchanski [EMAIL PROTECTED] To: Richard Anderson [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 2:34 PM Subject: Re: Cygwin prevents normal Windows shutdown On Mon, 21 Jul 2003, Richard Anderson wrote: When I start Cygwin 1.3.22-1 with the installed shortcut (which points to C:\cygwin\cygwin.bat) and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. Is there some way to prevent this behavior? Richard Anderson Richard, Apparently, bash doesn't react to the shutdown message that Windows XP sends it. I've observed similar behavior with Windows 9x. Can you close the bash window via the 'X' (Close) button? If not, then it's possible that the correct WM_CLOSE message simply isn't passed to or handled by the bash shell (and any other console Cygwin process). On Windows NT/2k, using the 'X' button sends a HUP signal to the shell. This doesn't seem to happen on Windows 9x (and, possibly, Windows XP -- I don't have an XP system to test this on). You could try to incite someone knowledgeable in Windows messaging (not me, sorry) to investigate this further. Igor Igor, Windows XP and 2K are derived the same code base (or at least more so than 2K and 98), so most systems calls should behave the same. The bash window closes normally when I click the Close button. All third-party Windows apps I have used except Cygwin show the normal behavior on Windows - they gracefully exit without invoking the End Process pop-up. So it's likely that Cygwin is not following the Windows API standard for catching and handling this interrupt. The so-called BASH window may close normally when you click the close box or type ALT-F4, but it is an abortive termination. You'll find, for example, that if you have set up your BASH options so it saves its history that this is not happening when you close the window in this manner. You must use logout (acceptable only if the shell is marked as a login shell) or exit (alwasy OK) lest you forgo all of BASH's normal shutdown processing. Appeals to the behavior of other third-party Windows applications are not entirely irrelevant, but also not directly applicable. Cygwin produces a POSIX emulation environment, and while it does so very well, it is not an entirely seamless melding of the two operating environments. As has been stated already, if you'd like to make (as opposed to suggest) an improvement, work on a way to send SIGHUP to processes when their windows are closed or when Windows sends one of its shutdown messages. I don't have to power to give them out, but a patch that is accepted or becomes the basis for an adopted enhancement to Cygwin could well earn you a gold star. Richard Anderson Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to diagnose Cygwin / Windows shutdown problem
Andrew, Cygwin apps don't have a Windows event handler do they? The two programming models (Win32 and POSIX) are fundamentally different, so based on my very limited understanding, it seems that Cygwin itself (code in Cygwin1.dll) would have to intercept these OS-generated events and translate them into POSIX signals (SIGUP, say). Randall Schulz At 17:16 2003-07-23, Andrew DeFaria wrote: Randall R Schulz wrote: Cygwin apps don't know about and cannot respond to the system-generated messages that request that applications quit in preparation for the system to shut down or the user to log off. Cannot respond to? When a system-generated message that requests that applications quit in preparation for the systme to shut down or the user to log off why can Cygwin apps (in particular bash or other shell) simply do what it would have done if TMOUT was just triggered? TMOUT If set to a value greater than zero, TMOUT is treated as the default timeout for the read builtin. The select command termi- nates if input does not arrive after TMOUT seconds when input is coming from a terminal. In an interactive shell, the value is interpreted as the number of seconds to wait for input after issuing the primary prompt. Bash terminates after waiting for that number of seconds if input does not arrive. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to resolve a link?
David, Investigate the options to test (the binary or the BASH built-in) that detect symbolic links: -h or -L (they are synonymous) and the command readlink (as in man readlink). Again, this is stock Unix / Linux stuff. Randall Schulz At 18:23 2003-07-22, David A. Cobb wrote: Recently, I was trying to do strace Xemacs . . . First I got a No such file error, so I changed to do strace `which xemacs` -- still a failure. which xemacs returns /usr/local/bin/xemacs.exe.lnk; that is, my normal handle to launch xemacs is a symlink to the executable whose name or location varies with the version-number. Given that its purpose is to locate what executable file one will use in a particular environment, should not 'which' resolve the symlink and return its target? What would happen on *nix? -- David A. Cobb -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Skipping the /proc filesystem
David, At 18:15 2003-07-22, David A. Cobb wrote: Maybe this is something any native *nix speaker knows, but I'm stull trudging up the learning curve. It is entirely non-Cygwin-specific, yes. If I do a (cygwin) find for some fragment of a filename, I get a whole pile of hits in the /proc/registry area - none of which is relevant. I would wish to tell find not to get involved with the /proc filesystem at all. Can that easily be done? Very easily: % find / -path '/proc' -prune -o -print To paraphrase, find starting in slash pruning away any path names that begin with /proc and print all others. Randall Schulz -- David A. Cobb -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to resolve a link?
Chris, At 18:29 2003-07-22, Christopher Faylor wrote: On Tue, Jul 22, 2003 at 09:23:13PM -0400, David A. Cobb wrote: Recently, I was trying to do strace Xemacs . . . First I got a No such file error, so I changed to do strace `which xemacs` -- still a failure. which xemacs returns /usr/local/bin/xemacs.exe.lnk; that is, my normal handle to launch xemacs is a symlink to the executable whose name or location varies with the version-number. Given that its purpose is to locate what executable file one will use in a particular environment, should not 'which' resolve the symlink and return its target? No. What would happen on *nix? The same thing as on cygwin. Really? Since Cygwin strace is not a Cygwin program, it does not get Cygwin symbolic links resolved. Whereas on Unix or Linux, a symlink would be resolved by the kernel if it was used by strace and it (strace) would successfully get its target executed. So wouldn't the behavior on Cygwin differ from a comparable invocation on Linux or Unix? Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to resolve a link?
At 20:08 2003-07-22, Christopher Faylor wrote: ... What would happen on *nix? The same thing as on cygwin. Really? Since Cygwin strace is not a Cygwin program, it does not get Cygwin symbolic links resolved. Whereas on Unix or Linux, a symlink would be resolved by the kernel if it was used by strace and it (strace) would successfully get its target executed. AFAIK, we were talking about which not strace. I thought it was obvious why strace wasn't working. strace will translate cygwin paths these days but it won't (yet) follow cygwin symlinks. Right. My mistake. RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [PATCH] : make cygpath use multiple filename arguments
Mark, Cygpath will process multiple names when it's operating as a filter. I suggest that your patch be changed to print each converted argument on a separate line. Randall Schulz At 13:53 2003-07-17, Mark Blackburn wrote: Dunno if anybody will find this useful or not: Currently if you say: # cygpath -w /usr /lib you get a usage error. With my patch you get: # cygpath -w /usr /lib c:\cygwin\usr c:\cygwin\lib Mark. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problems with @pathnames
Magnus, The @-file expansion feature is active only when a non-Cygwin program invokes a Cygwin executable. Try your examples from CMD.exe or COMMAND.exe and you'll see that @-file expansion works as advertised. Randall Schulz At 09:11 2003-07-15, Magnus Lewis-Smith wrote: Do you have to do anything special to turn on @pathname expansion? The Cygwin User Guide, Chapter 3 (Special Filenames) [http://cygwin.com/cygwin-ug-net/using-specialnames.html] states: Example 3-2. Using @pathname bash$ echo 'This is a long line' mylist bash$ echo @mylist @mylist bash$ /bin/echo @mylist This is a long line bash$ rm mylist bash$ /bin/echo @mylist @mylist which suggests that it should 'just happen'. However, I get: (~) echo 'This is a long line' mylist (~) echo @mylist @mylist (~) /bin/echo @mylist @mylist which is clearly not what we want. This has only been happening with recent cygwin1.dlls -- I'm using 1.3.22-1 now. I had an older setup -- long gone now, but probably 1.2.something where it was working. Any advice would be appreciated, particularly if I'm doing something really stupid. Thanks Magnus Lewis-Smith -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: What's up with the Cygwin homepage?
Steve, So far this morning (I tried first around 7:00 am and just now, 9:25 am PDT) I get no response at all from the Web page and Setup.exe cannot retrieve its mirror list. If it's relevant, here's the DNS resolution of cygwin.com: Non-authoritative answer: Name:cygwin.com Address: 67.72.78.218 Randall Schulz At 09:13 2003-07-12, Steve Burkett wrote: I'm getting a 'GTK+ and GNOME Mailing Lists' page. All right, who's been fiddling? :) Steve. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: posix and win32 enviornment
Andrew, At 14:48 2003-07-07, Andrew DeFaria wrote: Shankar Unni wrote: Igor Pechtchanski wrote: [...] you'll be using the MinGW libraries, and your program will not understand POSIX paths (i.e., you'll have to use Win32 ones). Well, to be totally, utterly nitpicky, I believe /WinNT/System32 is a valid POSIX filename which will be understood by Win32 programs as well (assuming that their current drive is C: :-). And also assuming that your Windows installation is in WinNT. With XP that's C:\Windows! For Windows 2000 the directory name is also /WinNT or /WINNT. (Hey you were the one that started this totally, utterly nitpicky stuff :-) ) And it ain't over yet. %SystemRoot% need not be on the C: drive. On my system, it's on D:, e.g. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Advice on where to look to solve a problem
Steve, This is elementary Unix script programming. Well, maybe intermediate scripting. The find command will do everything you want. Read the man page (man find). It's chock full 'o options. I do suggest you clarify your file age criteria. File time stamps have approximately second-level resolution (though find gives you only minutes or days as an age specification) so saying older than the current date sounds a little ambiguous. (No doubt you know what you mean. Just be sure you get it straight before writing your script or developing your find incantation.) Find also allows you to use the modification time of an existing file as the age reference. In conjunction with this, you might want to review the capabilities of the touch command, which allows to you set the modification time of a file to an arbitrary value. Good luck. Randall Schulz At 07:31 2003-07-08, Steve wrote: Hi; I'm on windows 2000 with cygwin. I need to make a script that will check all of the file modified dates on all of the files in a list of directories. If any of these dates is older then the current date I want to print the name of the file and the date to a file. I'm new to bash scripting and many unix commands. What are the commands that I want to loook at that could do these things for me? Thanks in advance Steve -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: send message/mail from command line
Andrew, The most minimal solution is ssmtp. More fully featured is exim. Man pages and extended documentation in /usr/doc/exim-* and /usr/doc/ssmtp-* are available for both of these. Randall Schulz At 18:52 2003-07-08, andrew goa wrote: Is it possible to send messages/mail from the command line in cygwin. If so point me to the manual please. Andrew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: find -exec oddity
Ken,
At 16:38 2003-07-07, Ken Dibble wrote:
Ok, I'm an idiot. I've looked in the FAQ, searched the mail lists
and checked sundry Unix sources (no, not the source code).
Well, I doubt greatly that you're an idiot. Confusion is the prelude to
enlightenment, after all...
(Compare that with Eudora whose mood watch feature seems to think the
first sentence of the previous paragraph is some kind of insult!)
However, we'd all appreciate it if you'd figure out how to use your
mail client to make sure text attachments are not placed in-line with
the message content. Not to do so defeats the purpose of attaching the
cygcheck output, which is to make list searching meaningful by
preventing the false hits that occur because of all the package and
file names that are included in the cygcheck output.
I can't make sense of this.
$ find ./ -mtime -1 -print | wc -l
55
$ find ./ -mtime -1 -ls | wc -l
55
$ find ./ -mmin -1440 -ls | wc -l
55
$ find ./ -mtime -1 -exec ls -l '{}' \; | wc -l
2046
Look carefully at the man page for find where the -ls option is
described. It says that -ls is equivalent to running ls with the
options -dils. The salient option here is -d which suppresses the
listing of a directory's contents when a directory is an explicit
argument to ls. You're not including -d in your invocation of ls, so
every directory produced by find contributes its entire contents to the
output of ls that is subsequently counted by wc -l.
$ find ./ -mtime -1 -exec ls -l {} \; | wc -l
2046
$ find ./ -mmin -1440 -exec ls -l {} \; | wc -l
2046
and just for grins
$ find ./ -print | wc -l
31701
$ find ./ -mtime -10 -print | wc -l
285
$ find ./ -mtime -100 -print | wc -l
15590
The oddity (bug?) appears to be tied to -exec somehow.
No. The -exec option is doing just what you ask and just what it should.
Attached is cygcheck -c -v -s.
As above.
I can't attach the file lists (unpiped find output) as the message
size then exceeds 100K and the redhat mailserver bounces it.
No matter. It's not needed.
Any help would be appreciated.
I hope my assumption about the problem is correct (file count
discrepancies), since you didn't really say what it was that perplexed you.
thanks,
Ken
Randall Schulz
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: [[ ]] test always reports a not found error in bash shell scrip t
Michael, At 09:21 2003-06-26, MATTHEWS,MICHAEL (HP-Vancouver,ex1) wrote: Thu 2003/JUN/26 0921 PDT Hello, I am porting a Linux build system to Windows XP by using the Cygwin 1.3.22-1 environment (see the attached text file for output from cygcheck -s -v -r). All of the bash shell scripts use the [[ ]] test in if statements, similar to: if [[ $(uname -s) != Linux ]] then # Do Cygwin stuff else # Do Linux stuff fi Whenever I run the script in the Cygwin bash shell, the conditional executes, but the following error is displayed in the terminal window: [[: not found My guess is that your scripts begin with something like this: #!/bin/sh Under cygwin, this invokes ash, not BASH. If I replace the double square brackets with single square brackets: if [ $(uname -s) != Linux ] then # Do Cygwin stuff else # Do Linux stuff fi I do not get any error message. I use the [[ ]] test because from what I read about the bash shell conditional testing, using [[ ]] is better than [ ], since [[ ]] is tested internally, whereas [ ] is tested in a separate shell with the test command. I would prefer to not have to change all of the test conditionals in our Linux bash shell scripts from [[ ]] to [ ]. Background information from my Cygwin: BASH_VERSINFO=([0]=2 [1]=05b [2]=0 [3]=9 [4]=release [5]=i686-pc-cygwin) BASH_VERSION='2.05b.0(9)-release' % bash --version GNU bash, version 2.05b.0(9)-release (i686-pc-cygwin) Copyright (C) 2002 Free Software Foundation, Inc. % help [ [: [ arg... ] This is a synonym for the test builtin, but the last argument must be a literal `]', to match the opening `['. [[ ... ]]: [[ expression ]] Returns a status of 0 or 1 depending on the evaluation of the conditional expression EXPRESSION. Expressions are composed of the same primaries used by the `test' builtin, and may be combined using the following operators ( EXPRESSION ) Returns the value of EXPRESSION ! EXPRESSIONTrue if EXPRESSION is false; else false EXPR1 EXPR2 True if both EXPR1 and EXPR2 are true; else false EXPR1 || EXPR2 True if either EXPR1 or EXPR2 is true; else false When the `==' and `!=' operators are used, the string to the right of the operator is used as a pattern and pattern matching is performed. The and || operators do not evaluate EXPR2 if EXPR1 is sufficient to determine the expression's value. Two things are germane here: 1) [[ ... ]] _is_ available in Cygwin BASH (of course). 2) The distinction between [ ... ] and [[ ... ]] is not what you seem to think it is. In particular, they're both BASH built-ins. I checked the versions of bash in Cygwin and in Linux and they are: Cygwin bash version : GNU bash, version 2.05b.0(9)-release (i686-pc-cygwin) Linux bash version : GNU bash, version 2.05b.0(1)-release (i686-pc-linux-gnu) The version of Linux we are using is Red Hat 8.0 Linux. -Michael Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: website broken
Hi, At 15:03 2003-06-25, Karsten M. Self wrote: on Wed, Jun 25, 2003 at 04:59:11PM -0400, Rolf Campbell ([EMAIL PROTECTED]) wrote: When I view www.cygwin.com, I get an empty page. /home/rcampbell wget -S www.cygwin.com --16:57:26-- http://www.cygwin.com/ = `index.html' Resolving www.cygwin.com... done. Connecting to www.cygwin.com[66.187.233.205]:80... connected. HTTP request sent, awaiting response... End of file while parsing headers. Retrying. /home/rcampbell telnet www.cygwin.com 80 Trying 66.187.233.205... Connected to www.cygwin.com. Escape character is '^]'. Connection closed by foreign host. Confirmed from three sites: West coast US, US central, and UK. I'm on the West coast (SF Bay Area) and have tried the site every time one of these reports come through and have had no trouble accessing it. And I have confirmed it is not locally cached data I'm viewing. This problem is not with the servers at RedHat, that much seems certain. Randall Schulz Host pings, web doesn't serve. Peace. -- Karsten M. Self -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bourne Shell Programming on Windows
TAM, Cygwin includes ash, BASH and pdksh (as well as zsh and tcsh), so the answer is pretty much yes, though with BASH you might want to investigate its Bourne shell compatibility mode. I'm unfamiliar with any details of pdksh's Bourne compatibility, but it should be pretty close or perhaps have a Bourne shell compatibility mode as BASH does. Randall Schulz At 09:13 2003-06-22, TAM wrote: Hi, I was wondering if I can do Bourne shell programming on Windows 2000 Pro using Cygwin. If not, is there any other program that will allow me to do so. Thanx TAM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
eBay Fraud (OT)
Hi, This is from the latest Risks digest (22.77--see news:comp.risks): -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- Date: Fri, 13 Jun 2003 09:14:12 -0400 From: John Reinke [EMAIL PROTECTED] Subject: eBay fraud Police in South Salt Lake, Utah, are working with eBay to determine just how many people were victimized by what authorities say was one of the biggest frauds in the auction site's history. Police arrested 31-year-old Russell Dana Smith last weekend after hundreds of auction winners complained that they sent $1,000 or more to a company named Liquidation Universe for laptop computers they never received. Police say the firm appears to have raked in $1 million from about 1,000 victims in just a few weeks. [...] [Source: Bob Sullivan, MSNBC, Man arrested in huge eBay fraud; Buyers criticize auction site's seller verification service] http://www.msnbc.com/news/925433.asp?0dm=C12LT [FJR: Guarantees are only as good as the guarantor. There ain't no free lunch. When will people take security seriously?] [This one is a long and ugly story. PGN] -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- (PGN is Peter G Neumann, the moderator of the Risks Forum.) Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Mozilla vis-à-vis Cygwin
Michael, Oh, yeah... Another D'Oh! moment: Now that you mention it, I remember your post. Sorry to act like it was a discovery. Apparently the people who earlier mentioned an interest in Mozilla under Cygwin / Cygwin-XFree86 had only an idle interest. I'll admit it's not a priority for me, I just wanted to let people know. As it turns out, it was redundant to do so. The old memory is going! Randall Schulz At 10:37 2003-06-17, Michael F. March wrote: I posted the same thing last month and no one seems to care. http://www.cygwin.com/ml/cygwin/2003-05/msg00599.html
Re: changing bash window title
At 07:54 2003-06-17, Igor Pechtchanski wrote: On Tue, 17 Jun 2003, Sanjay Goel wrote: Hi, the bash window has title Cygwin by default .. whenever I do a telnet or lynx .. it changes the title .. how do I restore it again or change it to something custom .. TIA Sanjay Sanjay, The default .bashrc has a commented out function settitle(). Just uncomment that line, restart bash, and you'll be able to run settitle Your Title (no quotes necessary). The function works for the console window, xterm, and rxvt. If your .bashrc doesn't have that function, look in /etc/skel/.bashrc, or search this list for settitle. Note the control characters. Igor Igor, Where do the contents of /etc/skel originate? I install everything available via Setup.exe, and my /etc/skel contains only .bash_profile which contains only this: -==- # ~/.bash_profile: executed by bash for login shells. if [ -e /etc/bash.bashrc ] ; then source /etc/bash.bashrc fi if [ -e ~/.bashrc ] ; then source ~/.bashrc fi -==- /etc/bash.bashrc contains only a comment and two blank lines. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Mozilla vis-à-vis Cygwin
Michael, Oh, yeah... Another D'Oh! moment: Now that you mention it, I remember your post. Sorry to act like it was a discovery. Apparently the people who earlier mentioned an interest in Mozilla under Cygwin / Cygwin-XFree86 had only an idle interest. I'll admit it's not a priority for me, I just wanted to let people know. As it turns out, it was redundant to do so. The old memory is going! Randall Schulz At 10:37 2003-06-17, Michael F. March wrote: I posted the same thing last month and no one seems to care. http://www.cygwin.com/ml/cygwin/2003-05/msg00599.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Mozilla vis-à-vis Cygwin
Hi, A while back there was some talk about the feasibility of a Cygwin-based Mozilla. In perusing the release notes for Mozilla 1.4 (http://www.mozilla.org/releases/mozilla1.4rc1/) I noticed this: - As of Mozilla 1.4b, it is possible to build Mozilla for Win32 using GCC. See the win32 build instructions (http://www.mozilla.org/build/win32.html) for details. Perhaps this represents a meaningful portion of a the porting work necessary to create a GCC- / Cygwin- / X-based Mozilla variant. Randall Schulz
RE: Bash 2.05 not reading my ~/.bashrc
Dean, At 07:52 2003-06-16, Schulze, Dean wrote: I checked the mail archives for this problem before posting but found nothing of any help. A search engine that uses boolean logic (or something like Google) would help a lot. Use the domain-restricted Google search feature at (http://www.google.com/advanced_search) to search the Cygwin mail archives. You can get this capability while skipping the advanced search page by using this syntax in a simple Google search: site:cygwin.com. I solved this problem by putting . .bashrc at the end of the /etc/profile. My experience with Cygwin is that it is very unstable. Every new release introduces new bugs. How about getting to a stable version and keeping it available instead of making everyone download the latest build? Your experience is not shared. Cygwin is very large and its components are not really part of a unified whole (that being a kind of illusion presented by the installer). Those pacakges maintained by a disparate group of volunteers and considering all the factors, are of very high quality generally. Furthermore, the changes visible to end users of Cygwin often reflect incorporation of upstream changes produced by the core developers of the various open source projects that Cygwin incorporates. Not to keep up with these would mean forever falling behind the current state of development of those programs. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Mozilla vis-à-vis Cygwin
Hi, A while back there was some talk about the feasibility of a Cygwin-based Mozilla. In perusing the release notes for Mozilla 1.4 (http://www.mozilla.org/releases/mozilla1.4rc1/) I noticed this: - As of Mozilla 1.4b, it is possible to build Mozilla for Win32 using GCC. See the win32 build instructions (http://www.mozilla.org/build/win32.html) for details. Perhaps this represents a meaningful portion of a the porting work necessary to create a GCC- / Cygwin- / X-based Mozilla variant. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash : stderr more (pipe for stderr)
Alex, At 00:25 2003-06-14, Alex Vinokur wrote: $ command | more # works only for stdout $ command | more bash: syntax error near unexpected token `' How to use pipe for stderr? BASH uses the Bourne and Korn shell syntax for redirection. You're using the CSH / tcsh variety. # Redirect standard out and standard error separately % cmd stdout-redirect 2stderr-redirect # Redirect standard error and out together % cmd stdout-redirect 21 # Merge standard error with standard out and pipe % cmd 21 |cmd2 Randall Schulz Thanks, Alex Vinokur -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: The other side of bell-style
Michael, Cygwin was changed to use the system beep as of Cygwin version 1.3.21: From http://cygwin.com/ml/cygwin/2003-03/msg00841.html: Changes since 1.3.20-1: - Use MessageBeep for cygwin bell. (Vaclav Haisman) So just update your Cygwin and you'll get what you want. Randall Schulz At 09:39 2003-06-13, Michael T. Davis wrote: Looking through the archives and searching the 'net, it looks like most people want to disable the bell in CYGWIN. In my case, I find the bell coming through my PC's speaker annoying, but only because it's not coming out of my audio card. I would prefer to be able to have the beep passed through my audio card and, ideally, allow the selection of what sound file (e.g. .WAV) would be played. ...Possible? Thanks, Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Vim and the navigating with arrow keys
Brian, At 06:27 2003-06-10, [EMAIL PROTECTED] wrote: True Vim'ers DO NOT navigate with arrow keys. I remember reading that somewhere. Certainly the correct way to navigate in Vim is with the H J K and L keys. Understood, acknowledged, yaddy yadda yaaa. That said - I like to use the arrow keys. It's habitual and something I've been doing for years and years. And like most folks, I resist change. Therefore, I'm a little disturbed that the latest Vim appears to have completely disabled the arrow keys for navigation, or even for mapping. You are mistaken. Arrow keys are working fine in: VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Jun 1 2003 19:49:13) If arrow keys are not functioning for you in Vim, the problem is not Vim itself. Is this a planned and permanent new condition?? The previous version 6.1-300 still has arrow keys enabled, but 6.2-1 does not - or so it appears. Now I do note, the navigating appears much more precise and improved with 6.2-1, no more having to do CTRL-L's to refresh the screen after navigating small text files. (Which was a bother). I don't use RXVT, but bash in a cmd shell. What TERM setting are you using? I have always found Vim to be virtually flawless in screen maintenance with TERM=cygwin under the Cygwin console-based terminal emulation. I'm a minimalist at heart and try to use native and ubiquitous utilities to the greatest extent possible - which is why I long ago chose Vi as my primary editor. Because it's everywhere, especially in UNIX, I'm never without my editor. Anyhow, I'd just to like to know if anyone else has noticed this, cares, or knows something about it. I can of course live without arrows, but I'd rather not if I don't have to. We're all deeply caring people here, even if a bit mean. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Vim and the navigating with arrow keys
Brian, At 07:25 2003-06-10, [EMAIL PROTECTED] wrote: ... However, I do take issue with your practically flawless line - for I still have the need to do CTRL-L refreshes with small files. Example: Simple text file with the following text: cygrunsrv -E cron Open in Vim, and do nothing but touch the L (lower case of course) key and navigate to the end of the line. The following text is the result: ccygrunsrv -E cro Again, I cannot recreate this symptom. How up-to-date are your other Cygwin packages? There have been termcap and terminfo updates in the past several weeks. Did you install them? Have you looked at you ~/.vimrc file lately to see if there's anything odd there? Perhaps clearing your ~/.viminfo would help? Do you use the tty option in your CYGWIN environment variable? I don't, so that could conceivably be a source of the dissimilarity between Vim's behavior on our respective systems. Of course a simple CTRL-L (lower case L) fixes this. I get the same result with the arrow keys. This is nothing new to me, and I've been living with it as long as I've used cygwin and vim together. The behavior occurs when navigating the first few lines of a large file, or any line of a file small enough to fit completely on the screen. There is no reason you should have to endure this misbehavior. None of this is crippling and if there is some setting I can change to correct it, it would be nice. I surely would not put up with it. I thank you sir for pointing out my incorrect TERM setting. Since I'm not qualified to give you a gold star, I'll simply pledge my support give you my promise to cast a ballot for you if a gold star referendum were ever held. ( hmmm, I can't remember if I'm registered to vote! ) Brian Kelly Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Sparse file criteria malfunction - binutils produces sparse .exe .dll files
Chris, At 10:44 2003-06-05, Christopher Faylor wrote: On Thu, Jun 05, 2003 at 05:56:05PM +0200, Markus Mauhart wrote: But nevertheless send me an email in case you find out more about since when typical unix/linux FSs support holes inside files ! Traditional UNIX has done this for at least 10 years. Jeez, Chris, I thought you were old like me. Unix (as in that quaint old piece of software written for the PDP-11 by Dennis Ritchie and Ken Thompson back in the 70s) has had sparse files (created by the simple expedient of seeking beyond the end of the file and then writing) for much longer than 10 years. This capability (which was transparent and not subject to user-level control) was present since at least version 6 of progenitor Unix, the first I ever used, which was current ca. 1976. Only the kernel and things like file system checkers and file system dump and restore tools that operated directly on disk structures had to know about sparse file allocation. Randall Schulz And, since I'm sufficiently trustworthy, I don't have to back up that claim with any real data. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Sparse file criteria malfunction - binutils produces sparse .exe .dll files
Chris, At 06:53 2003-06-06, Christopher Faylor wrote: ... Nevermind. I was testing in a directory where I'd set the compression bit on. So much for my trustworthiness... Never ascribe to malice something that can be explained by absent-mindedness. It's one of those Occam's razor things. I suppose we could go so far as to replace malice with meanness. cgf RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: rsync and cygwin paths
At 10:06 2003-06-04, Igor Pechtchanski wrote:
On Wed, 4 Jun 2003, Lapo Luchini wrote:
...
Please notice that there is a default prgoramm called cygpath that's
really useful to convert path- and file-names between the two version,
and it's not so hard to create wrapper scripts to convert them, e.g.
(I copied this long ago from I-don't-remember-where):
http://cygwin.com/cygwin-ug-net/using-utils.html#CYGPATH
NEWARGS=
for arg in $@ ;
do
if [ -e ${arg} ]; then
NEWARGS=${NEWARGS} `cygpath -p -w $arg`
else
NEWARGS=${NEWARGS} $arg
fi
done
Lapo,
Note that the above won't work correctly if the program is expected to
create the file with a given name... IMO, there is no way of writing a
generic wrapper script without knowing anything about program parameters.
Igor
Igor,
Strictly speaking, that's true. Certainly Lapo's script fragment is too
simple-minded to work in any kind of general setting.
However for many purposes it's feasible to write some simple-minded
heuristics that make the determination about when and how to apply
cygpath. I currently use a BASH script that uses a simple case
statement to paper over the Cygwin / Windows interface for invoking the
Java 2 SDK tools. The case statement's glob patterns detect whether any
given argument is (probably) a file name or PATH-like entity and then
applies cygpath as necessary. It can be fooled, of course, but in
practice it works fine for me.
Randall Schulz
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: rsync and cygwin paths
At 10:44 2003-06-04, Igor Pechtchanski wrote:
On Wed, 4 Jun 2003, Randall R Schulz wrote:
At 10:06 2003-06-04, Igor Pechtchanski wrote:
On Wed, 4 Jun 2003, Lapo Luchini wrote:
...
http://cygwin.com/cygwin-ug-net/using-utils.html#CYGPATH
NEWARGS=
for arg in $@ ;
do
if [ -e ${arg} ]; then
NEWARGS=${NEWARGS} `cygpath -p -w $arg`
else
NEWARGS=${NEWARGS} $arg
fi
done
Lapo,
Note that the above won't work correctly if the program is expected to
create the file with a given name... IMO, there is no way of writing a
generic wrapper script without knowing anything about program parameters.
Igor
Igor,
Strictly speaking, that's true. Certainly Lapo's script fragment is too
simple-minded to work in any kind of general setting.
However for many purposes it's feasible to write some simple-minded
heuristics that make the determination about when and how to apply
cygpath. I currently use a BASH script that uses a simple case
statement to paper over the Cygwin / Windows interface for invoking the
Java 2 SDK tools. The case statement's glob patterns detect whether any
given argument is (probably) a file name or PATH-like entity and then
applies cygpath as necessary. It can be fooled, of course, but in
practice it works fine for me.
Randall Schulz
Randall,
I agree, Java is not too hard. I believe I've posted the wrapper script
that I used at one point or another. Certainly the parameters to Java
itself can be recognized exactly. It's also easy enough to decide that
anything in the program arguments with a '/' in it is a filename, and
convert it accordingly. WFM (tm).
I was talking about the general case, for an unknown Win32 application.
Igor
Igor,
While I mostly only use my wrapper for Java, there's no specific
knowledge of the Java SDK tools built into it (there are 26 of them!).
The only time I've seen it mess up is when I use an argument to
javadoc with the English construct and / or (or, more likely, the
computer term I/O), the forward slash gets changed to a backslash.
This is pretty much the only kind of problem you're likely to get into
with a generic approach. Things that can be construed as Cygwin file
names but are not get inappropriately transformed, of course. One can
always refine the pattern detection in the wrapper script if necessary.
WFM? Of course. What else matters??
Randall Schulz
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Reply-To: cygwin@cygwin.com
Hi, The Reply-To: header (or, more precisely, control over it) belongs to the originator of the mail, not to the list server or its administrator. Randall Schulz At 13:40 2003-06-03, Biju G C wrote: cgf, When I reply to any mail from cygwin list it is going to the actual sender instead of [EMAIL PROTECTED] upon checking the header of the mail from the list i am not seeing Reply-To: [EMAIL PROTECTED] line. just like cygwin-xfree list can v added Reply-To: [EMAIL PROTECTED] to mail the header cheers biju -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Reply-To: cygwin@cygwin.com
At 15:54 2003-06-03, Biju G C wrote: --- Randall R Schulz [EMAIL PROTECTED] wrote: Hi, The Reply-To: header (or, more precisely, control over it) belongs to the originator of the mail, not to the list server or its administrator. Randall Schulz Then how is it happening in cygwin-xfree list? No were in my mail system I have mentioned [EMAIL PROTECTED] And I use same mail-id with same settings to access both cygwin and cygwin-xfree But they do it differently !!! And one does it right and the other does not. Following is the header of the mail (the one I send to list) after I got from cygwin-xfree list -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Multiwindow request
Jeremy, At 08:47 2003-06-02, Peter Colovas wrote: I think the multi-window mode of xfree is great work. Since the addition of the changeable window title it has been everything I need. I have a feature request. I don't know how difficult it would be, but it would be great if the right click menu in the trayy had the option to open an new xterm window. I sometimes close my only local window, and I hate to have to shut everything else donw just to get a new one. I think some kind of simple mechanism to extend the XWin tray icon's pop-up menu would be good, but to arbitrarily add an xterm item seems much to fixed, limited and narrow. Randall Schulz Thanks for all the great work. -- Peter W. Colovas
Re: Windows NT installation 1.3.22-1
Panos, This question probably belongs on the general Cygwin list, no on Cygwin-XFree. I've added that list to this reply's distribution. Further follow-ups and replies should go there only. I believe you're expecting a CSH-equivalent shell (tcsh, e.g.). That shell is available under Cygwin, if you install it, but it is not the default interactive shell. That role is filled by BASH. You can modify or replace the BAT file or shortcut you use to start a Cygwin shell to use the shell of your choice. If eventually you set up remote logins using SSH, you'll have to modify the password file to override the default shell recorded there, which again will be /bin/bash. Cygwin makes available the following interactive shells via its Setup.exe installer: ash bash ksh (pdksh) sh (actually a synonym for ash -- beware when writing scripts using #!/bin/sh) tcsh zsh Good luck. Randall Schulz At 02:51 2003-05-28, Panos Stavroulis wrote: Hi, I've just installed ver 1.3.22-1. I can't do the foreach command from the prompt and don't need to write a script. Is something wrong with my installation or I am doing something wrong. Sorry if my question is too simplistic. Thanks, Panos
Re: behaviour of for (( exp1; exp2; exp3 )); do COMMANDS; done
Sam, At 03:17 2003-05-28, Sam Edge wrote: Stuart Brady [EMAIL PROTECTED] wrote in [EMAIL PROTECTED] in gmane.os.cygwin on Tue, 27 May 2003 13:07:18 +0100: On Tue, May 27, 2003 at 12:42:21PM +0100, Sam Edge wrote: Make sure that if your script uses Bash-specific features, it starts with #!/bin/bash and not with #!/bin/sh. That way it'll work anywhere. You've made the assumption that bash is always in /bin. I've seen it in /bin, /usr/bin, /usr/local/bin, /usr/contrib/bin, and /opt/bash/bin. ~/bin would be another likely place for it. I just _knew_ I shouldn't have said anywhere. ;-) Unfortunately this is a general weakness in the #!/ syntax. (OT) Does anyone know if any of the common shells, when they see #!/bin/ at the front of a script, try a $PATH search for an executable if they can't find /bin/? This would seem like a good idea to me. The interpretation of #! lines is in the kernel (or, hereabout, Cygwin1.dll, a kernel by any other name), just as the kernel would how to handle a binary executable by examining its header. However, shells usually fall back to interpreting script if the kernel reports particular errors on the exec(2) system call (ENOEXEC, i.e.). When this happens, the shell knows that the file exists, that the permissions allow execution but the kernel could not execute the file because its format was not suitable. Then the shell will try to interpret the script as one of its own. (That, by the way, causes some odd errors when foreign executables are brought to Cygwin and executed. Cygwin1.dll and / or Windows cannot execute these so the shell starts interpreting a binary file as commands. Shell syntax errors ensue.) So the shells could be modified to do what you suggest, but if there are any that do it now, I don't know of them, but I really only know much about BASH these days. I seem to recall some discussion way back when as Berkeley Unix introduced this feature about PATH searching for #! executions being a possible security hole. To my knowledge, no Unix does this, but again, I claim no extensive knowledge of the current state of affairs. Randall Schulz Regards, -- Sam Edge -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Windows NT installation 1.3.22-1
Panos, This question probably belongs on the general Cygwin list, no on Cygwin-XFree. I've added that list to this reply's distribution. Further follow-ups and replies should go there only. I believe you're expecting a CSH-equivalent shell (tcsh, e.g.). That shell is available under Cygwin, if you install it, but it is not the default interactive shell. That role is filled by BASH. You can modify or replace the BAT file or shortcut you use to start a Cygwin shell to use the shell of your choice. If eventually you set up remote logins using SSH, you'll have to modify the password file to override the default shell recorded there, which again will be /bin/bash. Cygwin makes available the following interactive shells via its Setup.exe installer: ash bash ksh (pdksh) sh (actually a synonym for ash -- beware when writing scripts using #!/bin/sh) tcsh zsh Good luck. Randall Schulz At 02:51 2003-05-28, Panos Stavroulis wrote: Hi, I've just installed ver 1.3.22-1. I can't do the foreach command from the prompt and don't need to write a script. Is something wrong with my installation or I am doing something wrong. Sorry if my question is too simplistic. Thanks, Panos -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: behaviour of for (( exp1; exp2; exp3 )); do COMMANDS; done
Peter, Make sure your scripts explicitly state /bin/bash as their shell. The default shell (i.e. /bin/sh) under Cygwin is ash, not BASH. It produces the diagnostic you mention when given that command. Randall Schulz At 00:56 2003-05-27, Peter Oosterlynck wrote: When using a line like for (( i=1 ; i=5 ; i+=1 )); do echo $i; done in a bash script one expects to get a list of figures ranging from 1 to 5 right? I've never had problems with such constructs on my Linux machine but when doing this in a cygwin bash shell, then it works fine when typed in at the command line but fails with a syntax error Bad for loop variable when executed in a script. Where did I go wrong? Ideas anybody? Thanks in advance, Peter. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: redistributing cygwin1.dll
Yo! Presto Man, Where's that bait site you were going to set up? Or is it one of those hide-and-seek things? RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bash and xterm window title
Ajay,
The preferred answer is: Read the BASH manual, where the details of how
to use the special escape codes recognized in the PS1 string are fully
explained.
To wit:
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
PROMPTING
When executing interactively, bash displays the primary prompt PS1 when
it is ready to read a command, and the secondary prompt PS2 when it
needs more input to complete a command. Bash allows these prompt
strings to be customized by inserting a number of backslash-escaped
special characters that are decoded as follows:
\a an ASCII bell character (07)
\d the date in Weekday Month Date format (e.g., Tue May
26)
\D{format}
the format is passed to strftime(3) and the result is
inserted into the prompt string; an empty format results
in a locale-specific time representation. The braces are
required
\e an ASCII escape character (033)
\h the hostname up to the first `.'
\H the hostname
\j the number of jobs currently managed by the shell
\l the basename of the shell's terminal device name
\n newline
\r carriage return
\s the name of the shell, the basename of $0 (the portion
following the final slash)
\t the current time in 24-hour HH:MM:SS format
\T the current time in 12-hour HH:MM:SS format
\@ the current time in 12-hour am/pm format
\A the current time in 24-hour HH:MM format
\u the username of the current user
\v the version of bash (e.g., 2.00)
\V the release of bash, version + patchelvel (e.g., 2.00.0)
\w the current working directory
\W the basename of the current working directory
\! the history number of this command
\# the command number of this command
\$ if the effective UID is 0, a #, otherwise a $
\nnn the character corresponding to the octal number nnn
\\ a backslash
\[ begin a sequence of non-printing characters, which could
be used to embed a terminal control sequence into the
prompt
\] end a sequence of non-printing characters
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
I believe you're interested in the \w and / or \W sequences.
Randall Schulz
At 08:08 2003-04-05, you wrote:
Hi,
I had some problem with a recent version of tcsh and so I'm using bash. The only
problem I have
with bash is that it re-writes the window title with the current working directory. I
use a script
to name(title) my xterms and bash overwrites it. tcsh does not do that.
I set PS1=$ and now it doesn't do it. The original PS1 is set to:
$ echo $PS1
\[\033]0;\w\007 [EMAIL PROTECTED] \[\033[33m\w\033[0m\] $
The desired behavior in my case is just the prompt gets updated with the PWD and not
the window
title.
How can I do this?
TIA,
-ajay
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: vim quits and cygwin window contents not restored
Chuck, At 15:52 2003-04-05, Charles Wilson wrote: Randall R Schulz wrote: Chuck, I was meaning to write this up earlier, but work keeps getting in the way. When I used your new termcap entry, less (when it's displaying output piped to it via its standard input but not when it is given a file name argument) tells me WARNING: terminal is not fully functional. Well, I hate to be brusque, but I don't maintain termcap, just terminfo. I provided a termcap translation as an offhand thing; I didn't really think about it. Perhaps I should have thought about it, and then not done it g. I don't mind, but if you hate doing or being a thing, why do or be it anyway? Anyway, perhaps some codes were dropped in the terminfo - termcap autoconversion. Or perhaps my new-n-improved terminfo entry is wrong: but the only way to find out is to recompile less to use terminfo/ncurses, and run your testcase. I don't plan on doing that; sorry. If the *terminfo* entry breaks *existing* apps that use *ncurses*, then I want to know, and I'll fix it (patches gratefully accepted, etc etc). Otherwise, I don't care. Termcap is not my baby. It's no problem--I'll just stick with the previous cygwin termcap entry. But why send a termcap entry and then wash your hands of the consequences of it being used? You didn't include any disclaimers, so it seemed like the courteous thing to do to let you know about the problem. --Chuck Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to access a Linux partition
Martin, At 14:06 2003-04-04, Martin wrote: How does Cygwin access a Linux partition? I guess you still need help from us short-tempered chits, eh? There's no way to directly access a file system in Cygwin. Cygwin relies on Windows for file access. If you can find a file system driver for Windows that accesses one of the many Linux file system types, then Cygwin will have access to those file systems. Without non-standard (non-Microsoft) file system drivers, you're limited to FAT, NTFS and SMB. Thank You, You're most welcome. Martin Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: vim quits and cygwin window contents not restored
Hi, Chuck, Thanks for the clarification. I have no idea what was up with the MIME encoding or whatever it was that glitched. At 20:16 2003-04-02, you wrote: Randall R Schulz wrote: Since there were no attachments, I placed the text embedded in the message into a file named cygwin.terminfo and used tic as you prescribed. I get a diagnostic Name collision between cygwin cygwin. I tried removing the existing terminfo entry, but the result is unchanged. Igor is correct. There were two attachments, but the web archive inlined them. If you go to gmane, you'll see the attachments in their original form. But that shouldn't matter too much. The first attachment (or part) is the terminfo input -- the commentblock all the way down to the last dense block of 20 or so lines. That dense block is the termcap entry. You don't want to 'tic' that; it was generated from the longer file using 'tic -C' -- but any codes that termcap doesn't understand are dropped. So converting it BACK to terminfo format is a lossy conversion. Thanks for the clarification. I've set things straight with the terminfo entry. Vim seemed to work perfectly well with the termcap entry for some reason. The tabs all made it through intact. Again, you want the first group. But, if you're cut-n-pasting, you need to insure that each line begins with a tab, not 8 spaces (sometimes tic can be picky about that). You can also hand edit /etc/termcap (back it up, first) and paste the attached cygwin.termcap file into it, deleting the current definition. Can I trouble you to explain why your termcap replaces something so different in the existing /etc/termcap file: cygwin:\ :xn@:op=\E[39;49m:Km=\E[M:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:tc=linux: I understand that this entry incrementally modifies the linux entry. Your new one does not? You just decided to sever the connection? There's too much difference to handle this way? It was a bad idea for some reason? Enquiring minds want to know. Dammit. Just to avoid bridge burning, I added your new entry and renamed the old cygwin one. --chuck Thanks for fixing this up. It was a little annoying not to have the screen restored. Randy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Problem in tcsh
At 06:55 2003-04-03, Soumitra Pal wrote: Corinna, I did whatever you said. Current passwd is the following. ... But still the problem is not solved. Mine is latest cygwin. Thanks and regards, Soumitra. Soumitra, No one seems to have asked you about your readline options. I know next to nothing about tcsh, but BASH uses ~/.inputrc in which you can make completion ignore alphabetic case by using this directive: set completion-ignore-case on Does tcsh use ~/.inputrc or an equivalent? Does it support this option? OK. ... Doing my homework. ... According to the tcsh man page, the complete shell variable controls command completion options. If it's set to enhance, then alphabetic case is ignored. There are other options, of course. E.g., recognize_only_executables could be relevant here and can be expected to interact with other Cygwin mechanisms such as ntsec, actual file modes and owners, etc. Check out the The command-line editor and Completion and listing sections of the tcsh manual. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
Tim, At 07:28 2003-04-03, you wrote: ... Lack of cygwin support has impeded the market penetration of Windows XP64, but it seems Microsoft would rather lose out to linux and HPUX than let their customers run cygwin. It may be they don't understand how many customers depend on cygwin, which is their fault too, since they don't support those customers, just collect the fees and forget them. We don't care. We don't have to. We're the phone company. -- Lily Tomlin -- Tim Prince Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Re: Big Brother is Real
At 12:22 2003-04-03, Timothy C Prince wrote: ... We don't care. We don't have to. We're the phone company. -- Lily Tomlin __ They may care. I doubt their chances of overtaking linux-ia64 or making back their investment in XP64 this year are overwhelming. Tim Prince Tim, A serious response to a humorous remark is more humor. RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: vim quits and cygwin window contents not restored
Chuck, I was meaning to write this up earlier, but work keeps getting in the way. When I used your new termcap entry, less (when it's displaying output piped to it via its standard input but not when it is given a file name argument) tells me WARNING: terminal is not fully functional. Here's an excerpt, with context, from my /etc/termcap: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- # See ansi.sysk and nansi.sys above. nansi.sysk|nansisysk|PC-DOS Public Domain NANSI.SYS with keypad redefined for vi:\ :al=\E[1L:dc=\E[1P:dl=\E[1M:ei=:ic=\E[1@:im=:\ :is=U4 PC-DOS Public Domain NANSI.SYS with keypad redefined for vi 9-29-86\n\E[;75;8p:tc=ansi.sysk: cygwin|ansi emulation for Cygwin:\ :am:hs:in:ms:xo:\ :Co#8:it#8:pa#64:\ :7=^Z:@7=\E[4~:AB=\E[4%dm:AF=\E[3%dm:AL=\E[%dL:DC=\E[%dP:\ :DL=\E[%dM:DO=\E[%dB:F1=\E[23~:F2=\E[24~:F3=\E[25~:\ :F4=\E[26~:F5=\E[28~:F6=\E[29~:F7=\E[31~:F8=\E[32~:\ :F9=\E[33~:FA=\E[34~:IC=\E[%d@:K2=\E[G:LE=\E[%dD:\ :RI=\E[%dC:S2=\E[11m:S3=\E[10m:UP=\E[%dA:ae=\E[10m:\ :al=\E[L:as=\E11m:bl=^G:bt=\E[Z:cb=\E[1K:cd=\E[J:\ :ch=\E[%i%dG:cl=\E[H\E[J:cm=\E[%i%d;%dH:cr=^M:\ :cv=\E[%i%dd:dc=\E[P:dl=\E[M:do=\E[B:ei=\E[4l:fs=^G:\ :ho=\E[H:ic=\E[@:im=\E[4h:k1=\E[[A:k2=\E[[B:k3=\E[[C:\ :k4=\E[[D:k5=\E[[E:k6=\E[17~:k7=\E[18~:k8=\E[19~:\ :k9=\E[20~:k;=\E[21~:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:\ :kb=^H:kd=\E[B:kh=\E[1~:kl=\E[D:kr=\E[C:ku=\E[A:le=^H:\ :md=\E[1m:me=\E[0;10m:mk=\E[8m:mr=\E[7m:nd=\E[C:nw=^M^J:\ :op=\E[39;49m:r1=\Ec\E]R:rc=\E8:sc=\E7:se=\E[27m:sf=^J:\ :so=\E[7m:sr=\EM:ta=^I:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:\ :ts=\E];:u6=\E[%i%d;%dR:u7=\E[6n:u8=\E[?6c:u9=\E[c:\ :ue=\E[24m:up=\E[A:us=\E[4m: lcygwin:\ :xn@:op=\E[39;49m:Km=\E[M:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:tc=linux: ANSI console types # # This entry is good for the 1.1.47 version of the Linux console driver. # -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- The lcygwin is just to prevent a conflict without having to remove the old entry. Now if I switch back (rename cygwin in the above to wcygwin and lcygwin to cygwin), less works as usual for both standard input and file name arguments. Randall Schulz At 12:30 2003-04-03, you wrote: Randall R Schulz wrote: Can I trouble you to explain why your termcap replaces something so different in the existing /etc/termcap file: cygwin:\ :xn@:op=\E[39;49m:Km=\E[M:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:tc=linux: I understand that this entry incrementally modifies the linux entry. Your new one does not? You just decided to sever the connection? There's too much difference to handle this way? It was a bad idea for some reason? No, it's just that the existing termcap is very very different in structure from the existing terminfo entry for cygwin. ... --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Pipe behavior
Steven, At 16:28 2003-04-03, you wrote: Hello, I have a question about pipe behavior. I wrote a simple program that does a printf, sleeps for 5 seconds and then another printf. If I run the program with the following way: $ ./simple | cat The output is delayed until the program finished. I guessed that the pipe is buffered and doesn't flush until it is closed when the program ends. But then I ran the same program as an emacs subprocess and attached a buffer to it. In this scenario the first printf is displayed, 5 seconds pass and then the second printf is displayed. Emacs also uses pipes so I do not understand why the behavior is different. Pipes don't buffer in the manner you describe, but the standard I/O library does when its output is directed to a pipe or a plain file. Are you sure that Emacs uses pipes and not ptys (pseudo-ttys)? Which Emacs are you using? Cygwin or Windows? Thanks Steven Kilby Randall We don't need no stinkin' disclaimers Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: What package is GLX OpenGL from?
Hi, Everybody! (with a Dr. Nick Riviera intonation) With the Monty Python Spam song intonation: FAQ, FAQ, FAQ, FAQ FAQ, FAQ, FAQ, FAQ But in keeping with my policy of not taunting or scolding without including a constructive answer, go here: http://cygwin.com/packages/. For best results, use as much as you know about the name. The search is a non-anchored grep pattern match against the package content lists. File suffixes can help, but beware that some standard command names are symlinks or scripts, so a .exe suffix will not be present in those cases. Randall Schulz At 11:05 2003-04-02, you wrote: My appologies if this is a FAQ, but I haven't found the answer to this, or the more generic question: How do I determine what package file x came from? Help with either is greatly appreciated. Thanks. -- Brian Ford
Re: how do I configure ssmtp on pacbell.net?
Steve, At 23:34 2003-04-01, you wrote: I'm a pacbell dsl user. They gave me an IP address, but not a domain name. Are you sure? Perhaps they simply didn't tell you what it was. Is this you? % nslookup adsl-63-197-19-160.dsl.snfc21.pacbell.net Server: ... Address: ... Non-authoritative answer: Name:adsl-63-197-19-160.dsl.snfc21.pacbell.net Address: 63.197.19.160 Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin license
Ehud, [ To CGF: In partial fulfillment of my assigned penance for suggesting I would cease to use Cygwin in favor of Linux because of my fear of MS spy-ware. ] At 04:44 2003-04-02, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ... I'm intending to do a similar thing - to make a CD with some Cygwin programs and libraries and some other (proprietary) programs NOT linked to the Cygwin libraries. The sources for all the Cygwin programs and libraries will be on the same CD. Conventional, non-legalistic wisdom is that this would be an acceptable discharging of the GPL requirements to provide all sources necessary to rebuild programs that include GPL-ed content. I thought that this satisfy the GPL and I don't have to have a license from Red Hat. Please confirm or correct me. Disclaimers - I do not work for and cannot speak for Redhat - I am not a lawyer - Pointing to this mail will not serve as a defense if following this so-called advice gets you in trouble. You may safely ignore me. I will leave it to others to comment on the technical merits of using Cygwin without its intended installation and setup procedures. Ehud. Randall Schulz Appendix - detailed description of the software distributed - --- This distribution is of the SSH client. Only the following executable are needed: ssh.exe cygwin1.dll cygz.dll cygcrypto-0.9.7.dll. If rxvt window is preferred (easier support for Hebrew font and other niceties) then rxvt.exe and libW11.dll are also needed. NO registry setting or special directories (like /tmp or /etc) are needed. On the CD I put the following sources: cygwin-1.3.22-1-src.tar.bz2 openssh-3.6.1p1-1-src.tar.bz2 openssl-0.9.7a-3-src.tar.bz2 rxvt-2.7.10-2-src.tar.bz2 zlib-1.1.4-1-src.tar.bz2 . The running batch file is: c: set PATH=c:\tty\cygwin\bin set HOME=/cygdrive/c/tty cd \tty\cygwin\bin rxvt -fn -*-Web Hebrew Monospace-normal-r-*-*-15-*-*-*-c-*-iso8859-1 - -geometry 120x46+0+0 -bg navyblue -fg yellow -sl 350 -e ssh -v %1 Of course the rxvt command is on one line. There is a config file in the $HOME/.ssh that has all the targets. - -- Ehud Karni -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: how do I configure ssmtp on pacbell.net?
At 07:25 2003-04-02, Igor Pechtchanski wrote: On Wed, 2 Apr 2003, Randall R Schulz wrote: Steve, At 23:34 2003-04-01, you wrote: I'm a pacbell dsl user. They gave me an IP address, but not a domain name. Are you sure? Perhaps they simply didn't tell you what it was. Is this you? % nslookup adsl-63-197-19-160.dsl.snfc21.pacbell.net Server: ... Address: ... Non-authoritative answer: Name:adsl-63-197-19-160.dsl.snfc21.pacbell.net Address: 63.197.19.160 Randall Schulz Randall, Doesn't DSL give out dynamic IPs? If so, this means that the next time he connects, his IP (and, therefore, his domain name) will be different. Igor Igor, In my experience, even systems using DHCP will keep giving a given MAC the same DHCP address when the host's lease is renewed. If not, my scripts for adapting to changing IP / DNS on dial-in lines (posted earlier and available again, if desired) would handle configuring SSMTP in the rare case that the IP and DNS change. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: how do I configure ssmtp on pacbell.net?
Sergey, At 07:45 2003-04-02, Sergey Okhapkin wrote: Everyone may use free DNS service like dyndns.org. For example D:\nslookup sokhapkin.dyndns.org Server: barney.leapstone.com Address: 10.10.30.21 Non-authoritative answer: Name:sokhapkin.dyndns.org Address: 216.220.64.102 D:\nslookup 216.220.64.102 Server: barney.leapstone.com Address: 10.10.30.21 Name:216-220-64-102.c3-0.hlb-ubr1.hlb-ubr.nj.cable.rcn.com Address: 216.220.64.102 I don't care what is (current:-) IP address and DNS name assigned to me by the provider, all services are configured to use sokhapkin.dyndns.org domain name. That's nice to know. though most people will want to stick to the DNS provided by their ISP or corporate LAN, since that will probably give the best performance. But it any event, it's neither here nor there for the original poster's question. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: vim quits and cygwin window contents not restored
Charles, I must be missing something. At 00:29 2003-04-02, you wrote: Charles Wilson wrote: Sorry, I haven't been following this thread. See below. I'll try to figure out which parts are missing, and reinstate them -- look for a new release (of terminfo-) sometime in the next week. Try the following. First, save /usr/share/terminfo/c/cygwin somewhere handy. Then, download and save the attached file cygwin.terminfo, and run 'tic cygwin.terminfo' which will compile it and install it into your terminfo database. Since there were no attachments, I placed the text embedded in the message into a file named cygwin.terminfo and used tic as you prescribed. I get a diagnostic Name collision between cygwin cygwin. I tried removing the existing terminfo entry, but the result is unchanged. You can also hand edit /etc/termcap (back it up, first) and paste the attached cygwin.termcap file into it, deleting the current definition. Then I saw this, so I figured that there are two text attachments that got merged into a blob of in-line text, so I took the last 20 lines beginning with cygwin|ansi emulation for Cygwin:\ and gave them to tic, and it seems to work (tic likes it and the results reinstate screen context save and restore). Could you clarify what's up here? Am I the only one who didn't see attachments? Anyway, give that a shot. You'll note there are a lot of question marks in the comments in the cygwin.terminfo file. If anyone's feeling really ambitious and likes digging thru terminfo documentation, the fhandler_console.cc source code in cygwin, and playing with /usr/bin/tack.exe... --Chuck Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Make shows invalid contents
Martin, What does Igor's reply to my message about the Chuck's fixed termcap / termino entries have to do with this? Randall Schulz At 08:44 2003-04-02, Martin Gainty wrote: Hello- (makefile attached) all attempts to run make against valid attached makefile result in ... Thank You, Martin - Original Message - From: Igor Pechtchanski [EMAIL PROTECTED] To: Randall R Schulz [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 9:12 AM Subject: Re: vim quits and cygwin window contents not restored ... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: complete.tcsh doesn't handle spaces in $HOME
Hannu, Here's the full set of recommendations: Yours: Stick to [A-Za-z0-9-_.] characters in filenames, settings and such. Plus: Write all your scripts to accommodate the presence of spaces and shell metacharacters in file names. This is a true pain in the ass... I wish everybody could stick to iso-8859-1 or its siblings. This is unrealistic, chauvinistic and atavistic. Randall Schulz At 10:35 2003-04-02, you wrote: From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Aaron Humphrey An easy workaround for this problem is just to wrap all of the $HOME/filename conditions in double quotes, which would probably be a good idea in a future release of tcsh. Once I did this in complete.tcsh, tcsh started up just fine. My experience is: You can expect to have the exact same problem with quite a few scripts and other software. My advice: Stick to [A-Za-z0-9-_.] characters in filenames, settings and such. Sad to say, this does apply for almost any other OS too `:-P /Hannu E K Nevalainen, Mariefred, Sweden -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin license
At 10:40 2003-04-02, you wrote: On Wed, Apr 02, 2003 at 07:30:31AM -0800, Randall R Schulz wrote: [ To CGF: In partial fulfillment of my assigned penance for suggesting I would cease to use Cygwin in favor of Linux because of my fear of MS spy-ware. ] Good answer. You've earned the star. Wow. Praise from Caesar. I'm in heaven. cgf RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: stdio_init: couldn't make stderr distinct from stdout
Christian, At 11:22 2003-04-02, you wrote: Hello, I have cygwin, it works fine but when I run it from a Win2k Telnet session it fails: *=== Bienvenido al servidor Telnet de Microsoft. *=== C:\cd cygwin C:\cygwincygwin 468 [main] bash 472 dtable::stdio_init: couldn't make stderr distinct from stdout I've RDFM and STFW, but there aren't solutions. Really? http://www.google.com/search?q=%22stderr+distinct+from+stdout%22+Cygwin - http://sources.redhat.com/ml/cygwin/2000-12/msg00866.html - http://www.cygwin.com/ml/cygwin/2002-01/msg01395.html Uh-oh: Recursion alert: - http://www.cygwin.com/ml/cygwin/2002-01/msg01383.html Any idea?? Yup. Try harder. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin license
Igor, At 13:34 2003-04-02, you wrote: On Wed, 2 Apr 2003, Randall R Schulz wrote: At 10:40 2003-04-02, you wrote: On Wed, Apr 02, 2003 at 07:30:31AM -0800, Randall R Schulz wrote: [ To CGF: In partial fulfillment of my assigned penance for suggesting I would cease to use Cygwin in favor of Linux because of my fear of MS spy-ware. ] Good answer. You've earned the star. Wow. Praise from Caesar. I'm in heaven. cgf RRS Shall I change the star to say Randy? ];- Igor Now, now. Randall does the good stuff. Randy is the naughty alter-ego. We don't want to encourage Randy, do we? Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in Cygwin bash?
John, Yes, there's a limitation on the total volume of argument strings. All Unix systems have such a limit and so does Cygwin. The limits vary from system to system, though POSIX dictates a minimum value for this limit. If you've got to deal in some kind of open-ended argument list (lists of file names generated by find is probably the most common case), then you must deal with the fact that there's a limit to how many you can pass in a single command invocation. For cases where the total list of files can be processed in pieces, the xargs command will do the divvying up for you, invoking the command as many times as needed to process all the arguments it reads from standard input. Check it out--it should be in your script-writing repertoire. In cases where all of the arguments must be processed in a single invocation some accommodation must be made by the program that processes those strings. A typical approach is to accept arguments held in lines of a text file. Good luck. Randall Schulz At 18:06 2003-04-02, John Williams wrote: Hi folks, I've found a bizarro error that may in fact relate to Cygwin/bash. I'm using the latest version (ran setup and refreshed just yesterday). In the linux kernel configuration process, there is a rule in /linux-2.4.x/makefile that looks like this: dep-files: scripts/mkdep -- `find .` .hdepend The find command returns a huge list of header files, from which dependencies are derived. After some digging I've found that it fails when the length of the string returned by `find...` exceeds about 32K characters. It doesn't seem to matter how many file names are returned, just the total length of the string that contains them all. This may be a bug in the mkdep utility, but I suspect more that it might be a limitation in Cygwin or bash. Is there some fundamental limitation to the length of the argv[] array when launching programs under Cygwin/bash? I created a workaround by doing dep-files: rm -f .hdepend find | xargs scripts/mkdep -- .hdepend But this means I need to patch over the standard linux build distribution before doing anything under Cygwin. Can anyone confirm or deny?! :) Cheers, John -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in Cygwin bash?
John, Are you a famous composer? If so, are you _the_ famous composer? At 18:58 2003-04-02, John Williams wrote: Randall R Schulz wrote: John, Yes, there's a limitation on the total volume of argument strings. All Unix systems have such a limit and so does Cygwin. The limits vary from system to system, though POSIX dictates a minimum value for this limit. Anybody know the standard Cygwin limit off the top of their head? I'm guessing 32K, given what I saw with mkdep You shouldn't want to know this. If anything, you should want to know the POSIX minimum for this limit. For cases where the total list of files can be processed in pieces, the xargs command will do the divvying up for you, invoking the command as many times as needed to process all the arguments it reads from standard input. Check it out--it should be in your script-writing repertoire. Yup - I used xargs in my solution to this problem. It seems not many people build linux kernels under cygwin - I think if they did, this issue I've found would have been reported earlier, because it's the first step in the kernel configuration process. I'm guessing very few Linux kernels get built under Cygwin, but I could be wrong. That tyrant CGF, who won't let me leave, uses Linux to build Cygwin. Is that irony or hypocrisy? (Right, right. It's pragmatism.) Thanks for your reply, John Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin license
At 20:21 2003-04-02, you wrote: Randall R Schulz wrote: Good answer. You've earned the star. Wow. Praise from Caesar. I'm in heaven. And, as in the days of Rome, during the conquering hero's triumphal parade a slave would ride in the chariot with him. As the cheering throng tossed flowers in the hero's path, the slave would whisper in his ear over and over: This too shall pass. How apt. One can only hope. g --Chuck\ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls Question + bug?
Thorsten, At 06:42 2003-04-01, you wrote: * Hannu E K Nevalainen (garbage mail) (03-04-01 11:30 +0100) IMO the sense of it is still there, even in NT. Can't tell about XP - but I would be surprised if the changes were that many. XP is the first rocksolid Windows OS. Hardly. NT 4 and 2000 have always been perfectly stable and reliable for me, running for days and weeks on end without trouble. They have additional (subjective) benefit of not having garish, cartoonish GUIs, though 2K shows some tendencies. Fortunately, most of the silly stuff can be turned off. Marginal drivers and flaky hardware are not Microsoft's fault, though MS may not make it easy to produce a good driver, I don't really know how hard it is. I've been running _well known_ applications on NT that misbehaved every day. Well known does not imply high quality. Nor does the presence of a malfunction in itself point specifically to application problems, OS problems, driver problems or hardware problems. But they didn't normally crush the whole system. Crush? Thorsten Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Big Brother is Real
At 07:14 2003-04-01, you wrote: On Tue, 1 Apr 2003, Thorsten Kampe wrote: ... XP is the first rocksolid Windows OS. [snip] Thorsten ... with completely unrealistic licensing (see the last paragraph of http://www.aaxnet.com/editor/edit029.html#office). OH. MY. GOD. I installed SP3 on my Win2K. Ignorance is NOT bliss. I guess it really is time to move to Linux. Igor Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
Martin, I'm not sure I get your drift. I do mostly Java myself, but on every system except MacOS one must install the Java SDK or runtime separately. I doubt Sun likes that state of affairs and as a Java developer, neither do I, but it's how things are right now. Microsoft dispensed with Java because it's in a legal and market battle with Sun. The JVM it was shipping was horridly out-of-date anyway and not useful for serious Java application developers. Anyway, in this thread we're talking about licensing terms and privacy, not OS quality. Randall Schulz At 07:38 2003-04-01, you wrote: If XP is such a good OS why did they strip out the JVM? Some of us prefer writing component based Java over heavy and slow monolithic Visual Basic apps. I would purchase XP except I want to Manage my registry instead of Microsoft. 'Nuf Said. Martin - Original Message - From: Randall R Schulz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, April 01, 2003 8:29 AM Subject: Big Brother is Real At 07:14 2003-04-01, you wrote: On Tue, 1 Apr 2003, Thorsten Kampe wrote: ... XP is the first rocksolid Windows OS. [snip] Thorsten ... with completely unrealistic licensing (see the last paragraph of http://www.aaxnet.com/editor/edit029.html#office). OH. MY. GOD. I installed SP3 on my Win2K. Ignorance is NOT bliss. I guess it really is time to move to Linux. Igor Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
Thorsten, At 07:50 2003-04-01, you wrote: * Randall R Schulz (03-04-01 17:29 +0100) At 07:14 2003-04-01, you wrote: On Tue, 1 Apr 2003, Thorsten Kampe wrote: XP is the first rocksolid Windows OS. ... with completely unrealistic licensing (see the last paragraph of http://www.aaxnet.com/editor/edit029.html#office). OH. MY. GOD. I installed SP3 on my Win2K. Ignorance is NOT bliss. I guess it really is time to move to Linux. You won't. You would have to use Wine to get Cygwin running, and that is n-o-t s-u-p-p-o-r-t-e-d. I won't what? What are you saying? If I move to Linux (or Solaris or MacOS X or FreeBSD, etc.), Cygwin will become irrelevant for me. You're an odd bird, Thorsten. Thorsten Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
Herr Doktor Faylor, At 08:38 2003-04-01, you wrote: On Tue, Apr 01, 2003 at 08:24:15AM -0800, Randall R Schulz wrote: Thorsten, At 07:50 2003-04-01, you wrote: * Randall R Schulz (03-04-01 17:29 +0100) At 07:14 2003-04-01, you wrote: On Tue, 1 Apr 2003, Thorsten Kampe wrote: XP is the first rocksolid Windows OS. ... with completely unrealistic licensing (see the last paragraph of http://www.aaxnet.com/editor/edit029.html#office). OH. MY. GOD. I installed SP3 on my Win2K. Ignorance is NOT bliss. I guess it really is time to move to Linux. You won't. You would have to use Wine to get Cygwin running, and that is n-o-t s-u-p-p-o-r-t-e-d. I won't what? What are you saying? If I move to Linux (or Solaris or MacOS X or FreeBSD, etc.), Cygwin will become irrelevant for me. I don't recall giving you my permission to move to Linux, Randall. You're too valuable to the cygwin community for me to allow this move. Sorry. Yes, master. How shall I punish myself? cgf Randall Roy (heh!) Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
Chris, At 08:38 2003-04-01, you wrote: I don't recall giving you my permission to move to Linux, Randall. You're too valuable to the cygwin community for me to allow this move. Maybe a gold star would help persuade me to stay... Sorry. cgf Randy (there he is again) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
Chris, At 09:19 2003-04-01, you wrote: On Tue, Apr 01, 2003 at 09:05:51AM -0800, Randall R Schulz wrote: At 08:38 2003-04-01, you wrote: I don't recall giving you my permission to move to Linux, Randall. You're too valuable to the cygwin community for me to allow this move. Sorry. Yes, master. How shall I punish myself? Just monitor the list for the next GPL discussion and try to explain the GPL to someone who thinks they're being unfairly singled out. That should do it. OK, but I'm going to assume the operative word in this prescription for penance is try. Obligatory disclaimer: I ANAL. You? cgf RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Big Brother is Real
Günter, At 09:56 2003-04-01, you wrote: I missed out on that.. What does sp3 for win2k do? It opens a back door for MS snooping. DRM indeed! Btw. I only use amd cpu's. To my understanding they don't have the cpu id (I don't trust a software that allows me to turn the id of because obviously software can also turn it on ;) Pentium IV has dispensed with the CPU ID, too. Bad PR, I guess... If star office and open office can read/write Micro$oft documents there is hope, otherwise don't hold your breath. Too much has been written over the last 2 decades -and stored in word documents-. If you can't open it the tool can't be used in production environments. If it can, a seamless transition is possible. I just got a new laptop (birthday) and the first time of my life I will install 2 (TWO) OS's on it. (you know which ones) It's a constant battle since MS applications will continue to extend their file formats while giving out specs only under non-disclosure. This forces the Open Source community to reverse engineer the file formats. But they're not cryptographic after all. They're meant to be readily encoded and decoded by software, so it's a manageable problem. Keep in mind that there's a world outside business, too, where things like TeX, PostScript and PDF are the linguas franca. Many communities either formally proscribe or informally eschew DOC and PPT files. About the license policies integrated: I know that's not the right newsgroup and I will be very careful: The X box has highly sophisticated copy protection integrated in hard and software. It took a whole half year until it got cracked, but the point is that it cot hacked. I think we have to work with the legal system, not try to subvert it. Microsoft has a right to set the licensing terms it wants. We have a right to tell them to go to hell. Currently however, and as you note, the power relationship is highly skewed. It ain't easy to just say no to Microsoft. I heard/read that there are already a wealth of xp versions for download that have the 'call bill back' inherently disabled. The same is true for MS software. I haven't the latest statistics at hand, but the private household; those who made a copy from the office and brought it home for business and private use, won't pay extravagant prices if this is not possible anymore. Those will 'get' the grey copies because of the internets endless sources. Some OEM versions are also excused from the call-back requirements. A big problem seems to be the de facto standard of behavior by MS products. I loved Sun One's debugger since the function keys are identical to Visual Studio. I love JEDIT since the Ctrl-char functions are identical to the MS way (Ctrl-X, Ctrl-K, Ctrl-V, etc.). If the main competitors can (and no copyright can forbid that) emulate this functionality/behavior I see hope on the horizon. Many high-end applications, even jEdit, have user-configurable keyboard mappings. In other words: Have it your way! If, lastly Office 11 would not be backwards compatible with their previous documents, I see the sun rise! It's still cloudy here. günter Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Big Brother is Real
At 10:10 2003-04-01, you wrote: A lisp would be already a good start. Just don't write programs with it... Hey! Lisp is my all-time favorite language! Corinna -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Big Brother is Real
Günter, That first remark of mine was meant facetiously, of course. SP3 does more than just open a privacy hole (I assume). My guess (nope, I haven't done the research--I had my child-like naivete destroyed by Igor's URL just today!) is that it's during system update that you're going to be probed, but that's just a hunch. It seems likely that were you to successfully configure a firewall to prevent this system probing, you'd also prevent other more desirable activity or would simply cause Windows to refuse to function. Anyway, I shouldn't indulge in this kind of guesswork in public. WinXPNews (http://www.winxpnews.com/) seems to be a good source for this sort of information. If (and when) I really want to know, I'll probably start there. And Google, of course. Good luck. Don't let the bedbugs bite! Randall Schulz At 10:51 2003-04-01, günter strubinsky wrote: Thank you for the clarification, Randall! Fred mentioned the firewall issue. I have actually zone alarm installed and disallowed -permanently- the Microsoft software (with the exception as the usual suspects, DNS, etc.) to contact outside. Now I am not so sure anymore that I got hacked by anyone else but Bill. My system started to behave erratically when I had outlook and other ms programs running: The cpu was around 2-3% busy -never more during those phases- but everything stalled. (Including the task manager). I start to believe that those progs called home and waited for response from ms until they timed out which is why my system froze for about 30-60 seconds, execute a few time slices and then went into wait-state again. I have office xp installed... Is there any info out how the snoop works? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: making X server a COM object..
Harold, At 15:50 2003-03-31, you wrote: KH, The scope is probably beyond the scope of this mailing list. I think you would be better off working first on a version of Cygwin/XFree86 that compiled without Cygwin... then, and only then, could you even begin to worry about wrapping XFree86 with a COM interface. Cygwin /XFree86 without Cygwin is Win32/XFree86, or some such, is it not? It always seemed to me that the target specifier ought to come after the main program name: XFree86/Cygwin, XFree86/Win32, etc. Harold Randall Schulz
Re: Ping program?
Sam, You don't say which version of Windows you're running, but NT, 2000 and XP all include a ping program. Is it insufficient for your needs? % type ping ping is /cygdrive/d/WINNT/system32/ping Randall Schulz At 08:24 2003-03-31, you wrote: I'm dying here. Does anyone have a ping program that will compile under cygwin? I've downloaded about 27 ping programs and none compile. Thanks, Sam -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: command prompt window title
Anoop, At 11:38 2003-03-31, you wrote: I'm running cygwin's latest version 1.3.22-1. When I run cygwin from my desktop, it brings up a command prompt window with a title Cygwin. I modified cygwin.bat to make my default shell tcsh. Anyway, after I run vi, the window title changes to vi fname where fname is the file that I'm editing. When I quit vi, the title of the window remains that way until I quit the window, or I use vi again with another file, in which case it changes to vi newfilename. It sounds to me like there's a script or other intervening command definition handling your invocation of vi. Please show us the output of where vi (assuming, as you state above, that you're using tcsh). If you're using BASH, then show us the output of type -a vi. When running things like gcc or make the window title doesn't get affected at all...it continues to show Cygwin, unless I had previously run vi in that window. Is there a way to fix this? Is this a know issue? I have the screen shots at: http://www.ee.duke.edu/~ag/cygerrs.pdf Thanks, -Anoop -- Anoop Ghanwani Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: command prompt window title
At 15:19 2003-03-31, you wrote: On Mon, 31 Mar 2003, Randall R Schulz wrote: Anoop, At 11:38 2003-03-31, you wrote: ... Anyway, after I run vi, the window title changes to vi fname where fname is the file that I'm editing. When I quit vi, the title of the window remains that way until I quit the window, or I use vi again with another file, in which case it changes to vi newfilename. It sounds to me like there's a script or other intervening command definition handling your invocation of vi. Please show us the output of where vi (assuming, as you state above, that you're using tcsh). If you're using BASH, then show us the output of type -a vi. ... Thanks, -Anoop Randall Schulz Randall, Most likely there is no wrapper script. This is an option of vim itself. In vim, help title. Igor Igor, That explains why I could not find documentation for the title / notitle command when Thorsten mentioned it: I looked in the man and info documentation. However, in my Cygwin Vim I cannot get a title to show even when I :set titlestring=something and :set title. I tried suspending and resuming Vim, too, but still no title. Vim --version does indicate that it was configured for +title, so I'm uncertain what I'm doing wrong that keeps me from getting a title. Maybe it's being displaced through time and space to Anoop's system. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: command prompt window title
At 17:02 2003-03-31, you wrote: Randall, Most likely there is no wrapper script. This is an option of vim itself. In vim, help title. Igor Igor, That explains why I could not find documentation for the title / notitle command when Thorsten mentioned it: I looked in the man and info documentation. However, in my Cygwin Vim I cannot get a title to show even when I :set titlestring=something and :set title. I tried suspending and resuming Vim, too, but still no title. Vim --version does indicate that it was configured for +title, so I'm uncertain what I'm doing wrong that keeps me from getting a title. Maybe it's being displaced through time and space to Anoop's system. Randall Schulz Randall, I believe the title/notitle Thorsten meant was the option in the CYGWIN environment variable, and had nothing to do with vim. As for vim, when TERM=cygwin, the title of the Cygwin console is not changed, but I think this is related to the incomplete terminfo entry for cygwin. If you set TERM=xterm (in the Cygwin console), vim *will* set the title (I used the example in help title). Igor Igor, OK, but then why did you tell me this: This is an option of vim itself. In vim, help title. Really, it's of little consequence to me, but here's an excerpt from the Vim on-line help text: Only works if the terminal supports setting window titles (currently Amiga console, Win32 console, all GUI versions and terminals with a non- empty 't_ts' option - these are Unix xterm and iris-ansi by default, where 't_ts' is taken from the builtin termcap). I know very little about termcap or terminfo (nor which of them Vim uses), but if I cared enough about why this appears not to work for me, I'm sure I could figure it out. Here's a clue. Vim's :set title and :set notitle work if I invoke Vim thusly: % TERM=xterm vi The title string is restored to it's initial value and reset to Vim's titlestring setting when Vim is suspended and resumed (resp.), too. So it seems the termcap and / or terminfo descriptions for TERM=cygwin could have the necessary capabilities added (apparently identical to those used by xterm) so Vim could control the window title under the Cygwin console. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: (Aucun objet)
Jean-Luis, Even though you're using CYGWIN, which provides a very Unix-like environment and inside of which the PATH has a Unix-like syntax, the Sun Java compiler is a Windows application and it expects CLASSPATH to be formatted according to the Windows convention. The path components are separated with a semicolon. The path elements themselves, if they're absolute paths, must begin with a driver letter, followed by a colon, followed by an absolute path name. If you construct your CLASSPATH this way, things should work. Randall Schulz At 22:53 2003-03-31, you wrote: Hello I installed java (j2sdk1.4.0) in Windows. In general I work in LInux and I developped an application in JAVA and ANTLR. I installed CYGWIN and I want to complie my JAVA application in WINDOWS, i uses make for manage compilation. I set my PATH variable for JAVA access and this work fine. But when I want set my CLASSPATH variable, I am in trouble. The setting in CYGWIN environnement don't work, JAVA in out CYGWIN. The setting in CYGWIN script (set CLASSPATH=one dir) work but I want manage many dirs : A. If I set many dir in CYGWIN script this don't work B. If I set many dir in CYGWIN envi this don' work Some people have a the same pb ? Can you help me ? Boulanger JL -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Corrected: setup.exe beta (testing needed - really!)
Hi, You wrote vmtools and vmware. Is that http://www.vmguys.com/vmtools/ or http://www.vmware.com/? Both? Something else? It's really just idle curiosity. I had never heard of vmtools before, so I had to go look it up (it's Java XML stuff) and so it doesn't sound related, but I just thought I'd check. Randall Schulz At 20:50 2003-03-28, you wrote: I'd say there is something wrong with your system/installation of Windows... Could be. But, it is a clean win98 install, then I installed vmtools, then I've run cygwin setup (the experimental one), three times, and only done really minor things in the cygwin terminal (mkdir, touch, ls -l, cd). Oh, and I ran IE to go and get the experimental setup. Probably now I redo the same test with the non-experimental setup, and see what happens. VM as in running Windows on top of say Mac OS/Linux? Actually on top of Win2000. (Using vmware. It is the only way I have time to test stuff on virgin machines.) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Corrected: setup.exe beta (testing needed - really!)
Robert, Ah, right. I should have remembered that. I have VMware on this system (for a couple of months, now) and of course I installed the VMtools. I use VMware to run Linux under Windows since I now have a client who has some Java software that has to runs and build on both. Thanks for refreshing my memory. It was good to bump into the other VMTools, though. Randall Schulz At 21:40 2003-03-28, you wrote: VMWare comes with tools to allow the client OS (the one inside the VM) to interface with the host OS - i.e. mouse release so that the mouse can go from inside the VM to outside easily. These tools are called. vmtools. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Added setup.exe to User's Guide
At 14:15 2003-03-27, you wrote: On Thu, 27 Mar 2003, Christopher Faylor wrote: On Thu, Mar 27, [EMAIL PROTECTED]:11:35PM -0500, Igor Pechtchanski wrote: ***Groan***! Oh, no! Now look what you've done! Next thing you know, we'll be having a contest for the best Cygwin documentation poem! With the winner being awarded gold stars by cgf! ;-) Let the games begin. If it's cygwin related it won't be a sin. So, no reason to be mean and it will even be humorous; or maybe that remains to be seen. There was a young woman named Linda. She had problems installing a window: As she clicked on setup, It just crashed with a pop, And then burned her machine to a cinder. Still waiting for that gold star web page. Elfyn? You volunteering? cgf Oh, *that*... I have that ready to check in. Except... What was Elfyn's first star for? Can't find it in the archives... Igor Igor, From the subject thread entitled [PATCH] Trivial pthread testsuite fixes: On Wed, Mar 26, 2003 at 10:23:31PM -, Elfyn McBratney wrote: On Wed, 26 Mar 2003, Elfyn McBratney wrote: Brian, Your patch may get more attention from the cygwin-patches mailing list as per http://cygwin.com/lists.html. Yes, but it is by subscription only. I prefer to read the archives, at least until they are password protected also. It seems silly to me that in order to submit a Cygwin patch to the appropriate mailing list, you must receive all such patches in your inbox. If you just want posting privilages read the last few (4-5) lines of http://www.cygwin.com/ml/#rbl-sucks. **cgf sends Elfyn a virtual gold star. cgf I think the gold star was for pointing a plaintiff to the on-line documentation Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Added setup.exe to User's Guide
Andrew, At 11:41 2003-03-26, Andrew M. Inggs wrote: ... Specifically for CD-R, I have had trouble doing this because the URL-encoded directories that setup.exe creates to keep track of which mirror you select are not ISO9660 or Joliet friendly. I usually just rename the directory before burning to CD-R. What software do you use to write the CD? I use Nero and it warns me, but I just override it and everything seems to work. I think the problem is not character set, but rather the length of the full names. Perhaps you could shorten and / or remove some of the leading directory components? ... -- Andrew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Mozilla 1.3 built on cygwin?
Jeff, Just outta' curiosity, beyond the satisfaction of accomplishing it, what would be gained? Randall Schulz At 17:24 2003-03-26, [EMAIL PROTECTED] wrote: just outta curiosity, has anyone built Mozilla 1.3 on cygwin? thanks, JeffH -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Mozilla 1.3 built on cygwin?
Michael, At 21:32 2003-03-26, Michael F. March wrote: Jeff, Just outta' curiosity, beyond the satisfaction of accomplishing it, what would be gained? well you could ssh into your windows machine and run mozilla remotely from your xterminal ... umm - okay so thats not much of a gain... but... First off, I have said it before and I'll say it again, Evolution from Ximian needs to be ported to Cygwin.. Anyway.. There would be A LOT to be gained from having a Cygwin port of Mozilla. 1. You could easily hack on features the Windows and Unix source trees if Mozilla ran via Cygwin. Also, you could build Mozilla on Windows without having to use any MSFT products. OK. Whatever those are. I'm guessing the MS in MSFT is Microsoft. I don't know what the FT part is. Building from Cygwin while targeting native Windows APIs would presumably be feasible using MinGW and / or -mno-cygwin, but the result would presumably function just as Mozilla compiled with Visual Studio. 2. Having a complex GUI app like Mozilla ported to Cygwin could prove to be a stick in which to measure and compare the over all efficiency and performance of Cygwin. If the native Mozilla and the Cygwin version performed reasonably the same, then we would know that Cygwin is on track. If the Cygwin version lagged, it would set concrete goals for the Cygwin/XFree team. That's not going to happen any time soon. XFree86/Cygwin has no graphics acceleration. Apart from that, little if anything runs as fast through Cygwin as it does on the Win32 API even if GUI operation is ignored or irrelevant. I don't mean this as a criticism, but just a fact. I imagine the biggest win would be by getting some graphics acceleration in XFree86. 3. I hate where and how Mozilla puts user files under native Windows. The Cygwin port would be better... more like the Linux port. OK, but that's pretty minor in my book. 4. Don't underestimate how great it would be to be able to X in an check your email. Better yet, be able to run more than one user at a time be able to X in and check their email. If I was willing to use Mozilla for mail, that might be valid. Now KMail, that I'd use. As a long time Windows Mozilla user, I would welcome a Cygwin version with open arms. Open arms... Hmmm... Embrace Open Source. Finally.. Every major porting effort that Cygwin goes to does not kill or hurt Cygwin, it makes it stronger and more functional. Unquantifiable. It's clear that bringing otherwise unavailable software to Windows via Cygwin is an unqualified win. However, doing so for software already available on Windows, especially when it's not software that integrates with other Cygwin components, adds rather less. Take Perl, for example. There's a native Windows port and a Cygwin port. But Cygwin Perl is still a win because any Perl program can be run in a context of close interaction (pipelines, scripts, uniform pathname treatment, etc.) with other Cygwin programs. From this perspective, I'd say Cygwin Mozilla would be a rather small win. GUI-intensive, non-scriptable applications for X (which does not itself run unless the Windows GUI system is running beneath it) add rather little when those applications are already available as native Windows programs. And that old saw about what doesn't kill me ... is BS, though I imagine it's also largely irrelevant when applied to software. -- march Michael F. March Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
