Re: Fortune and the "fortune startrek" command
> Lets all say it together > One more time > Now cover your eyes and see if you can say it without reading it > Close enough. Humorous? To me, as a newcomer, no. Funny? Hardly. Insulting? I would say so. I don't mind jokes and hints, but I must say that that is a pretty depreciative answer to someones positive and frankly quite cheerful question. On 6/22/10, Christopher Faylor wrote: > On Tue, Jun 22, 2010 at 07:40:50PM +0200, Alexander T wrote: >>On Tue, Jun 22, 2010 at 10:35:30AM -0400, Christopher Faylor wrote: >>>You're exaggerating. Most of the time when maintainers receive private >>>email they redirect it to this list with a polite request to keep the >>>discussion public. There is no "head handing". >> >>O RLY? > > Yep. > > cgf > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fortune and the "fortune startrek" command
> You're exaggerating. Most of the time when maintainers receive private > email they redirect it to this list with a polite request to keep the > discussion public. There is no "head handing". O RLY? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 'cp' utility bug when .exe file exist.
Why not just do the exe magic for executing the files only? When opening, stating, copying, moving etc, you could leave it out. This seems the most reasonable compromise to me, but there could of course be cases which I am overseeing, but I wouldn't expect any script to rely on exe magic when opening a file for editing. On 6/9/10, Andy Koppe wrote: > On 9 June 2010 10:48, Julio Costa wrote: And this is where my head got reeeally spinning... can anyone, please, explain the reason to why this .exe magic exists, anyway? > > As far as I understand it, the original reason for it was that Windows > 9x always required it. Of course Cygwin 1.7 no longer supports 9x, so > from that perspective, it's no longer needed. > > >>> [Running in cmd.exe] >> The point is, that *is not* a reason, because it is easily fixed by >> "set PATHEXE=%PATHEXE%:.". > > That's a nice one. I certainly didn't know about that. > > Explorer still needs the .exe though. More importantly, a lot of build > scripts likely depend on the .exe being added automatically. > > The frequent questions and problems around this issue do make me > wonder though whether it wouldn't indeed be better to drop the .exe > magic completely, deal with the ensuing pain, but eventually be done > with it. > > Andy > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
Err, 'very deep' was a bit misleading, the error seemed to show up at 2-3 levels according to the last post in that thread. On 6/8/10, Alexander T wrote: > There is a similar post from 2009 where the conclusion is that this > can be caused by very deep forking > (http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it > possible that the make script does very deep, or is stuck in infinite, > recursion? > > On 6/8/10, Nasser M. Abbasi wrote: >> On 6/7/2010 7:03 PM, Charles Wilson wrote: >>> On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote: >>>> >>>> $ make test >>>> >>>>0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - >>>> Internal error: TP_NUM_W_BUFS too small. >>>> >>>> Error while converting image: No such file or directory >>>> >>>> Error: Cannot read 'img2.png': No such file or directory >>>> Converting image #1 >>>>0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - >>>> Internal error: TP_NUM_W_BUFS too small. >>> >> >> >>> I wonder if the 'test' procedure for latex2hmtl sets the $PATH to your >>> installed LaTeX implementation. >>> >>> Or worse, somehow sets a PERL5_INCPATH variable to point at the >>> perl/lib/ directory under G:\LATEX\. If THAT happened, then your >>> cygwin-perl would be trying to use native-perl's libraries (including >>> binary extensions)... >>> >>> Try, temporarily, moving G:/LATEX/perl out of the way. >>> >>> -- >>> Chuck >>> >> >> Ok, I did. I renamed my windows perl folder, but I still get the same >> error. >> >> May be someone can try to install Latex2html on their cygwin as I did >> and try this? May be this has nothing to do with windows 64 bit or >> windows 7, so any windows version might show this problem as well? >> >> Installation of l2h is easy on cygwin, just need to download l2h and >> untar and type ./configure, make, make install, make test >> >> Instructions how to install l2h on cygwin are on my page below: >> >> http://12000.org/my_notes/l2hwin/index.htm >> >> (need to edit one file, to make sure to tell l2h is under Unix) >> >> Not many people use l2h under cygwin, may be I am the first to try to do >> this on cygwin 1.7? >> >> == >> >> $ ls /cygdrive/G/LATEX | grep -i perl >> perl_NOT_USED_FOR_MINUTE >> >> $ echo $PATH >> /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem >> >> $ which perl >> /usr/bin/perl >> >> $ perl -v >> >> This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int >> (with 12 registered patches, see perl -V for more detail) >> >> $ make test >> >> Converting image #2 >>0 [main] perl 4396 C:\cygwin\bin\perl.exe: *** fatal error - >> Internal error: TP_NUM_W_BUFS too small. >> >> Error while converting image: No such file or directory >> >> Error: Cannot read 'img2.png': No such file or directory >> Converting image #1 >>0 [main] perl 712 C:\cygwin\bin\perl.exe: *** fatal error - >> Internal error: TP_NUM_W_BUFS too small. >> >> == >> >> --Nasser >> >> -- >> Problem reports: http://cygwin.com/problems.html >> FAQ: http://cygwin.com/faq/ >> Documentation: http://cygwin.com/docs.html >> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >> >> > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
There is a similar post from 2009 where the conclusion is that this can be caused by very deep forking (http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it possible that the make script does very deep, or is stuck in infinite, recursion? On 6/8/10, Nasser M. Abbasi wrote: > On 6/7/2010 7:03 PM, Charles Wilson wrote: >> On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote: >>> >>> $ make test >>> >>>0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - >>> Internal error: TP_NUM_W_BUFS too small. >>> >>> Error while converting image: No such file or directory >>> >>> Error: Cannot read 'img2.png': No such file or directory >>> Converting image #1 >>>0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - >>> Internal error: TP_NUM_W_BUFS too small. >> > > >> I wonder if the 'test' procedure for latex2hmtl sets the $PATH to your >> installed LaTeX implementation. >> >> Or worse, somehow sets a PERL5_INCPATH variable to point at the >> perl/lib/ directory under G:\LATEX\. If THAT happened, then your >> cygwin-perl would be trying to use native-perl's libraries (including >> binary extensions)... >> >> Try, temporarily, moving G:/LATEX/perl out of the way. >> >> -- >> Chuck >> > > Ok, I did. I renamed my windows perl folder, but I still get the same error. > > May be someone can try to install Latex2html on their cygwin as I did > and try this? May be this has nothing to do with windows 64 bit or > windows 7, so any windows version might show this problem as well? > > Installation of l2h is easy on cygwin, just need to download l2h and > untar and type ./configure, make, make install, make test > > Instructions how to install l2h on cygwin are on my page below: > > http://12000.org/my_notes/l2hwin/index.htm > > (need to edit one file, to make sure to tell l2h is under Unix) > > Not many people use l2h under cygwin, may be I am the first to try to do > this on cygwin 1.7? > > == > > $ ls /cygdrive/G/LATEX | grep -i perl > perl_NOT_USED_FOR_MINUTE > > $ echo $PATH > /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem > > $ which perl > /usr/bin/perl > > $ perl -v > > This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int > (with 12 registered patches, see perl -V for more detail) > > $ make test > > Converting image #2 >0 [main] perl 4396 C:\cygwin\bin\perl.exe: *** fatal error - > Internal error: TP_NUM_W_BUFS too small. > > Error while converting image: No such file or directory > > Error: Cannot read 'img2.png': No such file or directory > Converting image #1 >0 [main] perl 712 C:\cygwin\bin\perl.exe: *** fatal error - > Internal error: TP_NUM_W_BUFS too small. > > == > > --Nasser > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Anyone interrested in a package manager?
Hi All, I've read the mailing lists and found some posts back in 2003 talking about porting apt to cygwin. I'm going crazy needing to use the installer every time I forgot to install a program, and also dealing with version upgrades and conflicting versions. The installer.exe is also clunky when it comes to selecting in batch etc. It would also be great to make your own repos and update cygwin locally from the repo, like the setup.exe 'local install' does, but then command-line based. So I'm wondering if there are any news on this front. Regards, Alexander -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
