[ANNOUNCEMENT] Re: Updated: texinfo-4.13-4

2011-10-02 Thread Christopher Faylor
I've made a new version of 'texinfo' available for installation. This is the most recent version of texinfo available from ftp.gnu.org which means there has been no source code changes since the last release. The only reason for the release is to relink info.exe with a later version of the ncurse

Re: STATUS_ACCESS_VIOLATION

2011-10-02 Thread Christopher Faylor
On Sun, Oct 02, 2011 at 03:12:39AM -0700, Marc Girod wrote: >marco atzeri-4 wrote: >> My experience is that using the standard "problem report" improve the >> chance to correctly identify the root cause and reduce the number of >> guess that everyone could have. >> >One problem I have is that I us

Re: E484: Can't open file /usr/share/vim/syntax/syntax.vim

2011-10-02 Thread jan.kolar
Oleksandr Gavenko (aka gavenkoa) wrote: > >$ cat ~/.vimrc > syntax on > >$ vim > Error detected while processing /cygdrive/e/home/.vimrc: > line1: > E484: Can't open file /usr/share/vim/syntax/syntax.vim > Press ENTER or type command to continue > > This issue reported previously:

Re: pressing ENTER scrambles scrolled MS-DOS-console

2011-10-02 Thread jan.kolar
Paul Maier-2 wrote: > > Hi, > > scrolling up the console output to review the console history, then > pressing > Enter scrambles the console. > > This is Cygwin-specific: The same steps with Windows' cmd instead of bash > is working fine. > > > To reproduce: > > 1. Open Windows MS-DOS conso

Re: Cygwin LSA breaks code-signing -- how can I fix it?

2011-10-02 Thread jan.kolar
Alan Sinclair-2 wrote: > > After installing Cygwin LSA authentication, code signing fails coming in > over ssh from another machine. > This is cygwin 1.7.9 on x64 Windows 2003 (CYGWIN_NT-5.2-WOW64 AlansW2033 > 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin) > > Running locally, signing succeeds

Re: EXTERNAL: Re: Cygwin too slow while installing and working

2011-10-02 Thread João Moreira
2011/9/21 João Moreira: > On Wed, Sep 21, 2011 at 2:04 PM, jan.kolar wrote: >> >> What about the timing and output of the following: >> >> strace  bash --noprofile -norc -c /bin/echo >> > > timing: > real    0m9.988s > user    0m2.371s > sys     0m0.031s > > output: see attached txt > > > Joao > S

Re: STATUS_ACCESS_VIOLATION

2011-10-02 Thread jan.kolar
Marc Girod wrote: > > Hello, > > I keep my installation up-to-date on a weekly basis, and never fail to > rebaseall/peflagsall as many times as needed to be able to start emacs > in an X session without fork errors. Then I do a perlrebase. > > However, I eventually get STATUS_ACCESS_VIOLATION

Re: error while running shell in emacs

2011-10-02 Thread Ken Brown
On 10/2/2011 5:35 PM, Ken Brown wrote: On 9/30/2011 3:04 PM, Ken Brown wrote: On 9/30/2011 10:27 AM, Markus Hoenicka wrote: Hi, after moving to a new position I have set up a fresh Cygwin installation: CYGWIN_NT-5.1 sbhc123 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin I use some Emacs exten

Re: error while running shell in emacs

2011-10-02 Thread Ken Brown
On 9/30/2011 3:04 PM, Ken Brown wrote: On 9/30/2011 10:27 AM, Markus Hoenicka wrote: Hi, after moving to a new position I have set up a fresh Cygwin installation: CYGWIN_NT-5.1 sbhc123 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin I use some Emacs extensions which execute external programs us

Re: STATUS_ACCESS_VIOLATION

2011-10-02 Thread jan.kolar
Marc Girod wrote: > > > marco atzeri-4 wrote: >> >> Problem reports: http://cygwin.com/problems.html >> so at least we have an idea of your system >> >> in addition, have you checked >> http://cygwin.com/faq/faq.using.html#faq.using.bloda >> >> Antivirus and driver are the most likely

Windows GUI apps and gid in Cygwin

2011-10-02 Thread SJ Wright
Hi. This is a little thing, no errors or gripes involved, but I'm more than curious to see if anything can be done to change it. If I do an ls -lh on any file created or saved in a Windows app, such as XnView, I get this for a return string: -rwx--+ 1 steve None 210336 2011-03-25 21:15 g

Re: STATUS_ACCESS_VIOLATION

2011-10-02 Thread Marc Girod
marco atzeri-4 wrote: > > My experience is that using the standard "problem report" improve the > chance to correctly identify the root cause and reduce the number of > guess that everyone could have. > One problem I have is that I use this list via the (old) nabble web site, and this one doesn