public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
* Cygwin xterm and emacs-X11 broken in Windows 7
@ 2011-10-26 20:08 Zdzislaw Meglicki
2011-10-27 18:22 ` Ken Brown
0 siblings, 1 reply; 2+ messages in thread
From: Zdzislaw Meglicki @ 2011-10-26 20:08 UTC (permalink / raw)
To: cygwin-xfree; +Cc: cygwin
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Windows 7 (Enterprise): On X11 startup with startxwin I am getting a message:
startxwin: XFree86_VT property unexpectedly has 0 items instead of 1
The xterm window that pops up knows that it's "xterm" (the value of TERM
variable), but it's not configured properly. Curses don't work. Command
completion (in bash) doesn't work. "Less", "more", "vi" and "view" work like on
an undefined terminal (vi and view don't even want to come up).
This may be a non-X11 issue (a curses/term problem), so I'm cross-posting to
cygwin at cygwin dot com as well.
Perhaps related: in emacs-X11 entering the shell mode (M-x shell) kills the
shell. I just get a prompt, then "exit" and a message
Process shell finished
This does *not* happen in emacs-nox, neither does this happen in xemacs.
I attach the output of cygcheck -s -r -v.
Zdzislaw Meglicki
Indiana University
[-- Attachment #2: cygcheck.log.gz --]
[-- Type: application/x-gzip, Size: 32899 bytes --]
[-- Attachment #3: Type: text/plain, Size: 223 bytes --]
--
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/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Cygwin xterm and emacs-X11 broken in Windows 7
2011-10-26 20:08 Cygwin xterm and emacs-X11 broken in Windows 7 Zdzislaw Meglicki
@ 2011-10-27 18:22 ` Ken Brown
0 siblings, 0 replies; 2+ messages in thread
From: Ken Brown @ 2011-10-27 18:22 UTC (permalink / raw)
To: cygwin-xfree
[Removing the cygwin list from the CC.}
On 10/26/2011 4:08 PM, Zdzislaw Meglicki wrote:
[...]
> Perhaps related: in emacs-X11 entering the shell mode (M-x shell) kills the
> shell. I just get a prompt, then "exit" and a message
>
>
> Process shell finished
>
> This does *not* happen in emacs-nox, neither does this happen in xemacs.
It works fine for me, so my best guess is that this is related to your
other X problems. But you might try a recent Cygwin snapshot, on the
off chance that that helps. There have been several changes that have
an impact on processes running under emacs.
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/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-10-26 22:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-10-26 20:08 Cygwin xterm and emacs-X11 broken in Windows 7 Zdzislaw Meglicki
2011-10-27 18:22 ` Ken Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).