From: Steve o <bub@io.com>
To: Michael Anderson <mka@redes.int.com.mx>
Cc: gnu-win32@cygnus.com
Subject: Re: an x environment
Date: Tue, 05 Aug 1997 11:23:00 -0000 [thread overview]
Message-ID: <33E76B9D.60B1@io.com> (raw)
In-Reply-To: <33E754EE.46094188@redes.int.com.mx>
Michael Anderson wrote:
>
> Steve o wrote:
> >
> > fvwm2 ported without a hitch.
>
> Hi Steve:
>
> I've been using bash windows and vi for my work and wondering just how I
> might get X and fvwm working. Can you tell me the steps needed to do
> this? Which X server are you using and what other software needs to be
> installed? Config files? If you posted the process to the newsgroup, it
> might help out others wondering how to do this.
I am using Hummingbird's Exceed X Server,
http://www.hummingbird.com/products/exceed/
I set the environment variable DISPLAY=:0
I installed the "X client libs for NT" from
http://www.cygnus.com/misc/gnu-win32/
Fvwm needs xpm so I got that from:
ftp://ftp.x.org/contrib/libraries/xpm-3.4j.tar.gz
Fvwm can be obtained from:
http://www.hpc.uh.edu/fvwm/
The steps to install are:
tar -xvzf package.tar.gz
cd package
xmkmf -a
make
make install
Sometimes the install target in the Makefile will have:
cp foo /usr/local/bin/foo
These need to be changed to:
cp foo.exe /usr/local/bin/foo.exe
There are some sample .fvwm2rc files included in the distribution,
copy one of these to your home directory.
If you run fvwm, you'll want to set the Exceed
Xconfig->Window Mode->window manager to X.
You'll need Sergey's coolview and remote.tar.gz.
-steve
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-08-05 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-04 21:02 Steve o
[not found] ` <33E754EE.46094188@redes.int.com.mx>
1997-08-05 11:23 ` Steve o [this message]
1997-08-13 1:08 Jerome Gay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33E76B9D.60B1@io.com \
--to=bub@io.com \
--cc=gnu-win32@cygnus.com \
--cc=mka@redes.int.com.mx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).