Re: xterm

2007-08-31 Thread Larry Hall (Cygwin X)

Ronald Fischer wrote:

Cole Radcliffe wrote:
When I try to run xterm -e /usr/bin/bash -l from the 

cygwin shell I
get an error that says xterm Xt error: Can't open 

display DISPLAY

is not set


Make sure the X server is running first (run 'startxwin').


This might not sufficient - at least it is not in my system: 
Even when you start the X server (in my case in multiwindow

mode), but then try to start xterm from a CMD Cygwin shell
(such as from the shell you get when opening the Cygwin
icon which is created by default when you setup Cygwin initially),
you get the above error message.

The trick is that in your startxwin, you have to create at
least one xterm (or rxvt) initially. From this, you can then 
open others.


I don't know about your copy but te stock startxwin does this already.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 429-6305 - FAX
Holliston, MA 01746

--
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: xterm

2007-08-31 Thread Mark J. Reed
  Make sure the X server is running first (run 'startxwin').
 
  This might not sufficient - at least it is not in my system:
  Even when you start the X server (in my case in multiwindow
  mode), but then try to start xterm from a CMD Cygwin shell
  (such as from the shell you get when opening the Cygwin
  icon which is created by default when you setup Cygwin initially),
  you get the above error message.

Well, sure.

X allows individual programs running on one computer to display
selectively on a different one over the network, which is quite handy.
 You can also have multiple X servers running on the same host, thanks
to things like virtual consoles, Xnest,  Xvnc, etc.

But that means that an X client can't safely make assumptions about
where the X server is.  So you have to tell it.

You do this by supplying a display identifier string.  In the usual
case, a single X server on the same machine as the program, the
display identifier is almost always :0.

How do you provide this information?  The usual way is by setting the
environment variable DISPLAY.  If you have a shell that was started up
by an X program (like xterm or rxvt), that shell will inherit the
value of DISPLAY (if you type echo $DISPLAY you will see it).  So
that shell can automatically start up X programs; they will show up on
the same display as the window you type their command in.

However, a plain Cygwin shell running in a Windows command window has
no knowledge of X by default, and no DISPLAY variable set.  So when
you try to run an X program it complains about not being able to open
the display - because you haven't told it which display to open.  (Not
the most informative error message, and it probably ought to default
to :0, but I'm just the messenger. :))

You can tell each program manually where to display:

$ xterm -display :0

Or you can just set DISPLAY yourself first:

export DISPLAY=:0

If you're always (or almost always) going to have X running, you can
put the export command in your .bash_profile so that you can always
start X programs.  But that can cause difficulties - some programs,
such as vim, behave differently when DISPLAY is set, and may hang for
a while trying to get some information about the X environment if
DISPLAY is set when X isn't really running.

-- 
Mark J. Reed [EMAIL PROTECTED]

--
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

2007-08-31 Thread Fredrik Staxeng
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/



Re: emacs does not work, emacs-nox works

2007-08-31 Thread Larry Hall (Cygwin X)

Fredrik Staxeng wrote:

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?  



Thanks for the feedback.  Believe it or not, you've already implicitly
filed a bug report. ;-)  The normal procedure is to report all packaging
problems to the cygwin-apps list.  Chris Faylor has done this for you
already in this case so you needn't do so yourself.

'setup.exe' does handle dependencies as they are defined in 'hint'
files provided by Cygwin package maintainers.  Your sleuthing has uncovered
a missing package from the hint's dependency list for emacs.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 429-6305 - FAX
Holliston, MA 01746

--
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: xterm

2007-08-31 Thread Larry Hall (Cygwin X)

Mark J. Reed wrote:

  Make sure the X server is running first (run 'startxwin').

This might not sufficient - at least it is not in my system:
Even when you start the X server (in my case in multiwindow
mode), but then try to start xterm from a CMD Cygwin shell
(such as from the shell you get when opening the Cygwin
icon which is created by default when you setup Cygwin initially),
you get the above error message.


Well, sure.

X allows individual programs running on one computer to display
selectively on a different one over the network, which is quite handy.
 You can also have multiple X servers running on the same host, thanks
to things like virtual consoles, Xnest,  Xvnc, etc.

But that means that an X client can't safely make assumptions about
where the X server is.  So you have to tell it.

.
.
.
snip


While this is technically true, if the Cygwin X server has been started
with startxwin in the installed configuration, none of this is necessary.
Unless the OP reports that the X server has been started in this way but
still has a problem, I believe the most obvious cause of the problem
is that the X server is not running.  But since the OP also implied that
he may not be reading the list, I'm not sure we'll know for sure what
specifically is causing the problem.  So it's probably not worth speculating
about the multiple complicated ways that one can get this same message,
unless there's some follow-up from the OP that suggests doing so would be
worthwhile.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 429-6305 - FAX
Holliston, MA 01746

--
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/



Changing the font size

2007-08-31 Thread Cole Radcliffe
I tried to change the font size with the option -fs after the xterm
command however xterm did not recognize that option even though it
appeared in man xterm. I am guessing that it was just not compiled
into the cygwin version of xterm. Is there any other way to accomplish
this. I could just set the -fn option which stands for font name
and use a font that has a large standard size but someone would need
to explain to me how to set that up!

I just want to get the shell larger in general so it does not hurt my
eyes. Maybe there is another way just to scale everything up?

Thanks.

--
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/