Re: Problem Report

>b_gettext 9004 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. >Please report this problem to >the public mailing list cygwin@cygwin.com https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings -- Problem reports: https://cygwin.com/proble

Problem Report

b_gettext 9004 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:

Re: problem report

Am 13.09.2018 um 17:15 schrieb Jovanny Rodriguez: 1 [main] dash 13912 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings --- Diese E-Mail wurd

problem report

1 [main] dash 13912 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/

Re: Problem report

, Email: av...@il.ibm.com "Life can only be understood backwards but it must be lived forward? ? Søren Kierkegard From: Andrey Repin To: "Aviad Zlotnick" , cygwin@cygwin.com Date: 04/03/2018 20:05 Subject: Re: Problem report Greetings, Aviad Zlotnick! > [mai

Re: Problem report

Greetings, Aviad Zlotnick! > [main] startxwin 18048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD > pointer. Please report this problem to > the public mailing list cygwin@cygwin.com FAQ entry 4.46 http://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings This problem was fix

Problem report

[main] startxwin 18048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com Aviad Tel: +

Re: help developing a good problem report

On Thu, May 26, 2011 at 12:10:27PM -0500, Rance Hall wrote: >I've been noticing an issue with cygwin that I find annoying and would >like to fix. > >Ive never submitted a cygwin problem report before so this is a first. > >My issue now is that I dont actually understand the

Re: help developing a good problem report

On 26/05/2011 1:10 PM, Rance Hall wrote: I've been noticing an issue with cygwin that I find annoying and would like to fix. Ive never submitted a cygwin problem report before so this is a first. My issue now is that I dont actually understand the problem well enough to give a good r

help developing a good problem report

I've been noticing an issue with cygwin that I find annoying and would like to fix. Ive never submitted a cygwin problem report before so this is a first. My issue now is that I dont actually understand the problem well enough to give a good report. Here is what is happening: I'm us

Re: libtool m4 file problem report

Olivier Langlois wrote: > By running aclocal-1.6 -I m4, the tool returned messages saying that macros > > _LT_PREPARE_SED_QUOTE_VARS > _LT_PROG_ECHO_BACKSLASH > > were required but not defined. This should be fixed in the libtool-2.2.7a-3 (-12 for cygwin-1.7), that was released last night. It's

libtool m4 file problem report

I have encountered problems by reexecuting autoconf on a project that used to work fine with a previous version of cygwin. I cannot give details about on which versions it worked and since when it broke as the last successful configuration is many months old. However, I wanted to give the list o

Re: cron problem report

* Seiji Tokunaga (2004-03-01 21:27 +0100) > I have trouble getting my cron to work. Please consider explaining what you mean by this otherwise any answer to your report won't satisfy you. > % crontab -l > # DO NOT EDIT THIS FILE - edit the master and reinstall. > # (/tmp/crontab.3928 installed on

RE: cron problem report

> > % crontab -l > # DO NOT EDIT THIS FILE - edit the master and reinstall. > # (/tmp/crontab.3928 installed on Mon Mar 1 15:03:19 2004) > # (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 > corinna Exp $) > * * * * * `date` >> ${HOME}/foo.log > % Do not include backquotes on 'date' -

RE: cron problem report

Please try version 1.4. It has additional checks. http://sources.redhat.com/ml/cygwin/2004-02/msg01341.html > -Original Message- > From: Seiji Tokunaga [mailto:[EMAIL PROTECTED] > Sent: Monday, March 01, 2004 3:27 PM > To: [EMAIL PROTECTED] > Subject: cron problem re

cron problem report

Hi, I have trouble getting my cron to work. I have tried cron_diagnosis.sh 1.3 but I could not find any problems. I also did the suggestion from the cron_diagnosis.sh output but it does not work. Here is the crontab -l, cron_diagnose.sh output and the cygcheck -srv output. Hope you can help me. %

MailFilter Problem Report

MailFilter/ax has scanned an E-Mail you sent to <[EMAIL PROTECTED]>, and has detected that either the contents or an attachment is forbidden by the organizational policy. Please contact either the origial recipient or the Postmaster <[EMAIL PROTECTED]>. Details: From: "<[EMAIL PROTECTED]>" To

Re: problem report: gawk 3.1.1

