[ITP] OpenSP-1.5.1-1
Hello, I want to contribute/maintain OpenSP, version 1.5.1. Canonical homepage: http://openjade.sf.net/ Prerequisite for OpenJade. Monolithic tarball because it is a stable production release. In case the API/ABI changes I'll provide a library/runtime package with the DLL. setup.hint: sdesc: SGML parser, production release. ldesc: The OpenJade project provides a suite of tools and libraries for validating, processing and applying DSSSL (Document Style Semantics and Specification Language) style sheets to SGML and XML documents. requires: cygwin libintl2 libiconv2 http://anfaenger.de/cygwin/opensp/OpenSP-1.5.1-1.tar.bz2 http://anfaenger.de/cygwin/opensp/OpenSP-1.5.1-1-src.tar.bz2 http://anfaenger.de/cygwin/opensp/setup.hint Gerrit -- $ make signature make: *** No rule to make target `signature'. Stop.
setup / postinastall script question
Hello, will it work with setup.exe to set the PATH in a postinstall script? I.e.: export PATH=/usr/X11R6/bin:$PATH * do something * Gerrit -- =^..^=
Re: setup / postinastall script question
On Fri, 9 Jul 2004, Gerrit P. Haase wrote: Hello, will it work with setup.exe to set the PATH in a postinstall script? A postinstall script is just like any other shell script. I don't see any reason why it wouldn't. I.e.: export PATH=/usr/X11R6/bin:$PATH * do something * Gerrit Well, postinstall scripts are usually run with /bin/sh, which means that you'd have to use the following syntax: PATH=/usr/X11R6/bin:$PATH export PATH (note the quotes, BTW, as many Windows paths have spaces). HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Yaakov: libbonobo builds ok. (was: Re: Gerrit: plans for Gnome 2.6)
Yaakov, libIDL (Yaakov) ORBit2 (Yaakov) intltool intltool (Gerrit) libbonobo So this is the next on the list... I'll start now to build libbonobo. libbonobo builds fine with your libIDL and ORBit2 packages. Gerrit -- =^..^=
Re: setup / postinastall script question
On Jul 9 09:46, Igor Pechtchanski wrote: On Fri, 9 Jul 2004, Gerrit P. Haase wrote: export PATH=/usr/X11R6/bin:$PATH Well, postinstall scripts are usually run with /bin/sh, which means that you'd have to use the following syntax: PATH=/usr/X11R6/bin:$PATH export PATH Erm... `export FOO=bar' is perfectly valid bourne shell syntax. Just try it in ash. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Harold gone?
Render ? Harold, is .pc file missing here? Hm, Harold is gone... Who takes over all his packages? Gerrit -- =^..^=
Re: setup / postinastall script question
On Fri, 9 Jul 2004, Corinna Vinschen wrote: On Jul 9 09:46, Igor Pechtchanski wrote: On Fri, 9 Jul 2004, Gerrit P. Haase wrote: export PATH=/usr/X11R6/bin:$PATH Well, postinstall scripts are usually run with /bin/sh, which means that you'd have to use the following syntax: PATH=/usr/X11R6/bin:$PATH export PATH Erm... `export FOO=bar' is perfectly valid bourne shell syntax. Just try it in ash. Well, in all the bourne shell manuals I've seen, the export command can only take a list of names. The above is extended syntax that works in ash, but is certainly not valid bourne shell syntax (incidentally, IIRC, $(cmd) is not valid bourne shell syntax either, although it too works in ash). I understand that Cygwin's /bin/sh *is* ash, so if the postinstall script is intended to only run on Cygwin, the point is moot. I guess I was being conservative, as well as thinking that if the postinstall script is also reused in some other system that supports them (is it Debian's apt?), the above might cause a problem. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: Harold gone?
Gerrit P. Haase wrote: Hm, Harold is gone... Who takes over all his packages? Dunno if Harold is gone as in shall never darken our door again. He just relinquished primary control over the cygwin-xfree project. He didn't say anything about giving up any of his other packages, nor that he would stop reading these lists. Now, it may be true that he IS going to give up all of his pkgs and leave the cygwin community -- but so far, he hasn't said that, or if he did I missed it. Let's not probate the will until we're sure he's kaput. -- Chuck
Re: Harold gone?
Chuck hit the nail on the head. I handed over control of Cygwin/X because I am no longer interested in it. On the other hand, I still use Cygwin proper to get things done, so I can't exactly just sit there if package foo is not yet available for Cygwin and I need it for something I am working on... I'll have to package and maintain it myself. So Chuck was right in guessing that I am not giving up my non-X packages, but I am giving up the Cygwin/X project and I don't want to work on the X Server anymore, that is all. Harold Charles Wilson wrote: Gerrit P. Haase wrote: Hm, Harold is gone... Who takes over all his packages? Dunno if Harold is gone as in shall never darken our door again. He just relinquished primary control over the cygwin-xfree project. He didn't say anything about giving up any of his other packages, nor that he would stop reading these lists. Now, it may be true that he IS going to give up all of his pkgs and leave the cygwin community -- but so far, he hasn't said that, or if he did I missed it. Let's not probate the will until we're sure he's kaput. -- Chuck
Re: [ITP] OpenSP-1.5.1-1
+1 from me. I've been dying to get OpenJade on Cygwin for years. However, I can't remember if it was OpenSP or OpenJade itself that gave compilation problems. In other words, have you finished the tough part yet, or was OpenSP easy? Harold Gerrit P. Haase wrote: Hello, I want to contribute/maintain OpenSP, version 1.5.1. Canonical homepage: http://openjade.sf.net/ Prerequisite for OpenJade. Monolithic tarball because it is a stable production release. In case the API/ABI changes I'll provide a library/runtime package with the DLL. setup.hint: sdesc: SGML parser, production release. ldesc: The OpenJade project provides a suite of tools and libraries for validating, processing and applying DSSSL (Document Style Semantics and Specification Language) style sheets to SGML and XML documents. requires: cygwin libintl2 libiconv2 http://anfaenger.de/cygwin/opensp/OpenSP-1.5.1-1.tar.bz2 http://anfaenger.de/cygwin/opensp/OpenSP-1.5.1-1-src.tar.bz2 http://anfaenger.de/cygwin/opensp/setup.hint Gerrit
Re: Harold gone?
Harold schrieb: Chuck hit the nail on the head. I handed over control of Cygwin/X because I am no longer interested in it. On the other hand, I still use Cygwin proper to get things done, so I can't exactly just sit there if package foo is not yet available for Cygwin and I need it for something I am working on... I'll have to package and maintain it myself. So Chuck was right in guessing that I am not giving up my non-X packages, but I am giving up the Cygwin/X project and I don't want to work on the X Server anymore, that is all. Glad to hear that. My question was, if the pkgconfig file for render is missing in the released tarball or in the render sources or is just me who is missing it in /usr/X11R6/lib/pkgconfig? Gerrit -- =^..^=
Re: Yaakov: libbonobo builds ok. (was: Re: Gerrit: plans for Gnome 2.6)
Gerrit schrieb: Yaakov, libIDL (Yaakov) ORBit2 (Yaakov) intltool intltool (Gerrit) libbonobo So this is the next on the list... I'll start now to build libbonobo. libbonobo builds fine with your libIDL and ORBit2 packages. Here we have the first candidate for --enable-gtk-doc, the docs aren't included in the source tarball, they need to be generated. I'll try if I can finish at least the OpenSP / OpenJade build soon. Gerrit -- =^..^=
Re: Harold gone?
On Fri, Jul 09, 2004 at 11:42:57AM -0400, Charles Wilson wrote: Gerrit P. Haase wrote: Hm, Harold is gone... Who takes over all his packages? Dunno if Harold is gone as in shall never darken our door again. He just relinquished primary control over the cygwin-xfree project. He didn't say anything about giving up any of his other packages, nor that he would stop reading these lists. Now, it may be true that he IS going to give up all of his pkgs and leave the cygwin community -- but so far, he hasn't said that, or if he did I missed it. Let's not probate the will until we're sure he's kaput. Harold still seems to be here and I have asked *Alexander* (I called him Andrew in three or four different email messages yesterday) to subscribe to this list. I don't know if he's willing to maintain Harold's old packages or not. Andrew? Harold? cgf
Re: setup / postinastall script question
On Fri, Jul 09, 2004 at 10:45:39AM -0400, Igor Pechtchanski wrote: On Fri, 9 Jul 2004, Corinna Vinschen wrote: On Jul 9 09:46, Igor Pechtchanski wrote: On Fri, 9 Jul 2004, Gerrit P. Haase wrote: export PATH=/usr/X11R6/bin:$PATH Well, postinstall scripts are usually run with /bin/sh, which means that you'd have to use the following syntax: PATH=/usr/X11R6/bin:$PATH export PATH Erm... `export FOO=bar' is perfectly valid bourne shell syntax. Just try it in ash. Well, in all the bourne shell manuals I've seen, the export command can only take a list of names. The above is extended syntax that works in ash, but is certainly not valid bourne shell syntax (incidentally, IIRC, $(cmd) is not valid bourne shell syntax either, although it too works in ash). I understand that Cygwin's /bin/sh *is* ash, so if the postinstall script is intended to only run on Cygwin, the point is moot. I guess I was being conservative, as well as thinking that if the postinstall script is also reused in some other system that supports them (is it Debian's apt?), the above might cause a problem. FWIW, I didn't know that either of the above constructs worked in ash. I thought Igor's advice was correct. Learn something new...
Re: Harold gone?
On Fri, Jul 09, 2004 at 01:11:31PM -0400, Christopher Faylor wrote: On Fri, Jul 09, 2004 at 11:42:57AM -0400, Charles Wilson wrote: Gerrit P. Haase wrote: Hm, Harold is gone... Who takes over all his packages? Dunno if Harold is gone as in shall never darken our door again. He just relinquished primary control over the cygwin-xfree project. He didn't say anything about giving up any of his other packages, nor that he would stop reading these lists. Now, it may be true that he IS going to give up all of his pkgs and leave the cygwin community -- but so far, he hasn't said that, or if he did I missed it. Let's not probate the will until we're sure he's kaput. Harold still seems to be here and I have asked *Alexander* (I called him Andrew in three or four different email messages yesterday) to subscribe to this list. I don't know if he's willing to maintain Harold's old packages or not. Andrew? Harold? The sad thing is that the above Andrew is not a joke. Sigh. I can see I'm in for many weeks of apologies for calling Alexander Andrew. Sorry, *Alexander*. The even sadder thing is that I didn't need to even respond at all since the rest of this thread made things clear. Move along. Nothing to see here. cgf
Re: [ITP] OpenSP-1.5.1-1
On Fri, 9 Jul 2004 13:12:56 +0200, Gerrit P. Haase wrote: I want to contribute/maintain OpenSP, version 1.5.1. +1 from me, too.
Re: Project leadership change
Christopher Faylor wrote: On Thu, Jul 08, 2004 at 09:31:31PM +0200, Alexander Gottwald wrote: I have to make a sad announce: Harold Hunt, leader of the Cygwin/X project for some years will quit being the project leader because of his new job and family. With Harold quitting I'll take over leadership of the project and will be responsible for making releases, managing the website and documentation and managing the list. I hope I can come up with a similar performance as Harold had shown in the past and want to thank Harold for putting so much time and work into making Cygwin/X a great xserver with features similar to those from commercial ones. Thank you, Harold. After Harold, Kensuke and Takuma can not offer their time anymore we are now short on developers. This means that the external multiwindow windowmanager is not actively developed anymore and I can only continue working on small enhancements and bugfixes. Any help is greatly appreciated. I am also very sad that Harold is stepping down. It's the end of an era. However, thanks very much Andrew for your increased commitment to the project. Harold is leaving things in good hands. I presume you mean Alexander :-) This is one of the good things about open source. Harold etc have done fantastic work (as has Alexander) but they don't have to be forced into continuing it, others can... David
Re: Project leadership change
On Thu, Jul 08, 2004 at 07:07:35PM -0400, Christopher Faylor wrote: On Thu, Jul 08, 2004 at 09:31:31PM +0200, Alexander Gottwald wrote: I have to make a sad announce: Harold Hunt, leader of the Cygwin/X project for some years will quit being the project leader because of his new job and family. With Harold quitting I'll take over leadership of the project and will be responsible for making releases, managing the website and documentation and managing the list. I hope I can come up with a similar performance as Harold had shown in the past and want to thank Harold for putting so much time and work into making Cygwin/X a great xserver with features similar to those from commercial ones. Thank you, Harold. After Harold, Kensuke and Takuma can not offer their time anymore we are now short on developers. This means that the external multiwindow windowmanager is not actively developed anymore and I can only continue working on small enhancements and bugfixes. Any help is greatly appreciated. I am also very sad that Harold is stepping down. It's the end of an era. However, thanks very much Andrew for your increased commitment to the project. Harold is leaving things in good hands. Sigh. I used the name Andrew about 27 times yesterday when I was talking about Alexander. I am sorry Alexander. I've been reading your email for years now and you'd think I would know better. What can I say? I'm an idiot. Sorry. Anyway the sentiment is the same even if I can't get the names straight... cgf
Re: Problem with display
Does the remote machine have X forwarding turned on? Wey Leong wrote: Hi, I used ssh -Y -l username remote_IP to connect to a remote machine. After login to remote machine, I tried to run xterm and fluent. But both gave me an error saying that Can't open display (please see attached JPEG and LOG files). Why? Am I missing something? Please help me to solve the problem. Thank you very much. Regards, Wey Leong Department of Mechanical Industrial Engineering Ryerson University
Using xterm via cygwin
Hello, I'm attempted to start X windows on a WinXP machine with cygwin installed. My goal is to use xterm and telnet to a remote AIX machine. I'm attempting this because I need a more robust terminal then the standard 25x80 text-based emulations. However, the command xterm and xterm -display localhost:0 report the error: xterm Xt error: Can't open display I assumed this is because the X server is not running so I attempt startx and get this error: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-8 Contact: [EMAIL PROTECTED] XWin was started with the following command line: X :0 -multiwindow -clipboard Fatal server error: Cannot open log file /tmp/XWin.log winDeinitMultiWindowWM - Noting shutdown in progress giving up. xinit: No such file or directory (errno 2): unable xinit: No such process (errno 3): Server error. How can I correct this? Or if this is not a feasible plan, what other methods could you recommend to achieve the same goal. Much thanks in advance, Swade _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: Using xterm via cygwin
S Wade wrote: Fatal server error: Cannot open log file /tmp/XWin.log Try checking the permissions on /tmp and /tmp/XWin.log. /tmp should be world-writable, and XWin.log probably should be as well.
Re: GTK missing cygX11-6.dll (Was Re: Wrapping long lines)
On Fri, 9 Jul 2004, Robert McNulty Junior wrote: [snip] I'm trying, however, to catch up on my cygwin updating. Trying to figure out why GTK is telling me cygX11-6.dll (or something like that) is missing. I hope we get a new X11 mainatainer soon. We do have an X11 maintainer. However, he's not expecting to find X problems on the main Cygwin list, so you will have waited quite a bit for a reply. I've redirected this to the appropriate list (cygwin-xfree). Please keep the rest of the discussion on that list. Igor P.S. I've also changed the subject, as this had nothing to do with the thread this was in. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
RE: GTK missing cygX11-6.dll (Was Re: Wrapping long lines)
Thank, Igor. I trust your wisdom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Pechtchanski Sent: Friday, July 09, 2004 9:25 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: GTK missing cygX11-6.dll (Was Re: Wrapping long lines) On Fri, 9 Jul 2004, Robert McNulty Junior wrote: [snip] I'm trying, however, to catch up on my cygwin updating. Trying to figure out why GTK is telling me cygX11-6.dll (or something like that) is missing. I hope we get a new X11 mainatainer soon. We do have an X11 maintainer. However, he's not expecting to find X problems on the main Cygwin list, so you will have waited quite a bit for a reply. I've redirected this to the appropriate list (cygwin-xfree). Please keep the rest of the discussion on that list. Igor P.S. I've also changed the subject, as this had nothing to do with the thread this was in. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
OpenSSH disconnects when Windows user logging out
Hello, when using an secureshell on an Windows-Box, running cygwin and openssh, i receive an disconnect when the Windows user just loggs off (no shutdown nor restart !). The sshd service will never get stopped. I can reconncet without a noticeable delay. Any ideas? Regards, Oliver Geisen --- Systemadministrator Kreisboten Verlag Mühlfellner KG Telefon: 0881/686-63 Telefax: 0881/686-74 Mail: [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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Eduardo Chappa wrote: I happened to look at this message in Lynx and did not see anything bad about it, then it ocurred to me that you were referring to a GUI browser. This is the case when you are complaining about how it looks in your browser (probably most people browser), but it's not a defect of the message, per se (my logic is that it displays well in some browsers, bad in others, then the problem is not the message, but the browser). It's not a problem with a browser rather it's a direct result of usage of the HTML pre tag. pre means just that - preformatted. Now the person/process that created that html file could have choose to use something other than pre and the text would wrap approriately in any browser. I do understand your concern, but not everyone presses return at the end of a line (e.g. me), and you will have a hard time making people do that (I've already written hundreds of messages without pressing return at the end of the line). Precisely as you should IMHO. The responder cannot tell with any degree of certainty what the reader will be using to read the message, whether that person has his reader maximized, tall and skinny or short and fat. It's the reading client who should be responsible for wrapping the text to the windows current size. As such you should not be inserting artifical break the line here returns. My *editor* has automatic wrapping which inserts those CRs, and if it did not have them, you would see the same problem from me. Some mailers are configured to send format=flowed text, which would explain why you receive these long lines. This format is widely supported, and is even supported by Pine 4.60. format=flowed puts the burden on the receiving end, Where is should be IMHO (see above) normally an e-mail program, not a web browser, so if a web browser can not cope with this requirement, The web browser has no problem coping with this requirement - it's just that the web page writer purposely told the web browser not to wrap the text between the pre and /pre. the thing I would say is do not use a web browser, use an e-mail program, you are causing your own problem. I'd say fix the web page! Having said all that, you are free to express your preference on how you prefer that messages be sent to the list, but if you find that *your* browser is having a problem, I would advise you to use another browser to read such messages, All standards compliant web browsers should render that web page the same. -- Cannot find REALITY.SYS. Universe halted. -- 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/
regtool 1.8 on cygwin 1.5.10: Recursively remove registry keys
Hello, it seems that regtool cannot remove keys in registry if it's not empty. I have to remove all subkeys/values first, otherwise i get an Error (5) access denied. Is this true, or is there a way to remove whole trees from the registry ? Oliver Geisen --- Systemadministrator Kreisboten Verlag Mühlfellner KG Telefon: 0881/686-63 Telefax: 0881/686-74 Mail: [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/
correction to openssh-3.8p1-1 openssh.README
I was trying to build openssh-3.8p1-1 to debug an authorized_keys problem. I followed the instructions from: /usr/share/doc/Cygwin/openssh.README regarding the configure options. I also made sure I followed this requirement: You must have installed the zlib and openssl-devel packages to be able to build OpenSSH! However, this statemetn a little out of date apparently. Specifically, I also had to install minires-devel for the headers such as arpa/nameser.h and resolv.h and the resolv library. Hopefully this correction can make it into a future update and spare someone else some debugging time. Thanks to the package maintainers for all their work. -bri -- 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: error installing sshd on win2k3
I am installing sshd on win2k3. Windows 2300?! Microsoft must be /really/ confident about this version of the OS. ;-) (Sorry.) -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Jul 8 18:26, Christopher Faylor wrote: On Thu, Jul 08, 2004 at 03:56:49PM -0400, Igor Pechtchanski wrote: I've already explained why I don't think format=flowed is appropriate for this list (in particular, long command lines will also be wrapped if it ever were to be accepted). In any case, the definitive opinion will be that of CGF, and if he says that he doesn't care one way or another, then my opinion will be just that -- an opinion, and not a list custom of any sort. Well, since you asked, let me put it this way: I would never go out of my way to send a note specifically telling someone to wrap their text. My preference, however, would be to see some white space on the right side of my mail reading window which is about 132 columns in width. I, personally, try to format my email to fit within 80 columns and when I reply to a message I usually reformat it to the same width. It is my preference to see wrapping of text in messages to the cygwin lists. I know all of the yadda yadda obvious stuff about your preference my preference modern mail readers, etc. However, it has been a convention to wrap email to somewhere around 80 columns (especially in technical forums) for years and, personally, when I see email from someone which just goes on forever without line breaks my first thought is probably clueless. I don't know what Corinna's preferences are here but I wouldn't be surprised if she agreed with the above sentiments. Obviously some Sounds perfectly fine to me. My mail reader is no modern mail reader and I'm not interested to use one since I'm old-fashioned enough to dislike the mouse. So my mail reader is running in an 80 column window. Unwrapped mails and weird line breaks drop my attention span to read the whole posting to a minimum. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: OpenSSH disconnects when Windows user logging out
On Jul 9 08:17, Systemtechnik wrote: Hello, when using an secureshell on an Windows-Box, running cygwin and openssh, i receive an disconnect when the Windows user just loggs off (no shutdown nor restart !). The sshd service will never get stopped. I can reconncet without a noticeable delay. Any ideas? I just tried the same. My remote session didn't disconnect when the local user logged off. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: regtool 1.8 on cygwin 1.5.10: Recursively remove registry keys
On Jul 9 09:32, Systemtechnik wrote: Hello, it seems that regtool cannot remove keys in registry if it's not empty. I have to remove all subkeys/values first, otherwise i get an Error (5) access denied. Is this true, or is there a way to remove whole trees from the registry ? AFAICS, regtool has no recursive option. Patches welcome. See http://cygwin.com/contrib.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: negative error status: gcc vs. cl
-wrong-nil(!)-exit-status-
% nerr-cl.exe; echo $?
0
$? cannot distinguish exit(0) from exit(-2) ... this is
logical anarchy!
:) Ah, but those aren't just two different values passed to exit, they are
:) in fact two entirely different versions of the exit function: gcc links in
:) the version from newlib, whereas msvc links in the version from msvcrt.
What I meant was calling same msvcrt exit() with status = {0,-2} (in
nerr-cl.exe).
:) So the problem really is that the Windoze version of the exit function
:) isn't POSIX compliant. Still, we already knew that windoze != unix.
:) That's why cygwin exists, after all!
Right. Still, Cygwin could do better. See below.
:) Name one platform that *can* reliably test the exit status of binaries
:) that were written for a different platform? It's an achievement that it
:) can even run them.
Cygwin? When exit status is positive.
If one wrote:
% cat perr.c
int main()
{
exit (2);
}
she would get:
-unsigned-8b-exit-status-
% perr-cl.exe; echo $?
2
Isn't anybody finding weird that positive exit status works fine from gcc and
cl i.e. $? can always (gcc or cl) distinguish exit(0) from exit(2)? What I
meant with reliably.
Isn't the same int exit status being set from mscvrt to 0xfffe (nerr-cl.exe)
and 0x0002 (perr-cl.exe)?
Where does $? = 2 come from?
ksh :) yields the same Cygwin bug.
:) Don't blame me!
Never meant to. Cheers, daniel.
--
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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Brian Dessent wrote: RFC2822 (which obsoletes the old RFC822) states in section 2.2.1: There are two limits that this standard places on the number of characters in a line. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF. I am not sure this argument argues the point you think it does. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF. I believe that at this point they are talking about the byte stream that represents the encoded form of the message. If you are using quoted-printable encoding, then all encoded lines will be 78 characters or less, and so will be fitting in with the SHOULD specification, i.e. the most conformant. However, the original form of the message (what the composer sees, and what the reader should see) can have an arbitrarily large number of characters between newline characters (or between a newline and the start or end of the message). So, if you are using quoted-printable, you can cheerfully do paragraphs as long as you like, delimited by newline characters, and still be perfectly within the RFCs. Wrapping lines at less than 80 characters is the standard accepted way of sending text email. It may be the standard Accepted way, but you haven't actually given any reasons or pointers to reasons. One could say that you are not actually arguing your case, you're just saying that's the way it is, so it must be right. It's the least common denominator that's guaranteed to work everywhere. I disgree. For example (and this point has already been made) it does not work well on my PDA which cannot display 80 characters across the width of the display. When I read a message which has the additional unnecessary linebreaks, I get a somewhat jerky reading because every third line is prematurely cut off. If the message had been formatted into paragraphs, I would just see the paragraphs as the author originally wrote them. And what problems would there be with that flowed message in other environments? Every mail reader I have ever seen wraps lines. Every web browser I have ever seen wraps lines. The only problem here is that most archiving software rather unhelpfully mandates that the browser must not wrap at the right edge of the viewer's window. Even a dumb mail reader, which does not even decode the quoted-printable will see lines of 76 or so characters with an = sign at the end of each line. It's just like HTML email - can I read it? Yes. Do I want it in my inbox? Heck no. I don't think this is valid. If I sent you a format-flowed message, chances are your mail reader would wrap the lines and you wouldn't even know. Just because you can do something doesn't mean you should. Agreed. But conversely, just because something has always been done in a particular way, doesn't mean that it should never be reviewed. If there are logical reasons for changing, for example getting a better match to the conditions of a changed world, without creating backwards- compatibility problems, then change should be considered. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
My mail reader is no modern mail reader and I'm not interested to use one since I'm old-fashioned enough to dislike the mouse. So my mail reader is running in an 80 column window. Unwrapped mails and weird line breaks drop my attention span to read the whole posting to a minimum. How can you tell if you are reading flowed mail? Bill -- 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: correction to openssh-3.8p1-1 openssh.README
On Jul 9 07:46, Brian D. Carlstrom wrote: I was trying to build openssh-3.8p1-1 to debug an authorized_keys problem. I followed the instructions from: /usr/share/doc/Cygwin/openssh.README regarding the configure options. I also made sure I followed this requirement: You must have installed the zlib and openssl-devel packages to be able to build OpenSSH! However, this statemetn a little out of date apparently. Specifically, I also had to install minires-devel for the headers such as arpa/nameser.h and resolv.h and the resolv library. Hopefully this correction can make it into a future update and spare someone else some debugging time. Thanks for the heads up. I've send a correction upstream. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Jul 9 10:36, William Blunn wrote: My mail reader is no modern mail reader and I'm not interested to use one since I'm old-fashioned enough to dislike the mouse. So my mail reader is running in an 80 column window. Unwrapped mails and weird line breaks drop my attention span to read the whole posting to a minimum. How can you tell if you are reading flowed mail? Easily. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Christopher Faylor quoted Igor Pechtchanski: On Thu, Jul 08, 2004 at 03:56:49PM -0400, Igor Pechtchanski wrote: I've already explained why I don't think format=flowed is appropriate for this list (in particular, long command lines will also be wrapped if it ever were to be accepted). Long command lines will also be wrapped... I would contend that there is an issue of scale here. Detail -- (Please note all percentage fractions below are just ballpark guess- timates.) I would think that you are likely to see an ever-increasing number of messages which used flowed formatting. If the web archive system continues to emit web pages using PRE, then you will see an ever-increasing number of inconveniently-displayed messages. So this could easily become a kind of always-in-your-face problem, maybe causing a problem on, say, 25% of messages. Occasionally, there will be a long command line where it is important that there is no line break *if the command line is actually used*. If we assume that the web archive system allows flowed text to be wrapped, people reading the message, who don't need to use the command line will just skip over it. No problem for, say, 99% of the time. People reading the message, who *do* need to use the command line will see the command line hit the edge of the window, and continue on the next line. Doing copy-and-paste on the entire (line-wrapped) command line from the browser window will give you a (clipboard) object with *no* linebreaks in it. This is true for every browser I have ever seen. OK so that solves, say, 99% of the remaining 1%. Then we are down to the remaining 1% of the 1%, i.e. 0.01%. There will inevitably be some people who are terminally stupid and will assume that they can use advanced techniques without having acquired the necessary prerequisite background knowledge. They may either not see the wrapped portion of the command line, or will not know that you mustn't press enter/return in the middle of a command line. (The last part is not completely true, because in certain shells you can escape newlines and include them in your command line.) So, yes, you will get a problem 0.01% of the time with my scheme, but that compares to potentionally getting a problem 25% of the time if things are left the way they are now. Think of it this way: If we had already accepted that the web archive system wrapped flowed text, and someone came up arguing that it should not because it breaks long command lines, would they be given the time of day? I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Jul 9 10:36, William Blunn wrote: My mail reader is no modern mail reader and I'm not interested to use one since I'm old-fashioned enough to dislike the mouse. So my mail reader is running in an 80 column window. Unwrapped mails and weird line breaks drop my attention span to read the whole posting to a minimum. How can you tell if you are reading flowed mail? Easily. OK. When viewing a message in your mail reader, is it immediately obvious to you whether the message is (a) a flowed-text message or, (b) a message with additional line breaks every 80 or so characters (note: two following conditions apply to this question) ? If you have to issue additional instructions to your mail reader (for example to display additional information about the message), that that is not immediately obvious and therefore (I contend) does not count. Also looking at the RFC(2)822 header is considered cheating and does not count. What I am trying to get at it, does it make any material difference to you if the message is flowed or otherwise? Bill -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Jul 9 11:03, William Blunn wrote: I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. My 2ct are simply this: If somebody wants to be read, he or she should stick to the common rules. If somebody isn't able or willing to learn these rules, bad luck for him or her. I'm against pampering clueless people so that they can lean back and stay clueless. Call me mean. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: [ANNOUNCEMENT] Updated: libtool-devel-1.5.6-3
Charles wrote: The libtool-devel package contains the 1.5.6 version of libtool, a cross-platform tool for building libraries (shared and otherwise). It enables relatively trouble-free builds of DLLs on cygwin and mingw. Changes from 1.5-3: o routine update to latest release version o Includes Gerrit's expat fix -- but only the first part of the patch: http://www.cygwin.com/ml/cygwin/2003-09/msg01559.html http://www.cygwin.com/ml/cygwin/2003-04/msg01283.html http://www.cygwin.com/ml/cygwin/2003-04/msg01247.html Hurray;) Many thanks. OTOH I still need to use the second part of the patch if I don't want to patch several Makefile.am's all the time... o DESIGN DECISION: (this is a a change from pre-2002 behavior) libtool will refuse to create a shared library if any of its dependencies are available only as static archives. DLLs may only depend on other DLLs (*) (*) This is a good idea. But, we need workarounds for the standard runtime libs like libgcc.a, libstdc++.a, etc. These workarounds are implemented in this libtool release. This is great, now I don't need to use `pass_all' all the time when building C++ shared libraries (e.g. libextractor). BTW, it seems that not all announcements are going through to the cygwin list, I'm missing gettext and autoconf announcements and I'm also missing the gtk2-x11 announcement, or is just me who is not receiving all the mail from the list? Gerrit -- =^..^= http://nyckelpiga.de/donate.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/
Re: error installing sshd on win2k3
* Sam Edge (2004-07-09 10:18 +0200) I am installing sshd on win2k3. Windows 2300?! Microsoft must be /really/ confident about this version of the OS. ;-) No, win2k3 is win20003. But I admire people like PJ that are not afraid that people will laugh at them - just for the sake of saving one character to type (2k3 versus 2003) Thorsten -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
This seems like a reasonable discussion that can hopefully resolve this issue once and for all, and so, IMO, belongs on the list rather than in private e-mail. There is a phrase that goes: Be permissive in what you accept, and strict in what you send Now this is just a phrase, and by itself does not have significance. However it is well understood to be a concise summary of a set of ideas which are generally accepted to be sound. If you are developing a system which implements a web-accessible mail archive where the archive contains messages from many disparate sources, then I would have thought that this would be one guideline you should be paying attention to. It is trivially simple to handle flowed-text messages as well as messages with additional inexplicable linebreaks. I have set up several web-based systems which do this, and it wasn't hard. It hasn't caused any problems on the systems I set up, and has made things a lot easier by not having to waste time trying to browbeat users into doing things in a particular way. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
William Blunn wrote: I believe that at this point they are talking about the byte stream that represents the encoded form of the message. If you are using quoted-printable encoding, then all encoded lines will be 78 characters or less, and so will be fitting in with the SHOULD specification, i.e. the most conformant. Right, I understand that as well. And what problems would there be with that flowed message in other environments? Every mail reader I have ever seen wraps lines. Every web browser I have ever seen wraps lines. The only problem here is that most archiving software rather unhelpfully mandates that the browser must not wrap at the right edge of the viewer's window. My main problem with it is that it breaks quoting. When I reply to a message with no line breaks, my mail program has to either A) pick an arbitrary margin and reflow the entire message to that margin, adding to the first column of each line, or B) Insert a at the beginning of the paragraph and just let the long line dangle. To the person reading it will not appear correctly quoted (depending on screen width) because only the first line will have a prepended. If you have color highlighting enabled then this is even more apparent. Option (A) is leads to the conclusion that having the original message with line breaks inserted is the best way to go if you expect it to be quoted as part of a discussion, since that's the format it's going to end up in for every message in the thread except the original post. Option (B) just results in broken quoting, and therefore should be avoided. It's just like HTML email - can I read it? Yes. Do I want it in my inbox? Heck no. I don't think this is valid. It's valid in that I can view messages with long lines just fine, I just don't like them -- because I'm used to 80 column margins, they read better on my screen, and I believe that email works better that way. This is not a technical statement but rather an opinion. Likewise I CAN view HTML emails but I hate receiving them because they come festered with all sorts of colors and fonts. (There are further technical reasons why HTML email is stupid, so in that sense it is more valid than a simple statement of opinion.) Brian -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Jul 9 11:03, William Blunn wrote: I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. My 2ct are simply this: If somebody wants to be read, he or she should stick to the common rules. If somebody isn't able or willing to learn these rules, bad luck for him or her. I'm against pampering clueless people so that they can lean back and stay clueless. Call me mean. You're mean :-) Your rules appear to be arbitrary, and not based on anything relevant. It would be like saying: You have to begin and end each message with the word porcupine, otherwise we won't give you the time of day. You do also appear to be playing the game of That's the way it is, get over it. OK, if you own a particular domain (and I mean that in the general dictionary sense of the word), you can dictate any set of rules you like. It does appear though that these rules are arbitrary, without benefit, yet have identifiable problems, and their current sole purpose appears to be to identify members of a club. I only wish that I could go back in time and show the inventor of PRE the havoc they have wreaked by making it turn off wrapping by default. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ The contents of this e-mail and any attachments are confidential and may be legally privileged. If you have received this e-mail and you are not a named addressee, please inform us as soon as possible on +44 118 901 2999 and then delete the e-mail from your system. If you are not a named addressee you must not copy, use, disclose, distribute, print or rely on this e-mail. Any views expressed in this e-mail or any attachments may not necessarily reflect those of Tao's management. Although we routinely screen for viruses, addressees should scan this e-mail and any attachments for viruses. Tao makes no representation or warranty as to the absence of viruses in this e-mail or any attachments. Please note that for the protection of our business, we may monitor and read e-mails sent to and from our server(s). -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
-Original Message- From: cygwin-owner On Behalf Of William Blunn Sent: 09 July 2004 11:28 This seems like a reasonable discussion that can hopefully resolve this issue once and for all, LOL, you haven't been on the internet long have you? There is a phrase that goes: Be permissive in what you accept, and strict in what you send Now this is just a phrase, and by itself does not have significance. However it is well understood to be a concise summary of a set of ideas which are generally accepted to be sound. If you are developing a system which implements a web-accessible mail archive where the archive contains messages from many disparate sources, then I would have thought that this would be one guideline you should be paying attention to. There's another phrase that goes: If you're archiving people's posts for all time, there is a moral obligation on you to archive them absolutely *verbatim* and not tamper with, edit, reformat, or otherwise alter them. cheers, DaveK -- Can't think of a witty .sigline today -- 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: error installing sshd on win2k3
-Original Message- From: cygwin-owner On Behalf Of Thorsten Kampe Sent: 09 July 2004 11:27 * Sam Edge (2004-07-09 10:18 +0200) I am installing sshd on win2k3. Windows 2300?! Microsoft must be /really/ confident about this version of the OS. ;-) No, win2k3 is win20003. Talk about slipping your release date! cheers, DaveK -- Can't think of a witty .sigline today -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
William Blunn wrote: I only wish that I could go back in time and show the inventor of PRE the havoc they have wreaked by making it turn off wrapping by default. I'm pretty sure you were joking here but if not... That's the whole point of PRE, that it *doesn't* wrap. It's for text that's been preformatted, with linefeeds and spacing already determined. If PRE were to mangle the text by wrapping it at some margin, it would totally defeat the purpose of the tag. What really needs to be improved is mhonarc or whatever app is used to make the web archives. It should detect when the message contains no linebreaks and not use PRE but rather let the browser render it as normal text, so that it will be wrapped to the width of the screen as intended. Brian -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
-Original Message- From: cygwin-owner On Behalf Of Brian Dessent Sent: 09 July 2004 12:02 William Blunn wrote: I only wish that I could go back in time and show the inventor of PRE the havoc they have wreaked by making it turn off wrapping by default. I'm pretty sure you were joking here but if not... That's the whole point of PRE, that it *doesn't* wrap. It's for text that's been preformatted, with linefeeds and spacing already determined. If PRE were to mangle the text by wrapping it at some margin, it would totally defeat the purpose of the tag. What really needs to be improved is mhonarc or whatever app is used to make the web archives. It should detect when the message contains no linebreaks and not use PRE but rather let the browser render it as normal text, so that it will be wrapped to the width of the screen as intended. Actually it's easier than that, I think. All it needs to do is grep through the MIME headers. If it finds the format-flowed tag, it doesn't insert PRE. If it doesn't find it, it does. cheers, DaveK -- Can't think of a witty .sigline today -- 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: regtool 1.8 on cygwin 1.5.10: Recursively remove registry keys
it seems that regtool cannot remove keys in registry if it's not empty. I have to remove all subkeys/values first, otherwise i get an Error (5) access denied. Is this true, or is there a way to remove whole trees from the registry ? AFAICS, regtool has no recursive option. Patches welcome. See Maybe i write some kind to dir-crawler in perl/shell to do this... Thanks for you info ! Oliver Geisen --- Systemadministrator Kreisboten Verlag Mühlfellner KG Telefon: 0881/686-63 Telefax: 0881/686-74 Mail: [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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
If you're archiving people's posts for all time, there is a moral obligation on you to archive them absolutely *verbatim* and not tamper with, edit, reformat, or otherwise alter them. I wasn't suggesting tampering with them. Information should be preserved where possible. My contention is with the process used to emit those archived messages as web pages. Wrapping up e-mail in PRE is bogus because flowed text e-mail is not pre-formatted. Flowed text e-mail requires one very cheap operation (line wrapping) before it can be displayed, one which can, in fact, be carried out in the reader's web browser(!) So in fact there isn't even any load on the server(!) Not only that but the reader's web browser knows how wide the windor is and can wrap it at sensible place (rather than some arbitrary number of characters based on some anachronistic nonsense). A goodly fraction of e-mail is now flowed text, and it will only increase. Ignoring that is like sticking your head in the sand. Bill -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Jul 9 11:46, William Blunn wrote: It does appear though that these rules are arbitrary, without benefit, yet have identifiable problems, and their current sole purpose appears to be to identify members of a club. If you want to see it that way, fine with me. Fact is, I dislike when people don't give a damn for existing common rules which have turned out to work fine for all other people. Brian explained some problems fairly well. In my opinion, people writing a mail should use their brain instead of relying on automated systems or, worse, the recipient, to fix their avoidable mess. Successful communication needs rules. If somebody doesn't apply to these rules, which really aren't hard to find or follow, nobody is forced to read his or her posting, right? Nobody is forced to read my postings either. That's ok. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Dave Korn wrote: What really needs to be improved is mhonarc or whatever app is used to make the web archives. It should detect when the message contains no linebreaks and not use PRE but rather let the browser render it as normal text, so that it will be wrapped to the width of the screen as intended. Actually it's easier than that, I think. All it needs to do is grep through the MIME headers. If it finds the format-flowed tag, it doesn't insert PRE. If it doesn't find it, it does. I think it needs a little more intelligence than that. A message that has a Content-Transfer-Encoding of quoted-printable can be both preformatted with linebreaks, or flowed. You could even have a mix of both in the same message. It all depends on whether each line ends in '=' or not. If you go back and look at William's original message that started all this, there's no 'flowed' tag at all, just QP-encoding. Brian -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 10:34:01AM +0100, William Blunn [EMAIL PROTECTED] wrote: Brian Dessent wrote: RFC2822 (which obsoletes the old RFC822) states in section 2.2.1: There are two limits that this standard places on the number of characters in a line. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF. I am not sure this argument argues the point you think it does. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF. I believe that at this point they are talking about the byte stream that represents the encoded form of the message. If you are using quoted-printable encoding, then all encoded lines will be 78 characters or less, and so will be fitting in with the SHOULD specification, i.e. the most conformant. However, the original form of the message (what the composer sees, and what the reader should see) can have an arbitrarily large number of characters between newline characters (or between a newline and the start or end of the message). So, if you are using quoted-printable, you can cheerfully do paragraphs as long as you like, delimited by newline characters, and still be perfectly within the RFCs. Wrapping lines at less than 80 characters is the standard accepted way of sending text email. It may be the standard Accepted way, but you haven't actually given any reasons or pointers to reasons. One could say that you are not actually arguing your case, you're just saying that's the way it is, so it must be right. It's the least common denominator that's guaranteed to work everywhere. I disgree. For example (and this point has already been made) it does not work well on my PDA which cannot display 80 characters across the width of the display. When I read a message which has the additional unnecessary linebreaks, I get a somewhat jerky reading because every third line is prematurely cut off. If the message had been formatted into paragraphs, I would just see the paragraphs as the author originally wrote them. And what problems would there be with that flowed message in other environments? Every mail reader I have ever seen wraps lines. Every web browser I have ever seen wraps lines. The only problem here is that most archiving software rather unhelpfully mandates that the browser must not wrap at the right edge of the viewer's window. Even a dumb mail reader, which does not even decode the quoted-printable will see lines of 76 or so characters with an = sign at the end of each line. It's just like HTML email - can I read it? Yes. Do I want it in my inbox? Heck no. I don't think this is valid. If I sent you a format-flowed message, chances are your mail reader would wrap the lines and you wouldn't even know. Just because you can do something doesn't mean you should. Agreed. But conversely, just because something has always been done in a particular way, doesn't mean that it should never be reviewed. If there are logical reasons for changing, for example getting a better match to the conditions of a changed world, without creating backwards- compatibility problems, then change should be considered. I want to know how you would format a post like yours above using flowed format. I honestly can't think of any way to intersperse quotes and replies that way without picking a reasonably small width and putting newlines in. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
I only wish that I could go back in time and show the inventor of PRE the havoc they have wreaked by making it turn off wrapping by default. I'm pretty sure you were joking here but if not... Actually I was serious. That's the whole point of PRE, that it *doesn't* wrap. I don't think that is the whole point of PRE. I think the whole point of PRE is that newlines and other whitespace in the HTML source are interpreted literally. It appears that the design committee took it a step too far and decided that newlines in the rendered version of PRE can ONLY appear as a result of newlines in the source. This is counter to the normal behaviour nearly everywhere else in which text wraps when it hits the edge of the medium. It's for text that's been preformatted, with linefeeds and spacing already determined. If PRE were to mangle the text by wrapping it at some margin, it would totally defeat the purpose of the tag. If the pre-formatted text is too wide to fit the medium, then *something* has got to give somewhere. There has got to be *some* behaviour. Wrapping is a well-established and convenient way of doing this. Establishing a second (horizontal) scrolling domain is just plain hostile for text documents. What really needs to be improved is mhonarc or whatever app is used to make the web archives. It should detect when the message contains no linebreaks and not use PRE but rather let the browser render it as normal text, so that it will be wrapped to the width of the screen as intended. Sounds good to me, and also pretty much the response from my co-worker when I described the problem to him. His response was basically that the system should look at the message it is attempting to render as HTML and if all sequences of non-newlines are 80 characters or less, then use PRE, and if not, then use alternative formatting which allows for wrapping, e.g. TT with newline processing. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
William Blunn wrote: There is a phrase that goes: Be permissive in what you accept, and strict in what you send Now this is just a phrase, and by itself does not have significance. Yeah it appears in RFC1885 as Be conservative in what you send and liberal in what you receive., just a few paragraphs above where it recommends: Limit line length to fewer than 65 characters and end a line with a carriage return. -- J. Lambert -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Jon A. Lambert wrote: Yeah it appears in RFC1885 Sorry that's RFC 1855 -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
What really needs to be improved is mhonarc or whatever app is used to make the web archives. It should detect when the message contains no linebreaks and not use PRE but rather let the browser render it as normal text, so that it will be wrapped to the width of the screen as intended. Actually it's easier than that, I think. All it needs to do is grep through the MIME headers. If it finds the format-flowed tag, it doesn't insert PRE. If it doesn't find it, it does. As Brian indicated, many mail programs will not include the format- flowed tag where it would perhaps be appropriate. Whilst you could take the view that it is their problem, this does not get the baby bathed. In the real world, you would probably want to think about having a heuristic that looked for lines longer than, say, 80 characters, and flag those for wrapping as well. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
William Blunn wrote: That's the whole point of PRE, that it *doesn't* wrap. I don't think that is the whole point of PRE. I think the whole point of PRE is that newlines and other whitespace in the HTML source are interpreted literally. It appears that the design committee took it a step too far and decided that newlines in the rendered version of PRE can ONLY appear as a result of newlines in the source. This is counter to the normal behaviour nearly everywhere else in which text wraps when it hits the edge of the medium. Sometimes you want to express that something is all on one line. Perhaps it's a command, or the ouput of a command. I'm sure there's other instances that come up every now and then. If PRE were to wrap at the screen margin there'd be no way to do this. The way I see it the PRE tag is for saying to the browser, Hands off. This text has already been formatted how I want it and is to appear exactly as follows, and if that means the screen must scroll if it's too narrow then so be it. If it is used inappropriately (such as in the case of the list archives) and it causes awkward scrolling, then that's really the fault of the page design or the program that generated it, not of the tag. If you want the browser to wrap the text then it's not really preformatted anymore. Brian -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Yeah it appears in ... [RFC1855] as Be conservative in what you send and liberal in what you receive., just a few paragraphs above where it recommends: Limit line length to fewer than 65 characters and end a line with a carriage return. Limiting line length to fewer than 65 characters is about being conservative in what you send. My contention is about mail archivers being liberal in what you [they] receive. Bill -- William Blunn bill at tao-group dot com Tao, 62/63 Suttons Business Park, Earley, Reading, RG6 1AZ, UK Tel: +44 845 644 4458, Fax: +44 845 644 4459, Web: http://tao-group.com/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
-Original Message- From: cygwin-owner On Behalf Of William Blunn Sent: 09 July 2004 12:30 That's the whole point of PRE, that it *doesn't* wrap. I don't think that is the whole point of PRE. I think the whole point of PRE is that newlines and other whitespace in the HTML source are interpreted literally. The whole point of PRE is that whatever is wrapped in it is PREformatted and MUST NOT BE REFORMATTED. It appears that the design committee took it a step too far and decided that newlines in the rendered version of PRE can ONLY appear as a result of newlines in the source. Well duh. Adding formatting chars counts as reformatting it. This is counter to the normal behaviour nearly everywhere else in which text wraps when it hits the edge of the medium. No it doesn't. Different applications have different behaviours. Many have a choice of whether to wrap or not. And the non-wrapping behaviour is very intuitively obvious to people, because that's how written words on paper behave. If I reduce the width of a page by tearing it in half, the text doesn't reflow, I just lose half the text off the side. That's what I'm used to and that's what I'd call perfectly normal behaviour. If the pre-formatted text is too wide to fit the medium, then *something* has got to give somewhere. No, you either truncate or scroll it. What you DON'T do is reformat the stuff that is specifically tagged with do not under any circumstances reformat There has got to be *some* behaviour. Yes, but it doesn't *have* to violate the PRE tag. You just wish it did because your argument stands or falls on this false dilemma of the excluded middle. Wrapping is a well-established and convenient way of doing this. No matter how hard you wish, wrapping text always has and always will count as reformatting it. Your complaint appears to be that you believe the PRE tag ought to have been defined as a meaningless no-op. cheers, DaveK -- Can't think of a witty .sigline today -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, 9 Jul 2004, William Blunn wrote: Christopher Faylor quoted Igor Pechtchanski: On Thu, Jul 08, 2004 at 03:56:49PM -0400, Igor Pechtchanski wrote: I've already explained why I don't think format=flowed is appropriate for this list (in particular, long command lines will also be wrapped if it ever were to be accepted). Long command lines will also be wrapped... I would contend that there is an issue of scale here. [Some percentage analysis snipped] People reading the message, who *do* need to use the command line will see the command line hit the edge of the window, and continue on the next line. Doing copy-and-paste on the entire (line-wrapped) command line from the browser window will give you a (clipboard) object with *no* linebreaks in it. This is true for every browser I have ever seen. [snip] There will inevitably be some people who are terminally stupid and will assume that they can use advanced techniques without having acquired the necessary prerequisite background knowledge. They may either not see the wrapped portion of the command line, or will not know that you mustn't press enter/return in the middle of a command line. I think you're making an assumption here about the audience of this list. Over the years, it seems that most of the time a long command line (or a series of long command lines) was needed in a message was when a reasonably clueless person (not even subscribed to the list) requested help. So, the proportion of messages with long command lines with respect to people who are supposed to use those command lines is much higher than you estimated. (The last part is not completely true, because in certain shells you can escape newlines and include them in your command line.) This also assumes that people who are too stupid to know that you can't press Enter in the middle of a command line will know how to quote in the shell. Ha! A couple of other points: Sometimes it's not even possible to know, visually, whether the command is ended or continued. Command lines are just an example. Another example of when using long unterminated lines is justified is program output, in particular make or gcc. Reading those in flowed format is just excruciating. [snip] Think of it this way: If we had already accepted that the web archive system wrapped flowed text, and someone came up arguing that it should not because it breaks long command lines, would they be given the time of day? I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. I think you're arguing against yourself here. :-) The argument above is that once something is established and set up, most requests to change it will be viewed with suspicion, and rarely followed. But doesn't this exactly reflect the current situation? In summary, most mailing lists have netiquette rules and customs. Where they come from, be it from historical reasons, from necessity, from a majority vote by the founders, or just from a whim of the list moderator, is irrelevant. Once those rules are established, they are very hard to change from the outside. Most subscribers will adhere to those customs. Those that don't will see an occasional chiding by those who prefer the customs to be adhered to. Quoting an old Russian saying, One doesn't come to a remote monastery with his own code of rules. Or, in a more accepted phrasing, When in Rome, do as the Romans do. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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: error installing sshd on win2k3
Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Thorsten Kampe Sent: 09 July 2004 11:27 * Sam Edge (2004-07-09 10:18 +0200) I am installing sshd on win2k3. Windows 2300?! Microsoft must be /really/ confident about this version of the OS. ;-) No, win2k3 is win20003. Talk about slipping your release date! cheers, DaveK Or is 20003 when they finally secure all the holes? Thanks for the laugh! -- 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: OpenSSH disconnects when Windows user logging out
On Fri, 9 Jul 2004, Systemtechnik wrote: Hello when using an secureshell on an Windows-Box, running cygwin and openssh, i receive an disconnect when the Windows user just loggs off (no shutdown nor restart !). I just tried the same. My remote session didn't disconnect when the local user logged off. That's strange. I see an errormessage like: Received disconnect from 172.29.3.165: Command terminated on signal 1. Can you/anybody give me a hint how to solve this ? Or what to do next to find the source of it ? Looks like you aren't starting sshd as a service. Are you even using WinNT/2k/XP? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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: regtool 1.8 on cygwin 1.5.10: Recursively remove registry keys
On Fri, 9 Jul 2004, Systemtechnik wrote: it seems that regtool cannot remove keys in registry if it's not empty. I have to remove all subkeys/values first, otherwise i get an Error (5) access denied. Is this true, or is there a way to remove whole trees from the registry ? AFAICS, regtool has no recursive option. Patches welcome. See Maybe i write some kind to dir-crawler in perl/shell to do this... Try find -depth... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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: OpenSSH disconnects when Windows user logging out
Hello. when using an secureshell on an Windows-Box, running cygwin and openssh, i receive an disconnect when the Windows user just loggs off (no shutdown nor restart !). I just tried the same. My remote session didn't disconnect when the local user logged off. That's strange. I see an errormessage like: Received disconnect from 172.29.3.165: Command terminated on signal 1. Can you/anybody give me a hint how to solve this ? Or what to do next to find the source of it ? Looks like you aren't starting sshd as a service. Are you even using WinNT/2k/XP? Service is started as LocalSystem on WindowsNT 4.0 But your question pointed me to the right direction and i finally found the error. I choose Interact with desktop in the service-dialog to do funny things like starting applications for users :-) If i uncheck this, my sessions thays active, even if the user loggs off. I wonder if there is a way to prevent this ?! It would be very nice to start programs from within a ssh-shell, e.g. start iexplore c:\adminwarn.html to show the user that someone's working on his machine. Oliver Geisen --- Systemadministrator Kreisboten Verlag Mühlfellner KG Telefon: 0881/686-63 Telefax: 0881/686-74 Mail: [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: Building DLL
Gerrit P. Haase wrote: You don't need .def files on Cygwin. Just add -no-undefined to libxyz_LDFLAGS. OK, I'm making progress with getting XFCE to compile under cygwin (with help of one of the XFCE developers), but now we're running into the following: XFCE has a plugin mechanism, based on shared libraries. These plugins use functions/symbols from the program that they 'plug in to'. I.e. if I have appA, and libB is a plugin for appA, then libB contains calls that are defined in appA. How do I get this to work under cygwin? Obviously I can't link libB against appA! Maarten -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Brian Dessent wrote: My main problem with it is that it breaks quoting. When I reply to a message with no line breaks, my mail program has to either A) pick an arbitrary margin and reflow the entire message to that margin, adding to the first column of each line, or B) Insert a at the beginning of the paragraph and just let the long line dangle. To the person reading it will not appear correctly quoted (depending on screen width) because only the first line will have a prepended. If you have color highlighting enabled then this is even more apparent. Option (A) is leads to the conclusion that having the original message with line breaks inserted is the best way to go if you expect it to be quoted as part of a discussion, since that's the format it's going to end up in for every message in the thread except the original post. Option (B) just results in broken quoting, and therefore should be avoided. A long time ago I used emacs and it had a mode called gin-mode which stood for Guess INdentation mode. When faced with a bunch or levels of quoting one could use the fill-paragraph and it would fill the paragraph wrapping it correctly and properly handling the level of for quoting. As I said this was a long time ago. I wonder why current software is still having a problem with this... It's valid in that I can view messages with long lines just fine, I just don't like them -- because I'm used to 80 column margins, they read better on my screen, and I believe that email works better that way. If the format is flowing and the HTML email you get is 80 columns, couldn't you just size your window appropriately?!? In fact one might argue if you only want 80 characters of display for the message then sizing the window such that more than 80 characters of displayable space is, err, well a waste of screen real estate! This is not a technical statement but rather an opinion. Likewise I CAN view HTML emails but I hate receiving them because they come festered with all sorts of colors and fonts. As a person who regularly uses HTML style email and posting (much to many peoples chargrin and complaints) I rarely fester them with all sorts of colors and fonts. Other HTML emails and posts I receive are also rarely festered with all sorts of colors and fonts. Why? Because doing so takes time, knowledge and effort and most people simply don't take the time, have the knowledge nor can be bothered with the effort required. As such I don't think such an argument holds much water. IOW I think if people of your opinion see just one bolding they'll call it festered with all sorts of colors and fonts. -- RAM disk is *not* an installation procedure. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Dave Korn wrote: There's another phrase that goes: If you're archiving people's posts for all time, there is a moral obligation on you to archive them absolutely *verbatim* and not tamper with, edit, reformat, or otherwise alter them. Never heard that one. Got a reference? -- Jack Kevorkian for White House physician. -- 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: Building DLL
Maarten wrote: Gerrit P. Haase wrote: You don't need .def files on Cygwin. Just add -no-undefined to libxyz_LDFLAGS. OK, I'm making progress with getting XFCE to compile under cygwin (with help of one of the XFCE developers), but now we're running into the following: XFCE has a plugin mechanism, based on shared libraries. These plugins use functions/symbols from the program that they 'plug in to'. I.e. if I have appA, and libB is a plugin for appA, then libB contains calls that are defined in appA. How do I get this to work under cygwin? Obviously I can't link libB against appA! Put all the functions into a library. Link the application and the modules against this library (building only the appA's main() into the executable). It was also reported that creating an import library (or stub library) for the executables functions is sufficient if it is linked in, IIRC it was the same problem with naim plugins. Maybe there are some useful hints in the naim sources. Gerrit -- =^..^= http://nyckelpiga.de/donate.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/
Re: negative error status: gcc vs. cl
On Fri, Jul 09, 2004 at 11:24:04AM +0200, Daniel Lungu wrote:
-wrong-nil(!)-exit-status-
% nerr-cl.exe; echo $?
0
$? cannot distinguish exit(0) from exit(-2) ... this is
logical anarchy!
:) Ah, but those aren't just two different values passed to exit, they are
:) in fact two entirely different versions of the exit function: gcc links in
:) the version from newlib, whereas msvc links in the version from msvcrt.
What I meant was calling same msvcrt exit() with status = {0,-2} (in
nerr-cl.exe).
:) So the problem really is that the Windoze version of the exit function
:) isn't POSIX compliant. Still, we already knew that windoze != unix.
:) That's why cygwin exists, after all!
Right. Still, Cygwin could do better. See below.
Please read up on how the wait() function works. This is what cygwin
emulates on Windows.
--
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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Corinna Vinschen wrote: Fact is, I dislike when people don't give a damn for existing common rules which have turned out to work fine for all other people. You are ascribing malintent where either ignorance or disagreement may be present. You are assuming they don't give a damn instead of the more probable don't understand the issues or difference or the probable I disagree with your viewpoint regarding the issues you seem to have with this. I can also say as easily that format=flowed and even HTML email work fine for many people too. Successful communication needs rules. No, not at all. Successful comminication requires effort on both parts of the speaker and listener. Stifling rules stilfe communication. Rules or requirements should not be forced rather guidelines and conventions should merely be stressed - not shoved down other's throats. If somebody doesn't apply to these rules, which really aren't hard to find or follow, nobody is forced to read his or her posting, right? Nobody is forced to read my postings either. That's ok. Nobody's trying to force you to read. You shouldn't try to force them to write in a particular style. In the end communication, at least civil communication and I'd say any communication that is, in the long term, successsful, always requires *compromise* on both parties. Your stated opinion, Corina, is uncompromising. -- REALITY.SYS corrupted: Reboot universe? (Y/N/Q) -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
-Original Message- From: cygwin-owner On Behalf Of Andrew DeFaria Sent: 09 July 2004 16:03 Dave Korn wrote: There's another phrase that goes: If you're archiving people's posts for all time, there is a moral obligation on you to archive them absolutely *verbatim* and not tamper with, edit, reformat, or otherwise alter them. Never heard that one. Got a reference? Sure. It was said by Dave Korn, July 9th 2004. I stumbled across it at this site: http://cygwin.com/ml/cygwin/2004-07/msg00243.html but I think you may be able to find it here http://cygwin.com/ml/cygwin/2004-07/msg00271.html as well. HTH! cheers, DaveK -- Can't think of a witty .sigline today -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Brian Dessent wrote: William Blunn wrote: I only wish that I could go back in time and show the inventor of PRE the havoc they have wreaked by making it turn off wrapping by default. I'm pretty sure you were joking here but if not... That's the whole point of PRE, that it *doesn't* wrap. It's for text that's been preformatted, with linefeeds and spacing already determined. If PRE were to mangle the text by wrapping it at some margin, it would totally defeat the purpose of the tag. What really needs to be improved is mhonarc or whatever app is used to make the web archives. It should detect when the message contains no linebreaks and not use PRE but rather let the browser render it as normal text, so that it will be wrapped to the width of the screen as intended. IOW the pre tag is not the appropriate tag for the job in the case of a format=flowed message. -- Programmers don't die, they just GOSUB without RETURN. -- 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: Building DLL
Put all the functions into a library. Link the application and the modules against this library (building only the appA's main() into the executable). Hmmm, not sure if I can convinve the XFCE developers of such a change, as it's fairly major. It was also reported that creating an import library (or stub library) for the executables functions is sufficient if it is linked in, IIRC it this might be more acceptable, but I have no idea of how to go about that... Anybody knows more about how to do this? was the same problem with naim plugins. Maybe there are some useful hints in the naim sources. Maarten -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Andrew DeFaria Sent: 09 July 2004 16:03 Dave Korn wrote: There's another phrase that goes: If you're archiving people's posts for all time, there is a moral obligation on you to archive them absolutely *verbatim* and not tamper with, edit, reformat, or otherwise alter them. Never heard that one. Got a reference? Sure. It was said by Dave Korn, July 9th 2004. I stumbled across it at this site: http://cygwin.com/ml/cygwin/2004-07/msg00243.html but I think you may be able to find it here http://cygwin.com/ml/cygwin/2004-07/msg00271.html as well. HTH! Cute, but irrelevent. Or should I take the approach of: Oh so this is a relatively new thing! ;-) -- 5 days a week my body is a temple. The other two, it's an amusement park. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 11:27:55AM +0100, William Blunn wrote: I have set up several web-based systems which do this, and it wasn't hard. On Thu, Jul 08, 2004 at 06:26:27PM -0400, Christopher Faylor wrote: Finally, you (Igor) are right that we are not going to change the sourceware.org software to wrap in any other fashion than it does now. sourceware.org, the home of cygwin.com, is a technical site. The mailing lists that it sponsors are for technical discussions. In these discussions, the formatting of messages could conceivably actually *mean something*. It's entirely possible that someone meant to use 997 characters in one of the lines of their message to illustrate a point or even to provide a patch. So, I am not going to be spending my time hacking on the mailing list archiving software to add a special exception for cygwin mailing list denizens who want to forget about hitting enter and then read their messages on the web. If the use of pre in the archives causes you problems, then please suffer in silence or find some other archiving site. Maybe gmane would work better. Please do not insinuate that there is some technical or laziness barrier here. You are perched precariously on your soapbox and apparently haven't really given the issue any real contextual thought other than It's easy to do. They should do it. Is this clear? There will be no changes to the web site archiving. So, if this is what is causing everyone grave concern, then maybe this puts this issue to rest. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 11:03:00AM +0100, William Blunn wrote: Think of it this way: If we had already accepted that the web archive system wrapped flowed text, and someone came up arguing that it should not because it breaks long command lines, would they be given the time of day? Let's see. We're imagining things, are we? *I* think that if the tables were reversed and someone said that it breaks long command lines I would slap my forehead, say What was I thinking? and personally send the person a check for $372.21. Then I would spend all of my available time, ignoring wife, children, and job (pausing only to pat the dog occasionally) as I struggled to fix the archiving software. I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. Postulating how you think people would react and then using their supposed reaction to bolster your argument really isn't a very persuasive method for making a point. 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
This is a top post, sorry about that, I normally do not do this, but in order to show my point I will have to do it. Corinna, I agree with you 99.%, however, there's a consequence to your words that you are not seeing, which is this. Imagine that I were to read your post on a PDA, the way it would look in a 30 columns screen would like shown below, quite unreadable!. Now imagine that I connect my PDA to read my e-mail and I see your message, would it be useful to me? No, simply because you sent the message in a format that seems corrupted in my screen, that's why. In another words your words about being wanted to be read may back fire at you, in fact I wonder how useful is an archive if no one can read it (well this is not quite true, but it would be nice to be able to read it as intended in any medium). That's why the world is moving toward format=flowed. I encourage you to do the same, even if your old and grumpy, or just mean. Below is your quoted message *** Corinna Vinschen ([EMAIL PROTECTED] tv) wrote in the cygwin...: On Jul 9 11:03, William Blunn wrote: I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. My 2ct are simply this: If somebody wants to be read, he or she should stick to the common rules. If somebody isn't able or willing to learn these rules, bad luck for him or her. I'm against pampering clueless people so that they can lean back and stay clueless. Call me mean. Corinna -- Eduardo http://www.math.washington.edu/~chappa/pine/ -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Friday, July 09, 2004 10:39 AM, Christopher Faylor wrote On Fri, Jul 09, 2004 at 11:27:55AM +0100, William Blunn wrote: I have set up several web-based systems which do this, and it wasn't hard. On Thu, Jul 08, 2004 at 06:26:27PM -0400, Christopher Faylor wrote: Finally, you (Igor) are right that we are not going to change the sourceware.org software to wrap in any other fashion than it does now. sourceware.org, the home of cygwin.com, is a technical site. The mailing lists that it sponsors are for technical discussions. In these discussions, the formatting of messages could conceivably actually *mean something*. It's entirely possible that someone meant to use 997 characters in one of the lines of their message to illustrate a point or even to provide a patch. So, I am not going to be spending my time hacking on the mailing list archiving software to add a special exception for cygwin mailing list denizens who want to forget about hitting enter and then read their messages on the web. If the use of pre in the archives causes you problems, then please suffer in silence or find some other archiving site. Maybe gmane would work better. Please do not insinuate that there is some technical or laziness barrier here. You are perched precariously on your soapbox and apparently haven't really given the issue any real contextual thought other than It's easy to do. They should do it. Is this clear? There will be no changes to the web site archiving. So, if this is what is causing everyone grave concern, then maybe this puts this issue to rest. I always thought that the 'Because We're Just Mean' slogan was a joke. Well apparently I was wrong. I cannot believe the level of posturing I am seeing from the Cygwin-elite. I live in Memphis, TN, the town where Martin Luther King, Jr. was shot and killed for trying to change they way things were. If he and others had simply said, Blacks and whites are separate but equal. That's the way it has always been and that is how it should stay because it works. It doesn't matter if true equality has merits and would benefit some people; everybody else will just have to get over it, where would The South (that's what it's called down here) be today? Where would the United States be? Cygwin is an amazing project. The tools created by its members make working in a Windows-centric environment much more bearable. That does not give some of the project's top members the right to be complete holier-than-thou ass holes. I love what Cygwin has enabled me to do since I discovered it a few years ago. The community has always been quick to fix issues and keep the tools up-to-date. But this feeling that some people's opinions are golden while others are tin just doesn't make sense. And it has truly injured ~my~ opinion of the project as a whole. It is like when parents who think they know better simply say because I said so. Please at least look into alternatives or fixing the system that started this discussion. Notice that I have lovingly set my mailer to wrap at 76 characters and I am using Outlook-QuoteFix for some of the other niceties. I still have to manually fix in-line email addresses, though. I do this to try and appease the dysfunctional family of the online community of which I joyfully a member of. I know you can do 'mean'. Try 'nice' or at least 'thoughtful and open minded'. -Jason PS - I apologize in advance for the legal disclaimer at the bottom of my email message. This is tacked on by our SMTP gateway and I have no control over it. I have also put in a request to have the text wrap at character 72 instead of just a single incredibly long line. -- -- Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. == -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 09:18:30AM -0700, Eduardo Chappa wrote: *** Christopher Faylor ([EMAIL PROTECTED])...: :) On Fri, Jul 09, 2004 at 11:27:55AM +0100, William Blunn wrote: :) I have set up several web-based systems which do this, and it wasn't :) hard. :) :) On Thu, Jul 08, 2004 at 06:26:27PM -0400, Christopher Faylor wrote: :) Finally, you (Igor) are right that we are not going to change the :) sourceware.org software to wrap in any other fashion than it does :) now. :) :) sourceware.org, the home of cygwin.com, is a technical site. The :) mailing lists that it sponsors are for technical discussions. :) :) In these discussions, the formatting of messages could conceivably :) actually *mean something*. It's entirely possible that someone meant :) to use 997 characters in one of the lines of their message to :) illustrate a point or even to provide a patch. If someone sends a 997 characters line, I will see it wrapped in my e-mail program, 12 times wrapped. It will not be cut at the width of the screen. That's very helpful in my opinion. Maybe you're being purposely obtuse. I don't know. My point was that if I send specially formatted text in my messages to a technical mailing list I don't want the archiving software to unformat it for me. What it does to the email reader on your PDA is irrelevant. If someone provides a patch and I were to cut and paste that patch, I would call myself crazy, I would normally save the patch to a file directly, so this is not an issue. The issue is inspecting the patch in the archives. If you have to puzzle out where the line breaks actually occur because your web browser is helpfully wrapping things for you, then the utility of the archives has been diminished for some people (like me). On the other hand, just to mention something, instead of saying NO, it won't happen, maybe you may want to experiment on adding BR at the end of each line, or adding P instead of having empty lines, or things like that. Probably does not work out of the box, but it probably can be tuned to fit most messages, if not all. That's sort of presumptuous, don't you think? You don't even know how the archives are generated but you have no qualms about suggesting that I take my time trying to fix something which I've already indicated is not broken. Again, I am not going to spend any time trying to set up the cygwin mailing list as a special case. There are surely other sites archiving the mailing list out there somewhere. Use one of them if the formatting in the sourceware.org archive offends you. OTOH, if anyone wants to change the policy of sourceware.org, you are welcome to send email to the overseers mailing list and lobby for change. I don't think you are going to find a receptive audience, but I could be wrong. 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 11:38:11AM -0500, DePriest, Jason R. wrote: On Friday, July 09, 2004 10:39 AM, Christopher Faylor wrote On Fri, Jul 09, 2004 at 11:27:55AM +0100, William Blunn wrote: I have set up several web-based systems which do this, and it wasn't hard. On Thu, Jul 08, 2004 at 06:26:27PM -0400, Christopher Faylor wrote: Finally, you (Igor) are right that we are not going to change the sourceware.org software to wrap in any other fashion than it does now. sourceware.org, the home of cygwin.com, is a technical site. The mailing lists that it sponsors are for technical discussions. In these discussions, the formatting of messages could conceivably actually *mean something*. It's entirely possible that someone meant to use 997 characters in one of the lines of their message to illustrate a point or even to provide a patch. So, I am not going to be spending my time hacking on the mailing list archiving software to add a special exception for cygwin mailing list denizens who want to forget about hitting enter and then read their messages on the web. If the use of pre in the archives causes you problems, then please suffer in silence or find some other archiving site. Maybe gmane would work better. Please do not insinuate that there is some technical or laziness barrier here. You are perched precariously on your soapbox and apparently haven't really given the issue any real contextual thought other than It's easy to do. They should do it. Is this clear? There will be no changes to the web site archiving. So, if this is what is causing everyone grave concern, then maybe this puts this issue to rest. I always thought that the 'Because We're Just Mean' slogan was a joke. Well apparently I was wrong. I cannot believe the level of posturing I am seeing from the Cygwin-elite. I live in Memphis, TN, the town where Martin Luther King, Jr. was shot and killed for trying to change they way things were. If he and others had simply said, Blacks and whites are separate but equal. That's the way it has always been and that is how it should stay because it works. It doesn't matter if true equality has merits and would benefit some people; everybody else will just have to get over it, where would The South (that's what it's called down here) be today? Where would the United States be? If you really want to continue discussing this, then you really should stick to the topic rather than making inane Where would the United States be? analogies. Stick to the point, please. You do not seem to understand that this entire thread boils down to We want cgf to work on the mailing list archiving software. I am saying that I have no interest in doing so. It is as simple as that. I did state in another message that the current arrangement is site policy for sourceware.org, anyway, and I suggested a potential method for getting this changed. Rather than going on about how shocked and outraged you are by the awful meanness of people who don't want to spend lots of time working on mailing list archiving software for you, I think your ends would be better served by talking to the people who collectively run the sourceware.org site. You will have to convince project leaders from gcc, gdb, eCos, etc. that changing the way archiving works is a good idea and, if you want your ideas to really seem substantive, you might want to research how the current arrangement works and offer patches or at least details on how things could be changed. Of course, even if everyone in the overseers mailing list agrees that it is a wonderful idea not to use pre, you'll still have to find one of them to make the necessary changes. That could be tricky since we all have jobs, all contribute heavily to the free software community, and, perhaps most importantly, presumably are not particularly bothered by this issue. Good luck. -- 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/
can not create a multi-volume archive using tar
Sometime I need to move data between unix machines and win2k. I know, that cygwin can use raw drives, so 'tar -cvf /dev/fd0' can do a work for me. But this command does not work correctly with files which is bigger then 1.4MB -- it can not write data to diskettes as multivolume. Did anybody try that multi-volume archives? Al. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
*** Christopher Faylor ([EMAIL PROTECTED])...: :) On Fri, Jul 09, 2004 at 09:18:30AM -0700, Eduardo Chappa wrote: :) *** Christopher Faylor :) ([EMAIL PROTECTED])...: :) :) :) On Fri, Jul 09, 2004 at 11:27:55AM +0100, William Blunn wrote: :) :) I have set up several web-based systems which do this, and it :) :) wasn't hard. :) :) :) :) On Thu, Jul 08, 2004 at 06:26:27PM -0400, Christopher Faylor :) :) wrote: :) :) Finally, you (Igor) are right that we are not going to change the :) :) sourceware.org software to wrap in any other fashion than it does :) :) now. :) :) :) :) sourceware.org, the home of cygwin.com, is a technical site. The :) :) mailing lists that it sponsors are for technical discussions. :) :) :) :) In these discussions, the formatting of messages could conceivably :) :) actually *mean something*. It's entirely possible that someone :) :) meant to use 997 characters in one of the lines of their message to :) :) illustrate a point or even to provide a patch. :) :) If someone sends a 997 characters line, I will see it wrapped in my :) e-mail program, 12 times wrapped. It will not be cut at the width of :) the screen. That's very helpful in my opinion. :) :) Maybe you're being purposely obtuse. I don't know. My point was that :) if I send specially formatted text in my messages to a technical :) mailing list I don't want the archiving software to unformat it for me. :) What it does to the email reader on your PDA is irrelevant. What you do not understand is that i am talking about a PDA as a screen, like the one that you are reading your e-mail message. Since you wondered, I am not purposely obstuse, I am stating my opinion. We just happen to disagree on this point. :) If someone provides a patch and I were to cut and paste that patch, I :) would call myself crazy, I would normally save the patch to a file :) directly, so this is not an issue. :) :) The issue is inspecting the patch in the archives. If you have to :) puzzle out where the line breaks actually occur because your web :) browser is helpfully wrapping things for you, then the utility of the :) archives has been diminished for some people (like me). I understand, I see how this could be an issue. But adding BR, as I mentioned before fixes this problem. :) On the other hand, just to mention something, instead of saying NO, :) it won't happen, maybe you may want to experiment on adding BR at :) the end of each line, or adding P instead of having empty lines, or :) things like that. Probably does not work out of the box, but it :) probably can be tuned to fit most messages, if not all. :) :) That's sort of presumptuous, don't you think? No. :) You don't even know how the archives are generated but you have no :) qualms about suggesting that I take my time trying to fix something :) which I've already indicated is not broken. I do not need to know how the archives are generated to see that they are broken, but if you want to spare your time explaining this to me, I am happy to read it. I never used the word fix, please do not misunderstand me. I refer to this as enhance. Yes, it is broken, by the way. :) Again, I am not going to spend any time trying to set up the cygwin :) mailing list as a special case. There are surely other sites archiving :) the mailing list out there somewhere. Use one of them if the :) formatting in the sourceware.org archive offends you. It has not offended me. Did I say so? :) OTOH, if anyone wants to change the policy of sourceware.org, you are :) welcome to send email to the overseers mailing list and lobby for :) change. I don't think you are going to find a receptive audience, but :) I could be wrong. I don't think it's the time to send such request. I will wait a couple of years to do so. -- Eduardo http://www.math.washington.edu/~chappa/pine/ -- 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/
/usr/lib and /lib mount question
hi all- after installing gcc with the latest setup.exe i receive this error message when running gcc: $ gcc gcc: /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/specs: No such file or directory as such, make becomes completely unusable as do most configure scripts. i discovered /lib is mounted on /usr/lib from the faq. ls can see the file but gcc cannot. i attempted uninstalling and reinstalling without success. http://sources.redhat.com/ml/cygwin/2004-05/msg00963.html seemed in the same vein, but i don't believe this is a missing install issue. tia, alan Cygwin Configuration Diagnostics Current System Time: Fri Jul 09 10:04:28 2004 Windows XP Professional Ver 5.1 Build 2600 Service Pack 1 Path: C:\cygwin\usr\local\bin C:\cygwin\\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Program Files\Common Files\Adaptec Shared\System c:\j2sdk1.4.1_03\bin c:\apache-ant-1.5.4\bin c:\ajaynes\dev\openh323 Output from C:\cygwin\bin\id.exe (nontsec) UID: 1009(ajaynes) GID: 513(None) 513(None) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1009(ajaynes) GID: 513(None) 0(root) 513(None) 544(Administrators) 545(Users) SysDir: C:\WINDOWS\System32 WinDir: C:\WINDOWS HOME = `C:\cygwin\home\ajaynes' MAKE_MODE = `unix' PWD = `/home/ajaynes' USER = `ajaynes' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' ANT_HOME = `c:\apache-ant-1.5.4' APPDATA = `C:\Documents and Settings\ajaynes\Application Data' CLIENTNAME = `Console' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `JTEP04' COMSPEC = `C:\WINDOWS\system32\cmd.exe' CVS_RSH = `/bin/ssh' HOMEDRIVE = `C:' HOMEPATH = `\Documents and Settings\ajaynes' HOSTNAME = `jtep04' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:' JAVA_HOME = `C:\j2sdk1.4.1_03' LOGONSERVER = `\\JTEP04' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man:' NUMBER_OF_PROCESSORS = `1' OAA_HOME = `C:\rgiuli\dev\oaa\oaa2.3.0' OLDPWD = `/etc/skel' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 7, GenuineIntel' PROCESSOR_LEVEL = `15' PROCESSOR_REVISION = `0207' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 [EMAIL PROTECTED] \[\033[33m\w\033[0m\] $ ' SESSIONNAME = `Console' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINDOWS' TEMP = `C:\DOCUME~1\ajaynes\LOCALS~1\Temp' TERM = `cygwin' TMP = `C:\DOCUME~1\ajaynes\LOCALS~1\Temp' USERDOMAIN = `JTEP04' USERNAME = `ajaynes' USERPROFILE = `C:\Documents and Settings\ajaynes' WINDIR = `C:\WINDOWS' _ = `/usr/bin/cygcheck' POSIXLY_CORRECT = `1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:\cygwin\' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:\cygwin\/bin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:\cygwin\/lib' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options a: fd N/AN/A c: hd FAT32 28562Mb 69% CPUN d: cd N/AN/A C:\cygwin\ / system binmode C:\cygwin\/bin /usr/bin system binmode C:\cygwin\/lib /usr/lib system binmode . /cygdrive system binmode,cygdrive Found: C:\cygwin\\bin\awk.exe Found: C:\cygwin\bin\awk.exe Warning: C:\cygwin\\bin\awk.exe hides C:\cygwin\bin\awk.exe Found: C:\cygwin\\bin\bash.exe Found: C:\cygwin\bin\bash.exe Warning: C:\cygwin\\bin\bash.exe hides C:\cygwin\bin\bash.exe Found: C:\cygwin\\bin\cat.exe Found: C:\cygwin\bin\cat.exe Warning: C:\cygwin\\bin\cat.exe hides C:\cygwin\bin\cat.exe Found: C:\cygwin\\bin\cp.exe Found: C:\cygwin\bin\cp.exe Warning: C:\cygwin\\bin\cp.exe hides C:\cygwin\bin\cp.exe Found: C:\cygwin\\bin\cpp.exe Found: C:\cygwin\bin\cpp.exe Warning: C:\cygwin\\bin\cpp.exe hides C:\cygwin\bin\cpp.exe Found: C:\cygwin\\bin\find.exe Found: C:\cygwin\bin\find.exe Warning: C:\cygwin\\bin\find.exe hides C:\cygwin\bin\find.exe Found: C:\cygwin\\bin\gcc.exe Found: C:\cygwin\bin\gcc.exe Warning: C:\cygwin\\bin\gcc.exe hides C:\cygwin\bin\gcc.exe Not Found: gdb Found: C:\cygwin\\bin\grep.exe Found: C:\cygwin\bin\grep.exe Warning: C:\cygwin\\bin\grep.exe hides
Re: /usr/lib and /lib mount question
On Fri, 9 Jul 2004, Alan Jaynes wrote: hi all- after installing gcc with the latest setup.exe i receive this error message when running gcc: $ gcc gcc: /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/specs: No such file or directory as such, make becomes completely unusable as do most configure scripts. i discovered /lib is mounted on /usr/lib from the faq. ls can see the file but gcc cannot. i attempted uninstalling and reinstalling without success. http://sources.redhat.com/ml/cygwin/2004-05/msg00963.html seemed in the same vein, but i don't believe this is a missing install issue. I think you may have hit on the trailing slash in mount problem. Try issuing the following commands: mount -s -b c:/cygwin / mount -s -b c:/cygwin/bin /usr/bin mount -s -b c:/cygwin/lib /usr/lib and see if it helps. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-'Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 10:24:22AM -0700, Eduardo Chappa wrote: *** Christopher Faylor ...: Maybe you're being purposely obtuse. I don't know. My point was that if I send specially formatted text in my messages to a technical mailing list I don't want the archiving software to unformat it for me. What it does to the email reader on your PDA is irrelevant. What you do not understand is that i am talking about a PDA as a screen, like the one that you are reading your e-mail message. Rest assured, I know that PDAs have screens. If someone provides a patch and I were to cut and paste that patch, I would call myself crazy, I would normally save the patch to a file directly, so this is not an issue. The issue is inspecting the patch in the archives. If you have to puzzle out where the line breaks actually occur because your web browser is helpfully wrapping things for you, then the utility of the archives has been diminished for some people (like me). I understand, I see how this could be an issue. But adding BR, as I mentioned before fixes this problem. On the other hand, just to mention something, instead of saying NO, it won't happen, maybe you may want to experiment on adding BR at the end of each line, or adding P instead of having empty lines, or things like that. Probably does not work out of the box, but it probably can be tuned to fit most messages, if not all. That's sort of presumptuous, don't you think? No. I phrased that poorly. Let me restate. I think your suggestion was presumptuous. You don't even know how the archives are generated but you have no qualms about suggesting that I take my time trying to fix something which I've already indicated is not broken. I do not need to know how the archives are generated to see that they are broken, but if you want to spare your time explaining this to me, I am happy to read it. You're welcome to do this research yourself. Start by inspecting the email archives themselves for clues. Frankly, since I only barely understand what PDAs are and since I really don't know what this br stuff is all about, I don't think you'd want to engage me in a discussion about complicated stuff like mail archiving. You'd be spending all of your time explaining stuff to me. I never used the word fix, please do not misunderstand me. I refer to this as enhance. Yes, it is broken, by the way. So, it's broken and you want me to enhance it so that it won't be broken anymore but you were not suggesting a fix. Got it. Again, I am not going to spend any time trying to set up the cygwin mailing list as a special case. There are surely other sites archiving the mailing list out there somewhere. Use one of them if the formatting in the sourceware.org archive offends you. It has not offended me. Did I say so? I guess I was inferring from your multiple messages to this thread, and by your attempts to offer simple suggestions for enhancing things, that you did not like the current state of affairs. I stand corrected. OTOH, if anyone wants to change the policy of sourceware.org, you are welcome to send email to the overseers mailing list and lobby for change. I don't think you are going to find a receptive audience, but I could be wrong. I don't think it's the time to send such request. I will wait a couple of years to do so. Then you are done with this discussion except as a theoretical exercise, apparently. 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: /usr/lib and /lib mount question
On Fri, Jul 09, 2004 at 01:56:39PM -0400, Igor Pechtchanski wrote: On Fri, 9 Jul 2004, Alan Jaynes wrote: after installing gcc with the latest setup.exe i receive this error message when running gcc: $ gcc gcc: /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/specs: No such file or directory as such, make becomes completely unusable as do most configure scripts. i discovered /lib is mounted on /usr/lib from the faq. ls can see the file but gcc cannot. i attempted uninstalling and reinstalling without success. http://sources.redhat.com/ml/cygwin/2004-05/msg00963.html seemed in the same vein, but i don't believe this is a missing install issue. I think you may have hit on the trailing slash in mount problem. Try issuing the following commands: mount -s -b c:/cygwin / mount -s -b c:/cygwin/bin /usr/bin mount -s -b c:/cygwin/lib /usr/lib mount -f -s -b c:/cygwin / mount -f -x -s -b c:/cygwin/bin /usr/bin mount -f -s -b c:/cygwin/lib /usr/lib might work a little better. The -f is necessary for already mounted directories and the -x tells cygwin that the contents of the directory are all executable which speeds things up slightly. 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: Building DLL
At 11:24 AM 7/9/2004, you wrote: Put all the functions into a library. Link the application and the modules against this library (building only the appA's main() into the executable). Hmmm, not sure if I can convinve the XFCE developers of such a change, as it's fairly major. It was also reported that creating an import library (or stub library) for the executables functions is sufficient if it is linked in, IIRC it this might be more acceptable, but I have no idea of how to go about that... Anybody knows more about how to do this? was the same problem with naim plugins. Maybe there are some useful hints in the naim sources. Wouldn't this work, substituting executable for DLL in the obvious places? http://cygwin.com/cygwin-ug-net/dll.html#DLL-LINK There was also discussion of this in the email archives, if you're interested in that. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
*** Christopher Faylor ([EMAIL PROTECTED])...: :) On Fri, Jul 09, 2004 at 10:24:22AM -0700, Eduardo Chappa wrote: :) *** Christopher Faylor ...: :) Maybe you're being purposely obtuse. I don't know. My point was :) that if I send specially formatted text in my messages to a technical :) mailing list I don't want the archiving software to unformat it for :) me. What it does to the email reader on your PDA is irrelevant. :) :) What you do not understand is that i am talking about a PDA as a :) screen, like the one that you are reading your e-mail message. :) :) Rest assured, I know that PDAs have screens. That was not my point. Re read the text, maybe you'll get it the second time. If not, go back to high school before you read it for the third time, maybe you'll get it at that time. If not, just give up. :) If someone provides a patch and I were to cut and paste that patch, :) I would call myself crazy, I would normally save the patch to a file :) directly, so this is not an issue. :) :) The issue is inspecting the patch in the archives. If you have to :) puzzle out where the line breaks actually occur because your web :) browser is helpfully wrapping things for you, then the utility of the :) archives has been diminished for some people (like me). :) :) I understand, I see how this could be an issue. But adding BR, as I :) mentioned before fixes this problem. :) :) On the other hand, just to mention something, instead of saying NO, it :) won't happen, maybe you may want to experiment on adding BR at the :) end of each line, or adding P instead of having empty lines, or :) things like that. Probably does not work out of the box, but it :) probably can be tuned to fit most messages, if not all. :) :) That's sort of presumptuous, don't you think? :) :) No. :) :) I phrased that poorly. Let me restate. :) :) I think your suggestion was presumptuous. That's your opinion, I do not agree with that. I think it's a natural opinion. :) You don't even know how the archives are generated but you have no :) qualms about suggesting that I take my time trying to fix something :) which I've already indicated is not broken. :) :) I do not need to know how the archives are generated to see that they :) are broken, but if you want to spare your time explaining this to me, :) I am happy to read it. :) :) You're welcome to do this research yourself. Start by inspecting the :) email archives themselves for clues. No thanks, however I will make a deal with you. If I make this research, you do the change in the way the archives are generated, so that all people in this thread be happy. Do we have a deal? :) Frankly, since I only barely understand what PDAs are and since I :) really don't know what this br stuff is all about, I don't think :) you'd want to engage me in a discussion about complicated stuff like :) mail archiving. You'd be spending all of your time explaining stuff to :) me. Maybe, maybe not. We can try. It's up to you, not up to me. :) I never used the word fix, please do not misunderstand me. I refer :) to this as enhance. Yes, it is broken, by the way. :) :) So, it's broken and you want me to enhance it so that it won't be :) broken anymore but you were not suggesting a fix. Got it. I said enhance because I do think that it is possible to do better than a PRE tag, I said broken because a PRE tag is obviously wrong. You can keep it broken, or you can enhance it, up to you. I do not call it fix it, because it works very well, but it's not ideal. :) Again, I am not going to spend any time trying to set up the cygwin :) mailing list as a special case. There are surely other sites :) archiving the mailing list out there somewhere. Use one of them if :) the formatting in the sourceware.org archive offends you. :) :) It has not offended me. Did I say so? :) :) I guess I was inferring from your multiple messages to this thread, and :) by your attempts to offer simple suggestions for enhancing things, :) that you did not like the current state of affairs. I stand corrected. Yeah, don't draw conclusions like that. You are very good to add words where there weren't any. :) OTOH, if anyone wants to change the policy of sourceware.org, you are :) welcome to send email to the overseers mailing list and lobby for :) change. I don't think you are going to find a receptive audience, :) but I could be wrong. :) :) I don't think it's the time to send such request. I will wait a couple :) of years to do so. :) :) Then you are done with this discussion except as a theoretical exercise, :) apparently. I did not say so. You are very good to infer INCORRECT opinions out loud. You SHOULD not. This is not a theoretical exercise, you can do something about it that I can not. -- Eduardo http://www.math.washington.edu/~chappa/pine/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html
RE: can not create a multi-volume archive using tar
From: a111 Sent: Friday, July 09, 2004 6:56 PM Sometime I need to move data between unix machines and win2k. I know, that cygwin can use raw drives, so 'tar -cvf /dev/fd0' can do a work for me. But this command does not work correctly with files which is bigger then 1.4MB -- it can not write data to diskettes as multivolume. Did anybody try that multi-volume archives? Al. FWIW, there is several ways around such a problem. 1) Create a plain tar archive, (unless you can get the multivolume stuff going - creating a splitted archive on a spare partition) 2) 'split' the archive 3) 'dd' (or anything e.g. 'cdrecord') the pieces onto any media. but you might want to fight with tar... ;-) /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E --76-- ** on a mailing list; please keep replies on that particular list ** -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- 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/
FYI: negative error status: gcc vs. cl
Igor could be right about (status = 0x), just in case is not masked by
_exit() as for msvcrt exit()
% cat err.c
#include stdlib.h
int main(int argc, char **argv)
{
if (argc == 1)
return (0);
exit(strtol(argv[1], NULL, 16));
}
- b31 = b16 = 0 -
% err-cl 0x7ffeff5a ; printf %x\n $?
5a
- b16 = 1 -
% err-cl 0x7ff1ff5a ; printf %x\n $?
0
- b31 = 1 -
% err-cl 0x8ffeff5a ; printf %x\n $?
0
- havoc with b16 = 1 -
% err-cl 0x0001105a ; printf %x\n $?
Urgent condition on I/O channel
90
% err-cl 0x0001205a ; printf %x\n $?
Signal 32
a0
% err-cl 0x0001405a ; printf %x\n $?
Signal 64
c0
% err-cl 0x0001305a ; printf %x\n $?
Signal 48
b0
% err-cl 0x0001505a ; printf %x\n $?
d0
--daniel
--
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: can not create a multi-volume archive using tar
On Jul 9 20:55, a111 wrote: Sometime I need to move data between unix machines and win2k. I know, that cygwin can use raw drives, so 'tar -cvf /dev/fd0' can do a work for me. But this command does not work correctly with files which is bigger then 1.4MB -- it can not write data to diskettes as multivolume. Did anybody try that multi-volume archives? Did you try the -M or --multi-volume option of tar? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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/
HOw to install emacs?
I've been downloading emacs from the gnu site and running addpm.exe to install it on Windows 2003. I notice there is an emacs in the cygwin distribution but I cannot figure out how to run it. Do not I need to run addpm.exe like I do in the GNU distribution? I cannot find this program in the cygwin distribution. Thanks, Siegfried __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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/
Password Problem - Cygwin
Hi there Great job youre doing.I encountered this problem running cygwin under Windows XP. When changing my password with passwd.exe the program exited but to my horror the password which i had entered in did not work at my cygwin login or the windows login. What could be the problem? Thank you node _ For super low premiums ,click here http://www.dialdirect.co.za/quote -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Fri, Jul 09, 2004 at 11:37:10AM -0700, Eduardo Chappa wrote: *** Christopher Faylor ([EMAIL PROTECTED])...: If I make this research, you do the change in the way the archives are generated, so that all people in this thread be happy. Do we have a deal? Here's how it works: You do the research yourself, then you present your case where I have previously stated. My participation is not required. There are others who know about this and anyone who does reads the overseers mailing list. I do not want to be involved in doing this. I do not have the right to unilaterally change the mail archiving software on sourceware.org. I am not going to be your champion for this policy change for this site. :) OTOH, if anyone wants to change the policy of sourceware.org, you are :) welcome to send email to the overseers mailing list and lobby for :) change. I don't think you are going to find a receptive audience, :) but I could be wrong. :) :) I don't think it's the time to send such request. I will wait a couple :) of years to do so. :) :) Then you are done with this discussion except as a theoretical exercise, :) apparently. I did not say so. You are very good to infer INCORRECT opinions out loud. You SHOULD not. This is not a theoretical exercise, you can do something about it that I can not. If I am the only one with the power, then I am the one who can tell you that further discussion will have no practical effect. You are welcome to continue to expound on the virtues of format=flowed (even if it is off-topic here). When you do so, however, it will be merely a theoretical exercise since there will be no action taken here. 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: Password Problem - Cygwin
At 04:54 PM 7/9/2004, you wrote: Hi there Great job youre doing.I encountered this problem running cygwin under Windows XP. When changing my password with passwd.exe the program exited but to my horror the password which i had entered in did not work at my cygwin login or the windows login. What could be the problem? See 'man passwd', look for the Limitations note. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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: Where is libxml2.dll?
On Fri, 9 Jul 2004, Richard Heintze wrote: I am running Windows 2003 server with on which I have installed cygwin within the last month. I found a terrific little utility (webdav client) at http://www.gohome.org/nd/ which I downloaded and compiled (with gcc) with cygwin. At the bash command prompt, it appears to work. However, it is intended to be run from emacs. When I create a shell with emacs, it starts up a bash shell as a sub process and I get the error: this application has failed to start because libxml2.dll was not found. Re-installing the application my fix this problem.. Well there is no libxml2.dll on my system but the command works from the bash command prompt! HOw could this be? I notice there are libxml2.dll.a and libxml2.a and libxml2.la in my /usr/lib directory! This must be the one! Why cannot the bash shell find it when run under emacs? Do I need to put c:\cygwin\lib in my PATH environment variable? Thanks, Siegfried Siegfried, You don't need c:\cygwin\lib in your path, but you do need c:\cygwin\bin there if you intend to run Cygwin applications from Win32 ones. FWIW, the actual name of the DLL is cygxml2-2.dll (which you could have determined by examining /usr/lib/libxml2.la), but it's surprising that it looks for libxml2.dll. Can you start a regular bash shell from Emacs? Can you run cygcheck yourapp from that shell before running yourapp? What does the output of the above cygcheck command show? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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/
Source Code for cygwin1.dll
Hello, I am wishing to release a version of a Mud codebase I created and have it packaged ready to run in windows. I am looking for the specific files I need to have packaged up to meet the requirements for the source of the cygwin1.dll. Are there specific files required for the dll and do I need to provide any other source files for any other programs or libraries that might have been used to compile my source? Thanks. --Josh --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 7/5/2004 -- 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: Source Code for cygwin1.dll
At 06:34 PM 7/9/2004, you wrote: Hello, I am wishing to release a version of a Mud codebase I created and have it packaged ready to run in windows. I am looking for the specific files I need to have packaged up to meet the requirements for the source of the cygwin1.dll. Are there specific files required for the dll and do I need to provide any other source files for any other programs or libraries that might have been used to compile my source? Thanks. If your distribution uses Cygwin and you include the DLL with your distribution, you need the source required to build that version of the DLL. You can download the source for the Cygwin DLL with the binary package via 'setup.exe'. However, the preferred method of distribution is to *not* bundle the Cygwin DLL with your package but instead point folks to the Cygwin site, with any directions/recommendations you want to make. This is preferred because it helps to maintain the requirement that there be only 1 cygwin1.dll on the user's system. Otherwise, those who package and distribute their software separate from the Cygwin distribution or by means other than 'setup.exe' run the risk of generating conflicts if users already have or will install Cygwin in the future. All this is predicated on the notion that your package is open source of course. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Responding before I read the whole thread, as I'm sure this gets a whole lot uglier: On Jul 9 11:03, William Blunn wrote: I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. My 2ct are simply this: If somebody wants to be read, he or she should stick to the common rules. Common rules? I prefer to stick to Standards if at all possible. Like RFCs and such. If somebody isn't able or willing to learn these rules, bad luck for him or her. I'm against pampering clueless people so that they can lean back and stay clueless. Call me mean. You're mean ;-). -- Gary R. Van Sickle -- 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/
