date:20040318

Christopher Faylor wrote:

It seems like development for setup.exe is sort of stalled.
I agree completely.

At the very least, it would be nice to get out a new release which
resized correctly.  I know that the current implementation isn't perfect
but I wonder if it is better than the alternative of having a new user a
week sending in a suggestion that the browser should be resizeable.
Can we release setup.exe as is and maybe think about revitalizing
development somehow?  It would be nice if all of the things that
the parser understands were actually understand by the rest of
the program.
I would like to see this very much and think it is a wise decision.

In six days there has been zero discussion of this.  Does that mean that 
setup.exe maintainership is up for grabs?  If so, I've got things that I 
need to start doing with setup.exe, so I would be very interested in 
taking responsibility for setup.exe.  I have the time for it now as 
well, and a project I am working on will really need setup.exe to be 
more robust and reliable (such as not blindly and silently unpacking 
files to mount points that do not point to physical disk locations).

I'll start working on setup.exe next week and see how the maintainership 
question develops.

Harold

Re: setup.exe development stalled?

2004-03-18 Thread Joe Buehler

Harold L Hunt II wrote:

In six days there has been zero discussion of this.  Does that mean that 
setup.exe maintainership is up for grabs?  If so, I've got things that I 
need to start doing with setup.exe, so I would be very interested in 
taking responsibility for setup.exe.  I have the time for it now as 
well, and a project I am working on will really need setup.exe to be 
more robust and reliable (such as not blindly and silently unpacking 
files to mount points that do not point to physical disk locations).

I'll start working on setup.exe next week and see how the maintainership 
question develops.
My own suggestion would be to switch to NSIS to do initial Cygwin
setup, then use something standard like apt or rpm once the initial
setup is done.  Cygwin having its own installer is not a very good
use of resources.
--
Joe Buehler

Re: emacs 21.2-13 available

2004-03-18 Thread Corinna Vinschen

On Mar 16 14:54, Joe Buehler wrote:
 I haven't uploaded anything in a while so please let me know if
 there are any new requirements on the part of Cygwin package
 maintainers or packages...
 
 New GNU emacs package files are available at:
 
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-21.2-13-src.tar.bz2
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-21.2-13.tar.bz2
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-X11/emacs-X11-21.2-13.tar.bz2
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-X11/setup.hint
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-ctags/emacs-ctags-21.2-13.tar.bz2
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-el/emacs-el-21.2-13.tar.bz2
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-el/setup.hint
 http://68.98.176.216:3000/cygwin/emacs-21.2-13/setup.hint
 
 Changes:
 
 - recompile against latest XFree86 (the major reason for this release)
 - setup.hint changes due to rearrangements of various required runtime 
 libraries
 - moved documentation from /usr/doc to /usr/share/doc

Note that I'm not an emacs user so I can't tell if the binary works or
not.  These are just packaging observations:

- The info pages are still in /usr/info, they should be in /usr/share/info.

- Ditto for /usr/man vs. /usr/share/man.

- Don't supply emacs-ctags.  It conflicts with the ctags package which
  provides an emacs independent ctags (and etags).

- The emacs-21.2-13.tar.bz2 as well as the emacs-X11/emacs-X11-21.2-13.tar.bz2
  provide a /usr/bin/emacs.exe binary.  So the emacs packages conflict
  with each other.

Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Developermailto:[EMAIL PROTECTED]
Red Hat, Inc.

Re: setup.exe development stalled?

2004-03-18 Thread Robert Collins

On Fri, 2004-03-19 at 05:33, Harold L Hunt II wrote:
 Christopher Faylor wrote:
 
  It seems like development for setup.exe is sort of stalled.
 
 I agree completely.
 
  At the very least, it would be nice to get out a new release which
  resized correctly.  I know that the current implementation isn't perfect
  but I wonder if it is better than the alternative of having a new user a
  week sending in a suggestion that the browser should be resizeable.
  
  Can we release setup.exe as is and maybe think about revitalizing
  development somehow?  It would be nice if all of the things that
  the parser understands were actually understand by the rest of
  the program.
 
 I would like to see this very much and think it is a wise decision.
 
 In six days there has been zero discussion of this.  Does that mean that 
 setup.exe maintainership is up for grabs?  If so, I've got things that I 
 need to start doing with setup.exe, so I would be very interested in 
 taking responsibility for setup.exe.  I have the time for it now as 
 well, and a project I am working on will really need setup.exe to be 
 more robust and reliable (such as not blindly and silently unpacking 
 files to mount points that do not point to physical disk locations).
 
 I'll start working on setup.exe next week and see how the maintainership 
 question develops.

The 6 days means that I'm in the middle of changing jobs. Starting April
I have a new job with (hopefully) more personal time to do things like
setup.exe. I don't consider the maintainership up for grabs - but please
do start work on setup.exe, I'll happily review patches  we have 3 folk
with commit access who can commit. Assuming your patches are of high
quality, there is no reason that you can't get commit rights in the
future too.

Rob


-- 
GPG key available at: http://www.robertcollins.net/keys.txt.


signature.asc
Description: This is a digitally signed message part

Re: emacs 21.2-13 available

Corinna Vinschen wrote:

On Mar 16 14:54, Joe Buehler wrote:

I haven't uploaded anything in a while so please let me know if
there are any new requirements on the part of Cygwin package
maintainers or packages...
New GNU emacs package files are available at:

http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-21.2-13-src.tar.bz2
http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-21.2-13.tar.bz2
http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-X11/emacs-X11-21.2-13.tar.bz2
http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-X11/setup.hint
http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-ctags/emacs-ctags-21.2-13.tar.bz2
http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-el/emacs-el-21.2-13.tar.bz2
http://68.98.176.216:3000/cygwin/emacs-21.2-13/emacs-el/setup.hint
http://68.98.176.216:3000/cygwin/emacs-21.2-13/setup.hint
Changes:

- recompile against latest XFree86 (the major reason for this release)
- setup.hint changes due to rearrangements of various required runtime 
libraries
- moved documentation from /usr/doc to /usr/share/doc


Note that I'm not an emacs user so I can't tell if the binary works or
not.  These are just packaging observations:
- The info pages are still in /usr/info, they should be in /usr/share/info.

- Ditto for /usr/man vs. /usr/share/man.

- Don't supply emacs-ctags.  It conflicts with the ctags package which
  provides an emacs independent ctags (and etags).
- The emacs-21.2-13.tar.bz2 as well as the emacs-X11/emacs-X11-21.2-13.tar.bz2
  provide a /usr/bin/emacs.exe binary.  So the emacs packages conflict
  with each other.
I'd like to maintain the status quo for all of these to get this new 
version released as soon as possible.  A -14 release can contain all of 
these fixes, and I agree that it should follow quickly.

Harold

Re: emacs 21.2-13 available

2004-03-18 Thread Corinna Vinschen

On Mar 18 14:54, Harold L Hunt II wrote:
 Corinna Vinschen wrote:
 - The info pages are still in /usr/info, they should be in /usr/share/info.
 
 - Ditto for /usr/man vs. /usr/share/man.
 
 - Don't supply emacs-ctags.  It conflicts with the ctags package which
   provides an emacs independent ctags (and etags).
 
 - The emacs-21.2-13.tar.bz2 as well as the 
 emacs-X11/emacs-X11-21.2-13.tar.bz2
   provide a /usr/bin/emacs.exe binary.  So the emacs packages conflict
   with each other.
 
 I'd like to maintain the status quo for all of these to get this new 
 version released as soon as possible.  A -14 release can contain all of 
 these fixes, and I agree that it should follow quickly.

I disagree.  The above problems are showstoppers for me, most notably
the conflict with ctags.  And they aren't really difficult to fix.

Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Developermailto:[EMAIL PROTECTED]
Red Hat, Inc.

Re: emacs 21.2-13 available

Corinna Vinschen wrote:

On Mar 18 14:54, Harold L Hunt II wrote:

Corinna Vinschen wrote:

- The info pages are still in /usr/info, they should be in /usr/share/info.

- Ditto for /usr/man vs. /usr/share/man.

- Don't supply emacs-ctags.  It conflicts with the ctags package which
provides an emacs independent ctags (and etags).
- The emacs-21.2-13.tar.bz2 as well as the 
emacs-X11/emacs-X11-21.2-13.tar.bz2
provide a /usr/bin/emacs.exe binary.  So the emacs packages conflict
with each other.
I'd like to maintain the status quo for all of these to get this new 
version released as soon as possible.  A -14 release can contain all of 
these fixes, and I agree that it should follow quickly.


I disagree.  The above problems are showstoppers for me, most notably
the conflict with ctags.  And they aren't really difficult to fix.
If they were really showstoppers then emacs would have been pulled from 
distribution long ago.  It doesn't matter if they are critical, they 
won't make anything worse than waiting a few more days for another 
release would.

Harold

Re: Busted generic build script?

Igor Pechtchanski wrote:

On Thu, 18 Mar 2004, Harold L Hunt II wrote:
[snip]
Oops.  Mea culpa.  I've verified that it worked in bash, and ran the
script through sh -n (which turns out to not be enough).
Harold, could you please try the attached patch and see if it fixes things
for you?  If yes, I'll commit it to CVS.
Igor
Yes, the patch fixes the problem.

Thanks,

Harold

Re: Busted generic build script?

2004-03-18 Thread Igor Pechtchanski

On Thu, 18 Mar 2004, Harold L Hunt II wrote:

 Igor Pechtchanski wrote:

  On Thu, 18 Mar 2004, Harold L Hunt II wrote:
 [snip]
 
  Oops.  Mea culpa.  I've verified that it worked in bash, and ran the
  script through sh -n (which turns out to not be enough).
 
  Harold, could you please try the attached patch and see if it fixes things
  for you?  If yes, I'll commit it to CVS.
  Igor

 Yes, the patch fixes the problem.

 Thanks,
 Harold

Harold,

Great, committed.  Those quoting issues are tricky. :-)
Thanks very much for testing.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster.  -- Patrick Naughton

please upload: CLISP 2.33 stable

2004-03-18 Thread Sam Steingold

please upload the new stable release 2.33 of GNU CLISP
http://www.podval.org/~sds/data/setup.hint
http://www.podval.org/~sds/data/clisp-2.33-1-src.tar.bz2
http://www.podval.org/~sds/data/clisp-2.33-1.tar.bz2

thanks!
-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
http://www.camera.org http://www.iris.org.il http://www.memri.org/
http://www.mideasttruth.com/ http://www.honestreporting.com
The plural of anecdote is not data.

Re: [ITP] flip-1.19 - Convert between Unix and Dos line endings

2004-03-18 Thread Lapo Luchini

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andreas Seidl wrote:

 I guess that detects binary and interrupts gracefully are the
 main reasons to prefer that over the standard
 dos2unix/unix2dos?

 It handles Macintosh format as well. Another reason is the -t
 option, which tells you the type of the file, without modifying it.
 This comes handy, if a Macintosh user sends you some suspicious
 file.

I agree, pure detection is indeed useful, as is conversion to Mac
format.
Consider this a vote.

