Re: Paste from xterm to Emacs no longer works
Ken Brown kbr...@cornell.edu writes: While waiting for this, I'll make a wild guess that his problem is related to the selection changes that started with emacs-24.1. Browse the NEWS file (`C-h n') and search for Selection changes. Thank you for trying to help. I found that when I googled, but I did not find it helpful at first. I think the following is incomplete. *** `x-select-enable-primary' now defaults to nil. Thus, commands that kill text or copy it to the kill-ring (such as M-w, C-w, and C-k) also use the clipboard---not the primary selection. I think that x-select-enable-primary also affects C-y. I tried to paste with the scroll wheel, but apparently that generated mouse-4, not mouse-2. But I really want to paste with the right mouse button. In .emacs: (global-set-key [mouse-3] 'mouse-yank-primary) In .Xdefaults: XTerm*VT100.Translations: #override \ KeyBackSpace: string(0x7f) \n\ ~Shift ~Ctrl ~Meta Btn1Up: select-end(PRIMARY, CLIPBOARD) \n\ ~Shift ~Ctrl ~Meta Btn3Down:ignore() \n\ ~Shift ~Ctrl ~Meta Btn3Up: insert-selection(PRIMARY, CLIPBOARD) (When I first tried to post this, I got the backspace invokes help problem. I put in the fix for that also) -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/
Paste from xterm to Emacs no longer works
How do I get it to work again? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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: Paste from xterm to Emacs no longer works
This works for me: (global-set-key [mouse-3] 'mouse-yank-primary) -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/
startxwin.bat - Can't open display, but taskbar icon appears
and I can start xterm from that! I changed the timeoutfor checkX to 60, and then it works. What can make XWin.exe take so long to start up? Could it be reverse name lookup? If so, how can I solve that without providing working reverse lookup? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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: 1.7 - what's the right way to start X?
Larry Hall (Cygwin X) reply-to-list-only-l...@cygwin.com writes: On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? What about startxwin.bat doesn't work for you? There shouldn't be differences between 1.5 and 1.7 here. Now I have gotten startxwin.bat to work, and modified it to run my bash script. I had some strange problems on the way though. Previously, I had used the Cygwin Bash Shell to make some changes. I use mount -c /, change /etc/passwd to refer to right home directory /c/home/fstx, and put in my .profile and .bash_rc files. I don't remember doing the mkpasswd/mkgroup thing, but I could have. When I double-clicked startxwin.bat for the first time, it failed. I think XWin.exe did not start dfor some reason. But I immediately tried again, and this time I got an XTerm. However, I was in /home/fstx, not /c/home/fstx, and I got the mkpasswd message. When I tried to fix things, I discovered that the mount prefix was set back to /cygdrive. I can change it, but when I restart cygwin it goes back to /cygdrive. I can live with that (at least for now) But starting xterms seems to be very slow, and about 25% of time it fails with 2 [main] xterm 3128 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0xC005, errno 11 xterm: Error 29, errno 11: Resource temporarily unavailable Reason: spawn: fork() failed I have seen this problem before, and the solution was to run rebaseall, which broke emacs, and then reinstall libncurses to fix emacs. Is this the way to do it? Will it still break emacs? Will other things break? Will it break again when updating cygwin? I am running Windows 7 64-bit Enterprise. Despite the troubles I have had, I must say that I admire Cygwin for doing a very good job at an almost impossible task, and the developers for the heroic efforts to bring Cygwin to each new version of Windows, despite that Microsoft apparently couldn't care less about breaking it. -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/
1.7 - what's the right way to start X?
What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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: 1.7 - what's the right way to start X?
Larry Hall (Cygwin X) reply-to-list-only-l...@cygwin.com writes: On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? What about startxwin.bat doesn't work for you? There shouldn't be differences between 1.5 and 1.7 here. Well, I did not find it, so I assumed it had been replaced with something better. Something that a) does not pop up a command window and b) calls .xinitrc or something I have to admit I did not look at the Cygwin site before posting the question. I did so after, and saw the Cygwin/X section. -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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: X / gtk-x11 / flicker and other problems
John Emmas john...@tiscali.co.uk writes: monitor set to 1600x1200, Cygwin-X's text is still crisp and clear - whereas gtk-win32's looks decidedly fuzzy. Cygwin-X uses bit-mapped fonts, with only black and white pixels, perhaps gtk-win32 uses some form of antialiasing? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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: xinit requires util-linux which requires perl
Mark Geisert m...@maxrnd.com writes: In the interests of PTC I could try to figure out a better package to contain chkdupexe, or mcookie for that matter. Or recode chkdupexe as a shell script. Is anything else but startx using mcookie? If not, why not move it there. -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/
Cygwin-X on Windows 7 Beta Success!
I have been running Cygwin with X on Windows 7 Beta for a few weeks. It works. I think it works rather well considering what it does. I had to do the rebase/reinstall libncurses thing, but then most things work with only a few problems. First, the startxwin icon succeeds in bringing up the the X server, but not the xterm. But when I run my start script from a Cygwin command prompt it works. Then, the first xterm appears instantly, but the second one takes a while (half a minute?). This seems very strange to me, so perhaps I am imagining things. Also, sometimes, e.g when running M-x grep in emacs, what look like command prompt windows flashes by quickly. They appear and then disappear. This does not really bother me much, but it kills the show-off potential. The audience would womder about those flashing windows and stop paying attention to the good things. Is there any way I could help with fixing these problems? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/
How to get xterm to send ESC x when I press Alt-x
; xrdb -q | grep meta XTerm*metaSendsEscape: true ; xmodmap -e 'keysym Alt_L = Meta_L' -e 'keysym Alt_R = Meta_R' no longer seems to be sufficient. Is there something more that needs to be done? Or did this break again? Background: I am swedish. I want the key labeled Ö on my keyboard works exactly as the key labeled O, except of course there should be two dots on the letter. I also want to be able to use M-v to page up in emacs, using the Alt key as the Meta modifier. This of course works with Emacs under X, but I also cygwin xterm to ssh to a Linux box where I run emacs -nw. This is not possible using the default Meta behaviour, since the code for ö is 0366 (octal), which happens to be the same as (v + 128). But it works if Meta sends escape. -- Fredrik Stax\ang | rot13: [EMAIL PROTECTED] This is all you need to know about vi: ESC : q ! RET -- 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: emacs does not work, emacs-nox works
Larry Hall (Cygwin X) [EMAIL PROTECTED] writes: Fredrik Staxeng wrote: Xwin works, xterm works, but when I try to run emacs it just silently exits. Run 'cygcheck emacs' and see if it reports any missing DLLs. If so, find this missing package(s) you need to install via 'cygcheck -p missing DLL name'. Rerun 'setup.exe' and install those packages. Try again. Thank you for your help, it wprks now. Turns out the missing dll was cygtiff4.dll, which is in the libtiff4 package. Is setup.exe supposed to handle dependencies? Should I file a bug report? -- Fredrik Stax\ang | rot13: [EMAIL PROTECTED] This is all you need to know about vi: ESC : q ! RET -- 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/
emacs does not work, emacs-nox works
Xwin works, xterm works, but when I try to run emacs it just silently exits. -- Fredrik Stax\ang | rot13: [EMAIL PROTECTED] This is all you need to know about vi: ESC : q ! RET -- 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/
