[ANNOUNCEMENT] [Updated] Perl distributions
The following Perl distributions have been added to Cygwin or updated to their latest version on CPAN, respectively: x86/x86_64 -- perl-DateTime-1.44-1 perl-PerlIO-utf8_strict-0.007-1 perl-Sub-Name-0.21-1 perl-Sort-Key-1.33-1 noarch -- perl-Class-Factory-Util-1.7-1 perl-DateTime-Calendar-Julian-0.04-1 perl-DateTime-Format-Builder-0.81-1 perl-DateTime-Format-Strptime-1.74-1 perl-Package-DeprecationManager-0.17-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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: Either trim quoted text or STOP BOTTOM POSTING
On 8/24/2017 8:36 PM, L A Walsh wrote: > If you can't trim your quoted text, then please stop burying the > new stuff on the bottom. > Did you wake up on the wrong side of the bed. I see from a google search that you've had problems with style in the past even on this list. > > I've noticed it is most often bottom-poster who include all > previous quotes -- and that's the worst -- having to WADE > through EVERYTHING that came before, when EVERYONE on the > list has already received it. That's the rub: if you List etiquette frowns on both bottom and top posting and warrants to interleaving the replies. > want to bottom-post, then trim what you are quoting to that > which is necessary (and that's fine w/me). > But if you are not good about trimming, then put the *IMPORTANT* > stuff first (your NEW text). That's write -- the most important s/write/right > thing in your email is what YOU are writing. It should come > first. If you feel a need to quote large parts of the previous > conversation, put it in an appendix -- because most people will > have already received and read it. Including it again is > "superfluous", but that's why there are appendices. What I'm replying to follows what I'm quoting to give context to the reply. My reply should never be more important that the reason for the response. Without the context of what I'm responding to there is no reason to reply but I should create a new subject and thread. > > I DO pay attention to the subject BTW. Well all and good but you hijacked a thread to bring home a point which is in itself just wrong. https://wiki.openstack.org/wiki/MailingListEtiquette -- cyg 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
Aliases - I learned something new
In the research for my responses to the alias issue I learned something I didn't know. Not a big deal but I thought I would share. If the value of an alias ends in a space the word following the issuance of the alias command is also checked for alias expansion. Example: $ alias t1='echo abc' $ alias t2='dev' $ t1 t2 abc t2 $ alias t1='echo abc ' $ t1 t2 abc def -- cyg Simple P.S. I love learning new things, it just proves my wife's assumption that I don't know everything. ;p -- 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: Aliases - I learned something new
On 08/25/2017 10:00 AM, cyg Simple wrote: > If the value of an alias ends in a space the word following the issuance > of the alias command is also checked for alias expansion. In fact, this behavior is POSIX-mandated, so that you can do things like: alias exec='exec ' and get alias expansion on 'foo' when you do 'exec foo' > Example: > > $ alias t1='echo abc' > $ alias t2='dev' > $ t1 t2 > abc t2 > > $ alias t1='echo abc ' > $ t1 t2 > abc def Doesn't quite match what you typed above (dev vs. def), but illustrates the point. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org signature.asc Description: OpenPGP digital signature
Re: Either trim quoted text or STOP BOTTOM POSTING
I hadn't heard the name 'interleaved' style, I think that used to be called top-posting plus appropriate trimming. I sympathize with folks who are frustrated with whippersnappers not knowing email conventions. (It's almost as bad as not knowing how to use a manual gearshift :-) - Dan -- 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: Re: Strange errors with gcc and top, even after rebaseall
Hi, ok, then i need at work two 32bit versions, one for building software A and one for software B, and a 64bit version for working with Cygwin, e. g. locate, backups etc.. For switching between the versions i use moving (renaming) the directories of the other versions and replacing them with junction points to the active version. Is there a better way for switching? Rolf Freitag Gesendet: Donnerstag, 24. August 2017 um 13:16 Uhr Von: "Eliot Moss" An: cygwin@cygwin.com Betreff: Re: Aw: Re: Strange errors with gcc and top, even after rebaseall On 8/24/2017 3:16 AM, nobo...@web.de wrote: > Hi, > > the 64bit version, with all packages installed, has no problem. > But i also want a 32bit version. You can have the 32 bit version installed, but not all the packages. Cygwin's approach to making fork work as closely as possible to the way it works on Posix requires each Cygwin DLL to be put in its own reserved place in the address space. The sum total of the DLLs exceeds the available 32 bit address space. Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/[http://cygwin.com/faq/] Documentation: http://cygwin.com/docs.html[http://cygwin.com/docs.html] Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple[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: Strange errors with gcc and top, even after rebaseall
Greetings, nobo...@web.de! > ok, then i need at work two 32bit versions, one for building software A and > one for software B, Why can't you build both under one?… > and a 64bit version for working with Cygwin, e. g. locate, backups etc.. > For switching between the versions i use moving (renaming) the directories > of the other versions and replacing them with junction points to the active > version. > Is there a better way for switching? Why ever "switching" ? Default Cygwin usage pattern allows for two arch versions to live independently. -- With best regards, Andrey Repin Saturday, August 26, 2017 06:33:05 Sorry for my terrible english...
Re: convenient trimming of quoted text to make points
cyg Simple wrote: On 8/24/2017 8:36 PM, L A Walsh wrote: If you can't trim your quoted text, then please stop burying the new stuff on the bottom. Did you wake up on the wrong side of the bed. I see from a google search that you've had problems with style in the past even on this list. Maybe I'm one of the few who has RSI and gets irritated by having to go through extra steps to skip large walls of text. List etiquette frowns on both bottom and top posting and warrants to interleaving the replies. --- I know of no list where that is commonly practiced. Well all and good but you hijacked a thread to bring home a point which is in itself just wrong. To selectively quote things in your reply to make your point is the problem here, since I replied to the original subject, extensively. It was you who deleted the "on-topic" part of the message to make your point. -- 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
