On 05/05/2014 19:39, Nem W Schlecht wrote:
For over a month now I've been having issues with my xterms in Cygwin.
If I try to access *any* menu item under the Ctrl-mouse button menu
items (change font, turn on/off scrollbar, redraw window, etc.), my
xterm crashes the moment I un-press my mouse
Thanks for the reply, Jon! I'm happy you were able to reproduce the
issue - I assumed I had screwed something up in my environment. :)
Your attempted fix with rebase worked perfectly - all of my menus are
now working correctly. If you'd like me to do any additional testing
in the future, don't
On 01/08/2013 01:55, Jeremy Elson wrote:
I recently upgraded from the 32-bit to the 64-bit build of Cygwin
1.7.22 on Windows 8 x64. For the most part, everything works
identically (except faster!). But I have noticed one problem: xterm no
longer seems to respond to the magic escape codes that
On Thu, Aug 1, 2013 at 10:28 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
On 01/08/2013 01:55, Jeremy Elson wrote:
I recently upgraded from the 32-bit to the 64-bit build of Cygwin
1.7.22 on Windows 8 x64. For the most part, everything works
identically (except faster!). But I have
On Mon, Feb 11, 2013 at 12:23:43PM +0100, marco atzeri wrote:
after last package update I noticed two issues:
on .XWinrc I was forced to change
The first one was reported a week ago as FreeBSD #175782,
and is fixed in #289 (last Friday).
$ xfontsel.exe
Warning: Missing charsets in String
On 2/11/2013 12:42 PM, Thomas Dickey wrote:
On Mon, Feb 11, 2013 at 12:23:43PM +0100, marco atzeri wrote:
after last package update I noticed two issues:
on .XWinrc I was forced to change
The first one was reported a week ago as FreeBSD #175782,
and is fixed in #289 (last Friday).
nice to
From: Thomas Dickey
I did consider providing a special resource value that would suppress the
xterm-specific icon (such as none or default), but decided to see what
type of feedback I'd get first.
I like having a specific xterm icon in the taskbar to make it clear which X
application is
On Thu, Oct 18, 2012 at 04:35:24PM +, Matt Seitz (matseitz) wrote:
From: Thomas Dickey
I did consider providing a special resource value that would suppress the
xterm-specific icon (such as none or default), but decided to see what
type of feedback I'd get first.
I like having a
On Mon, Oct 15, 2012 at 05:58:10PM +, Matt Seitz (matseitz) wrote:
Did this update change the XTerm icon that is displayed in the Windows task
bar?
Previously, when I launched the XWin Server, I would see the x.org logo (a
black X with an orange ring) in the task bar as the icon for the
On Mon, Oct 15, 2012 at 11:58 AM, Matt Seitz wrote:
Did this update change the XTerm icon that is displayed in the Windows task
bar?
Yes, it reminds me of the Texas Rangers logo (American baseball team).
--
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us
--
Unsubscribe info:
On Mon, Oct 15, 2012 at 03:42:02PM -0600, Jim Reisert AD1C wrote:
On Mon, Oct 15, 2012 at 11:58 AM, Matt Seitz wrote:
Did this update change the XTerm icon that is displayed in the Windows task
bar?
Yes, it reminds me of the Texas Rangers logo (American baseball team).
Looking at that,
On Sat, Jul 28, 2012 at 02:49:22PM +0200, Paul Maier wrote:
Hi,
xterm -si doesn't work as expected.
The short answer is that it's always been that way :-)
This refers to the scrollTtyOutput, which in xterm is described:
scrollTtyOutput (class ScrollCond)
Specifies
On 11/9/2011 8:09 PM, Thomas Dickey wrote:
On Wed, 9 Nov 2011, Jesse Ziser wrote:
Hello,
I find that adding the following:
XTerm*vt100.metaSendsEscape: true
XTerm*vt100.altSendsEscape: true
XTerm*vt100.eightBitInput: false
to my .Xdefaults does not seem to change the way XTerm behaves WRT
On Wed, 9 Nov 2011, Jesse Ziser wrote:
Hello,
I find that adding the following:
XTerm*vt100.metaSendsEscape: true
XTerm*vt100.altSendsEscape: true
XTerm*vt100.eightBitInput: false
to my .Xdefaults does not seem to change the way XTerm behaves WRT meta-key
handling. It still sends 0xF7 for
I'm eagerly expecting an update to xterm 270 which I hope includes the
fix for the scrollbar drawing issue
You can get 269 from git:
http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/xterm;a=summary
To build 270 just modify the 269 .cygport.
When I build 269 or 270 the
On Thu, 19 May 2011, webmaster wrote:
I'm eagerly expecting an update to xterm 270 which I hope includes the
fix for the scrollbar drawing issue
You can get 269 from git:
http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/xterm;a=summary
To build 270 just modify the 269
perhaps your development environment lacks the FreeType library
(that would show up in the configure step)
Ah, indeed. Thanks!
For anyone who can't wait for xterm 261 to be included, here's
version 270: http://www.donsbox.com/~dfelicia/xterm-270-1.tar.bz2
--
Unsubscribe info:
On 01/04/2011 17:05, Jim Reisert AD1C wrote:
On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote:
On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote:
Could someone try this with the latest snapshot? I haven't made any
changes but I just want to confirm that it still fails with
On Mon, Apr 04, 2011 at 02:27:27PM +0100, Jon TURNEY wrote:
On 01/04/2011 17:05, Jim Reisert AD1C wrote:
On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote:
On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote:
Could someone try this with the latest snapshot? I haven't made any
FWIW, I know what is causing the problem but not how to fix it. It's
similar to
http://cygwin.com/ml/cygwin/2011-04/msg1.html
Rebasing should fix that particular problem but it's not a panacea.
The strace output in that other thread shows that GetLastError of 997
formerly caused some
On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C
jjreis...@alum.mit.edu wrote:
On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote:
Could someone try this with the latest snapshot? I haven't made any
changes but I just want to confirm that it still fails with something
close to what
On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote:
Could someone try this with the latest snapshot? I haven't made any
changes but I just want to confirm that it still fails with something
close to what will become Cygwin 1.7.9.
http://cygwin.com/snapshots/
You just have to
On Fri, Mar 25, 2011 at 01:22:42AM -0400, Christopher Faylor wrote:
On Thu, Mar 24, 2011 at 10:09:38PM -0600, Jim Reisert AD1C wrote:
On Thu, Mar 24, 2011 at 5:24 PM, webmaster wrote:
http://www.donsbox.com/~dfelicia/xterm-269[redacted]
Still dumps, but xterm came up anyway:
Exception:
On Wed, 23 Mar 2011, Yaakov (Cygwin/X) wrote:
On Wed, 2011-03-23 at 19:16 -0600, Jim Reisert AD1C wrote:
Thomas, that may well be true, but the latest one in the Cygwin
repository reports (261). It shows up as 261-1 in setup.exe
I just built 269 and will uploaded it with the rest of the X11
I just built 269 and will uploaded it with the rest of the X11 updates.
Probably in some FAQ and I just can't find it, but where would one get
xterm-269.cygport et al. for local building? Some git repository,
somewhere?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
where would one get xterm-269.cygport et al. for local building?Answered my
own question:
http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/xterm;a=summary
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
I just built 269 and will uploaded it with the rest of the X11 updates.
It doesn't help. I built using cygport from what you've got in git and
I still get:
Exception: STATUS_ACCESS_VIOLATION at eip=61020497
eax=00DA80E0 ebx=6124298C ecx=76A10D06 edx=00371D48 esi= edi=0028F9F4
On Thu, Mar 24, 2011 at 5:24 PM, webmaster wrote:
http://www.donsbox.com/~dfelicia/xterm-269[redacted]
Still dumps, but xterm came up anyway:
Exception: STATUS_ACCESS_VIOLATION at eip=61020497
eax=00DD00F8 ebx=61246A44 ecx=75570D06 edx=00334118 esi= edi=0028F9F4
ebp=61020BE0
On Thu, Mar 24, 2011 at 10:09:38PM -0600, Jim Reisert AD1C wrote:
On Thu, Mar 24, 2011 at 5:24 PM, webmaster wrote:
http://www.donsbox.com/~dfelicia/xterm-269[redacted]
Still dumps, but xterm came up anyway:
Exception: STATUS_ACCESS_VIOLATION at eip=61020497
eax=00DD00F8 ebx=61246A44
On Tue, Mar 22, 2011 at 11:28 AM, Jim Reisert AD1C
jjreis...@alum.mit.edu wrote:
On Tue, Mar 22, 2011 at 11:15 AM, webmaster wrote:
After updating to the latest cygwin 1.7.8, today, xterm constantly crashes.
cat xterm.exe.stackdump
[...]
Usually rebaseall fixes this problem, but not this
On Wed, 23 Mar 2011, webmaster wrote:
what is xterm -v?
$ xterm -v
XTerm(261)
That's from last June. #263 makes a fix for a problem which might be
relevant (and #265 fixes a regression from #263).
Note I built myself using cygport so that I could add
--disable-narrowproto (See thread
On Wed, Mar 23, 2011 at 3:17 PM, Thomas Dickey wrote:
#269 is current. At the moment, the only fixes I've made against that
are minor things (an incomplete change for the fullscreen feature, and
an obscure case of a control sequence from #251 changes).
Thomas, that may well be true, but the
On Wed, 2011-03-23 at 19:16 -0600, Jim Reisert AD1C wrote:
Thomas, that may well be true, but the latest one in the Cygwin
repository reports (261). It shows up as 261-1 in setup.exe
I just built 269 and will uploaded it with the rest of the X11 updates.
Yaakov
Cygwin/X
--
Unsubscribe
On Tue, Mar 22, 2011 at 11:15 AM, webmaster wrote:
After updating to the latest cygwin 1.7.8, today, xterm constantly crashes.
cat xterm.exe.stackdump
[...]
Usually rebaseall fixes this problem, but not this time. I also tried
building xterm with cygport, but same result. This is on
On my Win7 system, [xterm] crashes about 1/2 the time.
Right. Same, here. It used to crash a lot less frequently.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:
On Tue, 22 Mar 2011, webmaster wrote:
On my Win7 system, [xterm] crashes about 1/2 the time.
Right. Same, here. It used to crash a lot less frequently.
what is xterm -v?
(the last crash-related bug I recall was fixed last spring).
--
Thomas E. Dickey
http://invisible-island.net
On Tue, Mar 22, 2011 at 11:28 AM, Jim Reisert AD1C
jjreis...@alum.mit.edu wrote:
On Tue, Mar 22, 2011 at 11:15 AM, webmaster wrote:
After updating to the latest cygwin 1.7.8, today, xterm constantly crashes.
cat xterm.exe.stackdump
[...]
Usually rebaseall fixes this problem, but not this
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
Hi Ajay,
On Mon, Nov 1, 2010 at 5:59 AM, Ajay Jain wrote:
Hi,
I want my Xterm to display a constant title say mercury. So I use:
Xterm -T mercury. Further, I have placed the following line in my
.Xresources: xterm*allowTitleOps: 0. From my .vnc/xstartup, I also do:
xrdb -merge
On 8:59 PM, Thomas Dickey wrote:
As far as I know, xterm's never sent more than one byte for either x/y in
a button event. Ditto for rxvt. It sounds like a useful idea, except
that it would of course be incompatible with the existing applications.
So it would have to be enabled by a new
On Sat, 14 Aug 2010, Ryan Johnson wrote:
On 8:59 PM, Thomas Dickey wrote:
As far as I know, xterm's never sent more than one byte for either x/y in
a button event. Ditto for rxvt. It sounds like a useful idea, except that
it would of course be incompatible with the existing applications.
On Thu, 12 Aug 2010, Ryan Johnson wrote:
Hi all,
I'm running into a strange one...
At some point in the past (on linux because I didn't know about cygwin yet),
xterm used to send the following control sequence for a mouse click at row 1,
col 250
ESC [ M SPC \303\206 ! ESC [ M # \303\206 !
On Wed, 30 Jun 2010, Thomas Dickey wrote:
On Wed, 30 Jun 2010, webmaster wrote:
All releases of xterm newer that 229 (i.e. since June '08) have a
broken scrollbar. It never bothered me enough to post a message, but
I've been setting up some new systems and have found it annoying to
dig up
On Wed, 30 Jun 2010, webmaster wrote:
All releases of xterm newer that 229 (i.e. since June '08) have a
broken scrollbar. It never bothered me enough to post a message, but
I've been setting up some new systems and have found it annoying to
dig up xterm-229 and manually install it.
These
On Sun, 27 Jun 2010, Joseph Quinsey wrote:
The xterm faceSize resource and the -fs command line option do not seem to
work with xterm version 260. Installing the previous Cygwin version, 255,
fixes this.
hmm - I changed the handling of the renderFont resource, but didn't
notice breakage of
Attached are the results of appres XTerm and xterm.
appres_XTerm2
Description: Binary data
appres_xterm
Description: Binary data
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
On Sun, 27 Jun 2010, Joseph Quinsey wrote:
Thomas Dickey replied:
And I realize -fa also doesn't seem to work for me for 260.
thanks - it's some error in the way I added the logic for the renderFont
resource. You should be able to work around by adding
*renderFont:true
to your X resource
Larry Hall (Cygwin X reply-to-list-only-lh-x at cygwin.com writes:
On 5/6/2010 3:18 AM, Jyh-Shyong Ho wrote:
I read a series of discussion on this problem, have you been able to solve
this
problem?
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-i-cant-type-anything
Hi, Larry,
Hi,
I read a series of discussion on this problem, have you been able to solve this
problem?
I just had a PC with 64-bit Windows 7 installed, and try to install CYGWIN/X on
it, I encountered the same problem: the xterm no longer accepts keyboard input.
I tried various methods to solve this
On 5/6/2010 3:18 AM, Jyh-Shyong Ho wrote:
I read a series of discussion on this problem, have you been able to solve this
problem?
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-i-cant-type-anything
--
Larry Hall http://www.rfk.com
RFK Partners, Inc.
On 13/03/2010 21:47, Bob Kline wrote:
On 3/13/2010 1:05 PM, Bob Kline wrote:
I have used X under Cygwin successfully for years. Yesterday I did an
upgrade of my Cygwin installation and X stopped working. After
struggling to get things working again, I decided to just install
Cygwin fresh and
On 15/03/2010 05:42, David Barr wrote:
On Sun, Mar 14, 2010 at 7:17 AM, Jeff Spirkospi...@gmail.com wrote:
The icon runs from the Windows environment, so the run.exe and
bash.exe wrapper programs are needed to set up the proper cygwin
environment. Once you're in a cygwin shell, you already
On 3/15/2010 1:35 PM, Jon TURNEY wrote:
... I'm not sure if the difficulties starting a server mean you have
some other problem as well.
Thanks for your response, Jon. As you'll see from a more recent post, I
was able to solve both problems by going back to using a script instead
of the
On Mon, Mar 15, 2010 at 10:44 AM, Jon TURNEY
jon.tur...@dronecode.org.uk wrote:
No. startx and startxwin are different tools to solve different problems.
I keep adding more text to [1] to clarify this, but this doesn't appear to
help, perhaps because nobody actually reads it...
[1]
On Sat, Mar 13, 2010 at 11:39 PM, Bob Kline bkl...@rksystems.com wrote:
Jeff Spirko wrote:
If you see different results from running startxwin from the command
line vs. the icon, you should check to see if you have an old batch
file laying around
Thanks for the suggestion. I looked
On 3/14/2010 10:17 AM, Jeff Spirko wrote:
The icon runs from the Windows environment, so the run.exe and
bash.exe wrapper programs are needed to set up the proper cygwin
environment. Once you're in a cygwin shell, you already have the
cygwin environment set up. That's why you don't need to
On 3/14/2010 12:20 PM, Bob Kline wrote:
Attached is the log file from launch of X which does *not* result in
the failure dialog window, but whose X session is not able to use
input from the keyboard.
Sorry, that was the wrong log file (from an attempt to launch X from the
shortcut). Here
On Sun, Mar 14, 2010 at 7:17 AM, Jeff Spirko spi...@gmail.com wrote:
The icon runs from the Windows environment, so the run.exe and
bash.exe wrapper programs are needed to set up the proper cygwin
environment. Once you're in a cygwin shell, you already have the
cygwin environment set up.
On Sat, Mar 13, 2010 at 4:47 PM, Bob Kline bkl...@rksystems.com wrote:
On 3/13/2010 1:05 PM, Bob Kline wrote:
I have used X under Cygwin successfully for years. Yesterday I did an
upgrade of my Cygwin installation and X stopped working. After struggling
to get things working again, I
Jeff Spirko wrote:
If you see different results from running startxwin from the command
line vs. the icon, you should check to see if you have an old batch
file laying around
Thanks for the suggestion. I looked again for any old scripts which
might be found by the shell, but there
Hi All,
Somehow Cygwin mailing list shows #xC2; characters in my previous
message; it should have been all spaces instead.
Best Regards,
Andrew
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
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
On 30/12/2009 11:52, Timares, Brian (Harris Corp.) wrote:
I checked the FAQ, looked over the XWin.0 log, looked over the cygcheck
output which shows:
Sonic Solutions burning software containing DLA component
Detected: Named process.
ZoneAlarm Personal Firewall
Detected: HKLM Registry Key, Named
Christopher Faylor wrote:
On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote:
More information as promised, after getting the new run and checkX
(run2) packages announced this morning.
$ checkX -v
run2 0.3.2
0.3.2 announced? I didn't get any such message, and setup still only
Timares, Brian (Patriot) wrote:
Any other ideas? I keep updating but so far all I can do is launch
an Xterm manually and clean up, then everything seems fine til the
next time I relaunch it.
---
Do you have
DISPLAY=:0
set in your Windows environment?
(system properties, Advanced, Env
Linda Walsh wrote:
Timares, Brian (Patriot) wrote:
Any other ideas? I keep updating but so far all I can do is launch
an Xterm manually and clean up, then everything seems fine til the
next time I relaunch it.
Do you have
DISPLAY=:0
set in your Windows environment?
I didn't, but I do
On 12/03/2009 10:47 PM, Timares, Brian (Harris Corp.) wrote:
I do appreciate all the terrific replies--I've been on the net for
awhile and this is one of the friendliest lists I've been on.
Do you mind if I frame this and hang it on the Cygwin home page. ;-)
--
Larry Hall
More information as promised, after getting the new run and checkX
(run2) packages announced this morning.
$ checkX -v
run2 0.3.2
- QUOTE -
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
The X window showed up, but it blew up real good (the windows
disappeared, then the X icon.
Hi!
More information as promised, after getting the new run and checkX
(run2) packages announced this morning.
$ checkX -v
run2 0.3.2
0.3.2 announced? I didn't get any such message, and setup still only offers
0.3.1-1 to me.
vhaisbtim...@isb-timaresbrian-lt ~
$ XWin -multiwindow
[1]
On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote:
More information as promised, after getting the new run and checkX
(run2) packages announced this morning.
$ checkX -v
run2 0.3.2
0.3.2 announced? I didn't get any such message, and setup still only offers
0.3.1-1 to me.
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Just to be clear from the start, Cygwin 1.7 not 1.5.
ACK.
*blush* Sorry!
...
Thus, once more: What does
md5sum /usr/bin/checkX
yield?
a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216?
The 2nd:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
[...]
Thus, once more: What does
md5sum /usr/bin/checkX
yield?
a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216?
The 2nd:
vhaisbtim...@isb-timaresbrian-lt ~
$ md5sum /usr/bin/checkX
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
$ checkX -v
run2 0.3.0
So, you've got the situation I surmised in
http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html
Grr, I saw that, went and _thought_ I got the right version but
it seems the right version
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
$ checkX -v
run2 0.3.0
So, you've got the situation I surmised in
http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html
Grr, I saw that, went and _thought_ I got the right version
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
The X window showed up, but it blew up real good (the windows
disappeared, then the X icon. After a rebootit
didn't launch at all. I ran startxwin.sh from the Cygwin Bash
Shell, and it started.
At least we're getting *somewhere* :-)
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
On Mon, 30 Nov 2009, Andy Koppe wrote:
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.
On Mon, 30 Nov 2009, Andy Koppe wrote:
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.
Thank you! xterm now works again.
The solution was:
Run the Cygwin setup program, and on the Select Packages page,
choose Utils and within there choose termcap
and downgrade to version 20050421-1.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
On Nov 29 22:42, Yaakov S wrote:
On 29/11/2009 21:28, Joe Java wrote:
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
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
Thomas Dickey wrote:
On Mon, 30 Nov 2009, Andy Koppe wrote:
The latest termcap, which was automatically generated from terminfo,
has entries longer than 1K in it.
ok... (I thought cygwin was using GNU termcap, which supposedly works
with longer entries - though I recall _that_ being fixed
Corinna Vinschen wrote:
Isn't xterm linked against ncurses?
The new 1.7 xterm is. The old 1.5 xterm is still termcap based.
Why does it break on a termcap
file at all?
1.5 only, and it breaks because the termcap file was NOT generated using
'-r' to limit the number of allowed ':tc='
Just to be clear from the start, Cygwin 1.7 not 1.5. And I tried to
make this clear. And I tried to not let Outlook's word-wrap inter-
fere.
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
My guess: It's the
I wrote:
And I tried to make this clear.
email -^
*sigh*
Sorry!
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:
Timares, Brian (Patriot) wrote:
Just to be clear from the start, Cygwin 1.7 not 1.5.
ACK.
[...]
i) ```time checkX -t 12''
How long does it take?
vhaisbtim...@isb-timaresbrian-lt ~
$ time checkX -t 12
real0m0.098s
user0m0.046s
sys 0m0.031s
And *that* shouldn't happen!
I
Yaakov (Cygwin/X) wrote:
On 29/11/2009 21:28, Joe Java wrote:
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.
On 29/11/2009 21:28, Joe Java wrote:
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
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me,
that's the default version. But we need 0.3.1-1,
Timares, Brian (Patriot) wrote:
[...]
Nothing works. 1.7 doesn't work for me out-of-the-box (yes, I ripped
it all out and tried it fresh :-)
I open a DOS box and check processes and see bash running with an l or
a 1 in the left columnn, but nothing appears. If I launch an Xterm
it opens up.
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
[...]
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me, that's
the default version. But we need 0.3.1-1, which you only get when
explicitely
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me, that's
the default version. But we need 0.3.1-1, which you only get when
Tried
On Oct 5 17:46, Yaakov S wrote:
On 05/10/2009 13:47, Corinna Vinschen wrote:
--- sys.c.ORIG 2009-10-05 19:23:58.0 +0200
+++ sys.c2009-10-05 19:18:34.0 +0200
@@ -408,7 +408,11 @@ openTty(char *line)
int rc;
int tty = -1;
+#ifdef __CYGWIN__
+tty =
On Oct 4 17:06, Jim Reisert AD1C wrote:
On 10/4/2009 1:52 PM, Corinna Vinschen wrote:
Stracing shows that luit is called with `luit -argv0 -tcsh', but nowhere
in the strace tcsh is actually started. Rather, it looks like luit
starts /bin/sh with argv[0] set to -tcsh instead.
Interesting.
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
On 05/10/2009 11:30, Fergus wrote:
The only difference is the Cygwin version. -61 works, -62 hangs.
Likewise.
But this is not the same problem. Being unable to start the Xserver
is not the same as being unable to start an Xterm.
With everything up to date (cygwin, luit, xorg-server, ...
On Oct 5 10:20, Andy Koppe wrote:
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
On Oct 5 20:47, Corinna Vinschen wrote:
Unfortunately, luit has no alternative way to make the new tty the
controlling tty. What we need is a patch like this in luit:
--- sys.c.ORIG2009-10-05 19:23:58.0 +0200
+++ sys.c 2009-10-05 19:18:34.0 +0200
@@ -408,7
I start my xterms this way:
xterm EXEC xterm -e /usr/bin/tcsh
Is there an inherent problem with this?
- Jim
--
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
On 05/10/2009 13:47, Corinna Vinschen wrote:
And here's the problem. Cygwin doesn't have TIOCSCTTY, and the only way
to make a terminal a controlling tty in Cygwin is to call open() on it,
which tcsh misses to do. Bash, however, calls open(/dev/tty, O_RDWR),
so bash doesn't have this problem.
1 - 100 of 244 matches
Mail list logo
