XEmacs function rtf-clip-region no longer works within X
Hello, I recently installed cygwin on my new laptop and see this strange behavior. When I start XEmacs within X then the function rtf-clip-region, does not seem to work. After calling this function, pasting in Word pastes as plain text. If I start XEmacs outside X then the function works as expected. The same is true of the sibling function rtf-clip-buffer. On the other hand, rtf-export works correctly both within and outside X. I checked on my old machine that rtf-clip-* functions work correctly. That machine has the same version of XEmacs (21.4 (patch 22) \Instant Classic\ XEmacs Lucid) Attached file cygcheck.out contains the output of cygcheck -s -v -r. Thanks in advance, - hemal cygcheck.out Description: Binary data -- 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] run does not work well
Hello, I installed cygwin 1.7 and I have problem to use run utility. I have a windows shell script for launching rxvt with option depending on hosts : SET DISPLAY=127.0.0.1:0.0 if defined CYGWIN_ROOT goto :OK set CYGWIN_ROOT=%~dp0 :OK SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET PATH=%CYGWIN_ROOT%\bin;%PATH% %RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %* If I set RUN to nothing and so run : bash /usr/local/bin/rxvtwin.sh %* I have my rxvt windows with my console, that's the good behaviour. But if I use run utility, no windows appears but a process rxvt is created. I think run hide the console window but also the rxvt window. I'm open to show you anything you want if you can help me. Thanks in advance, -- Florent Fievez -- 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: [ANNOUNCEMENT] [1.7] X11R7.5 [Emacs-gtk]
Yaakov (Cygwin/X) wrote:
Cygwin/X has been updated to X.Org X11R7.5.
It seems that after this upgrade, my GTK build[*] of Emacs has some problem.
First, the link on desktop with which I start Emacs does not work any
more. It was created with:
-
emacs=Emacs-2
emacs_cmd=G_SLICE=always-malloc emacs -display 127.0.0.1:0.0
mkshortcut -AD \
-n ${emacs} \
-a bash -l -c '${emacs_cmd}' \
-i /usr/local/bin/emacs.ico \
-d Editor di testo \
/usr/bin/run.exe
-
i.e. its target is:
C:\cygwin-2\bin\run.exe bash -l -c 'G_SLICE=always-malloc emacs -display
127.0.0.1:0.0 '
But if I run from an X shell or MinTTY:
$ G_SLICE=always-malloc emacs -display 127.0.0.1:0.0
it starts with the following warnings:
-
$
(emacs:2632): Pango-WARNING **: Error loading GSUB table 0x6EAD
(emacs:2632): Pango-WARNING **: Error loading GPOS table 0x6EAD
-
and seems to work.
Before this upgrade, i.e. with X11R7.4, it started without problems.
The problems arise only with GTK build.
The X server is started with a link on desktop (created likewise that of
Emacs):
C:\cygwin-2\bin\run.exe bash -l -c 'rm -rf /tmp/.X11-unix; XWin
-multiwindow -clipboard -silent-dup-error '
which I have put also in Start | Programs | Automatic Execution
Also rebuilding from scratch does not help.
Cheers,
Angelo.
---
[*] I did the build (usually with sources from CVS head) configuring with:
${source_dir}/configure --prefix=/usr/local/emacs
i.e. GTK is the default. Adding '--with-x-toolkit=lucid' makes the
'Xaw3d' build.
--
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 open a standalone xterm
Duh. Guess I need more sleep :) Thanks! On Wed, Oct 28, 2009 at 12:10 AM, Larry Hall (Cygwin X) reply-to-list-only-l...@cygwin.com wrote: On 10/27/2009 11:02 PM, Joel Gwynn wrote: So it looks like if I first start up the multiwindow window manager like so: xwin -multiwindow, then I can run xterm, but I have to specify the display. What's the typical way of automating this? startxwin.bat or startxwin.sh. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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/ -- 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 open a standalone xterm
And now, sporadically, when I run startxwin.sh, sometimes it works, ie opens up the xterm, but sometimes some windows open, with text that I can't read quickly enough, then go away. If I close Xwin and try again, sometimes it will work, mostly not. I don't see anything amiss in /var/log/XWin.0.log. How to troubleshoot? On Wed, Oct 28, 2009 at 9:01 AM, Joel Gwynn joel...@gmail.com wrote: Duh. Guess I need more sleep :) Thanks! On Wed, Oct 28, 2009 at 12:10 AM, Larry Hall (Cygwin X) reply-to-list-only-l...@cygwin.com wrote: On 10/27/2009 11:02 PM, Joel Gwynn wrote: So it looks like if I first start up the multiwindow window manager like so: xwin -multiwindow, then I can run xterm, but I have to specify the display. What's the typical way of automating this? startxwin.bat or startxwin.sh. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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/ -- 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/
What is correct way to start xterm from .XWinrc?
My .XWinrc file has this menu line: xterm EXEC xterm -e tcsh Since my default shell in /etc/passwd is /bin/tcsh, why should I need to specify it here also? If I don't specify it, a new xterm doesn't execute my ~/.cshrc file. I do not have a ~/.login or ~/.profile file. What is the right way to do this? Thanks - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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 open a standalone xterm
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Joel Gwynn Sent: Wednesday, October 28, 2009 8:27 AM And now, sporadically, when I run startxwin.sh, sometimes it works, ie opens up the xterm, but sometimes some windows open, with text that I can't read quickly enough, then go away. If I close Xwin and try again, sometimes it will work, mostly not. You're not running startxwin twice, right? That won't work - you must run the xterm command from an existing xterm, a cygwin window, or the xterm icon in the start menu (which can be copied to the quicklaunch bar). Also, try running bash in an existing xterm to see if the problem is in your .bashrc, i.e. not with xterm or X. HTH, Mike
RE: How to open a standalone xterm
On Wed, 2009-10-28 at 11:49 -0700, Mike Ayers wrote: From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Joel Gwynn Sent: Wednesday, October 28, 2009 8:27 AM And now, sporadically, when I run startxwin.sh, sometimes it works, ie opens up the xterm, but sometimes some windows open, with text that I can't read quickly enough, then go away. If I close Xwin and try again, sometimes it will work, mostly not. You're not running startxwin twice, right? That won't work - you must run the xterm command from an existing xterm, a cygwin window, or the xterm icon in the start menu (which can be copied to the quicklaunch bar). Also, try running bash in an existing xterm to see if the problem is in your .bashrc, i.e. not with xterm or X. HTH, Mike test this.. in startxwin.sh or startxwin.bat ( whichever one you're calling to start X ), between the call to start Xwin and the call to start the xterm, add sleep 5 if that gets you an xterm every time, then decrement 5 until failure, leave the call in with failure + 1 -- 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 open a standalone xterm
Ha! That seems to do it. Although I also have to wait a bit between closing the xwin window and restarting, but that's not so bad. I guess there's some process that takes awhile to exit. Thanks, Joel On Wed, Oct 28, 2009 at 2:58 PM, Reid Thompson reid.thomp...@ateb.com wrote: On Wed, 2009-10-28 at 11:49 -0700, Mike Ayers wrote: From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Joel Gwynn Sent: Wednesday, October 28, 2009 8:27 AM And now, sporadically, when I run startxwin.sh, sometimes it works, ie opens up the xterm, but sometimes some windows open, with text that I can't read quickly enough, then go away. If I close Xwin and try again, sometimes it will work, mostly not. You're not running startxwin twice, right? That won't work - you must run the xterm command from an existing xterm, a cygwin window, or the xterm icon in the start menu (which can be copied to the quicklaunch bar). Also, try running bash in an existing xterm to see if the problem is in your .bashrc, i.e. not with xterm or X. HTH, Mike test this.. in startxwin.sh or startxwin.bat ( whichever one you're calling to start X ), between the call to start Xwin and the call to start the xterm, add sleep 5 if that gets you an xterm every time, then decrement 5 until failure, leave the call in with failure + 1 -- 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/ -- 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: X11R7.5 and C.UTF-8
On Wed, 28 Oct 2009, Ken Brown wrote: X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server technically speaking, there's no such locale as C.UTF-8, so I'd not expect portable code to accept it (C and UTF-8 are mutually exclusive). with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits immediately, and the log has complaints about the locale. If I instead use 'LANG=en_US.UTF-8', there's no problem. I've attached both logs and cygcheck output. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: X11R7.5 and C.UTF-8
On 10/28/2009 5:23 PM, Thomas Dickey wrote: On Wed, 28 Oct 2009, Ken Brown wrote: X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server technically speaking, there's no such locale as C.UTF-8, so I'd not expect portable code to accept it (C and UTF-8 are mutually exclusive). Maybe my terminology is wrong. But if you start mintty with no .minttyrc and with LANG unset, mintty will set LANG=C.UTF-8. Trying to then start the X server via startxwin.bat or startxwin.sh leads to the error I reported. The error did not occur in X11R7.4. There's been a lot of discussion in the various cygwin lists leading to the decision that C.UTF-8 should be the default. Ken -- 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: X11R7.5 and C.UTF-8
2009/10/28 Thomas Dickey: X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server technically speaking, there's no such locale as C.UTF-8, so I'd not expect portable code to accept it (C and UTF-8 are mutually exclusive). Technically speaking, portable code should make no assumption whatsoever about the locale string. The meaning of that string is up to the OS, and portable code should be using POSIX interfaces such as the multibyte conversion functions or nl_langinfo to get at its meaning. C.UTF-8 is a language-neutral locale with a UTF-8 charset. It is also being introduced by Debain: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522776. Xwin 1.6.x had no problem with C.UTF-8. Andy -- 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: X11R7.5 and C.UTF-8
2009/10/28 Ken Brown: Maybe my terminology is wrong. But if you start mintty with no .minttyrc and with LANG unset, mintty will set LANG=C.UTF-8. Yep. That's primarily for emacs' benefit, which parses the locale env variables itself instead of using setlocale(LC_CTYPE, ), thereby missing out on Cygwin's default locale. (http://www.opengroup.org/onlinepubs/007908799/xbd/envvar.html says that if LC_ALL, LC_CTYPE, and LANG are all either unset or empty, the implementation-dependent default locale shall be used. For Cygwin 1.7, the default locale uses UTF-8 and not ASCII as assumed by emacs. It works correctly in vim.) Andy -- 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: X11R7.5 and C.UTF-8
Thomas Dickey wrote: On Wed, 28 Oct 2009, Ken Brown wrote: X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server technically speaking, there's no such locale as C.UTF-8, so I'd not expect portable code to accept it (C and UTF-8 are mutually exclusive). No, actually they are not. The C or POSIX locale is defined entirely in terms of character values -- not hexidecimal equivalents. That is, the set alpha shall contain 'a', 'b'... etc. The standard actually doesn't require that an implementation specify the encoding in which those character values are represented at all. You can, if you want, use 'HEX_CHAR', 'OCTAL_CHAR', and 'DECIMAL_CHAR' representations -- which implicitly require a specific encoding -- but the standard defines the 'C' locale entirely in terms of CHAR and CHARSYMBOL, which are encoding-agnostic. http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html#tag_07_03 Personally, I think it's a hole in the standard that it doesn't actually talk about the POSIX locale with encoding Y -- but then, they don't want to show preference between ASCII and EBCDIC, so UTF-8 sneaks in there. -- Chuck -- 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: X11R7.5 and C.UTF-8
Xwin 1.6.x had no problem with C.UTF-8. Actually it's libX11 that makes the difference: Xwin 1.7.1 is fine after downgrading libX11 from 1.3.2-1 to 1.2.2-2. Andy -- 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: X11R7.5 and C.UTF-8
On 28/10/2009 14:22, Ken Brown wrote: X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits immediately, and the log has complaints about the locale. If I instead use 'LANG=en_US.UTF-8', there's no problem. I've attached both logs and cygcheck output. Thanks for the bug report. I'm afraid I'm not immediately able to reproduce this, though, using the command you give. On 28/10/2009 21:49, Andy Koppe wrote: Xwin 1.6.x had no problem with C.UTF-8. The significant change is probably that libX11 is no longer built with X_LOCALE (so that libX11 uses the native locale support rather than it's own). Exactly why this would cause a problem, I don't know. -- 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: X11R7.5 and C.UTF-8
2009/10/28 Jon TURNEY: On 28/10/2009 14:22, Ken Brown wrote: X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits immediately, and the log has complaints about the locale. If I instead use 'LANG=en_US.UTF-8', there's no problem. I've attached both logs and cygcheck output. Thanks for the bug report. I'm afraid I'm not immediately able to reproduce this, though, using the command you give. You might have LC_ALL or LC_CTYPE set, which would override LANG. Or perhaps startxwin.bat overrides things somewhere along the way? To avoid all that, you could try invoking Xwin directly with LC_ALL set, which is top dog among locale variables. LC_ALL=C.UTF-8 xwin -multiwindow It fails with en.UTF-8 too (which also is a legal Cygwin locale), but it works with en_US.UTF-8. The significant change is probably that libX11 is no longer built with X_LOCALE (so that libX11 uses the native locale support rather than it's own). Exactly why this would cause a problem, I don't know. Hmm, that sounds like it should have improved matters if anything. Andy -- 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: Re: 1.5.25-15: 100% CPU under xdmcp and Gnome
Larry Hall (Cygwin X) wrote: Any interest in trying Cygwin 1.7 http://cygwin.com/#beta-test? I don't know if it would help but it has a newer X and friends and is actively maintained. One day in and it seems to be helping - no problems to report so far and the original problem has gone away with 1.7. Thanks for the suggestion. Quinn -- 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 open a standalone xterm
Joel Gwynn wrote: Ha! That seems to do it. Although I also have to wait a bit between closing the xwin window and restarting, but that's not so bad. I guess there's some process that takes awhile to exit. possibly having to wait for the X server socket to completely free up between between shutdown and restart -- 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/
