I'm a bit confused about those. They didn't change during the xorg
transition, did they? I could have sworn they sent VT220-style ^[[1;
and ^[[4; but actually they send PC-style ^[[H and ^[[F. Of course I
should have realised this when I changed F1 to F4 to PC-style codes in
MinTTY ...
D'oh,
Andy
2009/6/23 Jon TURNEY:
Always assuming that /bin/bash exists, or that /bin/sh is bash is probably
bad style for portability across unicies.
However, in this specific case, it's probably ok.
You never know. If posix_spawn() ever gets implemented in Cygwin to
avoid the slowness of fork(),
2009/6/29 Jon TURNEY:
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?
font-adobe-dpi100 (and -dpi75?) should probably be xterm's or
xorg-server's dependencies as well, otherwise you get a warning
2009/7/28 neomjp:
The recent xterm is configured with --enable-luit, but /usr/bin/luit is
currently broken.
$ cygcheck -f `which luit`
luit-1.0.3-1
$ luit
Couldn't allocate pty: No such file or directory
The cause of this error and a possible fix is in
2009/9/30 Marc Girod:
Hello,
My last cygwin upgrade changed the fonts used in GNU emacs.
This is:
xorg-server 1.6.3-1 OK
emacs 23.1-10 OK
cygwin 1.7.0-61 OK
font-alias 1.0.1-1 OK
Until now, I belive I was using:
2009/10/1 Ken Brown:
I'm cc-ing the cygwin-xfree list, which is where I think fontconfig
questions belong. I can confirm that on my system, fc-list produces strange
output on the windows system fonts. I'm not sure if it's the same problem
you were reporting.
For example, I get the
2009/10/2 Yaakov (Cygwin/X):
The following package has been updated for Cygwin 1.7:
*** luit-1.0.4-1
This is an update to the latest upstream version, and should fix several bug
reports which have been reported to the list lately.
Working nicely here. Thanks!
Andy
--
Unsubscribe info:
2009/10/5 Corinna Vinschen:
There's a difference, though, when starting xterm via the `run -p xterm
-ls' shortcut. With Cygwin -61, xterm just starts tcsh and it works,
with Cygwin -62, xterm tries to start the shell via luit, and that
fails. If luit is missing on the system (renamed), xterm
2009/10/22 Edmund Spatzenegger:
I've tried to install XServer 1.6.0 but Cygwin setup only offers me 1.5.3
(I've downloaded the latest version of setup.exe: 2.573.2.3).
Is there anything else I have to do?
XWin 1.6.x is only available with the Cygwin 1.7 beta:
http://www.cygwin.com/#beta-test
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
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
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
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',
2009/10/29 Jon TURNEY:
I've put a patch in bugzilla [1] which can be applied to
/usr/share/X11/locale to temporarily repair this problem.
This needs to be looked at more deeply, though, as I'm not sure I've fully
understood what that locale data is being used for, or specified C.UTF-8
2009/11/3 Jon TURNEY:
On second look, this patch doesn't seem to be quite right, as it makes the
en_US.UTF-8 compose sequences available in C.UTF-8 (which is not the case in
the C locale).
I think that's ok. The compose sequences don't make sense in an ASCII
locale, since ASCII doesn't contain
2009/11/28 Ken Brown:
On 10/28/2009 6:07 PM, Andy Koppe wrote:
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
2009/11/30 Thomas Dickey:
Gone for Thanksgiving break, return and update cygwin, and now xterm
does not show anymore. I have not upgraded to the latest 1.7 (I am waiting
for the official release). I read the other messages and nothing seems to
work.
Does anyone have a SIMPLE solution
2009/11/30 Fergus:
(Sorry to send twice: originally sent yesterday Sunday 0728 GMT but never
arrived at cygwin-xfree at cygwin dot com; 2nd attempt today Monday 0752 GMT
and hope for better progress.) Message was:
Thank you.
1 Will this amendment eventually be incorporated into an updated
2009/11/30 Corinna Vinschen:
Gone for Thanksgiving break, return and update cygwin, and now xterm
does not show anymore. I have not upgraded to the latest 1.7 (I am
waiting for the official release). I read the other messages and nothing
seems to work.
Does anyone have a
2009/12/3 Linda Walsh:
C.UTF_8 doesn't exist.
Well, guess what: it does in Cygwin 1.7, and it's the default locale.
And it's also in the next Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522776.
Cygwin 1.7 also supports C.ISO-8859-1, C.CP1252, ...
Might want to try 'Console'
2009/12/3 Thomas Dickey:
From
http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html,
§7.2:
The tables in Locale Definition describe the characteristics and
behavior of the POSIX locale for data consisting entirely of
characters from the portable character set and the
2009/12/24 Simon Jean-Francois:
I wanted to share some of my experiences when upgrading to cygwin 1.7.1:
XWin would not start, /var/log/XWin.0.log reporting the following error:
(EE) Error compiling keymap (server-0)
After some time, I figured out the source of the problem:
/bin/sh
2009/12/30 Gary Carvell:
X issues including xterm ones should go to the cygwin-xfree list. I'm
sending this to both lists, but please respond on cygwin-xfree only.
With the upgrade to Cygwin 1.7, I found that the Alt key is no longer
recognized as a Meta key in xterm. This means the Alt based
2010/1/1 Thomas Dickey:
On Fri, 1 Jan 2010, Andy Koppe wrote:
XTerm*vt100.metaSendsEscape: true
Actually that's not a hack, but the correct solution. I think this
needs to be part of the default config in /etc/X11/app-defaults/XTerm.
However, the reason that it's not is because there's
2010/1/1 Thomas Dickey:
Is Cygwin also specifying a meta key?
(some people equate meta==alt, though they're not necessarily the same)
I don't know whether there's ever been an official policy decision on
that, but I think the general assumption among Cygwin users is that
Alt==Meta, since of
2010/1/7 Chuck:
Seems like the character mapped to the backspace key changed from ^H to
^? with the upgrade to 1.7. Is there a way to get the old mapping back?
What terminal do you use? (The cygwin-xfree list is meant for X issues.)
Andy
--
Unsubscribe info:
2010/1/7 Andrew Zhezherun:
I have a weird problem with the latest Cygwin 1.7. It happens with
both a fresh install on a Windows 7 machine and with an upgraded
install of Cygwin on a Windows XP machine. When I execute various
commands from Midnight Commander when it is running under Cygwin/X
2010/1/8 Chuck:
Seems like the character mapped to the backspace key changed from ^H to
^? with the upgrade to 1.7. Is there a way to get the old mapping back?
What terminal do you use? (The cygwin-xfree list is meant for X issues.)
The cygwin xterm program
You can change the backspace key
2010/1/15 Derek Greer:
I discovered that the problem is specific to my PS1 settings, but a bug
nevertheless. The prompt I've used for years is:
PS1='\[\033]0;\w\007\033[32m\][\h]: \[\033[33m ${PWD##*/}\033[0m\] '
Only non-printing must be enclosed in \[ ... \] , but you've got
${PWD##*/}
Markus Hoenicka:
xterm: Could not exec 4.90.2.20040617: No such file or directory
Jon TURNEY:
Google suggests '4.90.2.20040617' is a novell netware client version.
Good catch. I use a Windoze client on a Netware network at work, so
this client is likely to be installed. But then, why would
On 16 July 2010 15:39, Olwe Melwasul wrote:
On Fri, Jul 16, 2010 at 8:50 AM, Jon TURNEY wrote:
I installed cygwin/xcygwin 1.7.5 with KDE.
I don't know where you got KDE from, but it's not in the standard cygwin
distribution. If you have problems with KDE, perhaps you should try the
place
On 3 August 2010 14:35, Jon TURNEY wrote:
On 03/08/2010 10:00, Thomas Dickey wrote:
On Tue, 3 Aug 2010, Ryan Johnson wrote:
At some point an annoyance appeared with my xterm windows: The first time
I
use [ctrl]+mouse click in any window, that xterm becomes unresponsive for
about 5 seconds
On 7 August 2010 23:07, Jon TURNEY wrote:
Hmmm, looking again at the implementation of select(), I don't immediately
see that when waiting on /dev/windows, it checks that the message queue has
old messages on it before waiting. The MSDN documentation for
MsgWaitForMultipleObjects() seems to
On 9 August 2010 19:12, L.Wood wrote:
if cygwin terminal supports copy and paste, I couldn't figure it out...
Right click on titlebar, Edit-Mark, drag left mouse button to select,
right click to copy. Yep, it's terrible, but that's the standard
Windows console for you. Enable 'Quick Edit' in its
On 14 August 2010 12:57, Ryan Johnson wrote:
I just tried to pull down the Athena widget libraries (xaw and xaw3d) and
got an unmet dependency message for libXpm-devel.
It's not a big deal, since it offered to add it to my list, but a bit odd (I
just clicked on each once... none of the
On 15 August 2010 18:32, Dan Tsafrir wrote:
I've done exactly this, then tried to install some X stuff and got:
Package: xinit
xinit.sh exit code 8
Package: No package
xinit.sh exit code 8
It turns out that the above error message is generated by the second
On 11 October 2010 17:02, reckoner wrote:
Evidently, there is some subtle difference in how the DISPLAY variable,
which is set in the user startup files is processed by rxvt as opposed to
mintty.
Ultimately, although the DISPLAY variable is clearly set in the user startup
files, I
On 1 December 2010 11:34, Ajay Jain wrote:
I use bash on Xterm.
While working you press Ctrl-L, so that the screen gets cleared and
you see the currently line only. But you may want to see the last
outputs/prints. However, if you do a Ctrl-L/clear command, these
prints go away. In that case,
On 1 December 2010 21:24, Thomas Dickey wrote:
By the way, the clearing of the screen on ctrl/L is not done by xterm.
(PuTTY does this, in case you're mistaking it for xterm, otherwise
I'd assume bash is doing it).
Yep, bash sends '\e[2J' when ^L is pressed. PuTTY's behaviour of
interpreting
On 18 December 2010 01:33, Marshall, Lee wrote:
One has a windows icon and the text Warning: Missing charsets in String to
FontSet conversion
The other has the X icon with a menu bar and sh-3.2$.
My biggest objection to this is just the clutter of having a second, useless
window open
On 31 March 2011 19:45, Larry Breyer wrote:
I am really glad I switched from rxvt to mintty as it works great with or
without X11.
I am seeing one problem, though, where I wonder if there is a fix.
Mintty isn't actually an X11 program, so cygwin-xfree is the wrong
list for this. Please send
On 21 November 2011 17:57, Jim Reisert AD1C wrote:
All my work work is X-based, I'm super-comfortable with the
interface, for example, using the mouse for copy/paste which is a
little more awkward in mintty.
In what way?
Andy
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On 21 November 2011 23:45, Ryan Johnson wrote:
On 21/11/2011 4:25 PM, Jim Reisert AD1C wrote:
On Mon, Nov 21, 2011 at 1:20 PM, Ryan Johnson wrote:
Eh? Mouse copy/paste in mintty is identical to xterm AFAIK... select =
copy,
middle button = paste. If you're in a mouse-using terminal app you
43 matches
Mail list logo
