Adding font path to X server

Adding font path to X server

[Boylan, Ross]

I need the Cygwin X server to have access to fonts from dosemu; currently I have to add the path manually each time I start.  I thought I was following the manual by setting up .startxwinrc as
xset fp+ /usr/share/fonts/dosemu
xterm

but startxwin fails to start (details below).  How do I avoid having to set the path manually?

I'd appreciate cc's as my subscription to the list is currently in an odd state, and may not be working.

$ startxwin
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.17.1.0
OS: CYGWIN_NT-6.1 WIHS-1QS3PW1-DT 1.7.35(0.287/5/3) 2015-03-04 12:09 x86_64
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64)
Package: version 1.17.1-2 built 2015-02-23

XWin was started with the following command line:

/usr/bin/XWin :0 -multiwindow -auth
 /home/rdboylan/.serverauth.5388
......
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
xset:  bad font path element (#6), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
/home/rdboylan/.startxwinrc: line 2: $'xterm\r': command not found
xinit: connection to X server lost

The commands in .startwinxrc work fine when typed into an xterm after X launches.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Adding font path to X server

[Mark Geisert]

Boylan, Ross writes:
> I need the Cygwin X server to have access to fonts from dosemu; currently
I have to add the path manually each
> time I start.  I thought I was following the manual by setting up
.startxwinrc as
> xset fp+ /usr/share/fonts/dosemu
> xterm
> 
> but startxwin fails to start (details below).  How do I avoid having to
set the path manually?
> 
> I'd appreciate cc's as my subscription to the list is currently in an odd
state, and may not be working.

Sorry, no can do with the gmane ML gateway I'm using.  Hope you see this on
the mailing list.

> $ startxwin
> Welcome to the XWin X Server
[...]
> xset:  bad font path element (#6), possible causes are:
>     Directory does not exist or has wrong permissions
>     Directory missing fonts.dir
>     Incorrect font server address or syntax
> /home/rdboylan/.startxwinrc: line 2: $'xterm\r': command not found
> xinit: connection to X server lost
> 
> The commands in .startwinxrc work fine when typed into an xterm after X
launches.

You appear to have at least one CR character in your .startxwinrc file.  Use
d2u on the file to get rid of it/them.  If that alone doesn't fix your
issue, you may need to add 'xset fp rehash' after the existing 'xset'
command.  Be sure not to add more CR chars if you edit the file again :-) .

..mark



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: Adding font path to X server

[Boylan, Ross]

I did see your answer, and it worked!  Thanks very much.

I now have a very simple .startxwinrc.  I noticed the default one does a lot of stuff.  Should I try to include it or copy from it?  Is it getting sourced automatically anyway?  It looked as if the system startxwinrc sources the user .startxwinrc, hence my thought that it might be running anyway.

Ross
________________________________________
From: cygwin-owner@cygwin.com [cygwin-owner@cygwin.com] on behalf of Mark Geisert [mark@maxrnd.com]
Sent: Monday, March 30, 2015 9:21 PM
To: cygwin@cygwin.com
Subject: Re: Adding font path to X server

Boylan, Ross writes:
> I need the Cygwin X server to have access to fonts from dosemu; currently
I have to add the path manually each
> time I start.  I thought I was following the manual by setting up
.startxwinrc as
> xset fp+ /usr/share/fonts/dosemu
> xterm
>
> but startxwin fails to start (details below).  How do I avoid having to
set the path manually?
>
> I'd appreciate cc's as my subscription to the list is currently in an odd
state, and may not be working.

Sorry, no can do with the gmane ML gateway I'm using.  Hope you see this on
the mailing list.

> $ startxwin
> Welcome to the XWin X Server
[...]
> xset:  bad font path element (#6), possible causes are:
>     Directory does not exist or has wrong permissions
>     Directory missing fonts.dir
>     Incorrect font server address or syntax
> /home/rdboylan/.startxwinrc: line 2: $'xterm\r': command not found
> xinit: connection to X server lost
>
> The commands in .startwinxrc work fine when typed into an xterm after X
launches.

You appear to have at least one CR character in your .startxwinrc file.  Use
d2u on the file to get rid of it/them.  If that alone doesn't fix your
issue, you may need to add 'xset fp rehash' after the existing 'xset'
command.  Be sure not to add more CR chars if you edit the file again :-) .

..mark



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Adding font path to X server

[Mark Geisert]

Boylan, Ross writes:
> I did see your answer, and it worked!  Thanks very much.

Great!

> I now have a very simple .startxwinrc.  I noticed the default one does a
lot of stuff.  Should I try to include it
> or copy from it?  Is it getting sourced automatically anyway?  It looked
as if the system startxwinrc
> sources the user .startxwinrc, hence my thought that it might be running
anyway.

'man startxwin' probably answers your questions better than I could.  You
can always try putting whatever commands you want in your .startxwinrc and
taking out those that turn out to be unhelpful.  It's just a file of
commands.  People customize it to fine-tune their X Window Experience (tm).

..mark



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple