apparent solution to multi-shell problem

[KARR, DAVID via Cygwin]

This is a repost with additional information. I've managed to find a fix, but 
I'd like to understand what happened, and perhaps clean up some ancient code.

For the last few days, I've been struggling with a problem with Cygwin Emacs 
after reinstalling Cygwin, which I haven't had to do for a while.

I discovered that when I create the first shell buffer, it works fine. When I 
create the second shell buffer, it fails with this:
--
   bash: cannot set terminal process group (-1): Inappropriate ioctl for device
   bash: no job control in this shell


After I got away from the computer for a while, I realized that I might be able 
to narrow this down.  I thought that this might be a problem with the small 
façade package I wrote over "shell" a few decades ago, but I realized that if I 
just start Emacs and manually switch to a buffer and run "shell" and then do 
that again, that is basically the same thing.  I found that that repeats the 
problem.

So then I looked at my .emacs file, and I noticed the following.  Note that 
this is another block of code that I haven't changed in many years. I know that 
several of these lines are obsolete now, even some that aren't causing my 
problem:
--
(defun my-shell-mode-hook ()
;(add-hook 'comint-output-filter-functions
;   'shell-strip-ctrl-m nil t)
  (add-hook 'comint-output-filter-functions
'comint-watch-for-password-prompt nil t)
  (setq explicit-shell-file-name "bash")
  ;; For subprocesses invoked via the shell
  ;; (e.g., "shell -c command")
  (setq shell-file-name explicit-shell-file-name)
  (ansi-color-for-comint-mode-on)
  (shell-strip-ctrl-m)
  (setq shell-prompt-pattern "^\[[A-z0-9]+:[A-z0-9/]+\] ")
  (local-set-key "\C-xs" 'cycle-go-shell)
  (local-set-key "\C-xS" 'cycle-find-shell-or-shells-buffer-list)
  (local-set-key "\C-j" 'lfd-send-input)
  (local-set-key [f5] 'comint-previous-matching-input-from-input)
  (local-set-key [f12] 'compilation-shell-minor-mode)
  )
-

For most of this, I can't even remember what it was for.  I tried commenting 
out portions of this and retesting, and I finally narrowed it down to the two 
sets of the related "file-name" variables. When I comment both of those out and 
retest, the problem doesn't occur.  I see that the new value of 
"shell-file-name" is "/bin/bash", instead of the "bash" value that I was 
hardcoding before.  Certainly less code is better than more code, especially if 
it works, but it would be useful to understand if something changed recently 
that might have caused that error.

I also briefly examined some of these other blocks, and I see that apparently 
"shell-strip-ctrl-m" is obsolete.  Is it best to have this?:

(add-hook 'comint-output-filter-functions
'comint-strip-ctrl-m nil t)


-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: How to repair the symlinks in a copied cygwin64 tree

[KARR, DAVID via Cygwin]

Thanks.  I gave up on the backed-up tree a while ago and reinstalled Cygwin, 
but I'll keep this information in mind if I ever run into this again.

From: Cygwin  On Behalf Of Andrey 
Repin via Cygwin
Sent: Friday, August 9, 2024 3:07 AM
To: David Karr ; cygwin@cygwin.com
Cc: Andrey Repin 
Subject: Re: How to repair the symlinks in a copied cygwin64 tree

Greetings, David Karr! > At my work, I had to have my laptop reimagined for 
various reasons. I had > them save my cygwin64 tree to external storage first. 
I now have the laptop > back, and I copied the entire tree back in, but now I


Greetings, David Karr!



> At my work, I had to have my laptop reimagined for various reasons. I had

> them save my cygwin64 tree to external storage first. I now have the laptop

> back, and I copied the entire tree back in, but now I realize I should have

> done this differently, and I'm wondering how best to repair this. Some of

> you can probably guess, but now all of the files that were symlinks in

> Cygwin are now very small data files. I can tell they used to be symlinks

> because when I cat one, it shows "!" in the first characters.



These symlinks usually point to Cygwin directory tree and should be fine.

Just chmod +S them.



> What is the best strategy for repairing this? The most simple-minded

> approach that I can see is simply renaming the cygwin64 tree to get it out

> of the way, and then just reinstalling Cygwin, and then copying in all the

> files in my cygwin home directory in the saved tree. I will likely guess

> wrong on what packages I had installed before. Is there some way I can

> simply repair the symylink files directly?



Easiest I've encountered is to



0. Have a backup of your existing installation, for reference.

1. Install Cygwin anew.

2. Pull /etc/setup/installed.db from backup into a temporary directory.

3. Get a list of manually installed packages from backup

# sed -Ee '/ 1$/s/^([^[:space:]]+) [^[:space:]]+?(\.tar[^[:space:]]+ 1)$/\1 
\1-0\2/; t; d;' < $backup/installed.db

Warning note: There will be failures, not all package versions adhere to

the same pattern.

4. Append the list to the end of current /etc/setup/installed.db

5. Run setup to pull the package "updates".



> Besides the symlink problem, is there anything else that I might have

> broken by doing it this way?



None that I know.



> I'm guessing the correct way to have done this would have been instead

> storing the "tar czpf" output in external storage. I think that would have

> preserved the symlinks and restored them properly with "tar xzf".



It would have a chance of destroying permissions, I prefer reinstall, with

backup of /etc/ and /usr/local directories (that's where I keep custom stuff).

Since I don't use Cygwin's /home, it's easy for me.





--

With best regards,

Andrey Repin

Friday, August 9, 2024 12:54:41



Sorry for my terrible english...





--

Problem reports:  
https://urldefense.com/v3/__https://cygwin.com/problems.html__;!!BhdT!l3czdFqFecACnqETjVB_eY1UOMJ68HWpEmeoxXgc7mmyw-6v3UKg3kJVgyw8LPyf5ojJm6KYz_lgLg$

FAQ:  
https://urldefense.com/v3/__https://cygwin.com/faq/__;!!BhdT!l3czdFqFecACnqETjVB_eY1UOMJ68HWpEmeoxXgc7mmyw-6v3UKg3kJVgyw8LPyf5ojJm6KwJ5XCyA$

Documentation:
https://urldefense.com/v3/__https://cygwin.com/docs.html__;!!BhdT!l3czdFqFecACnqETjVB_eY1UOMJ68HWpEmeoxXgc7mmyw-6v3UKg3kJVgyw8LPyf5ojJm6KverV-Yg$

Unsubscribe info: 
https://urldefense.com/v3/__https://cygwin.com/ml/*unsubscribe-simple__;Iw!!BhdT!l3czdFqFecACnqETjVB_eY1UOMJ68HWpEmeoxXgc7mmyw-6v3UKg3kJVgyw8LPyf5ojJm6KEsFjOFQ$

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: Problems with X11 after reinstalling Windows

[KARR, DAVID via Cygwin]

I’ve managed to resolve this particular problem, I was missing some packages.

From: Cygwin  On Behalf Of Fergus 
Daly via Cygwin
Sent: Thursday, August 8, 2024 10:07 PM
To: 'cygwin@cygwin.com' 
Cc: Fergus Daly 
Subject: Re: Problems with X11 after reinstalling Windows

It sounds to me that you are missing components in your current configuration 
that were present in your previous working setup. Maybe try adding the xinit 
package (from the X11 category) to what you've already got. -- Problem reports: 
https: //urldefense. com/v3/__https: //cygwin. com/problems. 
html__;!!BhdT!jCDzsQkHa34wOIhxOp_hhFqd99PAZNmjuvPwOHsHa9dUuyNirIQQO4R6WIw8YuuNr8HEspIdRgNzwg$


It sounds to me that you are missing components in your current configuration 
that were present in your previous working setup.

Maybe try adding the xinit package (from the X11 category) to what you've 
already got.



--

Problem reports:  
https://urldefense.com/v3/__https://cygwin.com/problems.html__;!!BhdT!jCDzsQkHa34wOIhxOp_hhFqd99PAZNmjuvPwOHsHa9dUuyNirIQQO4R6WIw8YuuNr8HEspIdRgNzwg$

FAQ:  
https://urldefense.com/v3/__https://cygwin.com/faq/__;!!BhdT!jCDzsQkHa34wOIhxOp_hhFqd99PAZNmjuvPwOHsHa9dUuyNirIQQO4R6WIw8YuuNr8HEspIt1v4VQA$

Documentation:
https://urldefense.com/v3/__https://cygwin.com/docs.html__;!!BhdT!jCDzsQkHa34wOIhxOp_hhFqd99PAZNmjuvPwOHsHa9dUuyNirIQQO4R6WIw8YuuNr8HEspLea-Askg$

Unsubscribe info: 
https://urldefense.com/v3/__https://cygwin.com/ml/*unsubscribe-simple__;Iw!!BhdT!jCDzsQkHa34wOIhxOp_hhFqd99PAZNmjuvPwOHsHa9dUuyNirIQQO4R6WIw8YuuNr8HEspLu3Fn1oA$

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

After reinstalling Cygwin Emacs can only create a single shell buffer

[KARR, DAVID via Cygwin]

I've been using Cygwin and Cygwin Emacs for a long time on Windows 11.  I have 
to reinstall it every couple of years.  I just reinstalled Cygwin yesterday, 
and after having to remember a bunch of things, I finally got my Emacs window 
again.  However, the main thing I use it for is giving me a new problem.  I 
have a wrapper function that creates a new buffer and runs "(shell)".  This has 
literally worked fine for decades.  Today, it worked fine for the first shell.  
The package allows me to manage multiple shell buffers. When I tried to create 
the second shell buffer, it said this:

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

If I just kill this buffer at this point, I can safely interact with the first 
shell buffer.  However, if I execute any command, it seems to execute it in an 
infinite loop, and if I then kill the buffer, the Emacs process is completely 
hung, and I have to kill the entire process. 

This is using Emacs v29.4.

I've already reported this to the help-gnu-emacs list, and they said I should 
ask here instead.

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: Problems with X11 after reinstalling Windows

[KARR, DAVID via Cygwin]

I tried rebooting, but it didn't change anything. "emacs-X11" still says that 
the display is not available, and "startxwin" doesn't exist.

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

RE: New cygwin install hanging on postinstall

[KARR, DAVID]

> -Original Message-
> From: Andrey Repin [mailto:anrdae...@yandex.ru]
> Sent: Thursday, January 21, 2016 11:35 PM
> To: KARR, DAVID; cygwin@cygwin.com
> Subject: Re: New cygwin install hanging on postinstall
> 
> Greetings, KARR, DAVID!
> 
> >> > I was installing cygwin for the first time on a Win7-32bit
> box.
> 
> > It has 4g RAM.  Checking "Resource Monitor" while the install is
> running, there is 750MB "available".
> 
> How much memory is "available" is not an indication for a 32-bit
> OS. You
> simply can not allocate more than 2GB of RAM to a single process
> without much
> hackery. Which means, certain applications could hit a roadblock
> just because
> of that. Same applies to your 4GB statement: You just can not use
> it all with
> 32-bit OS without much hackery on OS level, and that means slowing
> down entire
> system.
> 
> You are really, really want 64-bit OS with more than 2GB RAM to see
> any light
> at the end of the tunnel.
> 
> On top of that, if you are still struggling with installation, and
> hints
> offered in other messages did not helped to date, the most simple
> way would be
> to eliminate the failed Cygwin install and start anew, this time
> only install
> a base (setup default) set of tools first time, may be accompanying
> them by
> choice things of convenience, like wget and/or procps. But nothing
> overgrown
> like TexLive.

Ok.  I understand the basic procedure for uninstalling Cygwin, but what's the 
best way to reset the installer to the "base" install?


--
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: New cygwin install hanging on postinstall

[KARR, DAVID]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Achim Gratz
> Sent: Thursday, January 21, 2016 12:10 PM
> To: cygwin@cygwin.com
> Subject: Re: New cygwin install hanging on postinstall
> 
> KARR, DAVID writes:
> > While it's sitting here, I dumped out "/var/log/setup.log.full".
> Here is the end of the file:
> > 
> > The following DLLs couldn't be rebased because they were in use:
> >   /usr/bin/cygssp-0.dll
> >   /usr/bin/cygperl5_22.dll
> >   /usr/bin/cyggcc_s-1.dll
> >   /usr/bin/cygcrypt-0.dll
> >   /usr/lib/perl5/vendor_perl/5.22/i686-cygwin-threads-
> 64int/auto/List/Util/Util.
> > dll
> >   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/IO/IO.dll
> >   /usr/lib/perl5/5.22/i686-cygwin-threads-
> 64int/auto/File/Glob/Glob.dll
> >   /usr/lib/perl5/5.22/i686-cygwin-threads-
> 64int/auto/Fcntl/Fcntl.dll
> >   /usr/lib/perl5/5.22/i686-cygwin-threads-
> 64int/auto/Encode/Encode.dll
> >   /usr/lib/perl5/5.22/i686-cygwin-threads-
> 64int/auto/Digest/MD5/MD5.dll
> >   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Cwd/Cwd.dll
> > 2016/01/21 09:15:40 running: C:\cygwin\bin\dash.exe
> "/etc/postinstall/0p_texlive
> > _prep.dash"
> > 2016/01/21 09:19:20 note: Nothing needed to be installed
> > 2016/01/21 09:19:20 Ending cygwin install
> > ---
> 
> So this isn't a fresh install and in fact there is not only some
> Cygwin
> process running but a full blown Perl that has loaded a number of
> modules.  How'd you manage to do that before Cygwin was ready
> installing?  Are you perhaps reporting from a follow-on invocation
> of
> setup.exe after the first install already failed?

Beats the heck out of me.  I didn't have Cygwin installed.  I ran the 
installer.  It hung at this point.  I eventually cancelled it, because it 
obviously wasn't going to complete.  This output is from one of the later 
retries.  I never attempted to run anything installed in cygwin, I'm just 
trying to complete the installation.

> For your current case, you need to get rid of _all_ running Cygwin
> processes.  Best idea is to open a shell and issue
> 
>   /usr/bin/rebase-trigger fullrebase
>   /usr/bin/pkill .
> 
> (you need to have procps installed for this command to be
> available).
> Then run setup again to have it re-do the rebase and run all
> postinstall
> scripts that failed before.  But I'm still interested how that
> initial
> failure could have occured, so if you could maybe look in
> /var/log/setup.log if something indicates what happened there that
> would
> be good.

More weirdness.  I ran a mintty window, and I ran those command lines, but it 
gives me lots of lines like this:
-
2 [main] bash 28452 child_info_fork::abort: C:\cygwin\bin\cygiconv-2.dll: 
Loaded to different address: parent(0x4D) != child(0x2E)
bash: fork: retry: No child processes
-

I don't believe either of these command lines did anything, but just to be 
sure, after I ran them I killed the window an reran setup, and got the same 
symptoms.


--
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: New cygwin install hanging on postinstall

[KARR, DAVID]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Stephen John Smoogen
> Sent: Wednesday, January 20, 2016 4:19 PM
> To: cygwin@cygwin.com
> Subject: Re: New cygwin install hanging on postinstall
> 
> On 20 January 2016 at 17:06, KARR, DAVID  wrote:
> > I was installing cygwin for the first time on a Win7-32bit box.
> It is hanging in postinstall, with "0/Perpetual" and
> "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now,
> and it hangs effectively forever on this step (waited 15-20 minutes
> each time).  What other information could I provide?  I looked at
> the end of the setup.log file, but that just indicates that
> installation was complete.
> >
> 
> How much memory does this system have? I know that TexLive is a
> real
> memory hog these days in certain parts.. Does removing TexLive from
> your install list go past this?

It has 4g RAM.  Checking "Resource Monitor" while the install is running, there 
is 750MB "available".

I tried searching for "texlive" and setting all of those to "uninstall".  The 
"postintall" step spends quite a while on "0p_000_autorebase.dash", but I 
noticed that before.  However, after that finishes, it then sits on 
"0p_texlive_prep.dash".

While it's sitting here, I dumped out "/var/log/setup.log.full".  Here is the 
end of the file:

The following DLLs couldn't be rebased because they were in use:
  /usr/bin/cygssp-0.dll
  /usr/bin/cygperl5_22.dll
  /usr/bin/cyggcc_s-1.dll
  /usr/bin/cygcrypt-0.dll
  /usr/lib/perl5/vendor_perl/5.22/i686-cygwin-threads-64int/auto/List/Util/Util.
dll
  /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/IO/IO.dll
  /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/File/Glob/Glob.dll
  /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Fcntl/Fcntl.dll
  /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Encode/Encode.dll
  /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Digest/MD5/MD5.dll
  /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Cwd/Cwd.dll
2016/01/21 09:15:40 running: C:\cygwin\bin\dash.exe "/etc/postinstall/0p_texlive
_prep.dash"
2016/01/21 09:19:20 note: Nothing needed to be installed
2016/01/21 09:19:20 Ending cygwin install
---

Note that the current time is currently 9:37AM.  The log file hasn't updated in 
almost 20 minutes.

I would run the script manually, but I don't know what to run.

I tried to exclude c:\cygwin from the virus scanner, but it seems doubtful that 
the installer would go through all the other steps if this was really an issue.

New cygwin install hanging on postinstall

[KARR, DAVID]

I was installing cygwin for the first time on a Win7-32bit box.  It is hanging 
in postinstall, with "0/Perpetual" and "/etc/postinstall/0p_texlive_prep.dash.  
I've tried this twice now, and it hangs effectively forever on this step 
(waited 15-20 minutes each time).  What other information could I provide?  I 
looked at the end of the setup.log file, but that just indicates that 
installation was complete.

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> On 5/7/2014 7:42 PM, KARR, DAVID wrote:
> >> -Original Message-----
> >> Of KARR, DAVID
> >> Sent: Monday, May 05, 2014 2:34 PM
> >>
> >>> -Original Message-
> >>> Of KARR, DAVID
> >>> Sent: Sunday, April 13, 2014 10:53 AM
> >>>
> >>> I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so,
> I
> >>> get a "fatal error" dialog from emacs-w32.  It asks me if I want to
> >> debug
> >>> it, but I'm not sure what info I could pull from gdb that would be
> >> useful.
> >>>
> >>> Is this a known problem?
> >>>
> >>> Is there any useful information I could provide?
> >>
> >> I installed the test 24.3.90.1 version, and it hasn't crashed once
> (yet).
> >
> > Since I reported this, I've seen it crash several times now, but it
> doesn't give the usual "Debug?" dialog, it just goes away.  It's died
> several times today.  I'll start running it from gdb to get a stacktrace.
> 
> As before, it would be good to know if it crashes when started with the
> -Q option.

Just so I'm clear, if I use "-Q" that doesn't load anything, so I can't really 
do much with that.  I can run it, and I can tell you if it ever fails, but it 
seems unlikely it ever will, because I can't really do anything with it.

So far, I haven't seen the Q instance fail, when my regular instance has failed 
several times.

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of KARR, DAVID
> Sent: Monday, May 05, 2014 2:34 PM
> 
> > -Original Message-
> > Of KARR, DAVID
> > Sent: Sunday, April 13, 2014 10:53 AM
> >
> > I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so, I
> > get a "fatal error" dialog from emacs-w32.  It asks me if I want to
> debug
> > it, but I'm not sure what info I could pull from gdb that would be
> useful.
> >
> > Is this a known problem?
> >
> > Is there any useful information I could provide?
> 
> I installed the test 24.3.90.1 version, and it hasn't crashed once (yet).

Since I reported this, I've seen it crash several times now, but it doesn't 
give the usual "Debug?" dialog, it just goes away.  It's died several times 
today.  I'll start running it from gdb to get a stacktrace.


--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of KARR, DAVID
> Sent: Sunday, April 13, 2014 10:53 AM
> Subject: Fatal error from Cygwin emacs-w32 every day or so
> 
> I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so, I
> get a "fatal error" dialog from emacs-w32.  It asks me if I want to debug
> it, but I'm not sure what info I could pull from gdb that would be useful.
> 
> Is this a known problem?
> 
> Is there any useful information I could provide?

I installed the test 24.3.90.1 version, and it hasn't crashed once (yet).

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Christopher Faylor
> Sent: Wednesday, April 23, 2014 11:42 AM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On Wed, Apr 23, 2014 at 05:56:16PM +, KARR, DAVID wrote:
> >(I really do dislike the spam filter on this list.  Failing because of
> >"cygwin" at "cygwin.com" in the body is really annoying.)
> 
> If you were replying to email rather than forwarding it you wouldn't
> have an issue.  We don't need to see the Date:, Sent:, From:, or
> -Original Message-.  It is pointless verbiage which make
> your responses harder to read.

I don't understand.  I never "forward" to reply here, I always use "Reply".

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Wednesday, April 23, 2014 8:46 AM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/23/2014 10:03 AM, KARR, DAVID wrote:
> >> -Original Message-
> >> Of KARR, DAVID
> >> Sent: Monday, April 21, 2014 7:21 PM
> >> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> >>
> >> *** Security Advisory: This Message Originated Outside of AT&T ***.
> >> Reference http://cso.att.com/EmailSecurity/IDSP.html for more
> information.
> >>
> >>> -Original Message-
> >>> Of Ken Brown
> >>> Sent: Monday, April 21, 2014 11:34 AM
> >>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>>
> >>> On 4/21/2014 1:25 PM, KARR, DAVID wrote:
> >>>>> -Original Message-
> >>>>> Of Ken Brown
> >>>>> Sent: Monday, April 21, 2014 4:16 AM
> >>>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>>>>
> >>>>> On 4/21/2014 1:14 AM, KARR, DAVID wrote:
> >>>>>>> -Original Message-
> >>>>>>> Of KARR, DAVID
> >>>>>>> Sent: Saturday, April 19, 2014 6:19 PM
> >>>>>>> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> >>>>>>>
> >>>>>>>> -Original Message-
> >>>>>>>> Of Ken Brown
> >>>>>>>> Sent: Saturday, April 19, 2014 4:38 PM
> >>>>>>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>>>>>>>
> >>>>>>>> On 4/15/2014 12:13 PM, Ken Brown wrote:
> >>>>>>>>> On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
> >>>>>>>>>>> Date: Mon, 14 Apr 2014 21:08:15 -0700
> >>>>>>>>>>> From: Ken Brown
> >>>>>>>>>>>
> >>>>>>>>>>>> I just saw it die, and this is the bt I get:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
> >>>>>>>>>>>> 0x000100551354 in wait_reading_process_output (
> >>>>>>>>>>>>  time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
> >>>>>>>>>>>>  read_kbd=read_kbd@entry=-1,
> >>>>> do_display=do_display@entry=true,
> >>>>>>>>>>>>  wait_for_cell=wait_for_cell@entry=4304630834,
> >>>>>>>>>>>>  wait_proc=wait_proc@entry=0x0,
> >>>>>>>>>>>> just_wait_proc=just_wait_proc@entry=0)
> >>>>>>>>>>>> @/usr/src/debug/emacs-24.3-7/src/process.c:4677
> >>>>>>>>>>>> 4677  if (wait_proc->gnutls_p /* Check
> for
> >>>>>>> valid
> >>>>>>>>>>>> process.  */
> >>>>>>>>>>>
> >>>>>>>>>>> This backtrace doesn't make sense.  If you look at the source
> >>> code,
> >>>>>>>>>>> you'll see that if wait_proc is NULL on entry to
> >>>>>>>>>>> wait_reading_process_output, then line 4677 is never reached.
> >>> I'm
> >>>>>>> not
> >>>>>>>>>>> sure what would cause a bogus backtrace like this.  BLODA?
> >>>>>>>>>>> Optimization?
> >>>>>>>>>>>
> >>>>>>>>>>> In any case, I suggest that you wait a week until I have a
> >> chance
> >>>>> to
> >>>>>>>>>>> build a pretest of 24.4 for you to try.  I'll build it without
> >>>>>>>>>>> optimization to make debugging easier.
> >>>>>>>>>>
> >>>>>>>>>> This is a known problem with GnuTLS support, it was solved in
> >> the
> >>>>>>>>>> Emacs repository last November (bzr revision 114956, if someone
> >>>>> wants
> >>>>>>>>>> the diffs), and surely should be solved i

RE: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of KARR, DAVID
> Sent: Monday, April 21, 2014 7:21 PM
> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> 
> *** Security Advisory: This Message Originated Outside of AT&T ***.
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> > -Original Message-
> > Of Ken Brown
> > Sent: Monday, April 21, 2014 11:34 AM
> > Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >
> > On 4/21/2014 1:25 PM, KARR, DAVID wrote:
> > >> -Original Message-
> > >> Of Ken Brown
> > >> Sent: Monday, April 21, 2014 4:16 AM
> > >> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> > >>
> > >> On 4/21/2014 1:14 AM, KARR, DAVID wrote:
> > >>>> -Original Message-
> > >>>> Of KARR, DAVID
> > >>>> Sent: Saturday, April 19, 2014 6:19 PM
> > >>>> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> > >>>>
> > >>>>> -Original Message-
> > >>>>> Of Ken Brown
> > >>>>> Sent: Saturday, April 19, 2014 4:38 PM
> > >>>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> > >>>>>
> > >>>>> On 4/15/2014 12:13 PM, Ken Brown wrote:
> > >>>>>> On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
> > >>>>>>>> Date: Mon, 14 Apr 2014 21:08:15 -0700
> > >>>>>>>> From: Ken Brown
> > >>>>>>>>
> > >>>>>>>>> I just saw it die, and this is the bt I get:
> > >>>>>>>>>
> > >>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
> > >>>>>>>>> 0x000100551354 in wait_reading_process_output (
> > >>>>>>>>> time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
> > >>>>>>>>> read_kbd=read_kbd@entry=-1,
> > >> do_display=do_display@entry=true,
> > >>>>>>>>> wait_for_cell=wait_for_cell@entry=4304630834,
> > >>>>>>>>> wait_proc=wait_proc@entry=0x0,
> > >>>>>>>>> just_wait_proc=just_wait_proc@entry=0)
> > >>>>>>>>>@/usr/src/debug/emacs-24.3-7/src/process.c:4677
> > >>>>>>>>> 4677  if (wait_proc->gnutls_p /* Check for
> > >>>> valid
> > >>>>>>>>> process.  */
> > >>>>>>>>
> > >>>>>>>> This backtrace doesn't make sense.  If you look at the source
> > code,
> > >>>>>>>> you'll see that if wait_proc is NULL on entry to
> > >>>>>>>> wait_reading_process_output, then line 4677 is never reached.
> > I'm
> > >>>> not
> > >>>>>>>> sure what would cause a bogus backtrace like this.  BLODA?
> > >>>>>>>> Optimization?
> > >>>>>>>>
> > >>>>>>>> In any case, I suggest that you wait a week until I have a
> chance
> > >> to
> > >>>>>>>> build a pretest of 24.4 for you to try.  I'll build it without
> > >>>>>>>> optimization to make debugging easier.
> > >>>>>>>
> > >>>>>>> This is a known problem with GnuTLS support, it was solved in
> the
> > >>>>>>> Emacs repository last November (bzr revision 114956, if someone
> > >> wants
> > >>>>>>> the diffs), and surely should be solved in the upcoming Emacs
> > 24.4.
> > >>>>>>
> > >>>>>> Thanks, Eli!  In that case I'll make a new release of emacs-24.3
> > with
> > >>>>>> that patch applied, to see if it resolves the issue for the OP.
> > >>>>>
> > >>>>> I've rebuilt emacs-24.3 with the gnutls fix.  David and Achim (and
> > >>>>> anyone else who's been experiencing these crashes), please try the
> > >>>>> following binary and let me know if it solves the problem:
> > >>>>>
> > >>>>>   http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
> 

RE: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Monday, April 21, 2014 11:34 AM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/21/2014 1:25 PM, KARR, DAVID wrote:
> >> -Original Message-
> >> Of Ken Brown
> >> Sent: Monday, April 21, 2014 4:16 AM
> >> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>
> >> On 4/21/2014 1:14 AM, KARR, DAVID wrote:
> >>>> -Original Message-
> >>>> Of KARR, DAVID
> >>>> Sent: Saturday, April 19, 2014 6:19 PM
> >>>> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> >>>>
> >>>>> -Original Message-
> >>>>> Of Ken Brown
> >>>>> Sent: Saturday, April 19, 2014 4:38 PM
> >>>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>>>>
> >>>>> On 4/15/2014 12:13 PM, Ken Brown wrote:
> >>>>>> On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
> >>>>>>>> Date: Mon, 14 Apr 2014 21:08:15 -0700
> >>>>>>>> From: Ken Brown
> >>>>>>>>
> >>>>>>>>> I just saw it die, and this is the bt I get:
> >>>>>>>>>
> >>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
> >>>>>>>>> 0x000100551354 in wait_reading_process_output (
> >>>>>>>>> time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
> >>>>>>>>> read_kbd=read_kbd@entry=-1,
> >> do_display=do_display@entry=true,
> >>>>>>>>> wait_for_cell=wait_for_cell@entry=4304630834,
> >>>>>>>>> wait_proc=wait_proc@entry=0x0,
> >>>>>>>>> just_wait_proc=just_wait_proc@entry=0)
> >>>>>>>>>@/usr/src/debug/emacs-24.3-7/src/process.c:4677
> >>>>>>>>> 4677  if (wait_proc->gnutls_p /* Check for
> >>>> valid
> >>>>>>>>> process.  */
> >>>>>>>>
> >>>>>>>> This backtrace doesn't make sense.  If you look at the source
> code,
> >>>>>>>> you'll see that if wait_proc is NULL on entry to
> >>>>>>>> wait_reading_process_output, then line 4677 is never reached.
> I'm
> >>>> not
> >>>>>>>> sure what would cause a bogus backtrace like this.  BLODA?
> >>>>>>>> Optimization?
> >>>>>>>>
> >>>>>>>> In any case, I suggest that you wait a week until I have a chance
> >> to
> >>>>>>>> build a pretest of 24.4 for you to try.  I'll build it without
> >>>>>>>> optimization to make debugging easier.
> >>>>>>>
> >>>>>>> This is a known problem with GnuTLS support, it was solved in the
> >>>>>>> Emacs repository last November (bzr revision 114956, if someone
> >> wants
> >>>>>>> the diffs), and surely should be solved in the upcoming Emacs
> 24.4.
> >>>>>>
> >>>>>> Thanks, Eli!  In that case I'll make a new release of emacs-24.3
> with
> >>>>>> that patch applied, to see if it resolves the issue for the OP.
> >>>>>
> >>>>> I've rebuilt emacs-24.3 with the gnutls fix.  David and Achim (and
> >>>>> anyone else who's been experiencing these crashes), please try the
> >>>>> following binary and let me know if it solves the problem:
> >>>>>
> >>>>>   http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
> >>>>>
> >>>>> You might have to do "chmod +x emacs-w32.exe" after uncompressing
> it.
> >>>>>
> >>>>> If it fixes the problem, I'll issue a new release of emacs-24.3.  If
> >>>>> not, I'll build a pretest of emacs-24.4 for you to try.
> >>>>
> >>>> Ok.  It's running.  As it only fails after random intervals, I'll
> have
> >> to
> >>>> keep it running for a while.  I'll give it a day or so.
> >>>
> >>> I came back to my computer and saw two dialogs, one saying that my VPN
> >> connection had died (that happens from time to time), and the other the
> >> Emacs failure dialog.  I started this executable from gdb, but it's
> saying
> >> that it doesn't have symbols, so the stacktrace probably isn't helpful,
> >> but this is what I saw:
> >>
> >> Right.  I just supplied a stripped binary for a quick test.  It's not
> >> suitable for debugging.
> >>
> >>> I've started it again, but not in gdb this time.
> >>
> >> If it crashes again, I'll build a pretest of 24.4 without optimization
> >> and issue it as a test release.
> >
> > It just failed again while sitting here in my office (no relation to
> VPN/network issues).
> 
> Could you try one more thing if you haven't already:  Start emacs with
> the -Q option, in case there's something in your initialization files
> that triggers the problem.

I started both a regular instance and the "-Q" instance around noon today (7 
hours ago).  The regular instance failed once since then, which I restarted.  
The Q instance hasn't failed yet.  That's not a definite, but it's lasted 
longer so far.  Note that I haven't changed my .emacs in a very long time.

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Monday, April 21, 2014 4:16 AM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/21/2014 1:14 AM, KARR, DAVID wrote:
> >> -Original Message-
> >> Of KARR, DAVID
> >> Sent: Saturday, April 19, 2014 6:19 PM
> >> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> >>
> >>> -Original Message-
> >>> Of Ken Brown
> >>> Sent: Saturday, April 19, 2014 4:38 PM
> >>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>>
> >>> On 4/15/2014 12:13 PM, Ken Brown wrote:
> >>>> On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
> >>>>>> Date: Mon, 14 Apr 2014 21:08:15 -0700
> >>>>>> From: Ken Brown
> >>>>>>
> >>>>>>> I just saw it die, and this is the bt I get:
> >>>>>>>
> >>>>>>> Program received signal SIGSEGV, Segmentation fault.
> >>>>>>> 0x000100551354 in wait_reading_process_output (
> >>>>>>>time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
> >>>>>>>read_kbd=read_kbd@entry=-1,
> do_display=do_display@entry=true,
> >>>>>>>wait_for_cell=wait_for_cell@entry=4304630834,
> >>>>>>>wait_proc=wait_proc@entry=0x0,
> >>>>>>> just_wait_proc=just_wait_proc@entry=0)
> >>>>>>>   @/usr/src/debug/emacs-24.3-7/src/process.c:4677
> >>>>>>> 4677  if (wait_proc->gnutls_p /* Check for
> >> valid
> >>>>>>> process.  */
> >>>>>>
> >>>>>> This backtrace doesn't make sense.  If you look at the source code,
> >>>>>> you'll see that if wait_proc is NULL on entry to
> >>>>>> wait_reading_process_output, then line 4677 is never reached.  I'm
> >> not
> >>>>>> sure what would cause a bogus backtrace like this.  BLODA?
> >>>>>> Optimization?
> >>>>>>
> >>>>>> In any case, I suggest that you wait a week until I have a chance
> to
> >>>>>> build a pretest of 24.4 for you to try.  I'll build it without
> >>>>>> optimization to make debugging easier.
> >>>>>
> >>>>> This is a known problem with GnuTLS support, it was solved in the
> >>>>> Emacs repository last November (bzr revision 114956, if someone
> wants
> >>>>> the diffs), and surely should be solved in the upcoming Emacs 24.4.
> >>>>
> >>>> Thanks, Eli!  In that case I'll make a new release of emacs-24.3 with
> >>>> that patch applied, to see if it resolves the issue for the OP.
> >>>
> >>> I've rebuilt emacs-24.3 with the gnutls fix.  David and Achim (and
> >>> anyone else who's been experiencing these crashes), please try the
> >>> following binary and let me know if it solves the problem:
> >>>
> >>>  http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
> >>>
> >>> You might have to do "chmod +x emacs-w32.exe" after uncompressing it.
> >>>
> >>> If it fixes the problem, I'll issue a new release of emacs-24.3.  If
> >>> not, I'll build a pretest of emacs-24.4 for you to try.
> >>
> >> Ok.  It's running.  As it only fails after random intervals, I'll have
> to
> >> keep it running for a while.  I'll give it a day or so.
> >
> > I came back to my computer and saw two dialogs, one saying that my VPN
> connection had died (that happens from time to time), and the other the
> Emacs failure dialog.  I started this executable from gdb, but it's saying
> that it doesn't have symbols, so the stacktrace probably isn't helpful,
> but this is what I saw:
> 
> Right.  I just supplied a stripped binary for a quick test.  It's not
> suitable for debugging.
> 
> > I've started it again, but not in gdb this time.
> 
> If it crashes again, I'll build a pretest of 24.4 without optimization
> and issue it as a test release.

It just failed again while sitting here in my office (no relation to 
VPN/network issues).

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of KARR, DAVID
> Sent: Saturday, April 19, 2014 6:19 PM
> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> 
> > -Original Message-
> > Of Ken Brown
> > Sent: Saturday, April 19, 2014 4:38 PM
> > Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >
> > On 4/15/2014 12:13 PM, Ken Brown wrote:
> > > On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
> > >>> Date: Mon, 14 Apr 2014 21:08:15 -0700
> > >>> From: Ken Brown
> > >>>
> > >>>> I just saw it die, and this is the bt I get:
> > >>>>
> > >>>> Program received signal SIGSEGV, Segmentation fault.
> > >>>> 0x000100551354 in wait_reading_process_output (
> > >>>>   time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
> > >>>>   read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
> > >>>>   wait_for_cell=wait_for_cell@entry=4304630834,
> > >>>>   wait_proc=wait_proc@entry=0x0,
> > >>>> just_wait_proc=just_wait_proc@entry=0)
> > >>>>  @/usr/src/debug/emacs-24.3-7/src/process.c:4677
> > >>>> 4677  if (wait_proc->gnutls_p /* Check for
> valid
> > >>>> process.  */
> > >>>
> > >>> This backtrace doesn't make sense.  If you look at the source code,
> > >>> you'll see that if wait_proc is NULL on entry to
> > >>> wait_reading_process_output, then line 4677 is never reached.  I'm
> not
> > >>> sure what would cause a bogus backtrace like this.  BLODA?
> > >>> Optimization?
> > >>>
> > >>> In any case, I suggest that you wait a week until I have a chance to
> > >>> build a pretest of 24.4 for you to try.  I'll build it without
> > >>> optimization to make debugging easier.
> > >>
> > >> This is a known problem with GnuTLS support, it was solved in the
> > >> Emacs repository last November (bzr revision 114956, if someone wants
> > >> the diffs), and surely should be solved in the upcoming Emacs 24.4.
> > >
> > > Thanks, Eli!  In that case I'll make a new release of emacs-24.3 with
> > > that patch applied, to see if it resolves the issue for the OP.
> >
> > I've rebuilt emacs-24.3 with the gnutls fix.  David and Achim (and
> > anyone else who's been experiencing these crashes), please try the
> > following binary and let me know if it solves the problem:
> >
> > http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
> >
> > You might have to do "chmod +x emacs-w32.exe" after uncompressing it.
> >
> > If it fixes the problem, I'll issue a new release of emacs-24.3.  If
> > not, I'll build a pretest of emacs-24.4 for you to try.
> 
> Ok.  It's running.  As it only fails after random intervals, I'll have to
> keep it running for a while.  I'll give it a day or so.

I came back to my computer and saw two dialogs, one saying that my VPN 
connection had died (that happens from time to time), and the other the Emacs 
failure dialog.  I started this executable from gdb, but it's saying that it 
doesn't have symbols, so the stacktrace probably isn't helpful, but this is 
what I saw:

Program received signal SIGTRAP, Trace/breakpoint trap.
0x07fefd773ca3 in KERNELBASE!DebugBreak ()
   from /c/Windows/system32/KERNELBASE.dll
(gdb)
(gdb) bt
#0  0x07fefd773ca3 in KERNELBASE!DebugBreak ()
   from /c/Windows/system32/KERNELBASE.dll
#1  0x00010056e6cb in ?? ()
#2  0x00429318 in ?? ()
#3  0x00010091ccd8 in ?? ()
#4  0x in ?? ()
(gdb)


I've started it again, but not in gdb this time.

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Saturday, April 19, 2014 4:38 PM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/15/2014 12:13 PM, Ken Brown wrote:
> > On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
> >>> Date: Mon, 14 Apr 2014 21:08:15 -0700
> >>> From: Ken Brown
> >>>
>  I just saw it die, and this is the bt I get:
> 
>  Program received signal SIGSEGV, Segmentation fault.
>  0x000100551354 in wait_reading_process_output (
>    time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
>    read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
>    wait_for_cell=wait_for_cell@entry=4304630834,
>    wait_proc=wait_proc@entry=0x0,
>  just_wait_proc=just_wait_proc@entry=0)
>   @/usr/src/debug/emacs-24.3-7/src/process.c:4677
>  4677  if (wait_proc->gnutls_p /* Check for valid
>  process.  */
> >>>
> >>> This backtrace doesn't make sense.  If you look at the source code,
> >>> you'll see that if wait_proc is NULL on entry to
> >>> wait_reading_process_output, then line 4677 is never reached.  I'm not
> >>> sure what would cause a bogus backtrace like this.  BLODA?
> >>> Optimization?
> >>>
> >>> In any case, I suggest that you wait a week until I have a chance to
> >>> build a pretest of 24.4 for you to try.  I'll build it without
> >>> optimization to make debugging easier.
> >>
> >> This is a known problem with GnuTLS support, it was solved in the
> >> Emacs repository last November (bzr revision 114956, if someone wants
> >> the diffs), and surely should be solved in the upcoming Emacs 24.4.
> >
> > Thanks, Eli!  In that case I'll make a new release of emacs-24.3 with
> > that patch applied, to see if it resolves the issue for the OP.
> 
> I've rebuilt emacs-24.3 with the gnutls fix.  David and Achim (and
> anyone else who's been experiencing these crashes), please try the
> following binary and let me know if it solves the problem:
> 
> http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
> 
> You might have to do "chmod +x emacs-w32.exe" after uncompressing it.
> 
> If it fixes the problem, I'll issue a new release of emacs-24.3.  If
> not, I'll build a pretest of emacs-24.4 for you to try.

Ok.  It's running.  As it only fails after random intervals, I'll have to keep 
it running for a while.  I'll give it a day or so.

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> From: KARR, DAVID
> Sent: Monday, April 14, 2014 11:24 AM
> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
> 
> > -Original Message-
> > Of Ken Brown
> > Sent: Sunday, April 13, 2014 5:43 PM
> > Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >
> > On 4/13/2014 10:53 AM, KARR, DAVID wrote:
> > > I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so,
> I
> > get a "fatal error" dialog from emacs-w32.  It asks me if I want to
> debug
> > it, but I'm not sure what info I could pull from gdb that would be
> useful.
> >
> > A gdb backtrace might or might not be helpful.  I would start with other
> > things first (see below).
> 
> I just saw it die, and this is the bt I get:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x000100551354 in wait_reading_process_output (
> time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
> read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
> wait_for_cell=wait_for_cell@entry=4304630834,
> wait_proc=wait_proc@entry=0x0, just_wait_proc=just_wait_proc@entry=0)
> at /usr/src/debug/emacs-24.3-7/src/process.c:4677
> 4677  if (wait_proc->gnutls_p /* Check for valid
> process.  */
> (gdb)

And to confirm a subsequent question:

(gdb) p wait_proc
$1 = (struct Lisp_Process *) 0x0
(gdb)

> >
> > > Is this a known problem?
> >
> > No.
> >
> > > Is there any useful information I could provide?
> >
> > Since this is a new computer, my first suggestion would be to check the
> > BLODA list (http://cygwin.com/faq/faq.html#faq.using.bloda).  If that
> > doesn't help, please make a more detailed report, following the
> > guidelines here:
> >

--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Sunday, April 13, 2014 5:43 PM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/13/2014 10:53 AM, KARR, DAVID wrote:
> > I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so, I
> get a "fatal error" dialog from emacs-w32.  It asks me if I want to debug
> it, but I'm not sure what info I could pull from gdb that would be useful.
> 
> A gdb backtrace might or might not be helpful.  I would start with other
> things first (see below).

I just saw it die, and this is the bt I get:

Program received signal SIGSEGV, Segmentation fault.
0x000100551354 in wait_reading_process_output (
time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
wait_for_cell=wait_for_cell@entry=4304630834,
wait_proc=wait_proc@entry=0x0, just_wait_proc=just_wait_proc@entry=0)
at /usr/src/debug/emacs-24.3-7/src/process.c:4677
4677  if (wait_proc->gnutls_p /* Check for valid process.  
*/
(gdb)

> 
> > Is this a known problem?
> 
> No.
> 
> > Is there any useful information I could provide?
> 
> Since this is a new computer, my first suggestion would be to check the
> BLODA list (http://cygwin.com/faq/faq.html#faq.using.bloda).  If that
> doesn't help, please make a more detailed report, following the
> guidelines here:
> 
> > Problem reports:   http://cygwin.com/problems.html
> 
> Ken
> 
> 
> 
> --
> 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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Monday, April 14, 2014 9:39 AM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/14/2014 9:28 AM, KARR, DAVID wrote:
> >> -Original Message-
> >> Of Ken Brown
> >> Sent: Monday, April 14, 2014 9:19 AM
> >> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>
> >> On 4/13/2014 6:46 PM, KARR, DAVID wrote:
> >>>> -Original Message-
> >>>> Of Ken Brown
> >>>> Sent: Sunday, April 13, 2014 5:43 PM
> >>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>>>
> >>>> On 4/13/2014 10:53 AM, KARR, DAVID wrote:
> >>>>> I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or
> so,
> >> I
> >>>> get a "fatal error" dialog from emacs-w32.  It asks me if I want to
> >> debug
> >>>> it, but I'm not sure what info I could pull from gdb that would be
> >> useful.
> >>>>
> >>>> A gdb backtrace might or might not be helpful.  I would start with
> >> other
> >>>> things first (see below).
> >>>>
> >>>>> Is this a known problem?
> >>>>
> >>>> No.
> >>>>
> >>>>> Is there any useful information I could provide?
> >>>>
> >>>> Since this is a new computer, my first suggestion would be to check
> the
> >>>> BLODA list (http://cygwin.com/faq/faq.html#faq.using.bloda).  If that
> >>>> doesn't help, please make a more detailed report, following the
> >>>> guidelines here:
> >>>>
> >>>>> Problem reports:   http://cygwin.com/problems.html
> >>>
> >>> (Sigh.  It died again while I was writing this note.)
> >>>
> >>> Ok.  I have McAfee on this box.  Note that we've had McAfee installed
> on
> >> all laptops here for quite a while, including my older Win32 box, which
> I
> >> didn't see this problem on.
> >>
> >> Are you sure there's nothing else?  Windows Defender maybe?
> >
> > I looked through the BLODA list, and I believe that McAfee is the only
> one that I have installed.
> 
> Windows Defender comes with Windows 7; have you disabled it?

I just checked, and it's turned off.


--
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: Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

> -Original Message-
> Of Ken Brown
> Sent: Monday, April 14, 2014 9:19 AM
> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> 
> On 4/13/2014 6:46 PM, KARR, DAVID wrote:
> >> -Original Message-
> >> Of Ken Brown
> >> Sent: Sunday, April 13, 2014 5:43 PM
> >> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
> >>
> >> On 4/13/2014 10:53 AM, KARR, DAVID wrote:
> >>> I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so,
> I
> >> get a "fatal error" dialog from emacs-w32.  It asks me if I want to
> debug
> >> it, but I'm not sure what info I could pull from gdb that would be
> useful.
> >>
> >> A gdb backtrace might or might not be helpful.  I would start with
> other
> >> things first (see below).
> >>
> >>> Is this a known problem?
> >>
> >> No.
> >>
> >>> Is there any useful information I could provide?
> >>
> >> Since this is a new computer, my first suggestion would be to check the
> >> BLODA list (http://cygwin.com/faq/faq.html#faq.using.bloda).  If that
> >> doesn't help, please make a more detailed report, following the
> >> guidelines here:
> >>
> >>> Problem reports:   http://cygwin.com/problems.html
> >
> > (Sigh.  It died again while I was writing this note.)
> >
> > Ok.  I have McAfee on this box.  Note that we've had McAfee installed on
> all laptops here for quite a while, including my older Win32 box, which I
> didn't see this problem on.
> 
> Are you sure there's nothing else?  Windows Defender maybe?

I looked through the BLODA list, and I believe that McAfee is the only one that 
I have installed.

> > I'm attaching the cygcheck.out file. I only elided my laptop hostname.
> 
> Nothing jumps out at me in the cygcheck output.
> 
> > I followed the instructions for creating a backtrace (running "gdb -p
> " before clicking YES, and then "continue", and then "bt").
> However, it just said "No stack.".
> 
> You might have to run emacs under gdb and put a breakpoint at
> emacs_abort in order to get a useful backtrace.  But I'm not sure it's

Ok, I'll see if I can do that.

> worth putting a lot of effort into debugging emacs-24.3 at this point,
> because emacs-24.4 is already in its pretest phase.  I'm traveling right
> now, but when I return in about a week I'll build the current pretest
> version for you to try.

Ok.

> One other question: Can you find a way to reproduce the problem, or does
> it just seem to happen randomly?

In fact, I've never seen it fail while I'm doing something in the Emacs window, 
it's always when I'm off doing something else.
 

--
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

Fatal error from Cygwin emacs-w32 every day or so

[KARR, DAVID]

I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so, I get a 
"fatal error" dialog from emacs-w32.  It asks me if I want to debug it, but I'm 
not sure what info I could pull from gdb that would be useful.

Is this a known problem?

Is there any useful information I could provide?

--
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: symlinks to scripts not found in path

[KARR, DAVID]

> -Original Message-
> Vinschen
> Sent: Thursday, April 10, 2014 9:00 AM
> Subject: Re: symlinks to scripts not found in path
> 
> On Apr 10 15:51, KARR, DAVID wrote:
> > On my old 32-bit Win7 box running Cygwin 1.7.26, I have an executable 
> > script that is
> intended to be symlinked to and executed as the symlink name.  This works 
> fine.
> >
> > On my new 64-bit Win7 box running Cygwin 1.7.29, I created the symlink 
> > using "ln -s" as
> before.  When I try to execute the script through the symlink, it fails to 
> find it in the
> path.  The script itself has the rx bits set.  I can execute the script 
> directly, although
> it doesn't do anything useful.
> >
> > I didn't see anything obvious in the FAQ or obvious searches.
> 
> Works fine for me:
> 
>   $  uname -rsm
>   CYGWIN_NT-6.3 1.7.29(0.272/5/3) x86_64
>   $ mkdir a b
>   $ cd a
>   cat > x.sh <   #!/bin/bash
>   echo Hello World
>   EOF
>   $ chmod +x x.sh
>   $ cd ../b
>   $ ln -s ../a/x.sh hello
>   $ ./hello
>   Hello World
> 
> Did you miss the #! by any chance?

Never mind, I had created the symbolic link with a relative path instead of 
absolute.  Once I recreated it correctly, it worked fine.

Thanks.

symlinks to scripts not found in path

[KARR, DAVID]

On my old 32-bit Win7 box running Cygwin 1.7.26, I have an executable script 
that is intended to be symlinked to and executed as the symlink name.  This 
works fine.

On my new 64-bit Win7 box running Cygwin 1.7.29, I created the symlink using 
"ln -s" as before.  When I try to execute the script through the symlink, it 
fails to find it in the path.  The script itself has the rx bits set.  I can 
execute the script directly, although it doesn't do anything useful.

I didn't see anything obvious in the FAQ or obvious searches.


--
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: "mount -c /" in 64-bit win7 not persisting

[KARR, DAVID]

> -Original Message-
> Corinna Vinschen
> Sent: Wednesday, April 09, 2014 11:45 AM
> Subject: Re: "mount -c /" in 64-bit win7 not persisting
> 
> On Apr  9 17:43, KARR, DAVID wrote:
> > I haven't installed a new Cygwin in quite a while.  I'm doing it this
> morning on a new 64-bit Win7 box.
> >
> > I typically set my cygdrive prefix to "/".  In the past, I believe I would
> do this once, and it wouldn't have to do it again, as it would persist
> somewhere.
> >
> > Now, it appears as if this goes away as soon as that shell goes away.
> >
> > I've checked some of the FAQs and did some searches, but I didn't find
> anything obvious.
> >
> > What am I missing?
> 
> The user's guide:
> 
>   http://cygwin.com/cygwin-ug-net/using.html#mount-table
> 
> Persisent mounting via mount(1) has been given up in favor of the
> /etc/fstab file a long time ago (2009).

Curious.  I didn't think it was THAT long ago that I last installed Cygwin.  
That works, in any case.  Thanks.

"mount -c /" in 64-bit win7 not persisting

[KARR, DAVID]

I haven't installed a new Cygwin in quite a while.  I'm doing it this morning 
on a new 64-bit Win7 box.

I typically set my cygdrive prefix to "/".  In the past, I believe I would do 
this once, and it wouldn't have to do it again, as it would persist somewhere.

Now, it appears as if this goes away as soon as that shell goes away.

I've checked some of the FAQs and did some searches, but I didn't find anything 
obvious.

What am I missing?

--
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: mintty shell gets frequent "8~" strings inserted into input

[KARR, DAVID]

> -Original Message-
> Larry Hall (Cygwin)
> Sent: Friday, January 24, 2014 12:14 PM
> Subject: Re: mintty shell gets frequent "8~" strings inserted into input
> 
> On 1/24/2014 2:57 PM, KARR, DAVID wrote:
> >> -Original Message-
> >> Larry Hall (Cygwin)
> >> Sent: Friday, January 24, 2014 11:35 AM
> >> Subject: Re: mintty shell gets frequent "8~" strings inserted into input
> >>
> >> On 1/24/2014 2:00 PM, KARR, DAVID wrote:
> >>> I'm on Cygwin 1.7.26 on Win7.
> >>>
> >>> I run mintty with "C:\Cygwin\bin\mintty.exe -e /bin/bash --login".
> >>>
> >>> Every minute or so, or randomly, my mintty shell prompt gets the string
> >>> "8~" inserted. If I leave the shell there, it will end up with a string
> of
> >>> them. What might be causing this?
> >>
> >> Check the archives.  I think there was a similar report that finally
> >> resolved itself as an overly zealous virus checker or something similar.
> >
> > Any idea what to search for?  I've already searched the internet and the
> > cygwin archives several months back with obvious search strings.
> 
> This is what I was thinking of:
> 
> <http://cygwin.com/ml/cygwin/2013-10/msg00069.html>

I don't know where the subject of virus scanners comes in here. I simply added 
the suggested line to ~/.inputrc and it seemed to resolve the problem.  I'm not 
quite certain what it did, but I do know it fixed my current problem.


--
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: mintty shell gets frequent "8~" strings inserted into input

[KARR, DAVID]

> -Original Message-
> Larry Hall (Cygwin)
> Sent: Friday, January 24, 2014 11:35 AM
> Subject: Re: mintty shell gets frequent "8~" strings inserted into input
> 
> On 1/24/2014 2:00 PM, KARR, DAVID wrote:
> > I'm on Cygwin 1.7.26 on Win7.
> >
> > I run mintty with "C:\Cygwin\bin\mintty.exe -e /bin/bash --login".
> >
> > Every minute or so, or randomly, my mintty shell prompt gets the string
> > "8~" inserted. If I leave the shell there, it will end up with a string of
> > them. What might be causing this?
> 
> Check the archives.  I think there was a similar report that finally
> resolved itself as an overly zealous virus checker or something similar.

Any idea what to search for?  I've already searched the internet and the cygwin 
archives several months back with obvious search strings.


--
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

mintty shell gets frequent "8~" strings inserted into input

[KARR, DAVID]

I'm on Cygwin 1.7.26 on Win7.

I run mintty with "C:\Cygwin\bin\mintty.exe -e /bin/bash --login".

Every minute or so, or randomly, my mintty shell prompt gets the string "8~" 
inserted.  If I leave the shell there, it will end up with a string of them.  
What might be causing this?

--
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: Cygwin Emacs and two other Cygwin processes seem to do a lot of "other" I/O while seemingly idle

[KARR, DAVID]

> -Original Message-
> Sent: Friday, October 18, 2013 11:20 AM
> Subject: Cygwin Emacs and two other Cygwin processes seem to do a lot of
> "other" I/O while seemingly idle
> 
> Win7x32, Cygwin 1.7.25, Emacs 24.3.1.
> 
> I've noticed when I scan the processes in SysInternals Process Explorer and
> sort by "I/O Delta Other Bytes", my Cygwin Emacs process is almost always at
> the top of the list.  In fact, the next processes in that sorted order are
> "at-spi-bus-launcher" and "at-spi2-registryd", both also from Cygwin.  The
> total from everything else in the list, again for the "I/O Delta Other Bytes"
> value, is just a fraction of the total from these three processes.
> 
> This is happening when Emacs is seemingly idle.
> 
> I'm not sure what "Other" is, compared to read or write.  At the current
> time, when I see it at the top of that sorted list, I don't see the disk
> light flashing a lot, and my cpu indicator is pretty low.  Also at the
> current time, I have four shell buffers open, all of which are just sitting
> at the shell prompt (these are all that show up in "list-processes").
> 
> However, I'm constantly annoyed with performance problems on my laptop, so
> I'm wondering whether this is having any impact.
> 
> This may be considered "trivial" or expected behavior, I'd just like to
> understand it a bit.

I'm continuing to see this problem.  I find that when my system is very 
sluggish, if I check total IO, those three processes are at the top of the 
list, and this is when I'm not doing anything directly with Cygwin.  At this 
point, if I kill my Emacs, rxvt, and X server, my performance improves 
considerably.


--
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: Emacs doesn't start from icon after update to 1.7.25 [attn: Chuck]

[KARR, DAVID]

> -Original Message-
> Sent: Wednesday, September 25, 2013 12:25 PM
> To: The Cygwin Mailing List
> Subject: Re: Emacs doesn't start from icon after update to 1.7.25 [attn:
> Chuck]
> 
> On 9/25/2013 2:36 PM, KARR, DAVID wrote:
> >> Looks fine.  I'm out of ideas.  Maybe Chuck (the run and run2
> >> maintainer) can help you if you want to pursue this.
> >
> > Anyone else (Chuck?) have any ideas on this?  As I can't open Emacs
> > from the shortcut anymore, my current workaround is opening an rxvt
> > window and running emacs from there.
> >
> > If it matters, I tried taking my shortcut's command line and altering
> > it like this:
> >
> > c:\cygwin\bin\strace.exe -f C:\Cygwin\bin\run.exe -p /usr/bin bash -l
> > -i -c "emacs -display 127.0.0.1:0.0 --debug-init" > strace.log
> >
> > I'm attaching that strace.log file.  I looked at it, and I didn't see
> > anything obvious.  I still chuckle over the reference to
> > "/home/corinna", but I'm pretty sure that has nothing to do with
> > this.
> 
> I saw this, but haven't had time to investigate. It's at the top of the
> list, right after finishing the port/respin of inetutils-1.9 for 32bit
> and 64bit cygwin.

Just checking for status.  Is this still pending investigation?

--
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: Emacs doesn't start from icon after update to 1.7.25 [attn: Chuck]

[KARR, DAVID]

> -Original Message-
> Sent: Wednesday, September 25, 2013 12:25 PM
> Subject: Re: Emacs doesn't start from icon after update to 1.7.25 [attn:
> Chuck]
> 
> On 9/25/2013 2:36 PM, KARR, DAVID wrote:
> >> Looks fine.  I'm out of ideas.  Maybe Chuck (the run and run2
> >> maintainer) can help you if you want to pursue this.
> >
> > Anyone else (Chuck?) have any ideas on this?  As I can't open Emacs
> > from the shortcut anymore, my current workaround is opening an rxvt
> > window and running emacs from there.
> >
> > If it matters, I tried taking my shortcut's command line and altering
> > it like this:
> >
> > c:\cygwin\bin\strace.exe -f C:\Cygwin\bin\run.exe -p /usr/bin bash -l
> > -i -c "emacs -display 127.0.0.1:0.0 --debug-init" > strace.log
> >
> > I'm attaching that strace.log file.  I looked at it, and I didn't see
> > anything obvious.  I still chuckle over the reference to
> > "/home/corinna", but I'm pretty sure that has nothing to do with
> > this.
> 
> I saw this, but haven't had time to investigate. It's at the top of the
> list, right after finishing the port/respin of inetutils-1.9 for 32bit
> and 64bit cygwin.

By the way, if it matters, I realized this is also happening on my other 
laptop, which is also Win7x32, and similar hardware.

--
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: Confused about several issues with setting up cron

[KARR, DAVID]

> -Original Message-
> From: KARR, DAVID
> Sent: Sunday, September 22, 2013 2:32 PM
> Subject: RE: Confused about several issues with setting up cron
> 
> > -Original Message-
> > Sent: Sunday, September 22, 2013 12:46 PM
> > Subject: Re: Confused about several issues with setting up cron
> >
> > On 09/22/2013 05:56 PM, bartels wrote:
> > > On 09/22/2013 03:00 AM, KARR, DAVID wrote:
> > >> CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin
> > >>
> > >> I want to set up a cron job, so I have to get cron configured. I'm
> trying
> > to follow the instructions I can find, but I'm seeing several issues.
> > >>
> > >> I'm surprised that there's nothing in the user guide or the FAQ about
> > setting up cron.  I had to settle for the various questions about this
> > >> on StackOverflow and others.
> > >
> >  >>> I want to set up a cron job, so I have to get cron configured.  I'm
> > trying
> >  >> to follow the instructions I can find, but I'm seeing several issues.
> >  >>> I'm surprised that there's nothing in the user guide or the FAQ about
> >  >> setting up cron.  I had to settle for the various questions about this
> on
> >  >> StackOverflow and others.
> >  >>
> >  >> Must say your reporting of events is also lacking crucial elements
> >  >> If you re-install and give me more details, then I will try and answer
> > your
> >  >> questions.
> >  > Ok.  I assume you mean re-installing cron, not Cygwin.
> > Yes, cron-config is what I meant.
> >  >
> >  > I followed the process described in the FAQ for removing a service.  I
> > then ran cron-config again.  When I did this before, I selected to run
> > cron as myself.  I decided to make it run as the local system account this
> > time (first running "passwd -R" and entering my password).  It
> > appeared to complete without errors or warnings.  I did this in a "run as
> > administrator" window.
> >  >
> >  > In a normal window, I then ran "crontab -e".  I figured this would put
> me
> > into "vi" with an empty buffer.  It just returned to the prompt.
> > You should see a vi session.
> > Do you have vi installed?
> > What is the value of EDITOR?
> 
> Yes, I have vi installed.  EDITOR was blank, but I tried setting it to "vi"
> and repeating the test, with no change.
> 
> > This could indicate a deeper problem, confusing not just cron.
> >
> >  > I then ran "crontab crontab" (the "crontab" file in my current directory
> > is the file with the one job I want to run), and then did "crontab
> > -l".  Nothing.
> >
> > Are you familiar with the crontab format? If not, try this:
> > $ man 5 crontab
> 
> Yes, I am familiar with it, but here's the crontab I'm trying to set, in any
> case:
> 
> 0 * * * * monitorDataSource
> 
> >  >
> >  > I then went back to the administrator window.  I ran "cronevents".  This
> > didn't show anything more than the cron service being started.  I
> > then ran "cronbug".  I'm attaching the gzipped copy of this.
> >  >
> > You will have more luck running cron 'as yourself': it is straightforward.
> > Running it as a privileged user is more complicated.
> >
> > Is there a specific reason why you want to run it as system?
> 
> No, only because running it as myself didn't work.
> 
> In any case, I tried stopping and removing the service and rerunning cron-
> config, running the service as myself.  It didn't make any difference.  No
> response from "crontab -e", and "crontab crontab" seemingly ignored.  Nothing
> in "/var/log/cron.log", and nothing in "cronevents" except for the service
> stopping and starting.

Any more ideas about this?

--
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

Confused about several issues with setting up cron

[KARR, DAVID]

CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin

I want to set up a cron job, so I have to get cron configured.  I'm trying to 
follow the instructions I can find, but I'm seeing several issues.

I'm surprised that there's nothing in the user guide or the FAQ about setting 
up cron.  I had to settle for the various questions about this on StackOverflow 
and others.

I must have done something at least half correct, because I believe this tells 
me that cron is running:

% cygrunsrv -L
cron

% cronevents
2013/09/20 21:14:06 [dk068x] crontab: PID 5924: (dk068x) LIST (dk068x)
2013/09/21 11:28:15 [dk068x] /usr/sbin/cron: PID 4980: (CRON) STARTUP (V5.0)
2013/09/21 11:28:16 [dk068x] cron: PID 8424: `cron' service started

However, I then do "crontab ", where "pathtomycrontabfile" 
is the path to my crontab file with the job I want to run.  I then do "crontab 
-l" and it prints nothing.  There is nothing in "/var/log/cron*".

I did get some errors when I ran "cron-config", but I unfortunately lost that 
output.


--
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: Emacs doesn't start from icon after update to 1.7.25

[KARR, DAVID]

> -Original Message-
> Sent: Friday, September 20, 2013 7:00 PM
> Subject: Re: Emacs doesn't start from icon after update to 1.7.25
> 
> On 9/20/2013 7:26 PM, KARR, DAVID wrote:
> > Today I updated 1.7.25.  I was a handful of minor releases behind at the
> time.
> >
> > After the update, I can't start Emacs from the icon anymore.  The shortcut
> command I have for it is the following:
> >
> >  C:\Cygwin\bin\run.exe -p /usr/bin bash -l -i -c "emacs -display
> 127.0.0.1:0.0 --debug-init"
> 
> I don't think this has anything to do with emacs.  There have been
> several reports of problems with run-1.3.0-1.  Try downgrading to the
> previous version of run, or switch to run2.

I first tried just changing the command line to "run2".  No change.  I then 
downgraded "run" to the previous version and changed it back to "run".  It now 
works as before.  Are there any diagnostics that would be useful to anyone?


--
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

Emacs doesn't start from icon after update to 1.7.25

[KARR, DAVID]

Today I updated 1.7.25.  I was a handful of minor releases behind at the time.

After the update, I can't start Emacs from the icon anymore.  The shortcut 
command I have for it is the following:

C:\Cygwin\bin\run.exe -p /usr/bin bash -l -i -c "emacs -display 
127.0.0.1:0.0 --debug-init"

When I run this, I see a window flash and disappear very quickly, and that's 
all I see.  I can't find any meaningful log information.

If I instead open up rxvt and execute "emacs", it starts up fine.

I did check the FAQ before writing this, but I didn't see anything obvious.

--
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

Were the Perl multithreading problems ever fixed?

[KARR, DAVID]

Last year I had reported some problems with a Perl script that utilizes 
multithreading.  I believe it was Reini Urban who told me that there were known 
problems with Perl multithreading and that an ETA for a set of fixes was not 
known yet.  Does anyone know if those particular Perl multithreading issues 
have been dealt with in later Cygwin releases?  I'm still on 1.7.17.

--
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: Backspace in shell doesn't backspace after Cygwin update

[KARR, DAVID]

> -Original Message-
> Behalf Of KARR, DAVID
> Sent: Thursday, January 03, 2013 2:03 PM
> Subject: Backspace in shell doesn't backspace after Cygwin update
> 
> My hard drive on my Win7 laptop crashed last week, and I'm now trying to
> get everything I had reinstalled.  After I reinstalled Cygwin (now at 1.7.17),
> I'm seeing some problems starting up Cygwin tools. I don't see anything
> specifically about this in the FAQ.
> 
> I normally run "C:\Cygwin\bin\rxvt.exe -display :0 -fn "Lucida Console-14" -tn
> rxvt-cygwin-native -e /bin/bash --login" from a shortcut for a shell outside 
> of
> Emacs.  When I do this now, it looks ok, but I'm now finding that the
> Backspace key just moves the cursor forward one character, not deleting the
> previous character.
> 
> I have another shortcut for "C:\Cygwin\bin\run.exe /usr/bin/rxvt.exe -
> display 127.0.0.1:0 -tn rxvt-cygwin -e /bin/bash --login".  This behaves the
> same as the previous with respect to Backspace. "mintty" does the same.
> 
> The Emacs shell is fine.
> 
> My CYGWIN variable is just set to "nodosfilewarning".
> 
> Pressing Ctl-v followed by backspace gets "^H".
> 
> This is the output of "stty":
> speed 38400 baud; line = 0;
> erase = ^H; swtch = ;
> 
> I compared my ~/.inputrc with /etc/defaults/etc/skel/.inputrc and there
> were only differences in comments.
> 
> What other information would be relevant?

I resolved this.  I took the advice I found on the internet, which was to 
reinstall terminfo.


--
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

Backspace in shell doesn't backspace after Cygwin update

[KARR, DAVID]

My hard drive on my Win7 laptop crashed last week, and I'm now trying to get 
everything I had reinstalled.  After I reinstalled Cygwin (now at 1.7.17), I'm 
seeing some problems starting up Cygwin tools. I don't see anything 
specifically about this in the FAQ.

I normally run "C:\Cygwin\bin\rxvt.exe -display :0 -fn "Lucida Console-14" -tn 
rxvt-cygwin-native -e /bin/bash --login" from a shortcut for a shell outside of 
Emacs.  When I do this now, it looks ok, but I'm now finding that the Backspace 
key just moves the cursor forward one character, not deleting the previous 
character.

I have another shortcut for "C:\Cygwin\bin\run.exe /usr/bin/rxvt.exe -display 
127.0.0.1:0 -tn rxvt-cygwin -e /bin/bash --login".  This behaves the same as 
the previous with respect to Backspace. "mintty" does the same.

The Emacs shell is fine.

My CYGWIN variable is just set to "nodosfilewarning".

Pressing Ctl-v followed by backspace gets "^H".

This is the output of "stty":
speed 38400 baud; line = 0;
erase = ^H; swtch = ;

I compared my ~/.inputrc with /etc/defaults/etc/skel/.inputrc and there were 
only differences in comments.

What other information would be relevant?

--
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

Installing cygwin on new box, getting "cygwin1.dll is missing"

[KARR, DAVID]

Today I started trying to install Cygwin on a new Win7 box.  It took a long 
time to get to the end, which included many "Can't open (null) for reading: No 
such file" dialogs along the way.  When it finally got close to finishing, I 
got a dialog which just says:

"The program can't start because cygwin1.dll is missing from your computer."

I've searched for occurrences of this particular symptom, but I didn't see 
anything useful.

What's curious is that when I try to dismiss the dialog, it just redisplays.  
Fortunately, it's not a modal dialog, so it lets me click "Cancel" on the setup 
dialog.  Also curiously, that doesn't even cause the "The program ..." dialog 
to go away.  Clicking OK at that point makes it go away.

I've tried this several times, with the same result. 

--
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: starting excel from crontab

[KARR, DAVID (ATTSI)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of cygwin.20.maillingl...@spamgourmet.com
> Sent: Wednesday, July 21, 2010 2:14 AM
> To: "cygwin@cygwin.com"
> Subject: starting excel from crontab
> 
> Hi folks,
> 
> I have the problem that I like to start Excel at the end of the workday
> from crontab.
> 
> Cron is running under a local system account.
> 
> The problem is that excel is started but does not popup. When I change
> the check box "Exchange Data with Desktop" I got always the error "***
> fatal error - could not load user32, Win32 error 1114" for all
> cronjobs.
> 
> How can I fix the problem.

You know, you ARE running on MS Windows.  It does actually provide some 
features that are occasionally useful.

If you want to run a Windows application on a schedule, just use "Start"->"All 
Programs"->"Accessories"->"System Tools"->"Scheduled Tasks".  I don't know that 
it's scheduling capabilities are quite as full as cron, but it likely will do 
what you need.

RE: Currently on 1.5.25, possible to update setup.exe to get python?

[KARR, DAVID (ATTSI)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Christopher Faylor
> Sent: Monday, February 08, 2010 10:51 AM
> To: cygwin@cygwin.com
> Subject: Re: Currently on 1.5.25, possible to update setup.exe to get
> python?
> 
> On Mon, Feb 08, 2010 at 10:26:39AM -0800, KARR, DAVID (ATTSI) wrote:
> >I'm currently on v1.5.25, but I don't want to upgrade yet.  I just
> need
> >to install Python, which I believe is one of the packages.  I tried
> >running my old setup.exe that I used with 1.5.25, but it's now
> >complaining about syntax errors in "setup.bz2".  It looks like I'll
> need
> >to at least upgrade my setup.exe, but I need to know beforehand if
> doing
> >that will force me to upgrade anything else.  If I download the
latest
> >setup.exe, will I be able to install the Python package that works
> with
> >1.5.25 without having to install anything else?
> 
> Go to http://cygwin.com/ and follow the links to the legacy version of
> Cygwin.  The web site mentions "Windows 95, Windows 98, or Windows Me"
> but the link really just brings you to a version of setup (setup-
> legacy)
> which will update/install 1.5.x versions of the packages.  These
> packages
> are, of course, no longer updated and offered as-is.

Thanks.  That worked fine.

--
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

Currently on 1.5.25, possible to update setup.exe to get python?

[KARR, DAVID (ATTSI)]

I'm currently on v1.5.25, but I don't want to upgrade yet.  I just need
to install Python, which I believe is one of the packages.  I tried
running my old setup.exe that I used with 1.5.25, but it's now
complaining about syntax errors in "setup.bz2".  It looks like I'll need
to at least upgrade my setup.exe, but I need to know beforehand if doing
that will force me to upgrade anything else.  If I download the latest
setup.exe, will I be able to install the Python package that works with
1.5.25 without having to install anything else?

--
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: Help getting emacsclient working from Eclipse

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of KARR, DAVID (ATTCINW)
> 
> I could use some help getting through a quoting problem.
> 
> I'm using Cygwin 1.5.25, Emacs 23.0.92.1, and Eclipse 3.5.1.
> 
> There's a "PathTools" plugin for Eclipse that lets me specify a
command
> line to open a file in an external editor, or open a shell in the
> directory the file is in.  I have no trouble with the latter, but the
> former gives me trouble when I try to use emacsclient to load the file
> in my running Emacs.  I was able to get it to work with Textpad, but
> I'd
> prefer to get emacsclient/emacs working.

Well, in any case, I've managed to get this working, although it
required both a BAT script and a Bash script.  Weird.

With "emacsclientbat.bat":
--
@echo off
c:\cygwin\bin\bash -l -c "emacsclienttocyg "%1""
--

And "emacsclienttocyg":
--
#! /bin/bash
path="$@"
emacsclient -n -a textpad "$(cygpath -u "$path")"
-

And the resulting command line:

c:\cygwin\home\\bin\emacsclientbat.bat "{path-slashes}"

--
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

Help getting emacsclient working from Eclipse

[KARR, DAVID (ATTCINW)]

I could use some help getting through a quoting problem.

I'm using Cygwin 1.5.25, Emacs 23.0.92.1, and Eclipse 3.5.1.

There's a "PathTools" plugin for Eclipse that lets me specify a command
line to open a file in an external editor, or open a shell in the
directory the file is in.  I have no trouble with the latter, but the
former gives me trouble when I try to use emacsclient to load the file
in my running Emacs.  I was able to get it to work with Textpad, but I'd
prefer to get emacsclient/emacs working.

As I got Textpad to work with this, it's clear that the wrinkle with
emacsclient is related to Cygwin, or perhaps emacsclient.  I've tried
numerous variations of the command line, but I still haven't found a way
to communicate the entire full path (which has spaces in it) to
emacsclient.

For instance, the command line which loads it into Textpad is just the
following ("{path-slashes}" is a marker for PathTools to substitute the
file path with forward slashes):

  cmd /C start textpad "{path-slashes}"

When I try to get this to work with emacsclient, nothing I have tried
ends up getting the full path to the file to emacsclient.  My current
command line is this:

  c:\cygwin\bin/bash -l -c "c:/cygwin/home//bin/emacsclienttocyg
"{path-slashes}""

where "emacsclienttocyg" is this:

#! /bin/bash
set -x
path="$@"
emacsclient -n -a textpad "$(cygpath -u "$path")"

When I run this command line in Eclipse, I see the following in the
Eclipse console:

-
c:\cygwin\bin/bash -l -c "c:/cygwin/home//bin/emacsclienttocyg
"C:/Documents and Settings//""
+ path=C:/Documents
++ cygpath -u C:/Documents
+ emacsclient -n -a textpad /c/Documents
-

As you can see, only the first word of the path gets set into the "path"
variable.  I've tried numerous variations of quoting in the command
line, all of which fail for different reasons.

I'd appreciate any ideas.

--
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: How to run bash in rxvt with both login shell and in a specific directory?

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> 
> On Wed, Sep 9, 2009 at 1:31 PM, Gary Johnson wrote:
> >    C:\cygwin\bin\rxvt.exe -e /bin/bash --login -c "cd /usr/local/src;
> exec bash -i"
> 
> A good solution, but it won't work if you do anything in .bash_profile
> that's not inherited by child shell processes (aliases, shell
> functions, etc), since .bash_profile won't be executed by the bash -i.
> 
> Of course, it's not good practice to do such things in .bash_profile;
> better to put them in .bashrc (and have .bash_profile source .bashrc
> so they happen in login shells, too)... but something to watch out
> for.

Hmm.  This (Gary's solution) didn't work.  Instead of leaving me in my Cygwin 
home or the target directory, it left me in my Windows home.  I don't know why.

I tried implementing Mark's solution, and that worked fine.  I don't have to 
look at it, so I won't complain. :)

How to run bash in rxvt with both login shell and in a specific directory?

[KARR, DAVID (ATTCINW)]

I'd like to have a command line that will run bash inside rxvt, both as
a login shell (so I get all my paths and profile) and in a specific
directory.  I know how to get it to a specific directory, and I know how
to make it a login shell, but I can't figure out how to get both.

If I use this:

C:\cygwin\bin\rxvt.exe -ls -cd "path" -e /usr/bin/bash -l

I get a login shell, but at my home dir, not at the specified path.

If I remove the last "-l", it goes to the correct directory, but it
didn't appear to load my profile (PATH isn't correct, for instance).

--
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: How to resolve 'Your group is currently "mkpasswd"' message

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of KARR, DAVID (ATTCINW)
> Sent: Tuesday, July 21, 2009 12:46 PM
> To: cygwin@cygwin.com
> Subject: How to resolve 'Your group is currently "mkpasswd"' message
> 
> After installing Cygwin 1.5.25 and bringing up RXVT, I got a message
> I've seen in the past, saying 'Your group is currently "mkpasswd"
...'.
> It advises me to run "mkpasswd" and "mkgroup" to fill in records in
> /etc/group and /etc/passwd.
> 
> If I run "mkpasswd -l" it completes quickly, but doesn't include my
> record.  I run "mkpasswd -d", which seems to be implied as the correct
> thing to do, but it doesn't run very quickly.  In fact, I've never
> waited long enough for it to complete.  I work for a very large
> company,
> if that's going to try to list all the login records in the entire
> company.
> 
> I tried doing "mkpasswd -l > /etc/passwd" and then "mkpasswd -d -u
>  >> /etc/passwd".  That appeared to take care of the
> /etc/passwd file for just my login (the only one I care about), but
I'm
> not sure of a similar approach for "mkgroup".  I tried using "mkgroup
-
> d
> -g ", but I'm not sure what group name to use.

Never mind.  The strategy of using "-ldu" on mkpasswd along with "-ld"
on mkgroup is useful.  We have 8 zillion users, but a much smaller
number of groups.  The "mkgroup -ld" completed in just a few minutes.

--
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

How to resolve 'Your group is currently "mkpasswd"' message

[KARR, DAVID (ATTCINW)]

After installing Cygwin 1.5.25 and bringing up RXVT, I got a message
I've seen in the past, saying 'Your group is currently "mkpasswd" ...'.
It advises me to run "mkpasswd" and "mkgroup" to fill in records in
/etc/group and /etc/passwd.

If I run "mkpasswd -l" it completes quickly, but doesn't include my
record.  I run "mkpasswd -d", which seems to be implied as the correct
thing to do, but it doesn't run very quickly.  In fact, I've never
waited long enough for it to complete.  I work for a very large company,
if that's going to try to list all the login records in the entire
company.

I tried doing "mkpasswd -l > /etc/passwd" and then "mkpasswd -d -u
 >> /etc/passwd".  That appeared to take care of the
/etc/passwd file for just my login (the only one I care about), but I'm
not sure of a similar approach for "mkgroup".  I tried using "mkgroup -d
-g ", but I'm not sure what group name to use.

--
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: Best way to create Windows .ico file for Emacs?

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Ken Brown
> Sent: Thursday, July 02, 2009 12:37 PM
> To: cygwin@cygwin.com
> Subject: Re: Best way to create Windows .ico file for Emacs?
> 
> On 7/2/2009 1:20 PM, KARR, DAVID (ATTCINW) wrote:
> > I'm sure this is a FAQ, but I've spent several minutes searching
> > resources for the proper way to do this, but I just can't find it.
> >
> > I have Cygwin Emacs 23.0.92 installed, which includes the
> "emacs.icon"
> > file, which I believe is an XPM file.  I need to create a Windows
ICO
> > file.  Searching the net, I find 8 zillion tools for image
> conversion,
> > including many that provide the path that I need (xpm->ico), but
what
> > I'm wondering is if there's a tool already installed (or available)
> with
> > Cygwin that can do this.  I looked through the ImageMagick man page
> and
> > didn't see it, which was the only obvious thing I knew to look at.
> 
> The emacs source contains several windows .ico files in the directory
> nt/icons.  You can either download the source and locate them or you
> can
> find them in the CVS repository:
> 
>http://cvs.savannah.gnu.org/viewvc/emacs/nt/icons/?root=emacs

Got it.  That's what I needed.  Thanks.

--
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: Best way to create Windows .ico file for Emacs?

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Yaakov (Cygwin/X)
> Sent: Thursday, July 02, 2009 10:41 AM
> To: cygwin@cygwin.com
> Subject: Re: Best way to create Windows .ico file for Emacs?
> 
> On 02/07/2009 12:20, KARR, DAVID (ATTCINW) wrote:
> > I'm sure this is a FAQ, but I've spent several minutes searching
> > resources for the proper way to do this, but I just can't find it.
> >
> > I have Cygwin Emacs 23.0.92 installed, which includes the
> "emacs.icon"
> > file, which I believe is an XPM file.  I need to create a Windows
ICO
> > file.  Searching the net, I find 8 zillion tools for image
> conversion,
> > including many that provide the path that I need (xpm->ico), but
what
> > I'm wondering is if there's a tool already installed (or available)
> with
> > Cygwin that can do this.  I looked through the ImageMagick man page
> and
> > didn't see it, which was the only obvious thing I knew to look at.
> 
> convert xpm:emacs.icon ico:emacs.ico

Hmm, it says "convert: Improper image header `emacs.icon'.
convert: missing an image filename `ico:emacs.ico'."

Perhaps this isn't actually an XPM file?  The header looks like this:

/* Format_version=1, Width=64, Height=64, Depth=1,
Valid_bits_per_item=16
 */
0x,0x,0x,0x,0x8000,0x,0x,0x0001,
0x8000,0x,0x007E,0x1C01,0x8000,0x,0x0006,0x1C01,

--
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

Best way to create Windows .ico file for Emacs?

[KARR, DAVID (ATTCINW)]

I'm sure this is a FAQ, but I've spent several minutes searching
resources for the proper way to do this, but I just can't find it.

I have Cygwin Emacs 23.0.92 installed, which includes the "emacs.icon"
file, which I believe is an XPM file.  I need to create a Windows ICO
file.  Searching the net, I find 8 zillion tools for image conversion,
including many that provide the path that I need (xpm->ico), but what
I'm wondering is if there's a tool already installed (or available) with
Cygwin that can do this.  I looked through the ImageMagick man page and
didn't see it, which was the only obvious thing I knew to look at.

--
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: Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Ken Brown
> Sent: Wednesday, July 01, 2009 4:58 PM
> To: cygwin@cygwin.com
> Subject: Re: Stuck trying to reinstall Emacs 23.0.92 and setup dying
> each time
> 
> On 7/1/2009 6:37 PM, KARR, DAVID (ATTCINW) wrote:
> > Ok, so that shows that emacs-el.lst.gz was corrupted.  I deleted it,
> > then reran setup. I clicked "Exp", then "View", then scrolled down
to
> > the three "emacs*" lines and set them all to "Reinstall" (the
> "Current"
> > column says "23.0.92-2") and clicked "Next".  It chugged for a bit,
> last
> > displaying "Uninstalling emacs-el", then reported "setup.exe has
> > encountered ...".  After dismissing the dialog, I looked at
> /etc/setup
> > again, and the corrupted "emacs-el.lst.gz" was there again.  I also
> > checked to see whether any other "*.lst.gz" files were corrupted,
and
> > there were none.
> 
> One other thought:  You don't actually need emacs-el.  This just
> provides source files for the emacs libraries, and you can always get
> them from the emacs source if you find you need them later.  Can you
> reinstall emacs and emacs-X11 and just "keep" emacs-el?

HA!  That did it.  Quite weird.  It sounds to me like there's something
about "emacs-el" that is corrupted at the source, rather than some
problem in setup.exe.

--
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: Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Mark Harig
> Sent: Wednesday, July 01, 2009 4:43 PM
> To: cygwin@cygwin.com
> Subject: RE: Stuck trying to reinstall Emacs 23.0.92 and setup dying
> each time
> 
> Wed, 1 Jul 2009 15:37:09 -0700 David Karr wrote:
> > Ok, so that shows that emacs-el.lst.gz was corrupted.  I deleted it,
> > then reran setup. I clicked "Exp", then "View", then scrolled down to
> > the three "emacs*" lines and set them all to "Reinstall" (the
> "Current"
> > column says "23.0.92-2") and clicked "Next".  It chugged for a bit,
> last
> > displaying "Uninstalling emacs-el", then reported "setup.exe has
> > encountered ...".  After dismissing the dialog, I looked at
> /etc/setup
> > again, and the corrupted "emacs-el.lst.gz" was there again.  I also
> > checked to see whether any other "*.lst.gz" files were corrupted, and
> > there were none.
> >
> 
> This message might be of some help to you:
> 
> http://sourceware.org/ml/cygwin/2008-06/msg00563.html
> 
> In particular, you could try downloading:
> 
> http://rapidshare.com/files/98717404/setup.exe

If I understand this correctly, this modified version (over a year old now) 
only deals with not leaving the corrupted .gz file when setup fails.  It 
doesn't address the failure of setup.  It seems to me that the corrupted .gz 
file is just a symptom of another problem that may or not be addressed by this 
modified setup.exe.

I guess I'll try it anyway, as I'm sure not getting anywhere yet.

RE: Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Ken Brown
> Sent: Wednesday, July 01, 2009 3:23 PM
> Cc: cygwin@cygwin.com
> Subject: Re: Stuck trying to reinstall Emacs 23.0.92 and setup dying
> each time
> 
> On 7/1/2009 5:31 PM, KARR, DAVID (ATTCINW) wrote:
> >> -Original Message-
> >> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> >> Behalf Of Ken Brown
> >> Sent: Wednesday, July 01, 2009 1:42 PM
> >> To: cygwin@cygwin.com
> >> Subject: Re: Stuck trying to reinstall Emacs 23.0.92 and setup
dying
> >> each time
> >>
> >> On 7/1/2009 12:20 PM, KARR, DAVID (ATTCINW) wrote:
> >>> I had set up Cygwin yesterday with the experimental Emacs 23.0.92.
> > I
> >>> had done other updates after that, forgetting the fact that since
> > I'm
> >>> using an experimental package, I have to set the Emacs-related
> pages
> >> to
> >>> "Keep".  I'm now in a state where I have the 23.0.92 executable,
> but
> >>> with /usr/share/emacs/21.2.  So, now I'm trying to run setup again
> > to
> >>> reinstall 23.0.92, or uninstall it, or anything.  No matter what I
> >> do,
> >>> setup dies hard, requiring a forced kill from task manager.
> >>>
> >>> What can I do to clean up from this situation?
> >> Does http://sourceware.org/ml/cygwin/2008-04/msg00065.html help?
> The
> >> bug discussed there was supposed to have been fixed
> >> (http://sourceware.org/ml/cygwin/2008-08/msg00128.html), but it
> >> wouldn't
> >> hurt to see if that's the problem.
> >
> > Hmm, well it's a little hard to tell.  It's clear it's not exactly
> the
> > same thing, because my copy of "/etc/setup/cygrunsrv.lst.gz" isn't
> > corrupted, it simply doesn't exist.
> 
> cygrunsrv happened to be the package that the poster of that message
> was
> having trouble with.  You should look at /etc/setup/emacs*.lst.gz.

Ok, so that shows that emacs-el.lst.gz was corrupted.  I deleted it,
then reran setup. I clicked "Exp", then "View", then scrolled down to
the three "emacs*" lines and set them all to "Reinstall" (the "Current"
column says "23.0.92-2") and clicked "Next".  It chugged for a bit, last
displaying "Uninstalling emacs-el", then reported "setup.exe has
encountered ...".  After dismissing the dialog, I looked at /etc/setup
again, and the corrupted "emacs-el.lst.gz" was there again.  I also
checked to see whether any other "*.lst.gz" files were corrupted, and
there were none.

--
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: Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Ken Brown
> Sent: Wednesday, July 01, 2009 1:42 PM
> To: cygwin@cygwin.com
> Subject: Re: Stuck trying to reinstall Emacs 23.0.92 and setup dying
> each time
> 
> On 7/1/2009 12:20 PM, KARR, DAVID (ATTCINW) wrote:
> > I had set up Cygwin yesterday with the experimental Emacs 23.0.92.
I
> > had done other updates after that, forgetting the fact that since
I'm
> > using an experimental package, I have to set the Emacs-related pages
> to
> > "Keep".  I'm now in a state where I have the 23.0.92 executable, but
> > with /usr/share/emacs/21.2.  So, now I'm trying to run setup again
to
> > reinstall 23.0.92, or uninstall it, or anything.  No matter what I
> do,
> > setup dies hard, requiring a forced kill from task manager.
> >
> > What can I do to clean up from this situation?
> 
> Does http://sourceware.org/ml/cygwin/2008-04/msg00065.html help?  The
> bug discussed there was supposed to have been fixed
> (http://sourceware.org/ml/cygwin/2008-08/msg00128.html), but it
> wouldn't
> hurt to see if that's the problem.

Hmm, well it's a little hard to tell.  It's clear it's not exactly the
same thing, because my copy of "/etc/setup/cygrunsrv.lst.gz" isn't
corrupted, it simply doesn't exist.  Does that imply anything?

--
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: Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Mark Harig
> Sent: Wednesday, July 01, 2009 10:49 AM
> To: cygwin@cygwin.com
> Subject: Re: Stuck trying to reinstall Emacs 23.0.92 and setup dying
> each time
> 
> KARR, DAVID wrote:
> 
> > I had set up Cygwin yesterday with the experimental Emacs 23.0.92.  I
> > had done other updates after that, forgetting the fact that since I'm
> > using an experimental package, I have to set the Emacs-related pages
> to
> > "Keep".  I'm now in a state where I have the 23.0.92 executable, but
> > with /usr/share/emacs/21.2.  So, now I'm trying to run setup again to
> > reinstall 23.0.92, or uninstall it, or anything.  No matter what I
> do,
> > setup dies hard, requiring a forced kill from task manager.
> >
> > What can I do to clean up from this situation?
> >
> Have you inspected the 'setup.log' and 'setup.log.full' files in
> /var/log/?
> They might provide some clues about where setup is having problems.  If
> those
> files do not make it clear what you need to do, then the experts on
> 'setup'
> might be able to help with the information those files provide.

I don't see anything informative there.  I see it starting to remove emacs 
(when I tried to uninstall it), but no red flags about failures.

> Also, which version of emacs does cygwin think is installed?
> 
>$ cygcheck -c emacs emacs-el


Cygwin Package Information
Package  VersionStatus
emacs23.0.92-2  OK
emacs-el 23.0.92-2  OK


However, "/usr/share/emacs/" only has a "21.2" directory, there is no 
"/usr/sbin/emacs", and when I try to start emacs-x11, it says this:

Warning: arch-dependent data dir (/usr/sbin/emacs/23.0.92/i686-pc-cygwin/) does 
not exist.
Warning: arch-independent data dir (/usr/share/emacs/23.0.92/etc/) does not 
exist.
Warning: Lisp directory `/usr/share/emacs/23.0.92/site-lisp' does not exist.
Warning: Lisp directory `/usr/share/emacs/site-lisp' does not exist.
Warning: Lisp directory `/usr/share/emacs/23.0.92/lisp' does not exist.
Warning: Lisp directory `/usr/share/emacs/23.0.92/leim' does not exist.
Error: charsets directory (/usr/share/emacs/23.0.92/etc/charsets) does not 
exist.
Emacs will not function correctly without the character map files.
Please check your installation!
Cannot open load file: warnings
> 
> 
> --
> 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: Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Jim Reisert AD1C
> Sent: Wednesday, July 01, 2009 10:15 AM
> To: cygwin@cygwin.com
> Subject: Re: Stuck trying to reinstall Emacs 23.0.92 and setup dying
> each time
> 
> As far as 1.7 is concerned, Emacs 23.0.92 is *not* an experimental
> release.  Uncheck the experimental box, then install the software.

Sorry, I should have made that clear.  I'm still on 1.5.  I'm not ready to make 
the jump to 1.7 yet.

> On Wed, Jul 1, 2009 at 10:20 AM, KARR, DAVID (ATTCINW)
> wrote:
> 
> > I had set up Cygwin yesterday with the experimental Emacs 23.0.92.  I
> > had done other updates after that, forgetting the fact that since I'm
> > using an experimental package, I have to set the Emacs-related pages
> to
> > "Keep".  I'm now in a state where I have the 23.0.92 executable, but
> > with /usr/share/emacs/21.2.  So, now I'm trying to run setup again to
> > reinstall 23.0.92, or uninstall it, or anything.  No matter what I
> do,
> > setup dies hard, requiring a forced kill from task manager.
> >
> > What can I do to clean up from this situation?
> 
> --
> Jim Reisert AD1C, , http://www.ad1c.us
> 
> --
> 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

Stuck trying to reinstall Emacs 23.0.92 and setup dying each time

[KARR, DAVID (ATTCINW)]

I had set up Cygwin yesterday with the experimental Emacs 23.0.92.  I
had done other updates after that, forgetting the fact that since I'm
using an experimental package, I have to set the Emacs-related pages to
"Keep".  I'm now in a state where I have the 23.0.92 executable, but
with /usr/share/emacs/21.2.  So, now I'm trying to run setup again to
reinstall 23.0.92, or uninstall it, or anything.  No matter what I do,
setup dies hard, requiring a forced kill from task manager.

What can I do to clean up from this situation?

--
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: programming API to determine whether in "Cygwin environment"

[Karr, David]

The "ant" shell script checks to see if "`uname`" contains the string
"CYGWIN". 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Tony Last
> Sent: Thursday, July 10, 2008 8:49 PM
> To: cygwin@cygwin.com
> Subject: programming API to determine whether in "Cygwin environment"
> 
> 
> My console program is built for native Windows (thus does not 
> reply on cygwin1.dll). However, people may want to use it in 
> a Cygwin environment and if they do I want it to behave in a 
> suitably "Unixy" way. The obvious example is that when it 
> prints out a pathname (which happens a lot) a Cygwin user 
> would prefer to see it in Cygwin style, including forward slashes.
> 
> So I'm looking for a boolean method which will allow a 
> program to tell whether it was run from within a Cygwin 
> shell. An environment variable would be fine as long as it's 
> standard. In fact I see a number of env vars which would 
> enable an educated guess but am wondering if there's a 
> defined standard and safe way.
> 
> TIA
> --
> View this message in context: 
> http://www.nabble.com/programming-API-to-determine-whether-in-
%22Cygwin-environment%22-tp18395872p18395872.html
> Sent from the Cygwin list mailing list archive at Nabble.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/
> 
> 

--
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: Emacs ignores signals

[Karr, David]

I'm guessing you weren't using the Cygwin-built xemacs.  I use Xemacs
built for Cygwin, and I haven't been able to send signals to
subprocesses for a long time.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Goei
> Sent: Saturday, April 14, 2007 9:47 AM
> To: cygwin@cygwin.com
> Subject: Emacs ignores signals
> 
> I just switched from xemacs to gnu emacs 21.3.50.1 on cygwin
> 1.5.24(0.156/4/2) with an X server (the latest versions I can 
> find). I have shell-mode working, except that signals sent to 
> the subprocess are ignored. For example, if I want to cancel 
> or stop a process, I should be able to type C-c C-c or C-c 
> C-z to interrupt or stop it. The "Signals" menu items are 
> also ignored. Any ideas? This works fine in xemacs.
> 
> -Edwin
> 
> --
> 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/
> 
> 

--
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: xargs gives grep/gawk too much

[Karr, David]

If the point of this note is to get your pipeline to work, would it help
if you added something like "-n 30" to the xargs command?  This should
execute one instance of 'grep -l -e "error '1234567890'"' for every 30
lines of output from the previous pipe entry.

$ echo path/* | \
tr ' ' '\n' | \
grep -v -e '\*' | \
xargs -r grep -l -e "error '1234567890'" | \
rest_of_pipe 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Buchbinder, 
> Barry (NIH/NIAID) [E]
> Sent: Friday, December 08, 2006 10:05 AM
> To: cygwin@cygwin.com
> Subject: xargs gives grep/gawk too much
> 
> I get the following error message:
>   xargs: grep: Argument list too long
> I've also gotten an equivalent error from xargs/gawk.
> 
> Of course, the whole idea of xargs is to avoid this error.  
> If I'm doing something wrong, I'd appreciate some hints of 
> what I am doing wrong or how to avoid this (other than "-s"). 
>  Otherwise, I suppose that this is a bug report.
> 
> The grep pipe, run under bash, that generates the error message is as
> follows:
> 
>   $ echo path/* | \
>   tr ' ' '\n' | \
>   grep -v -e '\*' | \
>   xargs -r grep -l -e "error '1234567890'" | \
>   rest_of_pipe
> 
> Asking xargs to report on its limits:
> 
>   $ echo path/* | \
>   tr ' ' '\n' | \
>   xargs --show-limits grep -e I_do_not_want_output
>   Your environment variables take up 2174 bytes
>   POSIX lower and upper limits on argument length: 2048, 1046528
>   Maximum length of command we could actually use: 1044354
>   Size of command buffer we are actually using: 34942
> 
> Everything should be up to date.  cygcheck.out is attached.  
> Let me know if you want any other information.
> 

--
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/

Any way to get cpu usage % of a process in Cygwin/windows on the command line?

[Karr, David]

Is there any way to get the CPU usage percentage of a process in Cygwin
or Windows, in a script?  The "ps" command in Cygwin is based on SYSV
ps, which doesn't appear to show the CPU usage (whereas BSD ps does).
Task Manager shows what I need, but I don't know how to get that in a
script.  The Sysinternals "pslist" command comes close, but it only
shows the total CPU time, not the relative percentage.

--
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: Re: After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash

[Karr, David]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of René Berber
> 
> Karr, David wrote:
> [snip]
> >>And the command you are running is?
> > 
> > 
> > C:\cygwin\usr\local\bin\i686-pc-cygwin\xemacs-21.4.13.exe
> 
> This is not the xemacs distributed by Cygwin... or is it?

This is the Xemacs built for Cygwin, but not distributed through cygwin.

> Continuing with the guess work, did you move the old xemacs 
> to /usr/local?

No, I didn't manually move anything.

> Have you checked if the old xemacs depends on libraries you 
> don't currently have? (i.e. cygcheck 
> /usr/local/bin/i686-pc-cygwin/xemacs-21.4.13)

I verified that all the dlls listed in this output exist (just piped it to 
"xargs ls").

Remember that the only change I made was upgrading Cygwin from 1.5.18 to 
1.5.19.  I didn't intentionally remove any libraries.

--
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: Re: After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash

[Karr, David]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of René Berber
> 
> Karr, David wrote:
> 
> > I have a desktop icon for running Xemacs 21.4.13.  This has been 
> > working fine.  Just today, I upgraded Cygwin from 1.5.18 to 
> 1.5.19.  
> > Now when I double-click the icon, it does nothing.  I then tried 
> > pasting the path to it into a DOS cmd prompt, and it still does 
> > nothing.  I then executed it directly from a bash prompt, and that 
> > worked.
> 
> And the command you are running is?

C:\cygwin\usr\local\bin\i686-pc-cygwin\xemacs-21.4.13.exe

> > I have a similar icon for 21.4.18, and that doesn't demonstrate the 
> > same problem, although 21.4.18 always runs a cmd window in the 
> > background, which 21.4.13 does not.
> 
> I think what affected your installation is a change of 
> version of Xemacs not the Cygwin dll.
> 
> This works for me with no problem:
> 
>   C:\cygwin\bin\run.exe xemacs

I did not upgrade Xemacs.  Executing the icon (which uses the path given 
above), or pasting that path into a cmd window, does nothing.  It just returns 
to the prompt and the window doesn't appear.  The upgrade of Cygwin did not 
affect the execution of 21.4.18 at all, only 21.4.13.  I'm not using 21.4.18 
regularly yet for other reasons.

--
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/

After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash

[Karr, David]

I have a desktop icon for running Xemacs 21.4.13.  This has been working
fine.  Just today, I upgraded Cygwin from 1.5.18 to 1.5.19.  Now when I
double-click the icon, it does nothing.  I then tried pasting the path
to it into a DOS cmd prompt, and it still does nothing.  I then executed
it directly from a bash prompt, and that worked.

I have a similar icon for 21.4.18, and that doesn't demonstrate the same
problem, although 21.4.18 always runs a cmd window in the background,
which 21.4.13 does not.

--
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/

Cygwin app to assess raw typing speed, as opposed to typespeed game?

[Karr, David]

Is there a Cygwin/gcc app that can assess raw typing speed, as opposed
to the typespeed typing game?  I'm looking for something that just has
rows of words and/or short phrases (that aren't moving around the
screen: ) ), and you just type exactly what's on the page.

--
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: Trying to set up Cygwin Perl script to send simple email

[Karr, David]

Never mind.  Net::SMTP seems more standard.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Karr, David
> Sent: Thursday, August 12, 2004 2:46 PM
> To: [EMAIL PROTECTED]
> Subject: Trying to set up Cygwin Perl script to send simple email
> 
> 
> I'm trying to configure my Cygwin Perl distribution so I can 
> write a simple script to send email.  I installed 
> Mail/Send.pm and Mail/Mailer.pm, but when I then try a simple 
> script based on the example in Mail::Send, it says "Can't 
> locate Mail/Mailer/testfile.pm in @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/
> 
> 

--
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/

Trying to set up Cygwin Perl script to send simple email

[Karr, David]

I'm trying to configure my Cygwin Perl distribution so I can write a
simple script to send email.  I installed Mail/Send.pm and
Mail/Mailer.pm, but when I then try a simple script based on the example
in Mail::Send, it says "Can't locate Mail/Mailer/testfile.pm in @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: Subversion eol-corrupting jar files on update

[Karr, David]

If the Cygwin port of subversion is really just using the mount mode to
determine this, then that seems like a bug to me.  Someone else pointed
out to me that subversion is able to determine that the "mime-type" of
".jar" is "application/octet-stream", and that should imply that it
should do no file conversion.

> -Original Message-
> From: [EMAIL PROTECTED] 
> 
> I'm having trouble with the svn in Cygwin corrupting jar 
> files on update or checkout.  It's doing an eol translation.  
> I've specified ".jar" in my svn properties, to indicate that 
> it should use the "eol-type" of "native".  My "mount" table 
> shows everything in "textmode".  Do I have to change to 
> binary in order for this to work?  I would have thought the 
> eol-type setting in the subversion config should deal with this.

--
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/

Subversion eol-corrupting jar files on update

[Karr, David]

I'm having trouble with the svn in Cygwin corrupting jar files on update
or checkout.  It's doing an eol translation.  I've specified ".jar" in
my svn properties, to indicate that it should use the "eol-type" of
"native".  My "mount" table shows everything in "textmode".  Do I have
to change to binary in order for this to work?  I would have thought the
eol-type setting in the subversion config should deal with this.

--
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/

Strategy to process all tokens on a line through "cygpath -w", ignoring non-path tokens

[Karr, David]

I have a situation where I have a command line that I need to preprocess
with "cygpath -w", changing all tokens which represent paths to convert
them to their windows equivalent.  All other tokens should pass through
unchanged.  Is there already a canned solution for this?  What would be
a reasonable strategy to get this done?

--
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: xemacs-21.4.14-2/xemacs-tags-21.4.14-2/xemacs-emacs-common-21.4.14-2

[Karr, David]

Now that Xemacs/Cygwin is installable from "cygwin-setup", what is the
difference between installing it from this, as opposed to using the
"xemacs-setup" that we get from xemacs.org?  If I've been updating my
installation over time from "xemacs-setup", what will happen the next
time I update it from "cygwin-setup"?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dr. Volker Zell
Sent: Sunday, February 08, 2004 8:54 AM
To: [EMAIL PROTECTED]
Subject: [ANNOUNCEMENT] Updated:
xemacs-21.4.14-2/xemacs-tags-21.4.14-2/xemacs-emacs-common-21.4.14-2


Hi

A new version of 'xemacs' has been uploaded to a server near you.


DESCRIPTION:

A powerful, highly customizable open source text editor and application 
development system


CYGWIN NEWS:


* Build with cygwin-1.5.7

* Removed --with-dragndrop from configure line

  This option prevented some W32 processes (notibly Opera/IE/Netscape)
from exiting
  when XEmacs was still running

* Workaround for the warning message

"Couldn't find an obvious default for the root of the
 XEmacs hierarchy."

  at Xemacs startup. Obviously it *finds* all of its files

* Added a copy of sample.init.el,a sample XEmacs initialization script,
to
  /usr/share/doc/xemacs-21.4.14
  See the comments at the start of the file for more information

* Removed empty /etc/postinstall directory from binary distribution

* Added crypt and minires as dependencies in setup.hint

* Removed cygipc from build dependencies in xemacs.README


INSTALLATION:
=
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Save it and run setup, answer the questions and pick up the
above mentioned package from the 'Editors' category.


DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need to
find a mirror which has this update.

These mirrors already got the package, the others will probably have 
the latest version of this package fairly soon:

In the US

   ftp://mirrors.rcn.net/pub/sourceware/cygwin/ 

has reliable high bandwidth connections.


QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.


CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To
unsubscribe to 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:

[EMAIL PROTECTED]


Enjoy
  Volker


--
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/


--
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: Installed 1.5.5, need to back off to 1.3.22

[Karr, David]

At end.

> -Original Message-
> From: Rick Rankin [mailto:[EMAIL PROTECTED] 
> 
> --- "David M. Karr" <[EMAIL PROTECTED]> wrote:
> > >>>>> "Larry" == Larry Hall <[EMAIL PROTECTED]> writes:
> > 
> > Larry> At 08:30 PM 10/9/2003, Karr, David you wrote:
> > >> I have version 1.3.22 installed on another box.  On 
> a new box, I
> > decided
> > >> to go for broke and install 1.5.5.  Unfortunately, 
> as others have
> > >> described, Xemacs doesn't work in this Cygwin 
> version.  I need to
> 
> What specific problem are you having with XEmacs? I use 
> XEmacs 21.4.14 on
> Cygwin 1.5.x constantly, and the only problem I have is that 
> cut-n-paste from
> external sources stops working after running a subshell. This 
> is annoying, but
> for me, at least, not a show-stopper. Supposedly, you can 
> work around this by
> adding
> 
> (setq process-connection-type nil) ;; use pipes instead of ptys
> 
> to your .emacs file, but I haven't tried it. I'm hoping to 
> have a go at
> debugging the problem when ptys are used, but I just haven't 
> had time yet.
> 
> I've seen postings about a font problem, but I haven't 
> experienced the problem
> myself.

When I start up Xemacs, the window appears, and it starts to show the
packages it's loading.  After a while, however, the display of the
window gets corrupted.  The window decorations and border disappear, and
text doesn't show up.  The toolbar icons look fine, however.  If I type
in the opening buffer, it just prints a red block cursor for each
character.  It's not "hung", as I can press the key to exit, and it
exits fine.

--
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/

Installed 1.5.5, need to back off to 1.3.22

[Karr, David]

I have version 1.3.22 installed on another box.  On a new box, I decided
to go for broke and install 1.5.5.  Unfortunately, as others have
described, Xemacs doesn't work in this Cygwin version.  I need to
somehow uninstall what I have and install version 1.3.22.  I've perused
the FAQ and install information, and did some searches on the mailing
list archives, but I don't see how to do this.  I did notice information
on how to "uninstall" cygwin, by manually deleting directories and
registry entries, but I didn't see how I can install an older version.

--
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: Swapping CTRL & CAPS

[Karr, David]

Go to http://www.sysinternals.com and get the "Ctrl2Cap" tool.

> -Original Message-
> From: Neal D. Becker [mailto:[EMAIL PROTECTED]
> 
> I've got xemacs-21.4.12 running fine on the latest cygwin.  Now I only
> have
> one problem.  I normally run linux/kde, and have the caps lock and
ctrl
> key
> swapped (so ctrl is where it's supposed to be).  You need ctrl for
emacs!
> 
> How can I swap/remap these keys when running on cygwin (non-x)?

--
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: Getting "cleartool" prompts to work in Cygwin

[Karr, David]

> -Original Message-
> From: Andrew DeFaria [mailto:[EMAIL PROTECTED]
> 
> Karr, David wrote:
> 
> >However, when I execute this in a Bash shell in RXVT, at the point
> >where it would issue the prompt, it just sits there doing nothing.
If I
> >then press Return, it immediately emits the prompt message, and then
> >takes that as my response.  If instead of pressing Return, I first
type
> >an expected response and press Return, then it takes that as my
> >response, which is an acceptable workaround (if I know what the
prompt
> >says).
> >
> >Is there a strategy I can use to get it to work the same way it does
in
> >a DOS box, printing the entire prompt message, and exiting normally?
> >
> No. The problem is that cleartool is written for Windows (i.e. DOS or
> cmd) which does not use ptys. rxvt, and apparently XEmacs both use
ptys.
> The only solution is to get Rational to fix cleartool (or to use a DOS
> box - or to specify all parameters on the command line so that there
is
> no prompting).

Is there any way to wrap all executions of "cleartool" in a "bridge"
that speaks pty and non-pty?


--
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/

Getting "cleartool" prompts to work in Cygwin

[Karr, David]

Uname -a: CYGWIN_NT-5.1 WG44KA2G55H 1.3.22(0.78/3/2) 2003-03-18 09:20
i686 unknown unknown Cygwin

The "cleartool" application (part of ClearCase) will often present
question prompts in normal operation, to confirm certain operations.
When I execute these commands in a DOS box, it works fine.

However, when I execute this in a Bash shell in RXVT, at the point
where it would issue the prompt, it just sits there doing nothing.  If I
then press Return, it immediately emits the prompt message, and then
takes that as my response.  If instead of pressing Return, I first type
an expected response and press Return, then it takes that as my
response, which is an acceptable workaround (if I know what the prompt
says).

If this Bash shell is inside XEmacs, however, when I press Return at the
invisible prompt, it takes my response and then kills the Bash shell
it's running in. :(

Is there a strategy I can use to get it to work the same way it does in
a DOS box, printing the entire prompt message, and exiting normally?


--
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/