- --
Lapo 'Raist' Luchini
[EMAIL PROTECTED] (PGP  X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkBaNLwACgkQaJiCLMjyUvu4YACfUW0SlRJVCcByjk3d3T8zRylc
3gwAn1w0DI80xkjYM7r+TJj95KHMtJB2
=OpKE
-END PGP SIGNATURE-

RE: WhizzyTeX

2004-03-18 Thread $BCOF,(B $B=E?M(B

(B
(B
(BFrom: Gregory Borota [EMAIL PROTECTED]
(BReply-To: [EMAIL PROTECTED]
(BTo: [EMAIL PROTECTED]
(BSubject: WhizzyTeX
(BDate: Thu, 18 Mar 2004 12:05:05 -0600
(B
(BI tried sending this message twice, it didn't go through, I try 
(Bagain with a two part message.
(B
(BI am interested in becoming a package maintainer for whizzytex.
(B
(Bsetup.hint
(B--
(Bsdesc: "A WYSIWIG environment for LaTeX"
(Bldesc: "WhizzyTeX is an emacs minor mode for incrementally
(B(TeXing and) previewing a LaTeX file that you are editing.
(B
(BIt works with cygwin xdvi-based and ghostview-based
(Bpreviewers, also with with Windows native previewers
(Blike MikTex Yap, dviout, etc."
(Bcategory: tex
(Brequires: bash emacs xemacs tetex-bin tetex-base tetex-extra 
(Btetex-x11 ghostscript-x11 XFree86-base
(B--
(B
(BGreg
(B
(B_
$BM'C#$H(B24$B;~4V%[%C%H%i%$%s!V(BMSN $B%a%C%;%s%8%c!http://messenger.msn.co.jp

Re: emacs 21.2-13 available

2004-03-18 Thread Joshua Daniel Franklin

--- Harold L Hunt II [EMAIL PROTECTED] wrote:
 If they were really showstoppers then emacs would have been pulled from 
 distribution long ago.  It doesn't matter if they are critical, they 
 won't make anything worse than waiting a few more days for another 
 release would.

It does make things worse. Once the packaging is fixed, users will
have another large download that can be avoided by doing it 
properly this time.

__
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

Re: Clipboard and XDCMP

2004-03-18 Thread Staf Verhaegen

[EMAIL PROTECTED] wrote:
Staf,

Can you copy and paste into the gdm login prompt? If so check the killinitclients line in the gdm config file. I have similar issues, and turning off killinitclients is not an option, but I havn't had the time to look into it, so I shan't complain.

Ryan.
I can copy and paste in the login prompt so probably the killinitclients 
option is the fault. Maybe an entry for the FAQ ?
Maybe I propose a change for the X server then ? Can't the clipboard handler 
be restarted once when it is deleted ? This will let the clipboard function 
also for gdm with killinitclients on.

Staf.

Can't start a specific remote X app any more

2004-03-18 Thread luke . kendall

I recently upgraded to Cygwin 1.5.7(0.109/3/2), including
XWin release 4.3.0.56 installed from XFree86-bin-4.3.0-16.tar.bz2

Now when I try to run one particular remote X application (my MUA) I get
this error:

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Atom id in failed request:  0xee
  Serial number of failed request:  12
  Current serial number in output stream:  15

The remote (linux) machine has not had its sshd config changed since
2002.  It has X11Forwarding yes, and used to work fine.

If I ssh -X into the machine, DISPLAY is set to localhost:10.0

The MUA runs fine on the Linux machine which I am connecting to with
ssh.  xmessage and other X applications I've tried also work okay.
The MUA is Postilion (a Tk/Tcl application built from the TkRat MUA,
but with the Nextstep Mail program's look and feel).

Other Tk applications work okay.

There's nothing odd in /tmp/XWin.log.

Any suggestions?

luke

Re: Can't start a specific remote X app any more

2004-03-18 Thread luke . kendall

On 18 Mar, To: [EMAIL PROTECTED] wrote:
  Now when I try to run one particular remote X application (my MUA) I get 
  this error: 
   
  X Error of failed request:  BadAtom (invalid Atom parameter) 
Major opcode of failed request:  18 (X_ChangeProperty) 
Atom id in failed request:  0xee 
Serial number of failed request:  12 
Current serial number in output stream:  15 

I tried running the MUA from inside gdb, and it worked. 
Basically, this is what happened

postilion -- error message above
repeat 3 times
ssh -X to my Linux machine
postilion -- error message above
xmessage -- ok
tkxplanet -- ok
postilion inside gdb -- ok
postilion -- ok
# log out
postilion -- this error message:

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Atom id in failed request:  0xee
  Serial number of failed request:  11
  Current serial number in output stream:  11

ssh -X to my Linux machine

$ tkxplanet
X Error of failed request:  BadAtom (invalid Atom parameter
  Major opcode of failed request:  20 (X_GetProperty)
  Atom id in failed request:  0xee
  Serial number of failed request:  11
  Current serial number in output stream:  11
$ xmessage ok
$ tkxplanet
X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Atom id in failed request:  0xee
  Serial number of failed request:  11
  Current serial number in output stream:  11

I haven't managed to run the MUA a 2nd time.

Ah.  Having just typed all this up, I just tried again in case it might
be time related.  Since both times it worked, it was about 10 minutes
after a series of failures.  Sure enough, it's working again at the
moment.

Any idea what might be going on here?

luke

Help with startxwin.bat

2004-03-18 Thread Neto, Antonio Jose Rodrigues

Please, could anyone help me with this!

I've install the cygwin on my Windows XP Professional and I'm try to use
startxwin.bat. It is Ok.

But, when I click on X (Show Root Window) - my screen and my mouse are
frozen and the Xwin.exe process is 100%.

Could you help me?

TIA

Best Regards

neto

PS : 

Cygwin Win95/NT Configuration Diagnostics
Current System Time: Wed Mar 17 14:13:04 2004
Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
Path: C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\cygwin\usr\X11R6\bin
c:\Program Files\Windows Resource Kits\Tools\
c:\PROGRAM FILES\THINKPAD\UTILITIES
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
c:\Program Files\ATI Technologies\ATI Control Panel
c:\Program Files\Support Tools\
Output from C:\cygwin\bin\id.exe (nontsec)
UID: 20508(neto) GID: 10545(mkgroup-l-d)
10545(mkgroup-l-d)
Output from C:\cygwin\bin\id.exe (ntsec)
UID: 20508(neto) GID: 10545(mkgroup-l-d)
0(root) 544(Administrators) 
545(Users) 10545(mkgroup-l-d)
SysDir: C:\WINDOWS\System32
WinDir: C:\WINDOWS
HOME = `c:\Documents and Settings\neto'
MAKE_MODE = `unix'
PWD = `/cygdrive/c/Documents and Settings/neto'
USER = `neto'
Use `-r' to scan registry
c: hd NTFS 25005Mb 51% CP CS UN PA FC Windows XP
d: hd FAT32 10067Mb 54% CP UN BACKUP
e: cd N/A N/A 
h: net NTFS 4096Mb 0% CP CS UN PA users
C:\cygwin / system binmode
C:\cygwin/bin /usr/bin system binmode
C:\cygwin/lib /usr/lib system binmode C:\cygwin\usr\X11R6\lib\X11\fonts
/usr/X11R6/lib/X11/fonts system binmode . /cygdrive system
binmode,cygdrive
Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cpp.exe
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gdb.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
802k 2003/09/15 C:\cygwin\bin\cygaspell-15.dll
61k 2003/08/09 C:\cygwin\bin\cygbz2-1.dll
54k 2002/01/27 C:\cygwin\bin\cygbz21.0.dll
14k 2003/08/10 C:\cygwin\bin\cygcharset-1.dll
7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll
842k 2003/09/30 C:\cygwin\bin\cygcrypto-0.9.7.dll
645k 2003/04/11 C:\cygwin\bin\cygcrypto.dll
598k 2003/11/03 C:\cygwin\bin\cygcurl-2.dll
22k 2004/02/10 C:\cygwin\bin\cygcygipc-2.dll
380k 2002/07/24 C:\cygwin\bin\cygdb-3.1.dll
831k 2003/09/20 C:\cygwin\bin\cygdb-4.1.dll
326k 2002/06/26 C:\cygwin\bin\cygdb2.dll
487k 2002/07/24 C:\cygwin\bin\cygdb_cxx-3.1.dll
1080k 2003/09/20 C:\cygwin\bin\cygdb_cxx-4.1.dll
155k 2004/01/07 C:\cygwin\bin\cygexpat-0.dll
71k 2004/01/13 C:\cygwin\bin\cygexslt-0.dll
654k 2003/11/04 C:\cygwin\bin\cygfltknox-0.dll
65k 2003/11/04 C:\cygwin\bin\cygfltknox_forms-0.dll
81k 2003/11/04 C:\cygwin\bin\cygfltknox_gl-0.dll
108k 2003/11/04 C:\cygwin\bin\cygfltknox_images-0.dll
129k 2004/03/11 C:\cygwin\bin\cygfontconfig-1.dll
45k 2001/04/25 C:\cygwin\bin\cygform5.dll
35k 2002/01/09 C:\cygwin\bin\cygform6.dll
48k 2003/08/09 C:\cygwin\bin\cygform7.dll
361k 2003/10/25 C:\cygwin\bin\cygfreetype-6.dll
213k 2004/02/05 C:\cygwin\bin\cyggd-2.dll
28k 2003/07/20 C:\cygwin\bin\cyggdbm-3.dll
30k 2003/08/11 C:\cygwin\bin\cyggdbm-4.dll
19k 2003/03/22 C:\cygwin\bin\cyggdbm.dll
15k 2003/07/20 C:\cygwin\bin\cyggdbm_compat-3.dll
15k 2003/08/11 C:\cygwin\bin\cyggdbm_compat-4.dll
69k 2003/08/10 C:\cygwin\bin\cyggettextlib-0-12-1.dll
12k 2003/08/10 C:\cygwin\bin\cyggettextpo-0.dll
134k 2003/08/10 C:\cygwin\bin\cyggettextsrc-0-12-1.dll
167k 2003/09/09 C:\cygwin\bin\cyggmp-3.dll
349k 2003/12/08 C:\cygwin\bin\cygGraphicsMagick++-0.dll
2169k 2003/12/08 C:\cygwin\bin\cygGraphicsMagick-0.dll
1506k 2003/11/05 C:\cygwin\bin\cyggsl-0.dll
190k 2003/11/05 C:\cygwin\bin\cyggslcblas-0.dll
489k 2003/08/09 C:\cygwin\bin\cygguile-12.dll
489k 2003/07/28 C:\cygwin\bin\cygguile-12abi13.dll
24k 2003/08/09 C:\cygwin\bin\cygguile-ltdl-1.dll
24k 2003/07/28 C:\cygwin\bin\cygguile-ltdl-1abi13.dll
62k 2003/08/09 C:\cygwin\bin\cygguile-srfi-srfi-13-14-v-1-1.dll
62k 2003/07/28 C:\cygwin\bin\cygguile-srfi-srfi-13-14-v-1-1abi13.dll
23k 2003/08/09 C:\cygwin\bin\cygguile-srfi-srfi-4-v-1-1.dll
23k 2003/07/28 C:\cygwin\bin\cygguile-srfi-srfi-4-v-1-1abi13.dll
11k 2003/08/09 C:\cygwin\bin\cygguilereadline-v-12-12.dll
11k 2003/07/28 C:\cygwin\bin\cygguilereadline-v-12-12abi13.dll
17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll
29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll
330k 2004/02/09 C:\cygwin\bin\cyghttpd.dll
958k 2003/08/10 C:\cygwin\bin\cygiconv-2.dll
22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll
37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll
21k 2001/06/20 C:\cygwin\bin\cygintl.dll
12k 2003/02/17 C:\cygwin\bin\cygioperm-0.dll
48k 2003/08/10 C:\cygwin\bin\cygjbig1.dll
132k 2003/08/11 C:\cygwin\bin\cygjpeg-62.dll
119k 2002/02/09 C:\cygwin\bin\cygjpeg6b.dll
60k 2003/09/17 C:\cygwin\bin\cygkpathsea-3.dll
60k 2003/07/27

Re: Can't start a specific remote X app any more

yn Thu, 18 Mar 2004 [EMAIL PROTECTED] wrote:

 I recently upgraded to Cygwin 1.5.7(0.109/3/2), including
 XWin release 4.3.0.56 installed from XFree86-bin-4.3.0-16.tar.bz2
 
 Now when I try to run one particular remote X application (my MUA) I get
 this error:
 
 X Error of failed request:  BadAtom (invalid Atom parameter)
   Major opcode of failed request:  18 (X_ChangeProperty)
   Atom id in failed request:  0xee
   Serial number of failed request:  12
   Current serial number in output stream:  15
 
 The remote (linux) machine has not had its sshd config changed since
 2002.  It has X11Forwarding yes, and used to work fine.
 
 If I ssh -X into the machine, DISPLAY is set to localhost:10.0


http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Re: Urgent: Help with startxwin.bat

On Wed, 17 Mar 2004, Neto, Antonio Jose Rodrigues wrote:

 Hi All,
 
 Please, could you help me?
 
 I've install the cygwin on my Windows XP Professional and I'm try to use
 startxwin.bat. It is Ok.
 
 But, when I click on X (Show Root Window) - my screen and my mouse are
 frozen and the Xwin.exe process is 100%.

Does it all work if you don't click on Show Root Window?

 Could you help me?
 
 Cygwin Win95/NT Configuration Diagnostics
 Current System Time: Wed Mar 17 14:13:04 2004
 Windows XP Professional Ver 5.1 Build 2600 Service Pack 1

much more important is /tmp/XWin.log

And you don't need to send a message three times in two days. 

-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Re: Massive CVS update

On Wed, 17 Mar 2004, Alexander Gottwald wrote:

 I will try to merge the XORG-RELEASE-1 branch more often into the 
 CYGWIN branch to be as close as possible to the xorg work and be
 able to make a stable release as soon as the other xorg developers
 make their release.

Some words on how I do the merge:

I have the two branches checked out with this layout

xorg-release-1/xc XORG-RELEASE-1
xc-cygwin-merge/xc CYGWIN

the commands are quite simple

#
# Get the latest from XORG-RELEASE-1
#
cd xorg-release-1/xc
cvs update
#
# Mark the checked out revisions
#
cvs tag -F XORG-CYGWIN-MERGE
#
# Merge changes between XORG-CYGWIN-LAST-MERGE and XORG-CYGWIN-MERGE
#
cd ../../xc-cygwin-merge/xc
cvs update -j XORG-CYGWIN-LAST-MERGE -j XORG-CYGWIN-MERGE
#
# clean up
#
remove conflicts, check that the tree builds
#
# Commit what has changed
#
cvs commit -m merge with XORG-RELEASE-1
#
# Mark the revisions as last merge point
#
cd ../../xorg-release-1/xc
cvs tag -F -r XORG-CYGWIN-MERGE XORG-CYGWIN-LAST-MERGE

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Re: X/Cygwin icon proposal

2004-03-18 Thread Michael Bax

Hi folks

The new icon with alpha looks quite bad on Windows 2000 and earlier systems,
with a thick white border -- see the attachment PNG.  The tips of the X on
some of the other versions of the icon  also look slightly blunt (minor
quibble), and the top and bottom rows are lost at 16x16.

Presumably we shouldn't be setting the default to something that uses a
feature unsupported by the majority of systems out there!  Alpha is nice,
but it is a new, optional feature; we still need to support low-colour
desktops by default.

Using the CVS icon as a starting point, I created a new icon using an
outlined white square as the background.  It is rendered at 16x16, 24x24 and
32x32 sizes, each for monochrome, 16 and 256 colours.  It has the correct
proportions of the thick and thin lines, properly anti-aliased and
quantised.  It's even rotationally invariant!  :-)

I have attached two files: a comparison of the icons in Overview.png, and
the improved icon in Improved.ico.

Cheers
Michael
attachment: Overview.pngattachment: Improved.ico

Installing tcltk does not force installation of XFree86-prog

2004-03-18 Thread Marc Daumas

...although X11/Xlib.h is needed.

--
Marc Daumas (CNRS-LIP) - http://perso.ens-lyon.fr/marc.daumas
mailto:[EMAIL PROTECTED] (suspect emails are discarded)
PGP Key FP : 86C8 3DB3 7118 517A AA13  5707 D617 13D6 7510 D750
ENS de Lyon - 46, allee d'Italie - 69364 Lyon Cedex 07 - FRANCE
Phone: (+33) 4 72 72 85 83 - Fax: (+33) 4 72 72 80 80

Starting X server on cygwin

2004-03-18 Thread Danielle

I've installed cygwin with all XFree86 options marked but I can't make it work.

When I type X or startx command lines appears like that:

[EMAIL PROTECTED] /cygdrive/c/cygwin/usr/X11R6/bin
$ X
bash: X: command not found

[EMAIL PROTECTED] /cygdrive/c/cygwin/usr/X11R6/bin
$ startx
bash: startx: command not found

[EMAIL PROTECTED] /cygdrive/c/cygwin/usr/X11R6/bin
$ ./startx
[: and: unknown operand
[: and: unknown operand
export: Settings/Danielle/.Xauthority: bad variable name
xinit: not found

What should I do?

Thanks,
Dani.

Re: Upcoming X.org release and splitting packages

2004-03-18 Thread Dr. Volker Zell

 Harold == Harold L Hunt, Harold writes:

Harold 1) Due to popular demand, rename the prog package to devel.  The
Harold name devel matches the defacto standard used by other packages for
Harold link libraries and header files; most people have no idea what the
Harold prog package is for, but they do know what a devel package is for.

yap

Harold 2) Split the bin package into at least a few pieces (but not too
Harold many pieces):

Harold 2a) bin-dlls will contain the .dll files only.  This would allow
Harold packages like emacs or xemacs to depend only on bin-dlls instead of on
Harold the entire bin package which includes programs not used by emacs nor
Harold xemacs.

great

Harold 2b) bin-lndir would contain the lndir utility.  lndir has no
Harold dependence on X libs and can be used by any programmer for non-X
Harold projects.

+1
especially useful for some packages configuring only in their source tree

Harold 2c) bin-apps would contain all other applications originally
Harold contained in bin but not contained in bin-dlls nor bin-lndir.

sure

Harold 3) Rename all fonts packages from f100, cyr, fenc, fnts, fscl to
Harold something like fonts-100dpi, fonts-cyrillic, fonts-encodings,
Harold fonts-75dpi, and fonts-scalable.

finally

Harold 4) Split the fnts package into a fonts-required and
Harold fonts-75dpi. fonts-required should be a very small package that
Harold would allow people to minimize their download if they are using Xdmcp
Harold to reach a KDE or Gnome desktop, both of which you client-rendered
Harold fonts (few fonts required on your Cygwin/X host in that case).

what ever you want, ...

Harold 6) Rename fsrv to font-server.

yap

Harold 7) Rename html to manual-pages-html.
Harold 8) Rename man to manual-pages.

maybe something with doc* is more in line with other packages

Harold Harold

go ahead

Ciao
  Volker

Re: Xemacs crash on WinXP

2004-03-18 Thread Jee Chung

I start my xemacs by invoking the command emacs  via my TWM's root menu (coded into my .twmrc file).  The version of emacs I have on my install says that it's 21.2.1.  My Cygwin install appears to be cygwin-1.5.7-1 from having examined the cygwin1.dll file.

JC

Dr. Volker Zell wrote:
Jee == Jee Chung writes:


Jee Ever since I updated by Cygwin installation about a week ago, my xemacs has 
been crashing repeatedly.  Usually, it starts up fine, I use it for a few minutes, then 
it either hangs (consumes CPU) then crashs or crashes spontaneously leaving a stack dump 
that looks like:
Jee bash:~ cat emacs.EXE.stackdump Stack trace:
Jee Frame Function  Args
Jee 0022E100  77E7AC21  (, 0020, 0002, )
Jee 0022E160  61087E49  (03C8, 0006, 0022E1B0, 2008CBEC)
Jee 0022E1B0  61086211  (0006, 2008CB70, 1000, )
Jee 0022E1D0  61026B4C  (06D0, EA60, 0014, 0022E20C)
Jee 0022E250  6108A855  (, 6102606B, 0004B14B, )
Jee 0022E2B0  61087E49  (03C8, 0006, 20396060, )
Jee 0022E2D0  61086211  (0057, 0022E348, 10417FDC, 200EF98B)
Jee 0022E310  200DFBA5  (, , 0002, 002C0DBC)
Jee 0022E330  200DFBEC  (, , 0024, 0022E2A0)
Jee 0022E3B0  2011B7D0  (3023BF20, 4023BF9C, 0005, 0022E454)
Jee 0022E400  200F002B  (4023BEFC, 0001, 0022E49C, 20549840)
Jee 0022E460  200EFB1C  (0002, 0022E498, 2068EA00, 0001)
Jee 0022E490  200EF5E9  (10272674, 4053DE00, 0022E570, 200948E0)
Jee 0022E570  200948F2  (0001, 0022E53C, 0001, 0022E54C)
Jee 0022E590  200937F2  (0001, , FF00, )
Jee 0022E5C0  20097197  (204C2850, 0001, 015A, 0022E660)
Jee End of stack trace (more stack frames may be present)
Jee All other Xfree86 program appear to be functioning fine.  Has anyone else seen a problem like this?

More info, please which version of xemacs, cygwin, bla, bla bla...
Especially how do you start XEmacs 
Jee JC

Ciao
  Volker

Re: cygXft-2.dll ?

libXft is the package.

A search through the Setup Package Search link at cygwin.com would 
have told you this:

http://cygwin.com/cgi-bin2/package-grep.cgi?grep=cygXft-2.dll

Harld

Bo Landarv wrote:
Hi.

I can't make a freshly installed cygwin X-server start.
sh /usr/X11R6/bin/startwin.sh
yields that cygXft-2.dll cannot be found.
It is not installed anywhere and I cannot find any package that contains 
it.

Regards
Bo Landarv

Re: Xemacs crash on WinXP

2004-03-18 Thread Dr. Volker Zell

 Jee == Jee Chung [EMAIL PROTECTED] writes:

Jee I start my xemacs by invoking the command emacs  via my TWM's root menu 
(coded into my .twmrc file).  The version of emacs I have on my install says that it's 
21.2.1.  My Cygwin install appears to be cygwin-1.5.7-1 from having examined the 
cygwin1.dll file.
Jee JC

Aha, so it's emacs and not XEmacs. Search the list, I think there are
known problems with emacs or even better download the new proposed
version from Joe Bühler. Or maybe switch to XEmacs

Ciao
  Volker

Re: Upcoming X.org release and splitting packages

Frédéric L. W. Meunier wrote:

On Wed, 17 Mar 2004, Harold L Hunt II wrote:


We will soon (possibly next week) be releasing a new version
of all Cygwin/X packages built from the source code tree
managed by X.org and hosted on freedesktop.org.  This will be
a very good thing since all of the Cygwin/X developers will
be able to stay in sync with the exact code that is in
distribution via CVS, compared to our current system today
where the code in distribution has many differences from that
in CVS.  The rebuild won't mean much to end users: all
libraries remain binary compatible with the current packages
and the contents of the release (programs, etc.) will be
almost identical.


What are the main differences between it and XFree86 4.4.0 ?
Are things like XTerm 185 included, or everything that goes to
XFree86 can't to X.org ?
I don't know about XTerm 185 specifically, but this release should 
contain all fixes and features that were added to the XFree86 project's 
source code tree for the 4.4.0 release.

2) Split the bin package into at least a few pieces (but not too many
pieces):
2a) bin-dlls will contain the .dll files only.  This would allow
packages like emacs or xemacs to depend only on bin-dlls instead of on
the entire bin package which includes programs not used by emacs nor xemacs.


Maybe do the same for Lesstif ?
Heh, one thing at a time.  :)

2b) bin-lndir would contain the lndir utility.  lndir has
no dependence on X libs and can be used by any programmer for
non-X projects.


Nice. lndir is very useful when a /path/to/configure options
doesn't work as expected due to lack of Automake support or
brokeness.
Yup, I use it all the time for that.

2c) bin-apps would contain all other applications
originally contained in bin but not contained in bin-dlls
nor bin-lndir.


I thought you'd split it more, like only adding what's really
essential, and move xbiff, xclock, xedit, xman, etc to a
separate package. But how to know what's essential ? And I
guess imake, makedepend, /usr/X11R6/lib/X11/config, etc could
go in devel ?
Well, I am debating whether or not to start going down this slippery 
slope... two or three category types of packages may be okay I suppose.

Harold

Re: Upcoming X.org release and splitting packages

David Fraser wrote:

Harold L Hunt II wrote:

We will soon (possibly next week) be releasing a new version of all 
Cygwin/X packages built from the source code tree managed by X.org and 
hosted on freedesktop.org. This will be a very good thing since all of 
the Cygwin/X developers will be able to stay in sync with the exact 
code that is in distribution via CVS, compared to our current system 
today where the code in distribution has many differences from that in 
CVS. The rebuild won't mean much to end users: all libraries remain 
binary compatible with the current packages and the contents of the 
release (programs, etc.) will be almost identical.

In case you have not noticed, I created a build and packaging script 
system for Cygwin/X last week (took 60+ hours). This script system 
does a few things for us, such as allowing us to easily distribute 
source tarballs via Cygwin's setup.exe. More importantly, the script 
system allows us to exercise a finer control over what files each 
package contains and how many packages we break the distribution up 
into. We can very easily rename current packages when we make the next 
release, we can split existing packages into pieces, or we could take 
a set of packages, roll them back together, then split that entire 
mess into mixed pieces of the originals.

I am mentioning this now because I can think of a few things that I 
would like to change in our package layout in time for the X.org 
release, but I would also like to get feedback from the community on 
what you think would be useful. Please take a look at my brief list of 
ideas below and send your thoughts to the mailing list if you have 
something about our packaging that you have wanted changed for a long 
time.

My Proposals for Packaging Changes
==
1) Due to popular demand, rename the prog package to devel. The 
name devel matches the defacto standard used by other packages for 
link libraries and header files; most people have no idea what the 
prog package is for, but they do know what a devel package is for.


+1

2) Split the bin package into at least a few pieces (but not too 
many pieces):

2a) bin-dlls will contain the .dll files only. This would allow 
packages like emacs or xemacs to depend only on bin-dlls instead of on 
the entire bin package which includes programs not used by emacs nor 
xemacs.

2b) bin-lndir would contain the lndir utility. lndir has no 
dependence on X libs and can be used by any programmer for non-X 
projects.

2c) bin-apps would contain all other applications originally 
contained in bin but not contained in bin-dlls nor bin-lndir.


This sounds great... although I wonder whether it would be good to split 
bin-apps into bin-apps (xterm, xeyes, etc) and bin-utils (xauth, xhost etc)
Not sure... it might work okay.

3) Rename all fonts packages from f100, cyr, fenc, fnts, fscl to 
something like fonts-100dpi, fonts-cyrillic, fonts-encodings, 
fonts-75dpi, and fonts-scalable.


+1

4) Split the fnts package into a fonts-required and fonts-75dpi. 
fonts-required should be a very small package that would allow people 
to minimize their download if they are using Xdmcp to reach a KDE or 
Gnome desktop, both of which you client-rendered fonts (few fonts 
required on your Cygwin/X host in that case).


+1

5) Rename the lib package to something more meaningful. The name 
currently implies that it might contain link libraries or run-time 
libraries, but it really contains files shared among X packages. 
Perhaps shared-files would be a better name. I would appreciate it 
if someone would look into what Debian and/or Fedora call this package.


Fedora has all the /usr/X11R6/lib/locale/ files, 
/usr/X11R6/lib/X11/rgb.txt /usr/X11R6/lib/X11/XErrorDB and 
/usr/X11R6/lib/X11/XKeysymDB in XFree86-libs-data, the 
/usr/X11R6/include/X11/bitmaps/ files in XFree86-devel, and on my system 
doesn't have /usr/X11R6/lib/X11/xedit/lisp/ files so I can't say.
So I guess libs-data is a good name...
Okay, thanks for looking into that.  libs-data doesn't sound too bad. 
 Now to figure out what debian calls it.

6) Rename fsrv to font-server.


+1

7) Rename html to manual-pages-html.

8) Rename man to manual-pages.


what about docs and docs-html for these too?
There was a different docs package that had the protocol 
specifications documents in it.  I figured that manual-pages would 
imply that these are documents read with man, not regular text 
documents.  The html package is just html versions of those manual pages.

I dunno... let me know what Fedora calls these packages.

Let us know what you think of those and send in your own suggestions 
as well.

Harold


Just some ideas
Thanks,

Harold

Re: Updated: XFree86-[base,xserv]

Earle,

Earle F. Philhower III wrote:
It's bad form to talk to yourself, but...

At 06:19 PM 3/17/2004 +, Earle wrote:

OK, I feel really stupid now.  I did test this locally but not with xterm
menus. I do most of my work in emacs, which seems OK, so didn't notice...
There's a transient property on the window that should be examined
before cascading it, I'll either back out the change or add the transient
property check tonight.


I've got the fix ready, but it seems freedesktop.org is down (www  cvs
both) tonight.  I'll try again tomorrow morning, but it turned out to be
that we have to check for 3 things @ line ~482 of winmultiwindowwindow.c:
1. Not predefined in hints (preplaced w/-geometry or by the app)
2. No WM_TRANSIENT_FOR ATOM attached (for things like splash screens)
3. No pWin-overrideRedirect (undecorated)
Okay, thanks for looking into this.

Adding those 3 changes makes everything back to hunkey-dorey in emacs,
xterm, xfig, xfontsel, and xemacs.  The main app window is cascaded
but menus aren't touched.
Glad you were able to fix it. :)

Harold, I'll look at the always-on-top stuff once these are checked in...
Thanks in advance,

Harold

Re: Clipboard and XDCMP

Staf Verhaegen wrote:

[EMAIL PROTECTED] wrote:

Staf,

Can you copy and paste into the gdm login prompt? If so check the 
killinitclients line in the gdm config file. I have similar issues, 
and turning off killinitclients is not an option, but I havn't had the 
time to look into it, so I shan't complain.

Ryan.


I can copy and paste in the login prompt so probably the killinitclients 
option is the fault. Maybe an entry for the FAQ ?
Maybe I propose a change for the X server then ? Can't the clipboard 
handler be restarted once when it is deleted ? This will let the 
clipboard function also for gdm with killinitclients on.
Of course it could be restarted... but I do not recall if the code is 
clean enough to be able to stop in the middle of a clipboard request, 
clean up properly, and reinitialize properly.  I would have to do some 
work just to make sure that that is possible.

Another thing that I had worked on was making the clipboard client not 
show up from the functions that return all windows attached to the 
system.  I didn't like that approach because I had to duplicate nearly 
90% of the code from the underlying function, rather than just changing 
its behavior slightly with a before or after modification.

I dunno... it works pretty well for me for the moment and I think we 
have some higher priority problems like crashes.

Harold

Re: Can't start a specific remote X app any more

Alexander,

Alexander Gottwald wrote:

yn Thu, 18 Mar 2004 [EMAIL PROTECTED] wrote:


I recently upgraded to Cygwin 1.5.7(0.109/3/2), including
XWin release 4.3.0.56 installed from XFree86-bin-4.3.0-16.tar.bz2
Now when I try to run one particular remote X application (my MUA) I get
this error:
X Error of failed request:  BadAtom (invalid Atom parameter)
 Major opcode of failed request:  18 (X_ChangeProperty)
 Atom id in failed request:  0xee
 Serial number of failed request:  12
 Current serial number in output stream:  15
The remote (linux) machine has not had its sshd config changed since
2002.  It has X11Forwarding yes, and used to work fine.
If I ssh -X into the machine, DISPLAY is set to localhost:10.0


http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding
Any reason we don't tell people to use ssh -Y instead of ssh -X? 
That is the new command-line parameter to use trusted X11 forwarding and 
it works like a charm.

Harold

Re: Massive CVS update

Thank you.  These instructions will help me when I have to do the same 
thing.

Harold

Alexander Gottwald wrote:

On Wed, 17 Mar 2004, Alexander Gottwald wrote:


I will try to merge the XORG-RELEASE-1 branch more often into the 
CYGWIN branch to be as close as possible to the xorg work and be
able to make a stable release as soon as the other xorg developers
make their release.


Some words on how I do the merge:

I have the two branches checked out with this layout

xorg-release-1/xc XORG-RELEASE-1
xc-cygwin-merge/xc CYGWIN
the commands are quite simple

#
# Get the latest from XORG-RELEASE-1
#
cd xorg-release-1/xc
cvs update
#
# Mark the checked out revisions
#
cvs tag -F XORG-CYGWIN-MERGE
#
# Merge changes between XORG-CYGWIN-LAST-MERGE and XORG-CYGWIN-MERGE
#
cd ../../xc-cygwin-merge/xc
cvs update -j XORG-CYGWIN-LAST-MERGE -j XORG-CYGWIN-MERGE
#
# clean up
#
remove conflicts, check that the tree builds
#
# Commit what has changed
#
cvs commit -m merge with XORG-RELEASE-1
#
# Mark the revisions as last merge point
#
cd ../../xorg-release-1/xc
cvs tag -F -r XORG-CYGWIN-MERGE XORG-CYGWIN-LAST-MERGE
bye
ago

Re: Xemacs crash on WinXP

2004-03-18 Thread Jee Chung

Well, I may invoking by saying emacs , but all indications are that it's the X version of emacs that starts up, because if I try to start emacs from the cygwin terminal:

[EMAIL PROTECTED] ~
$ which emacs
/usr/bin/emacs
[EMAIL PROTECTED] ~
$ /usr/bin/emacs
emacs: Cannot connect to X server :0.0.
Check the DISPLAY environment variable or use `-d'.
Also use the `xhost' program to verify that it is set to permit
connections from your machine.
Is there a different way to invoke Xemacs?  I do get xemacs as part of my Cygwin install and keep it updated regularly

JC



Dr. Volker Zell wrote:

Jee == Jee Chung [EMAIL PROTECTED] writes:


Jee I start my xemacs by invoking the command emacs  via my TWM's root menu 
(coded into my .twmrc file).  The version of emacs I have on my install says that it's 21.2.1.  My 
Cygwin install appears to be cygwin-1.5.7-1 from having examined the cygwin1.dll file.
Jee JC
Aha, so it's emacs and not XEmacs. Search the list, I think there are
known problems with emacs or even better download the new proposed
version from Joe Bühler. Or maybe switch to XEmacs
Ciao
  Volker

Re: Upcoming X.org release and splitting packages

On Thu, 18 Mar 2004, Harold L Hunt II wrote:

 Frédéric L. W. Meunier wrote:
  What are the main differences between it and XFree86 4.4.0 ?
  Are things like XTerm 185 included, or everything that goes to
  XFree86 can't to X.org ?

 I don't know about XTerm 185 specifically, but this release should
 contain all fixes and features that were added to the XFree86 project's
 source code tree for the 4.4.0 release.

Most of them. X.Org's changelog doesn't give enough detail to tell
without running diff.  However diff'ing the trees shows lots of keyword
mismatches (X.Org's copy is consistently incorrect), so there's a lot
of diff to read.

xterm patch #185 is post-4.4, and according to fd.o's CVS is not in the
release-1 branch.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Re: Cygwin/Xfree on second (low res) monitor

2004-03-18 Thread Saul Cozens

In the abscense of anyone shouting 'nooo - you fool!'  I commented 
out lines 244, 245 of wincreatewnd.c and recompiled.

I was shocked and  surprised to find that  the hack worked.  I'm now 
going to familiarise myself with the code a bit more before suggesting 
how this feature could be implemented better.  Any hints on why the 
lines are there in the first place would still be appreciated.

cheers

Saul

Saul Cozens wrote:

Hi,

I've been playing with Cygwin/XFree86 for a few day now - and frankly 
I'm astounded - it's great!  However, I have one little query that I 
hope someone can help me with!

I have a dualhead video card in my Win2K box with monitor-1 set to 
1280x1024 and monitor-2 (an LCD screen) set to 1024x768.  I wish to 
have my Win2K desktop on monitor-1 and the KDE desktop (started via 
XDMCP) of my Debian/Linux box on monitor-2. With CygwinXfree86 I could 
then move between the environments so quickly and easily that my head 
would spin!

Now I thought that I would be able to achieve this by doing
   xwin -screen 0 1024 768 -query linuxhost -nodecoration -clipboard
and moving the resultant window to monitor-2, but xwin seems to ignore 
the screen resolution when '-nodecoration' is set.  This was confirmed 
when I looked at the source code
wincreatewnd.c 229-233
 /*
  * User gave a width and height but also said no decoration.
  * In this case we have to ignore the requested width and height
  * and instead use the largest possible window that we can.
  */
The same seems to be true for -rootless and (obviously) -fullscreen,  
And as -multiplemonitors is intended to allow the Xwindow to occupy 
BOTH monitors I'm stuck!

So can anyone tell me why (before I try osmething stupid like simply 
removing this override and recompiling) or simply tell me another way 
to achieve my dual desktop dreams!

many thanks

Saul Cozens

Re: Can't start a specific remote X app any more

On Thu, 18 Mar 2004, Harold L Hunt II wrote:

 If I ssh -X into the machine, DISPLAY is set to localhost:10.0
  
  
  
  http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding
 
 Any reason we don't tell people to use ssh -Y instead of ssh -X? 
 That is the new command-line parameter to use trusted X11 forwarding and 
 it works like a charm.

I was not aware of that parameter.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Re: X/Cygwin icon proposal

What is New Alpha? I sent a few on the mailing list. Was it icon_test9 
(attached again here)? This one has 24bit icons, hopefully the prefered 
format on systems not supporting the alpha channel (crossing fingers).

And what is Original? If it's the one in the recent XWin.exe then it's 
an icon with alpha too. I don't seen any different between the two on 
your screenshot.

Michael Bax wrote:
The new icon with alpha looks quite bad on Windows 2000 and earlier systems,
with a thick white border -- see the attachment PNG.  The tips of the X on
some of the other versions of the icon  also look slightly blunt (minor
quibble), and the top and bottom rows are lost at 16x16.
That can be improved. I've been on a deadline at work for a couple weeks 
now so the 16x16 is basically a simple convertion from the original 
360x360 that I'm using for to create all the icons.


Presumably we shouldn't be setting the default to something that uses a
feature unsupported by the majority of systems out there!  Alpha is nice,
but it is a new, optional feature; we still need to support low-colour
desktops by default.
I don't care about the majority of the systems out there. I care about 
the majority of the system using Cygwin/XFree. And that can be very 
different.
That has nothing to do with cygwin but look at this poll of what gamers 
have (http://steampowered.com/status/survey.html): 90% of the OS are WinXP.
Gamers tends to have very recent machines, so tend to have a recent OS. 
What I mean by giving this link is that the majority can differ 
greatly depending of what subset of people you're looking at.

Geeks (where I put Cygwin users), I assume, would have a recent machine 
as their working machine and older systems for support (firewall, 
server, ...).
So I would think that there are more XP machines out there than you 
think. Now, is it majority? I can't say but I would not be surprised at 
all if it were.

The other thing, IMHO, is that the alpha icon on non-alpha system, while 
not the best icon that can be on such system, is not completely ugly 
either. The problems with the 16x16 can easily be fixed.
So between an icon that looks best on recent machines but not as good on 
older ones and one that looks best on older machines but not as good as 
it can be on recent ones, I prefer to think future/progress/whatever 
and take the first.



Using the CVS icon as a starting point, I created a new icon using an
outlined white square as the background.  It is rendered at 16x16, 24x24 and
32x32 sizes, each for monochrome, 16 and 256 colours.  It has the correct
proportions of the thick and thin lines, properly anti-aliased and
quantised.  It's even rotationally invariant!  :-)
I have attached two files: a comparison of the icons in Overview.png, and
the improved icon in Improved.ico.
Between the CVS and your improved, I prefer the one in CVS. The thin 
lines is acutally too thin in 16x16, the line is too blury on yours, the 
white background seems to wash over the black line.

	Nahor
inline: x_test9.ico

No menu to resize an xterm window

2004-03-18 Thread fai choy

Dear cygwin staff or anyone who can help,

I'm new to cygwin.
I've installed cygwin 1.5.8-1 and after I launched the
Xdisplay with startx, there is only 1 small black
window with yellow fonts. I tried to do right-click on
the mouse to invoke the menu for me to select the
resize option when the mouse cursor turns into a
cross, but there is no menu appearing. How can I
invoke the menu?
Thank you everyone.

Rgds
Choy
Nanyang Technological University
Singapore

__
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

Re: X/Cygwin icon proposal

On Thu, 18 Mar 2004, Nahor wrote:

 What is New Alpha? I sent a few on the mailing list. Was it icon_test9 
 (attached again here)? This one has 24bit icons, hopefully the prefered 
 format on systems not supporting the alpha channel (crossing fingers).

It looks good in the tray and taskbar, but not in the titlebar. (see attached 
images)

If you can build ico files with both alpha and non-alpha icons why not include
your version with alpha channel and for non-alpha either the boxed (which I liked)
or a plain two-color variant.

bye
ago
 
 I don't care about the majority of the systems out there. I care about 
 the majority of the system using Cygwin/XFree. And that can be very 
 different.
 That has nothing to do with cygwin but look at this poll of what gamers 
 have (http://steampowered.com/status/survey.html): 90% of the OS are WinXP.
 Gamers tends to have very recent machines, so tend to have a recent OS. 
 What I mean by giving this link is that the majority can differ 
 greatly depending of what subset of people you're looking at.

 Geeks (where I put Cygwin users), I assume, would have a recent machine 
 as their working machine and older systems for support (firewall, 
 server, ...).
 So I would think that there are more XP machines out there than you 
 think. Now, is it majority? I can't say but I would not be surprised at 
 all if it were.

cygwin is unix. unix is simple (shell and stuff) and this is the opposite 
of the bubble-gum os WinXP with alpha channel. 

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Re: X/Cygwin icon proposal

On Thu, 18 Mar 2004, Alexander Gottwald wrote:

 On Thu, 18 Mar 2004, Nahor wrote:
 
  What is New Alpha? I sent a few on the mailing list. Was it icon_test9 
  (attached again here)? This one has 24bit icons, hopefully the prefered 
  format on systems not supporting the alpha channel (crossing fingers).
 
 It looks good in the tray and taskbar, but not in the titlebar. (see attached 
 images)

Forgot them. Here they are.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723attachment: ico3.pngattachment: ico2.pngattachment: ico1.png

Re: Upcoming X.org release and splitting packages

2004-03-18 Thread Jack Tanner

Harold L Hunt II wrote:
5) Rename the lib package to something more meaningful.  The name 
currently implies that it might contain link libraries or run-time 
libraries, but it really contains files shared among X packages. Perhaps 
shared-files would be a better name.  I would appreciate it if someone 
would look into what Debian and/or Fedora call this package.
Common or shared are standard for Windows software. For example, 
C:\Program Files\Common Files\Microsoft Shared, C:\Program Files\Common 
Files\Symantec Shared...

-JT

Show Root Window/Hide Root Window -- [Checked/Unchecked] Show Root Window?

I was just about to remove the tray menu icon's Show Root Window and 
Hide Root Window items and add a single checked or unchecked item 
called Show Root Window.  I figured I had better do a sanity check and 
ask if there was a reason that this was not done in the first place... I 
can't remember if I didn't do it this was just because I didn't know the 
right functions to call, or if there was as valid but hidden reason for 
doing this.  Can anyone else recall a reason why this should not be done 
with a check mark next to the menu item?  It is supposed to be supported 
since Windows 95, so compatibility is not an issue.

Harold

Re: X/Cygwin icon proposal

Alexander Gottwald wrote:
It looks good in the tray and taskbar, but not in the titlebar. (see attached 
images)
You forgot to attach it... ok, got the other mail.


If you can build ico files with both alpha and non-alpha icons why not include
your version with alpha channel and for non-alpha either the boxed (which I liked)
or a plain two-color variant.
The issue is not (or not yet at least) about the non-alpha part being 
ugly, they are about the same than the old xwin icon. The problem is 
when a non-alpha system try to use the alpha-icon. Then you get that fat 
white line around the X or the garbled icon on NT (I assume).
So putting the white square for the non-alpha would not fix anything if 
the system doesn't select it over the 32b icon.

...
ok, from your images, your system at least uses the non-alpha icons. 
What color resolution is your monitor at?


cygwin is unix. unix is simple (shell and stuff) and this is the opposite 
of the bubble-gum os WinXP with alpha channel. 
Uh? I don't get your point. I personally don't buy a machine just to run 
unix. I use it to do other stuff (mostly compilation) that do make use 
of CPU power. So I have a recent machine, so I have XP. I assume that 
quit a dew (most?) geeks using Cygwin/XFree would be in the same case. 
But it's just a guess.

	Nahor

setup.exe copies files to wrong place

2004-03-18 Thread tulitanssi

Hello,

setup.exe seems to copy some files, e.g. font files, to a wrong drive.

For example, if setup.exe is located (and run) at D:\cygwin_install directory and
the target directory is C:\cygwin, then setup.exe copies lots of stuff
to D:\cygwin\usr\X11R6\lib\X11\fonts\...

It would seem that somewhere the target root is set to \cygwin instead of C:\cygwin ?

Tuli


..
 MTV3 Laajakaista - Hauskemman elämän puolesta.
 http://www.mtv3.fi/liittyma/hankinta/laajakaista/

Re: setup.exe copies files to wrong place

[EMAIL PROTECTED] wrote:

Hello,

setup.exe seems to copy some files, e.g. font files, to a wrong drive.

For example, if setup.exe is located (and run) at D:\cygwin_install directory and
the target directory is C:\cygwin, then setup.exe copies lots of stuff
to D:\cygwin\usr\X11R6\lib\X11\fonts\...
It would seem that somewhere the target root is set to \cygwin instead of C:\cygwin ?
No.

You have the 2nd problem described here:

http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof

Whether or not you admit it or know it, you at one time had Cygwin 
installed to d:\cygwin, which left in place a pointer to 
d:\cygwin\usr\X11R6\lib\X11\fonts as the location where fonts should be 
unpacked to.

Run 'mount', you may or may not notice that /usr/X11R6/lib/X11/fonts 
still points to the D drive (this was likely already corrected by the 
postinstall step).

I'm seeing this so often that I am *almost* motivated enough to write a 
patch to setup.exe to bitch when there are invalid mount points and 
asking the user if they would like to remove those mount points before 
unpacking packages.

Harold

Emacs menus act strangely

2004-03-18 Thread tulitanssi

Hi,

I just installed all new packages of X. Now when I start emacs from xterm's menu,
and try to click a menu from newly started emacs, the menu pops up away from
its usual place and doesn't work.

Cheers,
Tuli


..
 MTV3 Laajakaista - Hauskemman elämän puolesta.
 http://www.mtv3.fi/liittyma/hankinta/laajakaista/

Re: Emacs menus act strangely

[EMAIL PROTECTED] wrote:

Hi,

I just installed all new packages of X. Now when I start emacs from xterm's menu,
and try to click a menu from newly started emacs, the menu pops up away from
its usual place and doesn't work.
Already been reported and a fix is on the way.

Harold

Re: Xemacs crash on WinXP

2004-03-18 Thread Alejandro López-Valencia

On Thu, 18 Mar 2004 11:09:46 -0500, Jee Chung wrote in
[EMAIL PROTECTED]:

Well, I may invoking by saying emacs , but all indications are that it's the X 
version of emacs that starts up, because if I try to start emacs from the cygwin 
terminal:

[EMAIL PROTECTED] ~
$ which emacs
/usr/bin/emacs

Give yourself a tour by these two web sites:

http://www.xemacs.org/
http://www.gnu.org/software/emacs/emacs.html

And discover how unreasonable are your previous words...

Re: setup.exe copies files to wrong place

2004-03-18 Thread tulitanssi

Hi Harold,

and thanks for the fast response. All I admit is that I don't remember whether I 
installed it on D drive also ... ;)

But it is a good idea that setup.exe would warn if user is doing something which seems 
to be wrong.

Cheers,
Tuli

..
 MTV3 Laajakaista - Hauskemman elämän puolesta.
 http://www.mtv3.fi/liittyma/hankinta/laajakaista/

Re: X/Cygwin icon proposal

2004-03-18 Thread Benjamin Riefenstahl

Hi Nahor,


Nahor [EMAIL PROTECTED] writes:
 Geeks (where I put Cygwin users), I assume, would have a recent
 machine as their working machine and older systems for support
 (firewall, server, ...).
 So I would think that there are more XP machines out there than you
 think. Now, is it majority? I can't say but I would not be surprised
 at all if it were.

I can only speak for myself, of course.  But if I can avoid it I am
not going to buy XP anytime soon because of the licensing hassles.


benny

Re: Starting X server on cygwin

2004-03-18 Thread Danielle

Well, I've looked at that address and I've done all they asked but it still doesn't 
work. I've done as followS:


[EMAIL PROTECTED] ~
$ sh /usr/X11R6/bin/startxwin.sh

[EMAIL PROTECTED] ~
$ cp /etc/X11/xinit/xinitrc ~/.xinitrc

[EMAIL PROTECTED] ~
$ cd /usr/X11R6/bin  startx
bash: startx: command not found

[EMAIL PROTECTED] /usr/X11R6/bin
$ cd /usr/X11R6/bin/startx
bash: cd: /usr/X11R6/bin/startx: Not a directory

[EMAIL PROTECTED] /usr/X11R6/bin
$ PATH=%PATH:/usr/X11R6/bin

[EMAIL PROTECTED] /usr/X11R6/bin
$ startx
[: and: unknown operand
[: and: unknown operand
export: Settings/Danielle/.Xauthority: bad variable name

but I receive a message telling that the cygwin1.dll can't be found, but i have it in 
c:\cygwin\bin.

I've been trying to install a simulator player stage but it looks for X server and 
can't find it. I just can't make it work.

Thanks,
Dani.


It seems from the approach taken that you have not taken the time to
RTFM.  Take a look at:

http://x.cygwin.com/docs/ug/using.html#using-starting

Lou

* Danielle [EMAIL PROTECTED] [2004-03-18 10:17]:
 I've installed cygwin with all XFree86 options marked but I can't make it work.

 When I type X or startx command lines appears like that:

 [EMAIL PROTECTED] /cygdrive/c/cygwin/usr/X11R6/bin
 $ X
 bash: X: command not found

 [EMAIL PROTECTED] /cygdrive/c/cygwin/usr/X11R6/bin
 $ startx
 bash: startx: command not found

 [EMAIL PROTECTED] /cygdrive/c/cygwin/usr/X11R6/bin
 $ ./startx
 [: and: unknown operand
 [: and: unknown operand
 export: Settings/Danielle/.Xauthority: bad variable name
 xinit: not found

 What should I do?

 Thanks,
 Dani.

Re: X/Cygwin icon proposal

Nahor wrote:

 ok, from your images, your system at least uses the non-alpha icons.
 What color resolution is your monitor at?

16bit

  cygwin is unix. unix is simple (shell and stuff) and this is the opposite
  of the bubble-gum os WinXP with alpha channel.

 Uh? I don't get your point. I personally don't buy a machine just to run
 unix. I use it to do other stuff (mostly compilation) that do make use
 of CPU power.

The host I use at work is win2k. We have bought our _first_ XP host last
week. I don't know any company which choose XP over 2000. XP requries a
lot more resources than 2000 and a computer magizine even stated that XP
wastes about 200MHz. (2Ghz with XP is as fast as 1.8Ghz with win2k)
The other host is linux since compiling with cygwin is so slow (the 500Mhz
host compiles the xorg tree much faster than the 1.8Ghz windows/cygwin host)

 So I have a recent machine, so I have XP. I assume that
 quit a dew (most?) geeks using Cygwin/XFree would be in the same case.
 But it's just a guess.

This is a wild guess. gamers usally spend more on recent hardware than
geeks. geeks by unusual, cool hardware. but speed is not as important as
for gamers.

bye
ago

NP: Dekoy - Darkest Eve
-- 
 [EMAIL PROTECTED]
 http://www.gotti.org   ICQ: 126018723

Re: Urgent: Help with startxwin.bat

Neto, Antonio Jose Rodrigues wrote:

 But, when I click on X (Show Root Window) - my screen and my mouse are
 frozen and the Xwin.exe process is 100%.

I found the bug and it is fixed in the next release.

bye
ago
NP: Dekoy - Darkest Eve
-- 
 [EMAIL PROTECTED]
 http://www.gotti.org   ICQ: 126018723

Re: X/Cygwin icon proposal

Alexander Gottwald wrote:
Nahor wrote:


ok, from your images, your system at least uses the non-alpha icons.
What color resolution is your monitor at?


16bit


cygwin is unix. unix is simple (shell and stuff) and this is the opposite
of the bubble-gum os WinXP with alpha channel.
Uh? I don't get your point. I personally don't buy a machine just to run
unix. I use it to do other stuff (mostly compilation) that do make use
of CPU power.


The host I use at work is win2k. We have bought our _first_ XP host last
week. I don't know any company which choose XP over 2000. XP requries a
lot more resources than 2000 and a computer magizine even stated that XP
wastes about 200MHz. (2Ghz with XP is as fast as 1.8Ghz with win2k)
The other host is linux since compiling with cygwin is so slow (the 500Mhz
host compiles the xorg tree much faster than the 1.8Ghz windows/cygwin host)
Nonsense.  I have it running on an AMD K6-2 400 MHz chip with 384 MB RAM 
and it is *fast* once it finishes booting (which it does more quickly 
than even NT 4.0).  My wife uses this machine with OpenOffice.org and 
Mozilla at work with no performance complaints.  Before I sent it over 
to her job (she works at a university lab that didn't have enough money 
to buy her a computer) I was using it as my *primary* development 
machine at my job, running copies Visual Interdev 6.0, Visual Studio.NET 
2002, compiling lots of source code, running a web server, etc.  All of 
this with the eye candy settings left at the defaults.

So we are getting a little off topic here, but there is nothing about XP 
that makes it inherently slow or that makes it require a super fast 
machine to run.

So I have a recent machine, so I have XP. I assume that
quit a dew (most?) geeks using Cygwin/XFree would be in the same case.
But it's just a guess.


This is a wild guess. gamers usally spend more on recent hardware than
geeks. geeks by unusual, cool hardware. but speed is not as important as
for gamers.
Heh heh...

Harold

Interim source package compilation instructions

Here are some interim instructions for building the source packages 
until I update the Contributor's Guide (verified to work by a friend on 
another Cygwin install):

1) At the top of the following page is a list of packages that are
required for compiling Cygwin/X.  I recommend putting setup.exe in
Full view and just scanning the lists next two each other... it should
only take a few seconds to pick all of the packages... if it takes
longer you are trying too hard.
http://x.cygwin.com/docs/cg/prog-build-native.html

2) Next, you need to grab the source packages via setup.exe for the
following  (click the blank box in the src column for each of these
packages, it should turn to either a cross or an na (yes, that is dumb,
but that it what it does)).:
XFree86-base
XFree86-bin
XFree86-fenc
XFree86-fnts
XFree86-fscl
XFree86-man
XFree86-prog
XFree86-xserv
3) Cut and paste the following little ditty into a Cygwin bash shell. It
should finish in around than two hours, maybe more if you are slower
than an Athlon 1.2 GHz/512 MB RAM/7200 RPM HD.  After about 5 to 15
minutes you should see a file called /usr/src/build.log get created and
it will grow to about 3.4 MB before it is done.  Then
/usr/src/install.log will get created and will grow to about 1.3 MB
before it is done.  Then you will see lots of output in the console and
the final result should be less than 30 minutes away and should look
like a tar command ending (because it is).
cd /usr/src  \
cp xc/CYGWIN-PATCHES/XFree86-4.3.0.sh .  \
./XFree86-4.3.0.sh mkdirs  \
./XFree86-4.3.0.sh conf  \
./XFree86-4.3.0.sh build  build.log 21  \
./XFree86-4.3.0.sh install  install.log 21  \
./XFree86-4.3.0.sh strip  \
./XFree86-4.3.0.sh pkg  \
./XFree86-4.3.0.sh spkg
4) If you want to perform a clean rebuild, just run the following
command first before repeating step #3.  Beware that removing thousands
of files on my machine takes between 5 and 25 minutes (it varies for
some reason) and could take up to an hour if the Windows machine is
particularly slow.  Of course, Linux with ResierFS completes this
operation immediately.
cd /usr/src  \
./XFree86-4.3.0.sh quickclean
Harold

Re: Emacs menus act strangely

Howdy all,

 Subject: Re: Emacs menus act strangely
  I just installed all new packages of X. Now when I start emacs from xterm's menu,
  and try to click a menu from newly started emacs, the menu pops up away from
  its usual place and doesn't work.
 Already been reported and a fix is on the way.

It's in the CVS as of this morning, if you can compile yourself then just
cvs update and make Xwin.exe, OTW we'll have to wait for a new test
release...
-- 
-Earle F. Philhower, III
 [EMAIL PROTECTED]
 http://www.ziplabel.com

Re: Interim source package compilation instructions

On Thu, 18 Mar 2004, Harold L Hunt II wrote:

 4) If you want to perform a clean rebuild, just run the following
 command first before repeating step #3.  Beware that removing thousands
 of files on my machine takes between 5 and 25 minutes (it varies for
 some reason) and could take up to an hour if the Windows machine is

cygwin's file-delete is very slow.  Generally the Windows delete is much
faster (even counting emptying the trash).

 particularly slow.  Of course, Linux with ResierFS completes this
 operation immediately.

sort of.  I've observed that there's a big performance hit when I untar
large files or do other operations that create new files.  Haven't noticed
that it's an faq though.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

I cannot read a pdf file with gv

2004-03-18 Thread R. Manitra

Hello everyone,

I have a little problem using gv. Actually, when I try to view pdf file
I got a dialog box pops up with the following error message: 

---

Error: /invalidfileaccess in --file--
Operand stack:
   (/home/manitra/document_file_1.2.pdf)   (r)
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--  
--nostringval--   2   %stopped_push   --nostringval--  
--nostringval--   --nostringval--   false   1   %stopped_push   1   3  
%oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   1   3  
%oparray_pop   .runexec2   --nostringval--   --nostringval--  
--nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1109/1686(ro)(G)--   --dict:0/20(G)--   --dict:75/200(L)--  
--dict:104/127(ro)(G)--   --dict:238/347(G)--
Current allocation mode is local
AFPL Ghostscript 8.14: Unrecoverable error, exit code 1

--

However, I can open without any trouble any PS document. At first, I
thought that there was some problem with my ghostscript installation. I
did reinstall the latest version (Ghostscript 8.14) with all of the
third party libraries (jpeg, libnpg, zlib) as well as the fonts, but I
still get the same error message.

I use linux redhat 9.

Any help would be appreciated. 

Thank you very much.

R. Manitra

Re: Interim source package compilation instructions

Thomas Dickey wrote:

On Thu, 18 Mar 2004, Harold L Hunt II wrote:


4) If you want to perform a clean rebuild, just run the following
command first before repeating step #3.  Beware that removing thousands
of files on my machine takes between 5 and 25 minutes (it varies for
some reason) and could take up to an hour if the Windows machine is


cygwin's file-delete is very slow.  Generally the Windows delete is much
faster (even counting emptying the trash).
Are you referring to a delete through Windows Explorer?  I assume you 
are because you are referring to the trash.  In fact, I quite often do a 
Shift+Delete on the folder to delete it without sending it to the trash, 
but this takes just as long if not longer.  NTFS was just not designed 
for several thousand files, nor does it allow for good delete 
performance of entire directory trees.  Not to say that those were bad 
decisions, they were basically trade offs that they had to make to do 
other things, but it is annoying.

particularly slow.  Of course, Linux with ResierFS completes this
operation immediately.


sort of.  I've observed that there's a big performance hit when I untar
large files or do other operations that create new files.  Haven't noticed
that it's an faq though.
Not sure if you are talking about a performance hit under Cygwin or 
Linux?  I agree, untarring on Cygwin is horribly slow for large files. 
Linux usually doesn't have a problem with operations on thousands of 
files, at least not for me.

Harold

Re: Emacs menus act strangely

Earle F. Philhower, III wrote:

Howdy all,


Subject: Re: Emacs menus act strangely

I just installed all new packages of X. Now when I start emacs from xterm's menu,
and try to click a menu from newly started emacs, the menu pops up away from
its usual place and doesn't work.
Already been reported and a fix is on the way.


It's in the CVS as of this morning, if you can compile yourself then just
cvs update and make Xwin.exe, OTW we'll have to wait for a new test
release...
Huh... I didn't see the email message, so it must have gotten held up. 
I'll do an update and release it if it comes down.

Harold

Re: Cygwin/Xfree on second (low res) monitor

Saul,

Saul Cozens wrote:

In the abscense of anyone shouting 'nooo - you fool!'  I commented 
out lines 244, 245 of wincreatewnd.c and recompiled.
I like people compiling the source themselves and fixing their own 
problems.  Thanks for this :)

However, it would be useful if you sent in a diff so that we knew sort 
of what you were talking about and could maybe offer some tips.  I guess 
you got the code from CVS, in which case you could:

cd programs/Xserver/hw/xwin
cvs -z3 diff -u wincreatewnd.c  wincreatewnd.c.diff
If you got it from the src packages via setup.exe, then you would have 
to untar the original source and do something like the following:

cd /usr/src
diff xc-orig/programs/Xserver/hw/xwin/wincreatewnd.c \
xc/programs/Xserver/hw/xwin/wincreatewnd.c \
 wincreatewnd.c.diff
I was shocked and  surprised to find that  the hack worked.  I'm now 
going to familiarise myself with the code a bit more before suggesting 
how this feature could be implemented better.  Any hints on why the 
lines are there in the first place would still be appreciated.
I'm not sure why it works since I don't know what you changed. :)  I 
looked and saw comments at 244 and 245.

Harold

Re: X/Cygwin icon proposal

An icon doesn't deserve *this* much attention, but...

Nahor wrote...
 Subject: Re: X/Cygwin icon proposal
 Alexander Gottwald wrote:
  It looks good in the tray and taskbar, but not in the titlebar. (see attached 
  images)
  If you can build ico files with both alpha and non-alpha icons why not include
  your version with alpha channel and for non-alpha either the boxed (which I  
  liked)
  or a plain two-color variant.
..
  cygwin is unix. unix is simple (shell and stuff) and this is the opposite 
  of the bubble-gum os WinXP with alpha channel. 
 Uh? I don't get your point. I personally don't buy a machine just to run 
 unix. I use it to do other stuff (mostly compilation) that do make use 
 of CPU power. So I have a recent machine, so I have XP. I assume that 
 quit a dew (most?) geeks using Cygwin/XFree would be in the same case. 
 But it's just a guess.

Here's my two cents on the issue, as someone who has supported
an application for 7 years that, at one time, supported everything
from Win 3.1 w/Win32s through Windows XP:
   - Default to a safe setting for anything that's not critical. -
You'll save TONS of user grief, and by extension, your own.

Sure, at home I run WinXP.  But at my office, and lots of other
offices where XWin.exe is used people are still using Win NT or 2K.
You can't just go to your IT department and say gimme WinXP,
it's new and makes things faster and more fun!  And from the 
recent list archives it seems like there are home users w/Win98
using cygwin.

Default to a safe icon format but include the XP specific
one in the exe.  You can access it with a line TRAYICON ,101 in
your .xwinrc file no matter what.

Or, fix the code to detect the OS.  If OS=Win5.0 use alpha icon,
OTW use standard icon.  That can be done at runtime w/a few lines
of C.
-- 
-Earle F. Philhower, III
 [EMAIL PROTECTED]
 http://www.ziplabel.com

Re: Emacs menus act strangely

My change email has been spotty, I've only received notice of one
CVS commit I did myself.  Plus, it seems like freedesktop.org is
having some troubles: their website is inaccessible right now
at 12:45PM PST...

-- Original Message -
 Subject: Re: Emacs menus act strangely
 Date: Thu, 18 Mar 2004 15:18:01 -0500
 From: Harold L Hunt II [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 ...
 Huh... I didn't see the email message, so it must have gotten held up. 
 I'll do an update and release it if it comes down.
-- 
-Earle F. Philhower, III
 [EMAIL PROTECTED]
 http://www.ziplabel.com

Re: Upcoming X.org release and splitting packages

On Thu, 18 Mar 2004, [ISO-8859-1] Frédéric L. W. Meunier wrote:

 On Thu, 18 Mar 2004, Thomas Dickey wrote:
  xterm patch #185 is post-4.4, and according to fd.o's CVS is not in the
  release-1 branch.

 It may be worth to make it a separate package and start using
 your sources from http://invisible-island.net/xterm/ when
 they're newer (most of the time).

Not exactly - though I maintain my own rcs archives of xterm, the patch
numbers do correspond to commits in XFree86.  So there's no difference
from that standpoint (of being newer).  Occasionally there's a minor bug
fix I add to XFree86 but don't make a new xterm patch, but the reverse is
not true.

However, I do make xterm patches more frequently than XFree86 releases
occur - that's simply a matter of 60,000 lines of code compared to 3
million...

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Re: XWin Architecture

2004-03-18 Thread Jeremy Wilkins

snip
Something isn't right here.  I haven't seen Objective C in the 
miext/rootless code and it is compiled with gcc, not an Objective C 
compiler... are you sure you are looking at a publically released 
version of the code for all platforms?  I just took a look at 
rootlessWindow.c and it reads like straight C to me.  There may be a few 
files that are conditionally compiled for Mac OS/X that use Objective C, 
in which case you could ignore those.

Harold

Sorry didn't explain - I was trying to understand the code in hw/darwin 
- which I think uses miext/rootless to implement their X server.

Jeremy

Re: Upcoming X.org release and splitting packages

Thomas Dickey wrote:

On Thu, 18 Mar 2004, [ISO-8859-1] Frédéric L. W. Meunier wrote:


On Thu, 18 Mar 2004, Thomas Dickey wrote:

xterm patch #185 is post-4.4, and according to fd.o's CVS is not in the
release-1 branch.
It may be worth to make it a separate package and start using
your sources from http://invisible-island.net/xterm/ when
they're newer (most of the time).


Not exactly - though I maintain my own rcs archives of xterm, the patch
numbers do correspond to commits in XFree86.  So there's no difference
from that standpoint (of being newer).  Occasionally there's a minor bug
fix I add to XFree86 but don't make a new xterm patch, but the reverse is
not true.
However, I do make xterm patches more frequently than XFree86 releases
occur - that's simply a matter of 60,000 lines of code compared to 3
million...
I think this is reason alone for it to be a separate package.

I have this built as a Cygwin package using the default configure 
options at the moment.  The only patch required was to Makefile.in 
(attached) to get it to stop appending .exe to the uxterm shell script.

Thomas, can you recommend any configure options we should be using?  I 
can think that the following might be useful:

--enable-toolbar
--enable-wide-chars
--with-Xaw3d
Any thoughts?

Harold
--- Makefile.in.orig2003-12-31 12:12:25.0 -0500
+++ Makefile.in 2004-03-18 16:17:56.842128000 -0500
@@ -139,14 +139,13 @@
 actual_resize = `echo resize|   sed '$(transform)'`
 binary_xterm  = `echo xterm$x|  $(TRANSFORM)`
 binary_resize = `echo resize$x| $(TRANSFORM)`
-binary_uxterm = `echo uxterm|   $(TRANSFORM)`
 
 install \
 install-bin \
 install-full :: xterm$x resize$x $(BINDIR)
$(SHELL) $(srcdir)/sinstall.sh $(INSTALL_PROGRAM) xterm$x  @XTERM_PATH@ 
$(BINDIR)/$(binary_xterm)
$(INSTALL_PROGRAM) -s -m  755 resize$x $(BINDIR)/$(binary_resize)
-   $(INSTALL_SCRIPT) -m  755 $(srcdir)/uxterm $(BINDIR)/$(binary_uxterm)
+   $(INSTALL_SCRIPT) -m  755 $(srcdir)/uxterm $(BINDIR)/uxterm
 
 install \
 install-man \
@@ -189,7 +188,7 @@
 uninstall:
-$(RM) $(BINDIR)/$(binary_xterm)
-$(RM) $(BINDIR)/$(binary_resize)
-   -$(RM) $(BINDIR)/$(binary_uxterm)
+   -$(RM) $(BINDIR)/uxterm
-$(RM) $(MANDIR)/$(actual_xterm).$(manext)
-$(RM) $(MANDIR)/$(actual_resize).$(manext)
-$(RM) $(APPSDIR)/$(CLASS)

FYI: Newest Xwin / cygwin breaks kde 3.1.4

2004-03-18 Thread Bovy, Stephen J

The kde init splash screen appears,  it hangs on the
window manager init for a long time, and then it crashes
into the bit bucket.

Re: Upcoming X.org release and splitting packages

On Thu, 18 Mar 2004, Harold L Hunt II wrote:

 I have this built as a Cygwin package using the default configure
 options at the moment.  The only patch required was to Makefile.in
 (attached) to get it to stop appending .exe to the uxterm shell script.

 Thomas, can you recommend any configure options we should be using?  I
 can think that the following might be useful:

 --enable-toolbar

that's broken (some incompatible changes to Xaw from XFree86 4.4 that
I've not gotten around to investigating0.

 --enable-wide-chars

you need this for uxterm

 --with-Xaw3d

Some people like it.  Actually all of the Xaw flavors look very much alike
to me.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Re: Upcoming X.org release and splitting packages

On Thu, 18 Mar 2004, [ISO-8859-1] Frédéric L. W. Meunier wrote:

 Thomas, am (are) I (we) missing anything ? Are there any other
 options that are enabled or disabled in the xc version ?

Perhaps --enable-luit (though I don't recall if anyone's mentioned using
it with cygwin).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Re: X/Cygwin icon proposal

Earle F. Philhower, III wrote:
Default to a safe icon format
Beep, sorry, you're computer was taken over by the icon then crashed, 
please reboot :)
But anyway, the alpha *is* safe for other OS (well maybe not for NT, 
but I haven't heard back from haro about icon_test9 which seems to work 
fine for Alexander). It may not be to your taste but it is recognizable 
as the X logo.


Or, fix the code to detect the OS.  If OS=Win5.0 use alpha icon,
OTW use standard icon.  That can be done at runtime w/a few lines
of C.
Which one? The monochrome one? Or the one with the white background? 
Maybe the old one with the white specks? And how do you do the runtime 
thingy when XWin isn't running and Windows displays the icon in Explorer?

Maybe Halrold should only distribute the source code, and let people 
recompile xwin.exe by themselves that way they can choose their own 
prefered icon for the binary.

All that just for a stoopid icon. Baah...

	Nahor

Re: X/Cygwin icon proposal

Alexander Gottwald wrote:
ok, from your images, your system at least uses the non-alpha icons.
What color resolution is your monitor at?
16bit
That looks cool. Could you try in 24/32b and see if still get a thin 
white border? If it does, then Windows does select the correct non-alpha 
icon.
Another way to confirm it, did the older icons (test6 and earlier) also 
displayed thin borders?

	Nahor
inline: x_test6.ico

Re: I cannot read a pdf file with gv

2004-03-18 Thread Eric Hanchrow

 RM == R Manitra [EMAIL PROTECTED] writes:

RM Actually, when I try to view pdf file I got a dialog box pops
RM up with the following error message:

I just had a similar problem -- I couldn't open certain PDF documents
with gv.  (I was able to open them with no trouble with xpdf, but I
don't remember if Cygwin includes that program.)  I don't know if my
problem is the same as yours, but in any case, here's what I learned:
There are a number of different versions of the PDF standard, and
apparently GhostScript can only deal with some of them.  I found that
it worked just fine with version 1.3, but couldn't open version 1.5 (I
never tried version 1.4).

You can see which version your file is by simply running the `file'
command, like this:

$ file doc.pdf
doc.pdf: PDF document, version 1.3
$ 

-- 
Always code as if the guy who ends up maintaining your code will
be a violent psychopath who knows where you live.  John F. Woods

Re: Show Root Window/Hide Root Window -- [Checked/Unchecked] Show Root Window?

2004-03-18 Thread Jack Tanner

Harold L Hunt II wrote:

I was just about to remove the tray menu icon's Show Root Window and 
Hide Root Window items and add a single checked or unchecked item 
called Show Root Window.  I figured I had better do a sanity check and 
ask if there was a reason that this was not done in the first place... I 
can't remember if I didn't do it this was just because I didn't know the 
right functions to call, or if there was as valid but hidden reason for 
doing this.  Can anyone else recall a reason why this should not be done 
with a check mark next to the menu item?  It is supposed to be supported 
since Windows 95, so compatibility is not an issue.
http://sources.redhat.com/ml/cygwin-xfree/2003-06/msg00084.html.

:)

If you're out messing with the tray menu, you might also change Exit 
to Close and add an X (close) icon next to it... (to see what I mean, 
right-click on a Windows Explorer menu in the task bar).

-JT

Re: Cygwin/Xfree on second (low res) monitor

2004-03-18 Thread Saul Cozens

Unfortunately anoncvs.xfree86.org is unreachable at the moment, so I got 
an original copy of wincreatewnd.c and did a manual diff:

$ diff wincreatewnd.c wincreatewnd.c.orig
255,256c255,256
 //iWidth = GetSystemMetrics (SM_CXSCREEN);
 //iHeight = GetSystemMetrics (SM_CYSCREEN);
---
 iWidth = GetSystemMetrics (SM_CXSCREEN);
 iHeight = GetSystemMetrics (SM_CYSCREEN);
as you said- I got the line numbers wrong - I've must've been tinkering 
elsewhere.  Anyway, I can start this up with:
   XWin.exe -query linuxbox -screen 0 1024 768 -rootless -lesspointer 
-clipboard
and I do get a 1024x768 borderless window (on my 1280x1024 monitor-1) , 
which I can then move to monitor-2 using the Matrox PowerDesk hotkey for 
'swap Active Window'.

I'm now seeing if I can add an [-offset left top] command line 
option to save me that hotkey press!

any guidance appreciated,

Saul

Harold L Hunt II wrote:

Saul,

Saul Cozens wrote:

In the abscense of anyone shouting 'nooo - you fool!'  I 
commented out lines 244, 245 of wincreatewnd.c and recompiled.


I like people compiling the source themselves and fixing their own 
problems.  Thanks for this :)

However, it would be useful if you sent in a diff so that we knew sort 
of what you were talking about and could maybe offer some tips.  I 
guess you got the code from CVS, in which case you could:

cd programs/Xserver/hw/xwin
cvs -z3 diff -u wincreatewnd.c  wincreatewnd.c.diff
If you got it from the src packages via setup.exe, then you would have 
to untar the original source and do something like the following:

cd /usr/src
diff xc-orig/programs/Xserver/hw/xwin/wincreatewnd.c \
xc/programs/Xserver/hw/xwin/wincreatewnd.c \
 wincreatewnd.c.diff
I was shocked and  surprised to find that  the hack worked.  I'm now 
going to familiarise myself with the code a bit more before 
suggesting how this feature could be implemented better.  Any hints 
on why the lines are there in the first place would still be 
appreciated.


I'm not sure why it works since I don't know what you changed. :)  I 
looked and saw comments at 244 and 245.

Harold

Re: Can't start a specific remote X app any more

2004-03-18 Thread luke . kendall

On 18 Mar, Alexander Gottwald wrote:
   
   
  http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding 
   
  bye 

No, I read that before I posted (I should have said so, sorry).  Other X
applications start (sometimes - see below).

My investigations suggest that waiting 10 minutes and trying again is
a workaround.

But Harold's suggestion (to use trusted X forwarding), has worked twice
in succession now with no need for a 10 minute pause to get things
working, so that seems to be a solution.

I still don't understand why a 10 minute pause was needed with
old-style X forwarding, but hey, it works with -Y.

Thanks, Harold.

   X Error of failed request:  BadAtom (invalid Atom parameter) 
 Major opcode of failed request:  18 (X_ChangeProperty) 
 Atom id in failed request:  0xee 
 Serial number of failed request:  12 
 Current serial number in output stream:  15 
 
 I tried running the MUA from inside gdb, and it worked. 
 Basically, this is what happened
 
   postilion -- error message above
   repeat 3 times
   ssh -X to my Linux machine
   postilion -- error message above
   xmessage -- ok
   tkxplanet -- ok
   postilion inside gdb -- ok
   postilion -- ok
   # log out
   postilion -- this error message:
 
 X Error of failed request:  BadAtom (invalid Atom parameter)
   Major opcode of failed request:  20 (X_GetProperty)
   Atom id in failed request:  0xee
   Serial number of failed request:  11
   Current serial number in output stream:  11
 
   ssh -X to my Linux machine
 
 $ tkxplanet
 X Error of failed request:  BadAtom (invalid Atom parameter
   Major opcode of failed request:  20 (X_GetProperty)
   Atom id in failed request:  0xee
   Serial number of failed request:  11
   Current serial number in output stream:  11
 $ xmessage ok
 $ tkxplanet
 X Error of failed request:  BadAtom (invalid Atom parameter)
   Major opcode of failed request:  20 (X_GetProperty)
   Atom id in failed request:  0xee
   Serial number of failed request:  11
   Current serial number in output stream:  11
 
 I haven't managed to run the MUA a 2nd time.
 
 Ah.  Having just typed all this up, I just tried again in case it might
 be time related.  Since both times it worked, it was about 10 minutes
 after a series of failures.  Sure enough, it's working again at the
 moment.
 
 Any idea what might be going on here?

luke

Re: Can't start a specific remote X app any more

2004-03-18 Thread Igor Pechtchanski

On Fri, 19 Mar 2004 [EMAIL PROTECTED] wrote:

 On 18 Mar, Alexander Gottwald wrote:
 
   http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding
 
   bye

 No, I read that before I posted (I should have said so, sorry).  Other X
 applications start (sometimes - see below).

You didn't read far enough.  Try scrolling down ~15 lines to Starting
with OpenSSH 3.8...
Igor

 My investigations suggest that waiting 10 minutes and trying again is
 a workaround.

 But Harold's suggestion (to use trusted X forwarding), has worked twice
 in succession now with no need for a 10 minute pause to get things
 working, so that seems to be a solution.

 I still don't understand why a 10 minute pause was needed with
 old-style X forwarding, but hey, it works with -Y.

 Thanks, Harold.

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Atom id in failed request:  0xee
  Serial number of failed request:  12
  Current serial number in output stream:  15
 
  I tried running the MUA from inside gdb, and it worked.
  Basically, this is what happened
 
postilion -- error message above
repeat 3 times
ssh -X to my Linux machine
postilion -- error message above
xmessage -- ok
tkxplanet -- ok
postilion inside gdb -- ok
postilion -- ok
# log out
postilion -- this error message:
 
  X Error of failed request:  BadAtom (invalid Atom parameter)
Major opcode of failed request:  20 (X_GetProperty)
Atom id in failed request:  0xee
Serial number of failed request:  11
Current serial number in output stream:  11
 
ssh -X to my Linux machine
 
  $ tkxplanet
  X Error of failed request:  BadAtom (invalid Atom parameter
Major opcode of failed request:  20 (X_GetProperty)
Atom id in failed request:  0xee
Serial number of failed request:  11
Current serial number in output stream:  11
  $ xmessage ok
  $ tkxplanet
  X Error of failed request:  BadAtom (invalid Atom parameter)
Major opcode of failed request:  20 (X_GetProperty)
Atom id in failed request:  0xee
Serial number of failed request:  11
Current serial number in output stream:  11
 
  I haven't managed to run the MUA a 2nd time.
 
  Ah.  Having just typed all this up, I just tried again in case it might
  be time related.  Since both times it worked, it was about 10 minutes
  after a series of failures.  Sure enough, it's working again at the
  moment.
 
  Any idea what might be going on here?

 luke

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster.  -- Patrick Naughton

Re: Cygwin/Xfree on second (low res) monitor

Saul,

Saul Cozens wrote:

Unfortunately anoncvs.xfree86.org is unreachable at the moment, so I got 
an original copy of wincreatewnd.c and did a manual diff:
Wrong CVS tree:

http://x.cygwin.com/devel/server/

$ diff wincreatewnd.c wincreatewnd.c.orig
255,256c255,256
 //iWidth = GetSystemMetrics (SM_CXSCREEN);
 //iHeight = GetSystemMetrics (SM_CYSCREEN);
---
  iWidth = GetSystemMetrics (SM_CXSCREEN);
  iHeight = GetSystemMetrics (SM_CYSCREEN);
as you said- I got the line numbers wrong - I've must've been tinkering 
elsewhere.  Anyway, I can start this up with:
   XWin.exe -query linuxbox -screen 0 1024 768 -rootless -lesspointer 
-clipboard
and I do get a 1024x768 borderless window (on my 1280x1024 monitor-1) , 
which I can then move to monitor-2 using the Matrox PowerDesk hotkey for 
'swap Active Window'.

I'm now seeing if I can add an [-offset left top] command line 
option to save me that hotkey press!
It sounds like you would be better served by an option that allows you 
to specify which Windows monitor to run on?

Harold

Re: X/Cygwin icon proposal

Howdy Nahor,

For someone who's entire contribution to XWin has been
an alpha-blended X icon you've got some loud opinions...

 Subject: Re: X/Cygwin icon proposal
 From: Nahor [EMAIL PROTECTED]
 Earle F. Philhower, III wrote:
  Default to a safe icon format
 Beep, sorry, you're computer was taken over by the icon then crashed, 
 please reboot :)
 But anyway, the alpha *is* safe for other OS (well maybe not for NT, 
 but I haven't heard back from haro about icon_test9 which seems to work 
 fine for Alexander). It may not be to your taste but it is recognizable 
 as the X logo.

Looking really nasty under OSs earlier than XP is a bug I'd say.  Plus
it's probably rechnically an invalid icon resource under those OSes so
you may wnd up causing a boom (hey, under 95 or 98 it doesn't take
much to crash the system!)

  Or, fix the code to detect the OS.  If OS=Win5.0 use alpha icon,
  OTW use standard icon.  That can be done at runtime w/a few lines
  of C.
 Which one? The monochrome one? Or the one with the white background? 
 Maybe the old one with the white specks? And how do you do the runtime 
 thingy when XWin isn't running and Windows displays the icon in Explorer?

You've not very familiar with how a shortcut is made, are you?  Make the
1st icon in the file the clean X-in-a-white-box that's been there for some
time.  Windoze shortcuts then will use it by default.

Then, since you're so unhappy with the icon, submit a patch to the
x-create-shortcut-icons package that checks the OS version
and if it's XP or greater says create-shortcut w/icon 102, and voila...

 Maybe Halrold should only distribute the source code, and let people 
 recompile xwin.exe by themselves that way they can choose their own 
 prefered icon for the binary.

It's already there in CVS and his test releases, have a ball!
-- 
-Earle F. Philhower, III
 [EMAIL PROTECTED]
 http://www.ziplabel.com

Re: X/Cygwin icon proposal

Earle F. Philhower, III wrote:

Howdy Nahor,

For someone who's entire contribution to XWin has been
an alpha-blended X icon you've got some loud opinions...
He's done much more than that.  His full name is Jehan Bing and it 
looks like the bulk of his work is here:

http://x.cygwin.com/devel/server/changelog-050.html

He added the -nodecoration parameter, scrollbar support, build rules 
for Windows resource files, lots of stuff.


Subject: Re: X/Cygwin icon proposal
From: Nahor [EMAIL PROTECTED]
Earle F. Philhower, III wrote:
Default to a safe icon format
Beep, sorry, you're computer was taken over by the icon then crashed, 
please reboot :)
But anyway, the alpha *is* safe for other OS (well maybe not for NT, 
but I haven't heard back from haro about icon_test9 which seems to work 
fine for Alexander). It may not be to your taste but it is recognizable 
as the X logo.


Looking really nasty under OSs earlier than XP is a bug I'd say.  Plus
it's probably rechnically an invalid icon resource under those OSes so
you may wnd up causing a boom (hey, under 95 or 98 it doesn't take
much to crash the system!)

Or, fix the code to detect the OS.  If OS=Win5.0 use alpha icon,
OTW use standard icon.  That can be done at runtime w/a few lines
of C.
Which one? The monochrome one? Or the one with the white background? 
Maybe the old one with the white specks? And how do you do the runtime 
thingy when XWin isn't running and Windows displays the icon in Explorer?


You've not very familiar with how a shortcut is made, are you?  Make the
1st icon in the file the clean X-in-a-white-box that's been there for some
time.  Windoze shortcuts then will use it by default.
Then, since you're so unhappy with the icon, submit a patch to the
x-create-shortcut-icons package that checks the OS version
and if it's XP or greater says create-shortcut w/icon 102, and voila...
But Windows has rules for picking icons from executables (but they are 
hard to find documentation on) and I would hope it is possible to order 
the icons and provide the proper formats such that the default icon for 
the *executable* (not shortcut) would be the one that looks nicest on 
the system.

I could very easily swap the order of the boxed icon and the non-boxed 
icons in our resource file to make the boxed icon the default, but I 
would rather not do that since I prefer the non-boxed icon on the 
executable.  Of course, I am a pragmatic guy, and if that doesn't work 
on all platforms then I will have to either swap the icons or include a 
simpler ugly non-boxed icon as the default in addition to the alpha 
blended icon in our resource file.

Harold

Re: X/Cygwin icon proposal

Howdy Harold,

 Subject: Re: X/Cygwin icon proposal
 Date: Thu, 18 Mar 2004 18:22:12 -0500
 From: Harold L Hunt II [EMAIL PROTECTED]
  For someone who's entire contribution to XWin has been
  an alpha-blended X icon you've got some loud opinions...
.. http://x.cygwin.com/devel/server/changelog-050.html
 He added the -nodecoration parameter, scrollbar support, build rules 
 for Windows resource files, lots of stuff.

Sorry, then, Nahor, didn't recognize the handle.  (Just when I was
getting a good flamefest started, too!)
..
 But Windows has rules for picking icons from executables (but they are 
 hard to find documentation on) and I would hope it is possible to order 
 the icons and provide the proper formats such that the default icon for 
 the *executable* (not shortcut) would be the one that looks nicest on 
 the system.

Yes, the .EXE it's going to take IIRC the 1st icon it finds in the file
(lowest resid, I think).  What I'm really surprised about here is that
the ICON format lets you store a bunch of different formats in just
one ICON resource (you can specify a 1-, 16- , 256-, or 16M color,
all in 16x16, 32x32, and 48x48 in one ICON).  Does the one that
everyone is so riled up about have the other, fallback formats included?

If not, can they be added and tried out?  You could make the
non-alpha version of the ICON all the boxed-X and leave the
16M+alpha one as the floating X...

As long as it doesn't crash, it can be a picture of an emu as far as I
care, but that all centers on whether that emu is safe under earlier
OSs or not...Crashing emus stink...
-- 
-Earle F. Philhower, III
 [EMAIL PROTECTED]
 http://www.ziplabel.com

Re: X/Cygwin icon proposal

Earle F. Philhower, III wrote:

Howdy Harold,

Subject: Re: X/Cygwin icon proposal
Date: Thu, 18 Mar 2004 18:22:12 -0500
From: Harold L Hunt II [EMAIL PROTECTED]
For someone who's entire contribution to XWin has been
an alpha-blended X icon you've got some loud opinions...
.. http://x.cygwin.com/devel/server/changelog-050.html

He added the -nodecoration parameter, scrollbar support, build rules 
for Windows resource files, lots of stuff.

Sorry, then, Nahor, didn't recognize the handle.  (Just when I was
getting a good flamefest started, too!)
..
But Windows has rules for picking icons from executables (but they are 
hard to find documentation on) and I would hope it is possible to order 
the icons and provide the proper formats such that the default icon for 
the *executable* (not shortcut) would be the one that looks nicest on 
the system.

Yes, the .EXE it's going to take IIRC the 1st icon it finds in the file
(lowest resid, I think).
Yes, that is correct.

What I'm really surprised about here is that
the ICON format lets you store a bunch of different formats in just
one ICON resource (you can specify a 1-, 16- , 256-, or 16M color,
all in 16x16, 32x32, and 48x48 in one ICON).
Yup, that is what both of our icon files have.

Does the one that
everyone is so riled up about have the other, fallback formats included?
Yes, that is why this is so confusing.  :)  Windows *should* pick a 
format that it understands, but getting it to do so either requires 
tricks of ordering that MS doesn't make clear, or it requires including 
more formats than you'd think you would need.  Or, it is just not possible.

Let me summarize the two things we are discussing at the moment:

1) A Japanese user has reported that the new icon was garbled on his 
Windows NT (I believe) system.  This is an isolated case so far and I 
think it is due to something with that particular system and is not 
something that we should worry about unless it starts getting reported more.

2) On Windows 2000, the non-boxed X icon is showing up with a 2 pixel 
thick white border (I've seen it too at the computer lab) that looks 
pretty bad.  We are in the process of figuring out whether Windows is 
generating this ugliness from the alpha channel icon or from the 
non-alpha icons.  Jehan made some changes to the non-alpha icons as 
well, and it is remotely possible that those changes are causing this, 
not the alpha changes.

If the alpha icon is causing the ugliness on Windows 2000, then we still 
have tons of options to explore and Jehan is exploring them at a good 
rate.  We can work on this for a few weeks before it becomes time to 
either fix it or revert it.

As long as it doesn't crash, it can be a picture of an emu as far as I
care, but that all centers on whether that emu is safe under earlier
OSs or not...Crashing emus stink...
As far as I know, the Windows 95, 98, and Me OSes are not having 
problems with the 32 bit icons... it is only Windows 2000 possibly 
trying to treat the 32 bit icon as a 24 bit icon, with the result being 
ugliness but not crashing.

Harold

Re: X/Cygwin icon proposal

Harold L Hunt II wrote:

Earle F. Philhower, III wrote:

Howdy Nahor,

For someone who's entire contribution to XWin has been
an alpha-blended X icon you've got some loud opinions...


He's done much more than that.  His full name is Jehan Bing and it 
looks like the bulk of his work is here:

http://x.cygwin.com/devel/server/changelog-050.html

He added the -nodecoration parameter, scrollbar support, build rules 
for Windows resource files, lots of stuff.
Thanks for defending me, not being on the mailing list itself makes me a 
bit laggy to reply :P.

And by the way, the build rules for Windows resource files is your 
contribution not mine. :)

	Nahor/Jehan

Re: X/Cygwin icon proposal

Harold L Hunt II wrote:

it is only Windows 2000 possibly trying to treat the 32 bit icon as a 24 bit icon, with the result being ugliness but not crashing.
This may be fixed with the icon reordering (putting 24b before 32b). The 
screenshot that Alexander sent earlier show the thin white line instead 
of a thick one. So probably that Win2k uses the first one with 24b or 
more because, when win2k came out, both were identical.

	Nahor

Re: X/Cygwin icon proposal

Earle F. Philhower, III wrote:
Sorry, then, Nahor, didn't recognize the handle.  (Just when I was
getting a good flamefest started, too!)
Hehe, I got burnt that way too one day, telling someone to just 
contribute instead of ranting when the guy already contributed. :p

	Nahor

emacs crash under X on XP

2004-03-18 Thread Moira Regelson

There are a number of messages about X emacs crashing this week -- at last!  
I've been having this problem since I updated at the end of January, but I 
thought I'd messed something up because X was running when I did the update. 
 However, I just reinstalled all last week and emacs still crashes 
routinely.

Here's what I get out of the setup.log for versions:

initial 10/7/04 (worked wonderfully):
cygwin-1.5.5-1
emacs-X11-21.2-12
XFree86-bin-4.3.0-4
XFree86-xserv-4.3.0-18
1/27/04 (crashes started):
cygwin-1.5.6-1
XFree86-bin-4.3.0-8
XFree86-xserv-4.3.0-42
current (crashes ongoing):
cygwin-1.5.7-1
XFree86-bin-4.3.0-15
XFree86-xserv-4.3.0-55
Here's the bt from gdb (clearly not all compiled for debugging, but maybe 
this means something to someone?):

gdb /usr/bin/emacs

#0  0x20060e29 in libICE!_IcePaAuthDataEntries ()
#1  0x0022d5b0 in ?? ()
#2  0x204e3800 in ?? ()
#3  0x0020 in ?? ()
#4  0x00471f01 in libX11!_X11TransWrite ()
#5  0x20060ec2 in libICE!_IcePaAuthDataEntries ()
#6  0x20472000 in libICE!_IcePaAuthDataEntries ()
#7  0x0020 in ?? ()
#8  0x0022d5b0 in ?? ()
#9  0x20060ea8 in libICE!_IcePaAuthDataEntries ()
#10 0x204e3800 in ?? ()
#11 0x0022d5b0 in ?? ()
#12 0x20472000 in libICE!_IcePaAuthDataEntries ()
#13 0x20060ceb in libICE!_IcePaAuthDataEntries ()
#14 0x0001 in ?? ()
#15 0x0020 in ?? ()
#16 0x0022d5b0 in ?? ()
#17 0x0001 in ?? ()
#18 0x0022d5f0 in ?? ()
And here's the latest emacs.exe.stackdump:

Stack trace:
Frame Function  Args
0022D704  77E7AC21  (, 0020, 0002, 0001)
0022D764  61087E49  (0DF8, 0006, 0022D7B4, 2008CBEC)
0022D7B4  61086211  (0006, 2008CB70, 1000, )
0022D7D4  61026B4C  (06B0, EA60, 0014, 0022D810)
0022D854  6108A855  (, 6102606B, 000AF801, )
0022D8B4  61087E49  (0DF8, 0006, 20267C74, 302D2134)
0022D8D4  61086211  (202D2134, , 0022D96C, 5030080C)
0022D904  20129015  (20267C74, , 2012CB84, 302D20B4)
0022D934  2012B76A  (302D2134, 0022D96C, 0022D96C, )
0022D964  2012C113  (, 302D2134, 200EF9A5, 404E7D80)
0022D990  2012C195  (, 1026496C, 302D2134, 2012CB8F)
0022DA50  20059C34  (204D5E00, 302D2134, , )
0022DAC0  2001088C  (0022DD70, 0022DB08, 1028337C, 0022DB08)
0022DB00  2001027D  (0022DD70, 0022DEF0, 0022DEF0, 2011A6CB)
0022DB40  20013DCE  (0022DD70, 0022DEF0, 0022DB80, 200134D6)
0022DB90  20013659  (0022DD70, , , )
End of stack trace (more stack frames may be present)
Assistance will be greatly appreciated.  Like Zdzislaw Meglicki, I miss that 
reliable emacs!

Moira Regelson

_
Get tax tips, tools and access to IRS forms  all in one place at MSN Money! 
http://moneycentral.msn.com/tax/home.asp

Re: Installing tcltk does not force installation of XFree86-prog

2004-03-18 Thread Charles Wilson

Marc Daumas wrote:
...although X11/Xlib.h is needed.
You've stuck your finger right on a sore spot.

tcltk is a *native MS windowing* port of tk (tcl is GUI-agnostic; tk is 
the important bit wrt display technology).  The X11/Xlib.h file that 
cygwin's tk wants is NOT the one distributed by cygwin-xfree.  Neither 
will tk work with the X11/Xlib.h file distributed with xpm-nox.

Both tk and xpm-nox have their own fake Xlib.h files -- xpm-nox ships 
it in /usr/local/xpm-nox/X11/xlib.h.  cygwin's tk doesn't ship its 
version of that file at all.

Go here
http://www.neuro.gatech.edu/users/cwilson/cygutils/testing/
and download
tk-includes-8.4.tar.bz2
Unpack it somewhere so that you can explicitly use
  -I /this/way/to/tk's/X11/Xlib.h
but be careful not to clobber the real X11/Xlib.h
--
Chuck

AMD Athlon 1.33 GHz or 1.4 GHz?

Anyone out there got a left-over AMD Athlon Thunderbird 1.33 GHz or 1.4 
GHz?  I have been using an Iwill KA-266 motherboard as my primary board 
for the last three years with a 1.2 GHz Athlon on it.  Just this weekend 
I bought a new CPU cooler, 1 GB of PC2700 RAM (only requires PC2100) 
that I can run at CAS 2, and a new Antec Sonata case.  After I got all 
of this I was tweaking the settings for my new RAM, since I knew it 
could perform better than the default settings which are for PC2100 RAM 
at CAS 2.5.  I was able to change the RAM from normal settings to 
fast settings and changed the CAS from 2.5 to 2.  Zinf (MP3 player for 
Windows) went from 10% CPU usage to 1%!  I then went in an bumped the 
bus speed from 133 MHz to 146 MHz (10% increase) and measured an exact 
10% drop in my compile/build/package time from 120 minutes to 108 minutes.

I know that my board supports at least a 1.33 GHz Athlon, and I think it 
can support the 1.4 GHz as well (both are 133 MHz FSB with DDR).  I have 
seen the 1.33 GHz's Athlons still on sale for around $30 and was 
thinking that if anyone has retired either of these chips then I could 
get around another 15% performance improvement from spare parts that 
aren't doing any good.

So, does anyone have one of these chips?  Please email privately if you 
would be willing to mail it to me in return for more frequent Cygwin/X 
releases.  ;)

Harold

Re: X/Cygwin icon proposal

2004-03-18 Thread Michael Bax

Hi folks

This is a little long, but I have combined several points rather than
bombard the list with multiple messages.  Thanks for your patience.  :-)

___
Nahor wrote:

 What is New Alpha? I sent a few on the mailing list. Was it icon_test9
 (attached again here)? This one has 24bit icons, hopefully the prefered
 format on systems not supporting the alpha channel (crossing fingers).

The file you attached has issues under Windows 2000 (does not show icon
picture in Explorer).  But it was the latest version of your icon at the
time.  Original was from X.exe.

 I don't care about the majority of the systems out there. I care about
 the majority of the system using Cygwin/XFree. And that can be very
 different.

The majority of Cygwin users are not typical gamers.  They are more likely
to be similar in profile to hackers such as the Linux or BSD folks -- and
those are well known to be frequently using older generations of hardware
(and hence software).

Industry is still receiving PC's preloaded with Windows 2000 -- which will
be supported until 2007!  Remember, 2 years after Windows 2000 came on the
scene, IT organisations were still DEPLOYING Windonts NT!

Two years after the debut of Windows 2000, the number of *new* Windows NT
server licenses matched the number of Windows 2000 licenses.  And that's
just the new liceneses -- just think of the huge installed base.  And as for
desktops, by 2002 75% of desktops in industry were Windows 9x!

 Uh? I don't get your point. I personally don't buy a machine just to run
 unix. I use it to do other stuff (mostly compilation) that do make use of
 CPU power. So I have a recent machine, so I have XP. I assume that quit a
 dew (most?) geeks using Cygwin/XFree would be in the same case. But it's
 just a guess.

I'm sure that many Cygwin users have brand new machines.  But I am equally
sure that many more have older systems.

The baseline for support today must clearly be pre-XP systems.

 The other thing, IMHO, is that the alpha icon on non-alpha system, while
 not the best icon that can be on such system, is not completely ugly
 either.

Frankly, I disagree.  I wouldn't have put in the effort of designed a new
icon set if I thought it were OK!  :-)

 So between an icon that looks best on recent machines but not as good on
 older ones and one that looks best on older machines but not as good as it
 can be on recent ones, I prefer to think future/progress/whatever and
 take the first.

The problem is that the rest of the software world disagrees.  It is
standard software practice to support as many platforms as possible with the
*default* install, even if it is not as flashy as the others.  Sure, you can
have an option to enable alpha -- but don't make it the default.

Do you really want someone installing X/Cygwin for the first time to be
confronted with an amateurish-looking icon?  That was my first impression.
From a technical perspective, aesthetics are secondary -- but in the real
world, first impressions last.

 Between the CVS and your improved, I prefer the one in CVS. The thin
 lines is acutally too thin in 16x16, the line is too blury on yours, the
 white background seems to wash over the black line.

You originally said that my original monochrome X was ugly due to blocky
edges, but that is exactly the problem with your icon on Windows 2000
systems!  :-)

The lines in Improved.ico (why the quotes?) are actually in exactly the
correct anti-aliased proportion to represent the X logo within the limits of
the bitmap.  The CVS icon is incorrectly proportioned.

I do not argue that you personally prefer your version.  That is of course a
subjective choice!  However, Improved.ico has the proportions of the
original X vector logo; you may prefer something that looks different, but
that then is something different, not a faithful rendering of the X logo.

___
Ago wrote:

 If you can build ico files with both alpha and non-alpha icons why not
 include your version with alpha channel and for non-alpha either the boxed
 (which I liked) or a plain two-color variant.

 cygwin is unix. unix is simple (shell and stuff) and this is the opposite
 of the bubble-gum os WinXP with alpha channel.

Hear hear!  :-)

___
Earle wrote:

 - Default to a safe setting for anything that's not critical. -
 You'll save TONS of user grief, and by extension, your own.

Agreed.

 Looking really nasty under OSs earlier than XP is a bug I'd say.  Plus
 it's probably rechnically an invalid icon resource under those OSes so
 you may wnd up causing a boom (hey, under 95 or 98 it doesn't take
 much to crash the system!)

Strongly agreed.

 You've not very familiar with how a shortcut is made, are you?  Make the
 1st icon in the file the clean X-in-a-white-box that's been there for
 some

Re: X/Cygwin icon proposal

Michael,

Michael Bax wrote:

Harold wrote:

What I'm really surprised about here is that the ICON format lets you
store a bunch of different formats in just one ICON resource (you can
specify a 1-, 16- , 256-, or 16M color, all in 16x16, 32x32, and 48x48
in one ICON).
Does the one that everyone is so riled up about have the other,
fallback formats included?
Yup, that is what both of our icon files have.

Hi Harold, that's actually not quite correct. The existing CVS icon (that
you kindly sent me the link to) has no monochrome content and has a
messed-up 24x24 version. It also has some rendering glitches.
I was referring to the notion of many formats in one file, not to the
specific list of what formats we had. :)

That icon was not the latest version that Benny had created, as he
pointed out when he saw that link. Follow the link below, then open the
X-boxed.ico file to see the most recent version (which I uploaded after
he nudged me):

http://pdx.freedesktop.org/cgi-bin/viewcvs.cgi/xc/programs/Xserver/hw/xwin/?cvsroot=xorgonly_with_tag=CYGWIN

That's why I created Improved.ico, with careful rendering and anti-aliasing
to preserve the form of the original vector logo -- I hope you can use it.
Yes, preserving the form is important.
_
In summary:

So far 2 developers and 3 users have contributed to this discussion. It
appears unanimous among the users that the alpha icon should not be the
default.
Well, this is still an open technical question of can it be done. It
we *can* create an icon file that contains alpha icons that displays
fine on all platforms, then there is no reason to change the icon. I
consider this an open issue as Jehan is still exploring options and no
one has found a definitive source stating that it cannot be done. If we
*cannot* create such an icon file, then the choice about what we should
do for the default icon becomes much simpler and doesn't require so much
discussion.

So, lets hold off on dicussing this more until some one can prove that
we can or cannot create an icon with alpha formats that displays fine on
all versions of Windows.

Harold

Re: Upcoming X.org release and splitting packages

2004-03-18 Thread Frédéric L. W. Meunier

bOn Thu, 18 Mar 2004, Thomas Dickey wrote:

 On Thu, 18 Mar 2004, Harold L Hunt II wrote:

  Frédéric L. W. Meunier wrote:
   What are the main differences between it and XFree86 4.4.0 ?
   Are things like XTerm 185 included, or everything that goes to
   XFree86 can't to X.org ?
 
  I don't know about XTerm 185 specifically, but this release should
  contain all fixes and features that were added to the XFree86 project's
  source code tree for the 4.4.0 release.

 xterm patch #185 is post-4.4, and according to fd.o's CVS is not in the
 release-1 branch.

It may be worth to make it a separate package and start using
your sources from http://invisible-island.net/xterm/ when
they're newer (most of the time).

-- 
http://www.pervalidus.net/contact.html

Re: Upcoming X.org release and splitting packages

Thomas Dickey wrote:

On Thu, 18 Mar 2004, [ISO-8859-1] Fr?d?ric L. W. Meunier wrote:


Thomas, am (are) I (we) missing anything ? Are there any other
options that are enabled or disabled in the xc version ?


Perhaps --enable-luit (though I don't recall if anyone's mentioned using
it with cygwin).
Hmm... good idea... I don't know if we have luit support or not.  I 
would have to look into this.

Harold

Re: Upcoming X.org release and splitting packages

Thomas Dickey wrote:

On Thu, 18 Mar 2004, Harold L Hunt II wrote:


I have this built as a Cygwin package using the default configure
options at the moment.  The only patch required was to Makefile.in
(attached) to get it to stop appending .exe to the uxterm shell script.
Thomas, can you recommend any configure options we should be using?  I
can think that the following might be useful:
--enable-toolbar


that's broken (some incompatible changes to Xaw from XFree86 4.4 that
I've not gotten around to investigating0.
Good to know.

--enable-wide-chars


you need this for uxterm
Huh... this is disabled by default in my new build.  I wonder if our old 
version had it enable or not.

--with-Xaw3d


Some people like it.  Actually all of the Xaw flavors look very much alike
to me.
Same here.  I could hardly tell the difference in xfig sometimes.

Harold

Re: Upcoming X.org release and splitting packages