public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: cygwin@cygwin.com
Subject: Fonts: Cygwin/X, ssh -Y, TigerVNC -- who's in charge?
Date: Thu, 18 Jun 2020 17:53:22 +0100	[thread overview]
Message-ID: <f5b8sgkqprx.fsf@ecclerig.inf.ed.ac.uk> (raw)

[Warning, gnarly X-windows issues below, read at your own risk]

I run XEmacs on several Linux servers, and sometimes (always for the
time being) access them via (Cygwin) ssh -Y and/or (Windows)TigerVNC.

XEmacs and fonts are problematic in their own right, but I'm struggling
to understand the X-windows-as-such issues of this configuration, to try
to isolate my problem, which is that I'm not seeing things displayed in
the fonts I want.

In particular, I'm trying to understand as between the X servers running
on my remote servers (there has to be one, however simple, whichever way
I connect, because that's where my XEmacs instances are running, right?) 
and the Cygwin/X server on my machine at home.

Configuration 1)

I _think_ I understand that if I launch XEmacs inside an Xvnc instance
on a server, viewed using a vncviewer instance on my home machine, the
fonts available to it are determined by what fonts are available within
the remote Xvnc instance, in whatever form.

Am I also right in thinking that it does _not_ matter what fonts
TigerVNC-for-Windows finds on my Cygwin box at home?

Configuration 2)

If OTOH I launch Cygwin/XWin, and ssh -Y from a local xterm to a remote
server, where I launch XEmacs, I really don't know what happens.  Does
the sshd X server include a font server, or search for font.dirs, or???
Or does _all_ font-related activity depend on the Cygwin/X server?

Configuration 3)

Unfortunately, the configuration I like best is a mixture.  I launch
XEmacs inside an Xvnc instance on a server, viewed using a vncviewer
instance on my home machine, and fire up gnuserv inside it.  I close the
viewer, and ssh -Y back to the server from home, then run gnuclient from
the resulting shell, which brings up a separate window on the original
XEmacs instance.  I have no idea whose fonts matter in this case, can
anyone explain?

A related question: when running setup and looking at font packages, how
can I tell whether they contain new-style (fc-list will will list them,
they have names such as "DejaVu Sans Mono", or old-style (xlsfonts will
list them, they have names such as "-b&h-lucidatypewriter-medium-r...")?

Thanks,

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


             reply	other threads:[~2020-06-18 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 16:53 Henry S. Thompson [this message]
2020-06-25 21:43 ` Jon Turney
2020-06-26  9:35   ` Henry S. Thompson

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=f5b8sgkqprx.fsf@ecclerig.inf.ed.ac.uk \
    --to=ht@inf.ed.ac.uk \
    --cc=cygwin@cygwin.com \
    /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).