Re: [ANNOUNCEMENT] xwinclip Test 04 (Cygwin/XFree86 and Windows clipboard integration)
Explanation and fix for the ms-tnef attachments: http://help.netscape.com/kb/consumer/19981102-1.html - Original Message - From: "Brian Gallew" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, June 12, 2002 11:20 PM Subject: RE: [ANNOUNCEMENT] xwinclip Test 04 (Cygwin/XFree86 and Windows clipboard integration) > Harold L Hunt said: > > Eric Peabody's messages are getting bounced by the list server. > > Apparently his mail server is changing the format of the message > > somehow. Anyway, his reply is below. > > Most likely he's using MS Outlook and/or MS Exchange. They're famouns > for adding ms-tnef bits to messages. It *can* be disabled, but I have > no idea how to do it myself. I just know that the vendors who still > do business with me have all figured out how to do it. > The ones who couldn't figure it out no longer do business with me. > > >
Re: Trivial Feature Request: beep()
On my system the I get the beep through the speakers. The default beep is enabled in the control panel. The funny thing though, similarly to Harold I get different pitches, I get a high-pitched beep from the cmd.exe that sounds like a pc speaker but is coming from soundcard but from bash I get the sound I defined in the control panel. There was a thread on this before in cygwin list and more than once. Does not really relate to the XFree but I thought I'd mention it, maybe it is related somehow. There is one with Subject: 'Beeping' from 16/03/2002 on how to turn beeping OFF for readline (echo set bell-style none >>~.inputrc), for vi (:set vb) and HKEY_CURRENT_USER\Control Panel\Sound\Beep registry key which I think would be toggled by the control panel anyway but still would not hurt to check. My rxvt does not beep because I run it with -vb option (no visual bell). There is same option for xterm. Could this be somehow related to the problem? I cannot check because my xfree is older than the packaged ones and does not beep at all. Eugene. - Original Message - From: "Brian Gallew" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 11, 2002 11:59 PM Subject: Trivial Feature Request: beep() > Is it possible to make the X11 bell work? "xset q" tells me the bell > should be ringing, but I can't seem to get it to work. >
Re: [ANNOUNCEMENT] WindowMaker, libPropList, and Openboxsetup.exepackages available for testing
WindowMaker is working OK. Had a glitch in the beginning. I could not see wmaker in /usr/local where all other window managers I have compiled (or tried to compile) live (openbox, blackbox, icewm). I tried to run it from the command line and got a dialog from wmaker saying it could not find libX11.dll. I put it into my .xinitrc file and ran startx. I got same error then a series of errors same or similar dialogues from wdwrite.exe but then, after all that, I got the windowmaker desktop and never been able to reproduce the error, it starts every time now. Anyone else had a similar problem? Also, I am wondering. All other window managers seem to default to /usr/local and so does the Makefile to the WindowMaker. Is there a particular reason it installs into /bin? (I have tried to compile it but failed with unresolved reference to Xsetlocale at linktime. This might be simple but I am without a clue in this area so far.) Eugene. - Original Message - From: "Harold Hunt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 1:45 AM Subject: RE: [ANNOUNCEMENT] WindowMaker, libPropList, and Openboxsetup.exepackages available for testing > Scott, > > So, does WindowMaker work? Does Openbox work? I need to know before I > release the packages into the wild... > > Harold > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Scott Alexander > > Sent: Monday, April 29, 2002 11:44 AM > > To: Harold Hunt; Richard Drake; [EMAIL PROTECTED] > > Subject: Re: [ANNOUNCEMENT] WindowMaker, libPropList, and > > Openboxsetup.exepackages available for testing > > > > > > Just muddled arround with my proxy settings and have connected > > and done the > > update. > > > > Scott. > > > > - Original Message - > > From: "Harold Hunt" <[EMAIL PROTECTED]> > > To: "Richard Drake" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Monday, April 29, 2002 4:31 PM > > Subject: RE: [ANNOUNCEMENT] WindowMaker, libPropList, and > > Openboxsetup.exepackages available for testing > > > > > > > Rich, > > > > > > I was able to connect to huntharo-4 and grab setup.ini with > > setup.exe from > > > my other machine just fine. > > > > > > Do you have a firewall or proxy server? Have you told setup.exe to use > > your > > > proxy server? > > > > > > Harold > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Drake > > > > Sent: Monday, April 29, 2002 11:20 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: [ANNOUNCEMENT] WindowMaker, libPropList, and > > > > Openboxsetup.exepackages available for testing > > > > > > > > > > > > Harold, > > > > > > > > still no luck. we need another data point to isolate the problem > > > > .. somebody else needs to try to point setup.exe to that location... > > > > > > > > -rich > > > > > > > > Harold Hunt wrote: > > > > > > > > > > Richard, > > > > > > > > > > Hmm... you mention that you can see the directory with your > > > > browser... that > > > > > means that your browser has a connection open to my ftp > > > > server... and I'm > > > > > not sure how many connections my server allows per host. Thus, > > > > you may want > > > > > to close your browser, wait a few minutes, then open setup.exe > > > > and try to > > > > > connect again (without opening your web browser to that > > > > address). That may > > > > > help... > > > > > > > > > > Harold > > > > > > > > > > > -Original Message- > > > > > > From: [EMAIL PROTECTED] > > > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Drake > > > > > > Sent: Monday, April 29, 2002 10:48 AM > > > > > > To: Harold Hunt; [EMAIL PROTECTED] > > > > > > Subject: Re: [ANNOUNCEMENT] WindowMaker, libPropList, and Openbox > > > > > > setup.exepackages available for testing > > > > > > > > > > > > > > > > > > Harold, > > > > > > > > > > > > I tried pointing setup.exe to > > > > > > ftp://huntharo-4.user.msu.edu/pub/cygwin/ but it tries to connect > > > > > > and then comes back with "Unable to get setup.ini from > > > > > > ftp://huntharo-4.user.msu.edu/pub/cygwin/";. I'm a relative > > > > > > newbie .. am i missing something with setup.exe? (I can see that > > > > > > directory with my browser). > > > > > > > > > > > > -rich > > > > > > > > > > > > PS: Love the cygwin & cygwin/xfree products! > > > > > > > > > > > > > > > > > > Harold Hunt wrote: > > > > > > > > > > > > > > Point setup.exe at: > > > > > > > ftp://huntharo-4.user.msu.edu/pub/cygwin/ > > > > > > > > > > > > > > There is a setup.ini there that has all the XFree86 > > packages plus > > > > > > > WindowMaker, libPropList, and Openbox. > > > > > > > > > > > > > > I've tested the packages locally, but I'd like someone to do an > > > > > > install on > > > > > > > there system before I post the packages to the mirror network. > > > > > > > > > > > > > > Oh, I also figured out how to do source packages (using the > > > > > > generic Cygwin
Re: [ANNOUNCEMENT] WindowMaker, libPropList, and Openbox setup.exe packages available for testing
Had no problems connecting or getting setup.ini. I have an older version of setup.exe though, if that matters at all. One funny side-effect: I only wanted windowmaker so I tried selecting skip for all X packages. Clicking down the column would work for the first couple but then all the 'Skip' status' would revert back to version numbers. I fiddled trying to select 'Skip' on packages in different order and after a while succedded in disabling all but windowmaker. Maybe it is something to do with the older version of the setup.exe? Eugene. - Original Message - From: "Harold Hunt" <[EMAIL PROTECTED]> To: "cygx" <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 12:31 AM Subject: [ANNOUNCEMENT] WindowMaker, libPropList, and Openbox setup.exe packages available for testing > Point setup.exe at: > ftp://huntharo-4.user.msu.edu/pub/cygwin/ > > There is a setup.ini there that has all the XFree86 packages plus > WindowMaker, libPropList, and Openbox. > > I've tested the packages locally, but I'd like someone to do an install on > there system before I post the packages to the mirror network. > > Oh, I also figured out how to do source packages (using the generic Cygwin > build script), so each of these new packages has a source file as well (if > you wish to see what was changed to make them compile on Cygwin). > > Enjoy, > > Harold >
Re: Windows placed directly onto desktop (dream or reality)
X-Win32 from www.starnet.com and Hummingbird Exceed X server provide native window modes but they are both pricey commercial products and they don't have the advantage of the having the whole cygwin environment. It is handy to be have the ability to have native X windows, provides more seamless integration with native GUI. I look forward to XFree86 support for it. - Original Message - From: "Jesse Pepper" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 12, 2002 5:21 PM Subject: Windows placed directly onto desktop (dream or reality) > Hi All, > > Sorry in advance if this issue has already been discussed, but I > couldn't find any info on it. > > I have a recollection of running XWin on a windows box, and being able > to display windows directly onto the desktop. > > That is, one "ms windows" window per x-window. Is this actually a dream > I had, or is it really possible. If so, how does one go about achieving > this high state. > > I want to be able to overlay "ms windows" windows and "x windows" over > one another. > > Thanks, > > Jesse > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.346 / Virus Database: 194 - Release Date: 10/04/2002 > >
Re: logos
I think they look quite good. In the last logo thread I got the impression that people wanted the established Cygwin logo for letter C, maybe you can add a variation on that to your list. - Original Message - From: "Nupur Saurabh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 12, 2002 1:40 PM Subject: logos > hi all, > > attached are some logos > > with some graphics > > http://www.geocities.com/nupursarpal/logog.jpg > > http://www.geocities.com/nupursarpal/logod.jpg > > http://www.geocities.com/nupursarpal/logof.jpg > > http://www.geocities.com/nupursarpal/logoc.jpg > > > > without graphics > > http://www.geocities.com/nupursarpal/logoa.jpg > > http://www.geocities.com/nupursarpal/logoe.jpg > > > suggestions, comments and feedback are welcome > > nupur
Re: cx-logos
It is a good point that maybe just CX is not enough and it should be Cygwin + X logos but nupur's logo is also much easier on the eye than Chris's. Vivid red and green on a bright blue background - that is violent on the eyes. Long ago in the time of eight-color displays there were no other options but now we have more range to work with. Maybe some sort of compromise between the two? Nupur's color scheme was simple but, I thought, good.
Re: Missing terminfo data in XFree86 4.2.0
Good observation. I never really missed the xterm entries, but now that you
mentioned it, they are not there. I noticed it also because of the handy
script from Alan Dobkin (re ncftp missing libs). The original files are in
terminfo-5.2-1 package.
The setup text (in the Xinstall.sh) states that new termcap entries are
needed to take advantage of some new features of xterm, whatever they are.
There is a way to generate most of those entries from the
/usr/X11R6/lib/X11/etc/xterm.termcap:
captoinfo /usr/X11R6/lib/X11/etc/xterm.termcap
"/usr/X11R6/lib/X11/etc/xterm.terminfo", line 90, terminal 'xterm-color':
enter_alt_charset_mode but no acs_chars
"/usr/X11R6/lib/X11/etc/xterm.terminfo", line 90, terminal 'xterm-color':
exit_alt_charset_mode but no acs_chars
"/usr/X11R6/lib/X11/etc/xterm.terminfo", line 144, terminal 'xterm-sco':
enter_alt_charset_mode but no acs_chars
"/usr/X11R6/lib/X11/etc/xterm.terminfo", line 144, terminal 'xterm-sco':
exit_alt_charset_mode but no acs_chars
These will generate all missing files except for xtermm. Comparing these
files to their backed up namesakes shows that they are different. Could
these be the files that were intended to be generated originally by setup? I
do not know anything about mechanics of xterminfo to be able to go beyond
the mechanical regeneration of the files. I am not even sure what the errors
mean. Something to do with acsc@ part of the definition which man terminfo
mentiones but even then I am not sure what the manpage is talking about.
- Original Message -
From: "Michael" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, April 06, 2002 12:48 AM
Subject: Missing terminfo data in XFree86 4.2.0
> Hi
>
> I ran into the following problem with the current XFree86 distribution,
but
> could not find any mention of any solution here or elsewhere.
>
> SYMPTOMS
>
> * "vt102" terminal setting (TERM) in xterm windows instead of "xterm"
> * "WARNING: terminal is not fully functional" error messages from /bin/les
s
> * Missing /usr/share/terminfo/x/xterm and other terminfo data files
>
> CAUSE
> -
> 1. The current XFree86 for Cygwin distribution is missing the file
>xterm.terminfo (but not xterm.termcap) in Xlib.tgz. (However this is
>not true for other distributions, eg FreeBSD.) It is missing in the
>distribution available from the Cygwin mirrors and the distribution
>available directly from XFree86.
> 2. After unpacking the distribution files, the script Xinstall.sh asks the
>user whether to update the terminfo entries. The default is no, but
the
>blurb notes that new features will be unavailable otherwise.
>
> If the user says yes:
> 3. The script moves a number of existing terminfo entries to *.bak
> 4. The script tries to run tic on /usr/X11R6/lib/X11/etc/xterm.terminfo to
>replace them
> 5. Since this file is not present, tic fails
> 6. The following terminfo files are subsequently effectively missing:
xterm,
>xterms, xterm-24, xterm-vi, xterm-65, xterm-bold, xtermm, xterm-boldso,
>xterm-ic, xterm-r6, xterm-old, xterm-r5, vs100
>
> INTERIM SOLUTIONS
> -
> During install (pre-emptive):
> * Do not elect to update terminfo entries
> After install (treatment):
> * Setting the TERM variable to another value such as cygwin or ansi is
> a temporary workaround
> * Moving the renamed files back to their original names reverses the
> damage ("mv xterm.bak xterm" etc)
>
> DISTRIBUTION FIX?
> -
> Include the file or change the installation script
>
> QUESTIONS
> -
> * Is there some reason xterm.terminfo is missing, or is this an error?
> * Is it possible to use e.g. the FreeBSD distribution's xterm.terminfo
file?
> * Is it advised against updating the terminfo data?
> * If so, then what about updating termcap entries (suggested by
Xinstall.h)?
> * What is lost by not using the new terminfo data?
>
> Thanks
> Michael
>
Re: Invisible X client window borders
not much help from me but I had the same problem with TWM myself, no border when resizing. I think I had border when I was moving but I am not sure it was a while ago. I downloaded and compiled Blackbox and the problem doesn't show up under that. - Original Message - From: "Dwight Schauer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 25, 2002 2:26 PM Subject: Invisible X client window borders > I'm not sure if this is an Xserver problem or a a window manager on. In TWM > and in Afterstep I don't get the rectangle or grid when moving or resizing > client windows. The proper window decoration does show up on the x clients. > > I have an Nvidia GeForce II MX and Windows XP. (On an Athlon Thunderbird). > > I installed the latest Cygwin and Xfree a few days ago. I'm running AfterStep > v. 1.8.11 compiled and running under Cygwin/XFree. > > I did the same at work a week ago on a different machine, and resizing, > placing, and moving windows is fine. (I don't have window contents shown on > resize or move, and I use manual window placement if there is no room to > display the window). At work on Cygwin/XFree the grid/rectangle shows up > correctly in Afterstep, as it does on a native Linux XFree86 server. > > Apart from that, XFree and Afterstep seem to be running fine on Cygwin. I > can't get aterm to work, (it compiles and run and can get as far as > displaying the shell prompt, but then it locks up) so I'm using the cygwin > provided rxvt instead and it runs fine under X.
