RE: cygwin: /proc and /cygdrive insvisible

> > Mit freundlichen Grüssen, > > ? "With friendly Grüssen". I knew that high school German would come in handy some day... ;-) -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation:

RE: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")

> At 08:47 PM 7/11/2004, you wrote: > >> On Sat, Jul 10, 2004 at 09:54:05AM -0500, Eduardo Chappa wrote: > >> >That was CGF himself, he volunteered to not to volunteer. > He brought > >> >this topic onto himself. > >> > >> This statement is disingenuous. For shame. > >> > > > >Perhaps, perhaps

RE: Extending long threads

> GARY VANSICKLE wrote: >> There's three reasons people knee-jerk against HTML email: >> >> 1. It isn't ASCII (i.e. the "Back in my day a child would open up a >> gift and within seconds he'd either burst into flames or lose a limb! >> That&

RE: PCYMTNQREAIYR Please Configure Your Mailer To Not Quote Raw E-mail Addresses In Your Replies.

cygwin-ownerXXXYOU_KNOW_THE_REST wrote on Sunday, July 11, 2004 7:54 PM: >> On Sun, July 11, 2004 10:22 pm, LDR said: >>> --- Igor Pechtchanski <[EMAIL PROTECTED]> wrote: >>> >>> *PCYMTNQREAIYR* -- Please Configure Your Mailer To Not Quote Raw E-mail Ad

RE: PCYMTNQREAIYR Please Configure Your Mailer To Not Quote Raw E-mail Addresses In Your Replies.

> On Sun, July 11, 2004 10:22 pm, LDR said: > > --- Igor Pechtchanski <[EMAIL PROTECTED]> wrote: > > > > > >> *PCYMTNQREAIYR* -- Please Configure Your Mailer To Not Quote Raw > >> E-mail Addresses In Your Replies. > >> > > > >> . > >> > > > > - What

RE: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")

> On Sat, Jul 10, 2004 at 09:54:05AM -0500, Eduardo Chappa wrote: > >That was CGF himself, he volunteered to not to volunteer. He brought > >this topic onto himself. > > This statement is disingenuous. For shame. > Perhaps, perhaps not. I'm still waiting for somebody, other than you Chris[1],

RE: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")

> >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. Can somebody show me w

RE: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")

> 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

RE: Extending long threads (was: RE: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?"))

> 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

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 compa

RE: higher-level IO very slow with cygwin1.dll 5.10 (due to set_flags?)

> > Possibly I should add that I am comparing the behavior of > version 1.5.10 to a much older version that I was using > before. It wasn't by chance... oh... say... B20? ;-) > So whatever is causing this odd behavior on my system > may not be a feature that was new to version 1.5.10. I am >

RE: Delete key... was home directory.

> > Am I the only one that thinks reading a 12 page document, and possibly > > editing 5 different config files is a hell of a lot of work just to get > > the delete key to work?!?!?! > > You want to make the "delete key" delete in bash? No, he just wants the delete key to work as God intended it

RE: Delete key... was home directory.

> Am I the only one that thinks reading a 12 page document, and possibly > editing 5 different config files is a hell of a lot of work just to get > the delete key to work?!?!?! No, you're not. Some things Unix got pretty well right early on. Other things, Unix will refuse to ever get right. I

[SEMI-OT]: XP SP2 (was: RE: Unable to open files including Korean names)

> Hello from Gregg C Levine > Actually Gary, its called SP2 RC1, for XP. Its going through that > phase, with SP1 RC2 due out towards the end of the month, and the > actual SP2 going to the RTM phase so that its in time to be released > by the 21 July, date. (If you can believe that.) > I of cour

RE: Unable to open files including Korean names

> I did some test and found out that ``every file whose path includes > Korean characters weren't openable.'' Still, I could move arround those [snip] I just installed the XP SP2 "preview" or whatever they call it. One of the things in the very long list of things it claims to fix is some proble

RE: more pain - YAM

> > When you send messages to a mailing list, you invite discussion. That > is why we have mailing lists. > Well, that's why other organizations have mailing lists anyway. (Please send all "we're just mean"s to the list or not at all. I have a very thin skin and get offended if somebody sends

RE: flushall

> >Not sure what an "hdf5" is, but in general it is not possible to do > >sync-to-backing-storage from an arbitrary account in Windows. Not > >even on > >removable media, which of course is where you often need it most. > >Microsoft's rationale behind this escapes me, but there it is. > >Furthermo

RE: flushall

> I'm trying to port some code that uses flushall() to cygwin. > The non-windows version of the code uses 'system("sync")' > but this fails the builtin tests. > > The code is hdf5-1.6.2, in case that helps. > Not sure what an "hdf5" is, but in general it is not possible to do sync-to-backing-sto

RE: Data loss in Cygwin's creator?

> I got this *System Error* message in my e-mail: > > > *plonk* > > Ahh... > > > cgf > > I'm concerned that creator might be dropping some critical data. > However someone more knowledgeable in these matters will have debug > this. > > I also don't have a 64 sheet test roll installed in my bath

RE: Data loss in Cygwin's creator?

> I got this *System Error* message in my e-mail: > > > *plonk* > > Ahh... > > > cgf > > I'm concerned that creator might be dropping some critical data. > However someone more knowledgeable in these matters will have debug > this. > > I also don't have a 64 sheet test roll installed in my bat

RE: Maildir and Cygwin

> On Thu, Apr 22, 2004 at 08:26:00AM -0700, Eduardo Chappa wrote: > > > :) > that Cygwin is different (e.g. we could do this in the cygwin > > :) > applications mailing list). > > :) > > :) Why do you want to change so many programs when all you need is a > > :) cygwin managed mount? > > IMO, the

RE: Comparative Performance of C++ Compilers (including gcc cygming special)

[snip] > > New copying methods have been added and checked: > > Test file modes : text, binary > -- > > Testsuites > -- > C-01 : Functions getc() and putc() > C-02 : Functions fgetc() and fputc() > C-03 : Functions fr

RE: Maildir and Cygwin

> Hello, > >I have been trying to fix a patch for maildir for Pine, and while > thinking about this I recalled that support for Maildir in Cygwin (e.g > Mutt) has been discussed a couple of times. It seems to be that the only > thing stopping people from being able to use it is a agreement on

RE: working sync() code

[snip] > > SUSv3 has this to say about sync(): > > > The sync() function shall cause all information in memory that updates > file > systems to be scheduled for writing out to all file systems. > > The writing, although scheduled, is not necessarily complete upon return > from > sync(). > >

RE: working sync() code

> Hi all, > > I found a way to issue an actual sync() on win32, and as browsing > through winsup directory gave me only this > > > winsup/sygwin/syscalls.cc #1128 > extern "C" int > sync () > { >return 0; > } > > > I think cygwin DLL might benefit from a code I found by looking in > sync.e

RE: Bogus assumption prevents d2u/u2d/conv/etal working on mixed files.

> Noo... Please, remove all of these safety checks. > There must be some kind of user sanity presupposition. Or else the tools > soon will be crippled to a state where they are unusable for normal work. FWIW I'm with Hannu. Should rm ask you, "Do you *really* want to delete this file?", or make

RE: cygwin... from Turkey

> Subject: Re: cygwin... from Turkey "...NER NERRR! Keep on rockin' in the Free world!..." ;-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: