mintty 3.5.1-1: -p center no longer works

2021-11-07 Thread Bryan Higgins
mintty 3.5.1-1: -p center no longer works. Reverted to 3.5.0, which is fine.: -- 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

gdb20030901-1: aborts with stack dump

2003-09-19 Thread Bryan Higgins
Here is gdb.exe.stackdump, for what it's worth: Exception: STATUS_ACCESS_VIOLATION at eip=610B7374 eax=0010 ebx=0010 ecx=0004 edx= esi=D012 ebp=0022F518 esp=0022F50C program=c:\cygwin\bin\gdb.exe cs=001B ds=0023 es=0023 fs=0038 gs= ss=0023 Stack trace: Frame Function A

Re: getopt: ugly linker messages

2003-09-18 Thread Bryan Higgins
Christopher Faylor wrote: >You can use unistd.h if you want. If you knew this already why were you >asking the question? >From the gnu getopt(3) man page (mysteriously missing in cygwin): #include int getopt(int argc, char * const argv[], const char *optstring)

Re: getopt: ugly linker messages

2003-09-18 Thread Bryan Higgins
On Thu, 18 Sep 2003 15:56:07 -0400, Christopher Faylor wrote: >On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote: >>How can I suppress the linker messages >> >>Info: resolving _opterr by linking to __imp__opterr (auto-import) >>Info: resolving _optarg by lin

getopt(3) man page missing

2003-09-18 Thread Bryan Higgins
getopt(3) (referred to in getopt(1), by the way) seems to be missing from the man pages. Bryan Higgins, Albany, California -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com

getopt: ugly linker messages

2003-09-18 Thread Bryan Higgins
-import) which now appear? Bryan Higgins, Albany, California -- 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/

Lastest gdb aborts with stack dump

2003-09-18 Thread Bryan Higgins
The latest gdb aborts with a stack dump whenever I use the "finish" command. I've reverted to the previous version, which is fine. ---- Bryan Higgins, Albany, California -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.co

RE: source command broken in bash

2002-11-26 Thread Bryan Higgins
Found it--there was a file "x" in /usr/bin. The "which" command didn't find it, for some reason. Thanks for checking. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ:

RE: source command broken in bash

2002-11-26 Thread Bryan Higgins
It turns out I was trying to source a file named x, and x appears to be spe- cial in Cygwin. If I type x (after deleting my file x), I get the gawk usage. There are no aliases to x, and "whence x" yields nothing. If I then exit the shell will ^D, I get a bunch of other crap. If you could confirm

"source" command broken in bash

2002-11-26 Thread Bryan Higgins
Neither "source" nor "." work for me in bash--it displays the gawk usage message! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/