Re: tic0 dependency, was: urxvt-X terminfo and Bash readline
Charles Wilson Mon, 01 Jun 2009 14:27:05 -0400 Note that in most cases (e.g. cygwin installations that were in service prior to 2-3 months ago, and had installed rxvt-unicode back then) already had the old database entry installed -- and so only need the new one which *does* happen automagically. It's the mix of I want to use an old program that hasn't been recompiled against the new ncurses, AND I am just now installing rxvt-unicode for the first time, AND I'm using the old program from inside this spiffy new terminal that causes problems. Tom Roche Fri, 30 Sep 2011 13:56:58 -0400 [This week] I installed a brand new cygwin onto a cygwin-virginal, just-been-imaged box, then installed rxvt-unicode-* on it days later. Certainly I have no interest in using some old program that hasn't been recompiled against the new ncurses: I just want cygwin (which I regularly recommended to OP) to work OOTB. So ISTM (unless I'm missing something, in which case, please enlighten me), there's a bug here. Either - `info` is 'an old program that hasn't been recompiled against the new ncurses', and should be. Charles Wilson Fri, 30 Sep 2011 20:28:05 -0400 This. info.exe is linked to cygncurses-8.dll, which is the last version of ncurses on cygwin that used the old database So ... given that (correct me if wrong) `info` is part of the base cygwin distribution, that would seem to be a bug. Am I missing something? If not, what would be the appropriate way to request this bug be fixed? Or has that request already been made? your assistance is appreciated, Tom Roche tom_ro...@pobox.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
tic0 dependency, was: urxvt-X terminfo and Bash readline
After installing packages=rxvt-unicode-* on a fresh cygwin, and starting `urxvt-X`, I got me@it ~ $ info cygwin info: Terminal type `rxvt-unicode' is not smart enough to run Info. Google pointed me to http://cygwin.com/ml/cygwin/2009-06/msg9.html where I noted Charles Wilson Mon, 01 Jun 2009 14:27:05 -0400 Programs compiled against ncurses anytime in the last 2-3 months now over 2 yrs ago use the new terminfo database, which organizes the entries by the 2-char hex code of the first letter[.] Older programs continue to use the old terminfo database. Both databases coexist in the /usr/share/terminfo directory. The rxvt-unicode postinstall script will install a copy of the correct entry into both databases, but ONLY if you have the correct program(s) installed: /usr/bin/tic.exe from the ncurses package (most everybody will have this) -- installs into the new database under .../72/ /usr/bin/tic0.exe from the 'tic0' package (few people install this) -- installs into the old database under .../u/ To get this right, first install the 'tic0' package, and then (re)install the rxvt-unicode-common package. I did that, and now can `info cygwin`. But ... Note that in most cases (e.g. cygwin installations that were in service prior to 2-3 months ago, and had installed rxvt-unicode back then) already had the old database entry installed -- and so only need the new one which *does* happen automagically. It's the mix of I want to use an old program that hasn't been recompiled against the new ncurses, AND I am just now installing rxvt-unicode for the first time, AND I'm using the old program from inside this spiffy new terminal that causes problems. ... in my case, that appears to be false. I installed a brand new cygwin onto a cygwin-virginal, just been imaged, box, then installed rxvt-unicode-* on it days later. Certainly I have no interest in using some old program that hasn't been recompiled against the new ncurses: I just want cygwin (which I regularly recommended to OP) to work OOTB. So ISTM (unless I'm missing something, in which case, please enlighten me), there's a bug here. Either - `info` is 'an old program that hasn't been recompiled against the new ncurses', and should be. - install of packages=rxvt-unicode-* should do what's necessary to install files=rxvt-unicode* into /usr/share/terminfo/r/, i.e., make package=tic0 an install-time dependency. If there is another case, or if further debugging is required, please let me know. Else, please let me know if/how I should file the bug. TIA, Tom Roche tom_ro...@pobox.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: how to set X resources in Cygwin?
Tom Roche Sun, 18 Sep 2011 22:14:23 +0100
summary: I'm running an up-to-date cygwin X on wxpsp3. I get both
xterm and urxvt-X to start, but cannot get either to pickup settings
from .Xdefaults or .Xresources. What am I doing wrong?
Andrew DeFaria Mon, 26 Sep 2011 10:15:48 -0700 (rearranged)
Is $HOME set correctly for X?
Dunno what you mean by for X. $HOME looks correct to me:
# after starting X, in xterm
tlroche@tlrZ61t ~$ echo -e ${HOME}
/home/tlroche
I would have thought an xrdb -load ~/.Xdefaults would be a cure all
(provided you xrdb'ed it to the proper X server!).
Out of curiosity, what does ax xrdb -query reveal?
tlroche@tlrZ61t ~$ xrdb -query
tlroche@tlrZ61t ~$ xrdb -query | wc -l
0
tlroche@tlrZ61t ~$ xrdb -all -query | wc -l
0
tlroche@tlrZ61t ~$ cat .Xdefaults
! copy/mod from
! http://www.saltycrane.com/blog/2007/09/cygwin-x-ratposoin-screen-rxvt-setup/
! https://wiki.archlinux.org/index.php/X_resources#Xterm_resources
! Note:
! * need to capitalize first letter (or 2) of application? see
! http://xwinman.org/resource.php
XTerm*background: white
! XTerm*foreground: black
XTerm*cursorColor: red
XTerm*font:xft:Bitstream Vera Sans Mono:size=8
XTerm*boldFont:xft:Bitstream Vera Sans Mono:size=8:style=Bold
XTerm*scrollBar: True
XTerm*rightScrollBar: True
XTerm*scrollKey: True
XTerm*saveLines:
XTerm*toolBar: True
!! see https://wiki.archlinux.org/index.php/Urxvt
Urxvt*background: white
Urxvt*foreground: black
! run fc-list for a list of available fonts
Urxvt*font: xft:Bitstream Vera Sans Mono:size=8
Urxvt*boldFont: xft:Bitstream Vera Sans Mono:size=8:style=Bold
URxvt*scrollBar: False
URxvt*scrollTtyOutput: False
URxvt*scrollTtyKeypress: True
URxvt*secondaryScroll: True
URxvt*saveLines:
URxvt.perl-ext-common: default,tabbed
tlroche@tlrZ61t ~$ xrdb -load ~/.Xdefaults
tlroche@tlrZ61t ~$ xrdb -query
XTerm*background: white
XTerm*cursorColor: red
XTerm*font: xft:Bitstream Vera Sans Mono:size=8
XTerm*boldFont: xft:Bitstream Vera Sans Mono:size=8:style=Bold
XTerm*scrollBar:True
XTerm*rightScrollBar: True
XTerm*scrollKey:True
XTerm*saveLines:
XTerm*toolBar: True
Urxvt*background: white
Urxvt*foreground: black
Urxvt*font: xft:Bitstream Vera Sans Mono:size=8
Urxvt*boldFont: xft:Bitstream Vera Sans Mono:size=8:style=Bold
URxvt*scrollBar:False
URxvt*scrollTtyOutput: False
URxvt*scrollTtyKeypress:True
URxvt*secondaryScroll: True
URxvt*saveLines:
URxvt.perl-ext-common: default,tabbed
But if I restart X: no change in display of xterm or urxvt-X
And if I restart wXP: no change.
BTW, instead of Xterm and Rxvt you might look into using mintty from
Cygwin itself. It's a quite nice terminal emulator.
I'll give that a try, except that I think I should solve this first: not using
.Xdefaults seems like a prior issue. Or should I instead just invoke my X apps
with ginormous command lines?
TIA, Tom Roche tom_ro...@pobox.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: how to set X resources in Cygwin?
bumpity-bump: http://cygwin.com/ml/cygwin-xfree/2011-09/msg00016.html ... Date: Sun, 18 Sep 2011 22:14:23 +0100 ... summary: I'm running an up-to-date cygwin X on wxpsp3. I get both xterm and urxvt-X to start, but cannot get either to pickup settings from .Xdefaults or .Xresources. What am I doing wrong? details: ... Assistance would be sincerely appreciated! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
extending a VS python with cygwin
summary: I've got a version of python that I need for other purposes. I'm trying to build duplicity to use with that python. I'm getting m...@cygwinbox ~/bin/duplicity-0.6.09$ python setup.py install ... error: Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing -c mingw32 to setup.py. How to do this? details: I mostly run linux, and I've been using python-based `duplicity` http://duplicity.nongnu.org/ to back that up. I've got an older winxp box (SP3, uptodate with WU) which I keep mostly to run ArcGIS, which has happily run many versions of cygwin (which I keep uptodate) over the years. I'd like to be able to restore my linux home to my cygwin home for the rare occasions when I need to use the winxp box. To do that, I'd like to install duplicity on the cygwin box. That install process (best described by the somewhat downlevel http://blog.khorun.com/2008/09/using-duplicity-on-windows-under-cygwin.html ) works for the install of the prerequisite GnuPGInterface and boto python modules (process=[download tarball, tar xfz, python setup.py install]) but fails for the install of duplicity itself, with the error: m...@cygwinbox ~/bin/duplicity-0.6.09$ python setup.py install ... error: Python was built with Visual Studio 2003; Note that I'd cheerfully replace that version of python (the 2.5.2 that shipped with my ArcGIS 9.3), except that I use some ArcGIS extensions which seem to choke on other pythons :-( so I'd prefer to build against that if at all possible. extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing -c mingw32 to setup.py. I tried to take the advice offered, but fail: m...@cygwinbox ~/bin/duplicity-0.6.09$ python -c mingw32 setup.py install Traceback (most recent call last): File string, line 1, in module NameError: name 'mingw32' is not defined m...@cygwinbox ~/bin/duplicity-0.6.09$ python setup.py -c mingw32 install usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option -c not recognized m...@cygwinbox ~/bin/duplicity-0.6.09$ python setup.py install -c mingw32 usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'mingw32' What's the appropriate syntax here? Or how else should I fix this build problem? TIA, Tom Roche tom_ro...@pobox.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
sshd starts but won't accept connections?
I recently installed sshd (using ssh-host-config and cygrunsrv) on an
up-to-date cygwin on which the ssh client works. sshd starts, but when I
try to access the cygwin sshd from other boxes on the LAN, their
known-good ssh clients hang. How to fix? Details:
The cygwin box runs winxp sp3 and is regularly Windows Update-d. Its
cygwin is up-to-date per setup-2.686 and ftp://mirrors.kernel.org. The
cygwin box has been successfully running the ssh client with ssh-agent
and keychain for some time. It is on a LAN (router running DD-WRT)
with several linux boxes running ubuntu karmic (also up-to-date) which
run both the ssh client and server. Each of the boxes has static DHCP
leases (aka reserved IP#s). I have the same ID on all boxes.
Two of the linux boxes are 192.168.1.102 and 192.168.1.104. The cygwin
box (192.168.1.106) has long been able to ssh/scp to either linux box.
I'd like to get sshd working on the cygwin box, both for convenience
and as a dry-run for installing sshd on a cygwin box at my office. So
I installed sshd on the cygwin box using instructions=openssh.README.
Packages={cygrunsrv, openssh} were previously installed, so I ran
ssh-host-config, choosing to run sshd as a service using cygrunsrv.
I rebooted the cygwin box, and it successfully started sshd.exe (per
Task Manager).
When I do (on the cygwin box)
ping 192.168.1.102
ssh -l me 192.168.1.102
the cygwin box connects to the linux box promptly (using ssh-agent).
When I do (from either linux box)
ping 192.168.1.106
I get response from the cygwin box. But when I do
ssh -l me 192.168.1.106
the shell hangs until ^C. No routing or other errors, but no connection,
either. However if I do (from 192.168.1.102)
ssh -l me 192.168.1.104
I get a prompt connection.
So how to to make sshd on the cygwin box accept connections?
TIA, Tom Roche tom_ro...@pobox.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: sshd starts but won't accept connections?
Tom Roche 3/5/2010 11:10 AM how to to make sshd on the cygwin box accept connections? Larry Hall (Cygwin) Fri, 05 Mar 2010 11:36:43 -0500 Have you configured the firewall on your Windows machine to allow 'sshd' to use the port you've configured? Andrew Schulman Fri, 5 Mar 2010 20:11:16 + (UTC) Agreed. Yep. For the benefit of the next poor dumb bleep/ (and perhaps some debugging instructions could go in openssh.README?) (and presuming * one is running winXP with theme=Classic * windows commands are in the cygwin path ), the resolution process was 1 Determine sshd's windows process#. Lookup sshd.exe in Task Manager, or run $ tasklist | fgrep -ie 'sshd' You should get response like sshd.exe 2280 Console 0 4,800 K where process#=2280. 2 Determine the port# on which that process# is running. In bash, run $ netstat -ano | fgrep -e process# from previous step/ You should get response like TCP0.0.0.0:220.0.0.0:0 LISTENING 2280 where port#=22. 3 Add an exception for that port# to Windows Firewall: StartSettingsControl PanelWindows FirewallExceptionsAdd Port: Name=sshd (or whatever text you like) Port number=port# from previous step/ hit button=OK 4 Test connection from ssh client. (Presumably on another device, but I'm not sure that's required.) Reboot not required. thanks, Tom Roche tom_ro...@pobox.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
cygwin 1.7/emacs 23.1 time bug/workaround status?
summary: A cygwin-1.7/emacs-23.1 time bug and its workaround is known, but is it being tracked? details: Tom Roche Sun, 27 Dec 2009 21:51:58 -0500 (EST) After updating cygwin [from 1.5.x] to 1.7.1-1, Which has been otherwise delightful! which updated my emacs to 23.1, I now see (current-time-string) Mon Dec 28 01:21:44 2009 (current-time-zone) (-3600 GMT) when bash says $ date Sun Dec 27 21:21:44 EST 2009 Eli Zaretskii Mon, 28 Dec 2009 06:09:32 +0200 Try asking on the Cygwin list first. Or first try googling better :-( This bug was noted 10 months ago: http://www.cygwin.com/ml/cygwin/2009-02/msg00148.html I've built emacs 23 under both cygwin 1.5 and 1.7, and it runs fine for me except for a glitch involving time zones: Emacs gets the local time zone wrong by 4 hours. I've reported this to the emacs-devel list [1], and the developer who responded asked me to try to get some advice on this list. Here are two facts that might provide clues: 1. The problem disappears if I set the environment variable TZ before starting emacs. E.g. * in winxp SystemAdvancedEnvironment VariablesSystem variables set TZ= America/New_York This worked for me. * in cygwin bash, `export TZ=America/New_York` (I haven't tested) 2. The problem disappears if I run emacs under gdb. [This, of course, makes debugging difficult.] I would appreciate any advice or hints as to how I (and the emacs developers) might track this down. Also, the developers would find it useful to have a description of how cygwin handles Windows time zones. Is this bug currently being tracked by anyone? On the cygwin side, I don't know where there is a queryable bug tracker. On the emacs side, I don't see it in http://debbugs.gnu.org/cgi/pkgreport.cgi?include=subject%3Acygwin;package=emacs (which I believe is the Gnu Emacs bug tracker). TIA, Tom Roche tom_ro...@pobox.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: fastpath 0 - xterm?
Tom Roche Mon, Jun 29, 2009 at 02:29:30PM -0400 Since I'm not seeing this in the FAQ, I wanted to propose the following item: what would be required to go from zero to xterm? I.e. from a Cygwin-less windows box (windows = 2k) to getting a Cygwin/X xterm up on one's screen? Christopher Faylor Mon, 29 Jun 2009 16:45:18 -0400 You do understand what the F in FAQ stands for, right? I suspect folks frequently ask, Just how much pain will this involve? You may have noted that other projects frequently seek to demonstrate how easy it is to setup and do some simple task. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cannot convert string nil2 to type FontStruct
Tom Roche Sun, Jun 28, 2009 at 9:32 PM Despite installing package=font-misc-misc (recommended by http://cygwin.com/cgi-bin2/package-grep.cgi?grep=nil2 ) via setup.exe, everytime I start an xterm I get Warning: Cannot convert string nil2 to type FontStruct Jon TURNEY Mon, Jun 29, 2009 at 6:51 AM Installing the font-alias package and restarting the X server or xset fp rehash should fix that. Indeed font-alias did! (restarting, anyway--I usually shutdown before installing anything) Note to future enquirers: installing this one package seems to take a rather exceptionally long time, due to its postinstall script, but only ~60 sec. I think the problem is that the font-alias package contains the alias from the name 'nil2' to '-misc-nil-medium-r-normal--2-20-75-75-c-10-misc-fontspecific' an XLFD name which matches the actual font inside the 'nil2.pcf.gz' file. Perhaps to avoid this, xterm's setup.hint should list font-alias as a requirement since it names fonts defined there in it's default resources? I hope some day to understand X sufficiently well to make a reasoned judgement about this. Your assistance is appreciated, Tom Roche tom_ro...@pobox.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
fastpath 0 - xterm?
Since I'm not seeing this in the FAQ, I wanted to propose the following item: what would be required to go from zero to xterm? I.e. from a Cygwin-less windows box (windows = 2k) to getting a Cygwin/X xterm up on one's screen? From my recent experience, it seems to me the minimal install would be 0 whatever setup.exe wants to install by default/ 1 font-misc-misc 2 font-alias 3 ncurses 4 xinit 5 xterm Note that * this is not a minimal package set, as I've no interest in second-guessing what goes into the default Cygwin install * my personal experience was colored by my need to get emacs up, so I only tested adding the above plus emacs-X11 and font-adobe-dpi75. * I only tested on xp Perhaps someone else can test the following underdetailed (fastpath/ debug-free) 10-step procedure to go from zero to xterm: 0 login in as an admin 1 Decide where you want to install cygwin. Call that CYGWIN_ROOT, and note CYGWIN_BIN=CYGWIN_ROOT/bin 2 download latest setup.exe from http://cygwin.com/ 3 download and install the default packages plus font-misc-miscto avoid font problems font-aliasto avoid font problems ncurses maybe only for emacs? xinit to get startxwin.bat xterm for your xterm and let setup.exe install an icon (noting to where the icon installs, e.g. your desktop) 4 Add CYGWIN_BIN to your windows %PATH% 5 Run the Cygwin (non-X) bash, e.g. from the icon. 6 Configure your mounts. 7 Verify your mounts in a new Cygwin (non-X) bash (i.e. closing the one you initially opened). 8 Copy startxwin.bat (which should be in CYGWIN_BIN) to a suitable location (e.g. $HOME) and edit it appropriately. Obviously lotsa handwaving here, but a simple rootless, WM-less setup would include the (single) line %RUN% XWin -multiwindow -clipboard -emulate3buttons and running a simple xterm would involve a (single) line like %RUN% xterm +tb -sl 1000 -sb -rightbar -ms red -fg black -bg white -e /usr/bin/bash --login 9 run startxwin.bat; xterm ? success : debug FWIW, Tom Roche tom_ro...@pobox.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Cannot convert string nil2 to type FontStruct, was: post-upgrade problems
Tom Roche Mon, May 25, 2009 at 3:54 PM After upgrading from X 6.8.99.901-1 to 7.4-1, I had font problems, but could launch an xterm from the new cygwin. After attempting to fix that by installing fonts, I cannot launch an xterm Jon TURNEY Wed, May 27, 2009 at 4:48 PM (heavily edited) http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-how-do-i-get-rid-of-xterm-menu http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-where-are-my-fonts Thanks: those (and fiddling) have solved most of my problems. The one annoyance that remain is this: Despite installing package=font-misc-misc (recommended by http://cygwin.com/cgi-bin2/package-grep.cgi?grep=nil2 ) via setup.exe, everytime I start an xterm I get Warning: Cannot convert string nil2 to type FontStruct This doesn't seem to cause any functional problem, it just annoys. (I.e. I hafta hit Enter to get my prompt back.) Uninstalling and reinstalling font-misc-misc (via setup.exe) was no fix. Any suggestions? TIA, Tom Roche tom_ro...@pobox.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
post-upgrade problems
summary: After upgrading from X 6.8.99.901-1 to 7.4-1, I had font problems, but could launch an xterm from the new cygwin. After attempting to fix that by installing fonts, I cannot launch an xterm from the new cygwin. details: I'm attempting to debug a problem with the cygwin upgrade I attempted today (25 May 09). I haven't upgraded for about a year, so I went from xorg-x11-* version=6.8.99.901-1 to version=7.4-1. (For details of the old config, see http://www.unc.edu/~tr/cygcheck_20090525old_1404.txt Note that, * while `cygcheck` shows my winXP=SP2, I believe it's actually SP3, and up-to-date, except for WGA. * I'm able to switch between my old and new cygwins by changing windows paths and cygwin mounts. The old cygwin still works correctly: I'm using it to compose and send this post. ) I initially upgraded to the configuration represented by http://www.unc.edu/~tr/cygcheck_20090525new_1420.txt It had font-related problems: 0 When I started my initial xterm (via a copy of startXwin.bat), I noticed that it showed a toolbar, whereas my previous cygwin's xterms did not. Is that working as designed? 1 When I started my initial xterm, I noticed that all the chars in the toolbar were in the same huge font, though the body text of the xterm is normal. When I run emacs from the initial xterm $ emacs --debug-init I get the following problems 3 In the launching xterm: I see the error text Warning: Cannot convert string -*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-* to type FontStruct Warning: Cannot convert string -*-helvetica-medium-r-*--*-120-*-*-*-*-iso8859-1 to type FontStruct 4 In the launched emacs: all char in its menubar were in same huge font as the launching xterm's menubar. 5 In the launched emacs: all char in the body of its frame (i.e. where the text of a file would display) displayed as boxes, i.e. as unrepresentable. After perusing the cygwin-xfree archives, I decided I needed to install fonts. Instead of being cautious, I just installed all the font-* packages, resulting in the configuration http://www.unc.edu/~tr/cygcheck_20090525new_1530.txt but something went horribly wrong, since now I can't even launch an xterm :-( When I run my startXwin.bat, 0 the window for that batch file pops up briefly 1 the window for Xwin.exe opens briefly, then closes and I never get my xterm. When I try to open an xterm (or emacs) by right-clicking on the X in my tray and then choosing Applications xterm, nothing happens. (The only thing that I'm able to open with trayrclickApplications is notepad.) What should I do to fix this? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
problem setting cygwin $PATH
I'm attempting to debug a problem with the cygwin upgrade I attempted
today (25 May 09). But before I post about that, I'd like to fix a
problem I just noticed with my {old, backed-up, still working} cygwin:
duplicate cygwin paths.
I have this win32 path (formatted for clarity) before running cygwin,
taken from Control Panel\System\Advanced\Environment Variables:
e:\ProgramFiles\WindowsResourceKits\Tools\
e:\ProgramFiles\Cygwin\20090525old\bin
e:\ProgramFiles\Cygwin\20090525old\usr\X11R6\bin
C:\Program Files\ThinkPad\Utilities
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\Program Files\Diskeeper Corporation\Diskeeper\
C:\Program Files\ThinkPad\ConnectUtilities
e:\ProgramFiles\MySQL\Server\5.0\bin
C:\Program Files\Common Files\Lenovo
e:\ProgramFiles\OpenAFS\Common
e:\ProgramFiles\OpenAFS\Client\Program
which matches the output from cmd's `path`. But from a subsequent
Cygwin xterm (formatted for clarity):
$ echo $PATH
/usr/local/bin
/usr/bin
/bin
/usr/X11R6/bin
/usr/local/bin
/usr/bin
/bin
/usr/X11R6/bin
/e/ProgramFiles/WindowsResourceKits/Tools/
/usr/bin
/usr/X11R6/bin
/c/Program Files/ThinkPad/Utilities
/c/WINDOWS/system32
/c/WINDOWS
/c/WINDOWS/System32/Wbem
/c/Program Files/Diskeeper Corporation/Diskeeper/
/c/Program Files/ThinkPad/ConnectUtilities
/e/ProgramFiles/MySQL/Server/5.0/bin
/c/Program Files/Common Files/Lenovo
/e/ProgramFiles/OpenAFS/Common
/e/ProgramFiles/OpenAFS/Client/Program
Noted duplicate cygwin paths above. However I'm not setting PATH in
any of the usual places:
$ fgrep -e 'PATH' .bash_profile .profile profile | fgrep -ve 'KEY_PATH'
profile:# PATH=/usr/local/bin:/usr/bin:/bin:${PATH}
$ find . -maxdepth 1 -type f | grep -ve '~$' | xargs fgrep -e 'PATH' | fgrep
-ve 'KEY_PATH'
./.bash_history:echo $PATH
./.bash_history:echo $PATH
./.bash_history:echo $PATH
./profile:# PATH=/usr/local/bin:/usr/bin:/bin:${PATH}
Where else could these duplicate paths be set? Alternatively, how to
ensure that no duplicate paths are set?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: iconv.h?
Gerrit P. Haase wrote: http://cygwin.com/cgi-bin2/package-grep.cgi?grep=iconv.h Doh! Thanks, and thanks for fixing the setup.hint. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwinized XSL processor? (or sed for path transform?)
On Tue, 11 Mar 2003, Tom Roche wrote: my script does a lot of path translations like cygpath=/g/eclipse/builds/foo winpath=g:\\eclipse\\builds\\foo and it doesn't iterate over the paths. (Not a big deal, but it offends my software aesthetics :-) Igor Pechtchanski Tue, 11 Mar 2003 17:57:49 -0500 (EST) I suspect the -p and -f options to cygpath might be of some help to you. No, but cygpath -a is a great help! I can iterate over the windows paths, and get the cygwin paths from them with `cygpath -a $winpath`. Thanks for the suggestion! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwinized XSL processor? (or sed for path transform?)
Is there a cygwinized XSL processor? What I mean, why I ask: Occasionally I need to strip cruft out of a bunch (~1k) of xml files. Since they're distributed throughout a filesystem, and some additional processing is required, I use a bash script to get the input files. Feeding them to the processor should be trivial, but unfortunately the only command-line XSL processors I know about are Instant Saxon (from http://sourceforge.net/project/showfiles.php?group_id=29872 ) and Xalan (from http://xml.apache.org/xalan-j/ ). Instant Saxon is native windows, which is nice for this application, except that it chokes on the cygwin paths emitted by my script. Running Xalan from the commandline (like java org.apache.xalan.xslt.Process -in file -xsl file -out file ) would involve running a java, which (I suspect) would also choke on cygwin paths. As a result, my script does a lot of path translations like cygpath=/g/eclipse/builds/20030311_1000-WB210-AD-V51D-W2/eclipse/plugins winpath=g:\\eclipse\\builds\\20030311_1000-WB210-AD-V51D-W2\\eclipse\\plugins and it doesn't iterate over the paths. (Not a big deal, but it offends my software aesthetics :-) If I had a cygwinized XSL processor I wouldn't hafta do this. Does anyone know where I can get one? Alternatively, if I had more sed chops, I could script the path transformation, but I don't know how to do that either. (Could someone tell me how to do that?) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cygwinized Emacs HOWTO
Thanks to the help of lots of folks, I now have emacs goodness in both bash and X. I've tried to transfer the knowledge to http://www.emacswiki.org/cgi-bin/wiki.pl?CygwinizedEmacsHOWTO Feel free to add/modify. HTH another newbie. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
how to make startxwin.bat just like startx?
Is there a way to have startxwin.bat behave just like startx? I.e. to have the XFree86 window resulting from running startxwin.bat be just like the one resulting from running cygwin.bat, and then startx? I'd like to not maintain two sets of configuration files, so I'd like to be able to just work with startx, e.g. to have startxwin.bat invoke it somehow. Can that be done? if so, how?
Re: cygwin/emacs remaps C-h
On Mon, 14 Oct 2002, Tom Roche wrote: C-h is mapped to DEL in both X and -nox. So as a result I see (out-of-the-box) * Backspace removes character to left of mark * Delete removes character under mark * C-h removes character to left of mark Is there any way to restore it to its normal help-command role (without also screwing up Backspace and Delete)? I.e. make C-h, Backspace, and Delete works in Cygwin the way they do in normal NT emacs. which is: * Backspace removes character to left of mark * Delete removes character under mark * C-h prefixes help commands Eli Zaretskii Tue, 15 Oct 2002 08:19:00 +0200 Does the function normal-erase-is-backspace-mode help? Well, with that * Backspace prefixes help commands * Delete removes character under mark * C-h prefixes help commands So I'm still only 2/3rds of the way there. How to make Backspace remove the character left of mark? Fredrik Staxeng 15 Oct 2002 12:30:13 +0200 The backspace key should send ^? to the application running in cygwin window. Complain to the cygwin people, they ought to know better. Ask for xterm as the emulation while you at it, not yet another stupid emulator specific type. Does anyone know how I might configure this? Backspace is now the only aberrant key (in normal-erase-is-backspace-mode). Kris Thielemans Tue, 15 Oct 2002 11:04:39 does that mean you've sorted out the terminal problem then? (I didn't have any problems are doing the CYGWIN and TERM stuff) Yes, but it didn't work until after I installed emacs-X11! by the way, if you don't have a /usr/lib (as you mentioned), there's something very wrong with your installation! For example, your package list mentions libiconv2 1.8-2 libintl10.10.40-1 libintl20.11.5-1 libncurses5 5.2-1 libncurses6 5.2-8 libreadline44.1-2 libreadline54.3-2 these should all be in /usr/lib (which is actually the same as /lib due to your mount points) Hmm. I should probably try reinstalling. I did not delete my old cygwin (1.3.10) install before putting the new one on--perhaps that causes problems? Perhaps I should * nuke all my cygwins * install emacs-X11 note that C-h does work if you launch emacs from an xterm No, C-h was wrong for me out of the box after installing (and using) emacs-X11. (or use the X version). I'll try that. XWin comes up, now I need to learn how to set it up. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwin/emacs display problems, was: terminal-mode cygwin/emacs problem
Kris Thielemans Tue, 15 Oct 2002 11:04:39 does that mean you've sorted out the terminal problem then? (I didn't have any problems are doing the CYGWIN and TERM stuff) No, even after un/reinstalling, I still see * When emacs starts up, the display is usually shifted either down a line or to the right a column from where it should be, with extraneous characters showing in either the minibuffer, or the top of the display (first line under windows titlebar) or both. * After startup, the minibuffer's contents, and sometimes that of the window, shifts to the right. I can move it back via the horizontal scrollbar, but then I lose the first column of the minibuffer prompt (or of the contents of the window). * After startup, if I change buffers, garbage characters from the previous buffer (i.e. normal 7-bit ASCII chars, just ones that don't belong in the current buffer) are often visible in the new one. note that C-h does work if you launch emacs from an xterm Well, it took me awhile to figure out how to do this (nothing in the FAQ or User's Guide :-), but now I've documented it at http://www.emacswiki.org/cgi-bin/wiki.pl?CygwinizedEmacsHOWTO -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwin emacs HOWTO?
Is there a cygwin emacs HOWTO? If so, I'd appreciate a pointer. Use case: I download/setup cygwin 1.3.13-1, and download/setup emacs 21.2. I run bash, and (from ~) $ emacs emacs: Terminal type cygwin is not defined. If that is not the actual type of terminal you have, use the Bourne shell command `TERM=... export TERM' (C-shell: `setenv TERM ...') to specify the correct type. It may be necessary to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well. I get the same message for 'emacs -nw'? What do I need to tell emacs? or cygwin? or both? FWIW, I've been running cygwin ~daily for about a year (since 1.3.9), and running GNU emacsen for almost ten years (on various platforms, lately mostly w2k) (never ran xemacs). I was thrilled to hear today that there was a cygwin emacs, but I'll be a lot more thrilled if I can get it to work :-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin emacs HOWTO?
Tom Roche wrote: Is there a cygwin GNU emacs HOWTO? If so, I'd appreciate a pointer. I've made space for one at http://www.emacswiki.org/cgi-bin/wiki.pl?CygwinizedEmacsHOWTO I'm adding stuff as I learn, and I encourage folks who already know more to contribute. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
terminal-mode cygwin/emacs problem, was: cygwin emacs HOWTO?
terminal-mode cygwin/emacs problem emacs: Terminal type cygwin is not defined. If that is not the actual type of terminal you have, use the Bourne shell command `TERM=... export TERM' (C-shell: `setenv TERM ...') to specify the correct type. It may be necessary to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well. Tom Roche wrote: I get the same message for 'emacs -nw'? What do I need to tell emacs? or cygwin? or both? Joe Buehler replied: Make sure terminfo is installed -- there should be a file /usr/lib/terminfo/c/cygwin. There is not: there is not even /usr/lib. But when I run setup, it says Keep and version == 5.2-3. Unset TERMINFO if it is set. It is not: $ echo $TERM cygwin $ echo $TERMINFO Make sure the CYGWIN variable includes tty. I'm assuming you mean in the Windows environment? If so: I went to Control PanelSystemAdvancedEnvironment, made a new system variable CYGWIN, gave it the value tty (minus the quotes), and even rebooted: no change. Also, note that there is a separate package for X11 emacs. If you don't install it, all you get from the emacs package is the usual terminal-mode emacs. OK, I'll give that a shot. FWIW, cygcheck -s -v -r Cygwin Win95/NT Configuration Diagnostics Current System Time: Mon Oct 14 17:54:21 2002 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 2 Path:d:\bin d:\bin\cygwin\1.3.13-1\bin C:\WINNT\system32 C:\WINNT C:\WINNT\System32\Wbem G:\bin\cmvc\1.7\CMVC\EXE SysDir: C:\WINNT\System32 WinDir: C:\WINNT CYGWIN = `tty' Path = `d:\bin;d:\bin\cygwin\1.3.13-1\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;G:\bin\cmvc\1.7\CMVC\EXE; ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\tlroche.TLRIBM2312565\Application Data' CMVC_CASESENSE = `ignore' CommonProgramFiles = `C:\Program Files\Common Files' COMPUTERNAME = `TLRF204' ComSpec = `C:\WINNT\system32\cmd.exe' HOMEDRIVE = `C:' HOMEPATH = `\' INCLUDE = `C:\Program Files\ObjREXX\API' LIB = `C:\Program Files\ObjREXX\API' LOGONSERVER = `\\TLRF204' NLSPATH = `G:\bin\cmvc\1.7\CMVC\EXE\NLS\%N' NUMBER_OF_PROCESSORS = `1' OS = `Windows_NT' Os2LibPath = `C:\WINNT\system32\os2\dll;' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PCOMM_Root = `c:\pcomm2' PDBASE = `d:\ProgramFiles\Infoprint' PD_SOCKET = `6874' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 10, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `080a' ProgramFiles = `C:\Program Files' PROMPT = `$P$G' SOUNDPATH = `C:\WINNT' SystemDrive = `C:' SystemRoot = `C:\WINNT' TEMP = `c:\temp' TMP = `c:\temp' USERDOMAIN = `TLRF204' USERNAME = `tlroche' USERPROFILE = `C:\Documents and Settings\tlroche.TLRIBM2312565' windir = `C:\WINNT' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\13 HKEY_CURRENT_USER\Software\Cygnus
Re: terminal-mode cygwin/emacs problem
emacs: Terminal type cygwin is not defined. If that is not the actual type of terminal you have, use the Bourne shell command `TERM=... export TERM' (C-shell: `setenv TERM ...') to specify the correct type. It may be necessary to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well. Tom Roche wrote: I get the same message for 'emacs -nw'? What do I need to tell emacs? or cygwin? or both? Joe Buehler replied: Make sure terminfo is installed -- there should be a file /usr/lib/terminfo/c/cygwin. Well, I tried reinstalling terminfo, and now $ find / -name '*terminfo*' /etc/setup/terminfo.lst.gz /lib/terminfo /usr/doc/Cygwin/terminfo-5.2.README /usr/doc/terminfo-5.2 /usr/share/terminfo and emacs runs! However the display not quite right: when emacs starts up, the display is usually shifted either down a line or to the right a column from where it should be, with extraneous characters showing in either the minibuffer, or the top of the display (first line under windows titlebar) or both. Joe Buehler replied: note that there is a separate package for X11 emacs. If you don't install it, all you get from the emacs package is the usual terminal-mode emacs. So I tried installing emacs-X11: it also works, but it shares the same display-shifting defect as emacs-nox. How can I fix this? Alternately, is there a better way to report the problem (e.g. a bugzilla)? But for anyone else who gets the Terminal type error: try reinstalling. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwin/emacs remaps C-h
I have begun running the cygwinized emacs GNU Emacs 21.2 (i686-pc-cygwin) of 2002-10-14 that is setup.exe-able from cygwin 1.3.13-1. It was very easy to setup, but it has its quirks. One is that C-h is mapped to DEL in both X and -nox. Is there any way to restore it to its normal help-command role (without also screwing up Backspace and Delete)? I.e. make C-h, Backspace, and Delete works in Cygwin the way they do in normal NT emacs. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