Pieter Prinsloo wrote: > Hi. > > Have a query/problem with gawk version 3.1.1-5 dated 17/Oct/2002. > (allthough the problem as stated is for cygwin - it can also be > emulated in Linux > with gawk 3.1.0) > > Given the following example > ==ort awk program file={ >one =printf("%s",$1); >two

RE: problem report: gawk 3.1.1

> -Original Message- > From: Pieter Prinsloo [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 20, 2003 6:45 PM > To: [EMAIL PROTECTED] > Subject: Re: problem report: gawk 3.1.1 > >> Have a query/problem with gawk version 3.1.1-5 dated 17/Oct/2002. > > D

Re: problem report: gawk 3.1.1

* Pieter Prinsloo (03-02-20 18:44 +0100) >>> (allthough the problem as stated is for cygwin - it can also be emulated in >>> Linux with gawk 3.1.0) >> Great! So it isn't Cygwin specific or related and therefor offtopic here. > > How you got to that great conclusion that it is not cygwin specific

Re: problem report: gawk 3.1.1

Hi. >> Have a query/problem with gawk version 3.1.1-5 dated 17/Oct/2002. > Did you read the thread "awk CR/LF issue"? It's been a topic today. Yep - that should be obvious - but not the same problem. >> (allthough the problem as stated is for cygwin - it can also be emulated in >> Linux >> with

Re: problem report: gawk 3.1.1

* Pieter Prinsloo (03-02-19 23:09 +0100) > Have a query/problem with gawk version 3.1.1-5 dated 17/Oct/2002. Did you read the thread "awk CR/LF issue"? It's been a topic today. > (allthough the problem as stated is for cygwin - it can also be emulated in > Linux > with gawk 3.1.0) Great! So it i

problem report: gawk 3.1.1

Hi. Have a query/problem with gawk version 3.1.1-5 dated 17/Oct/2002. (allthough the problem as stated is for cygwin - it can also be emulated in Linux with gawk 3.1.0) Given the following example short awk program file==={ one = sprintf("%s",$1); two = sprintf("%s",$2); printf("LEFT

RE: Problem report: pipes and suspending do not work well together

> Previously reported. Fixed in snapshots for a while and will > be in the > next release. OK, sorry for bothering you and thanks for your response. I searched cygwin.com mailing list archives with Google but couldn't find anything related to this problem so I thought it was not reported alre

Re: Problem report: pipes and suspending do not work well together

On Thu, Oct 10, 2002 at 05:29:33PM +0300, [EMAIL PROTECTED] wrote: >I am using the newest Cygwin net release (upgraded today by re-running >Cygwin Setup to make sure this is not fixed yet). I noticed this >problem while writing a long pipeline ending with "| less" and then >trying to suspend the

Problem report: pipes and suspending do not work well together

Hello and thanks for your attention, I am using the newest Cygwin net release (upgraded today by re-running Cygwin Setup to make sure this is not fixed yet). I noticed this problem while writing a long pipeline ending with "| less" and then trying to suspend the processes. When I do this the C

Re: [BUG] Patch.exe problem report

On Wed, Feb 20, 2002 at 02:27:00PM -0500, Charles Wilson wrote: >>It now opens the source file in O_TEXT mode and writes >>it in O_BINARY so that the destination file is always >>written out with UNIX LFs. > >Ummm...is that really a good idea? patch will now autoconvert every >"dosmode" file to

Re: [BUG] Patch.exe problem report

Corinna Vinschen wrote: > On Thu, Feb 14, 2002 at 01:46:16PM +0100, Pierre Muller wrote: > >> >>I already mentioned the following bug some time ago, >>but I now took the time to identify the problem. >>[...] >> > > I've just uploaded a new version of patch to cygwin.com. > It should arrive on t

Re: [BUG] Patch.exe problem report

On Thu, Feb 14, 2002 at 01:46:16PM +0100, Pierre Muller wrote: > > > I already mentioned the following bug some time ago, > but I now took the time to identify the problem. > [...] I've just uploaded a new version of patch to cygwin.com. It should arrive on the mirrors at least tomorrow. It no

Re: [BUG] Patch.exe problem report

At 07:46 AM 2/14/2002, Pierre Muller wrote: >I already mentioned the following bug some time ago, >but I now took the time to identify the problem. > > >The problem appears if you are using patch to >apply a patch on a binary mounted device >while your patch uses a temporary directory that

[BUG] Patch.exe problem report

I already mentioned the following bug some time ago, but I now took the time to identify the problem. The problem appears if you are using patch to apply a patch on a binary mounted device while your patch uses a temporary directory that is located on a text mounted dir. The temprary fil