Hello,
installing gxditview (and Cygwin/X) in Cygwin does not suffice
to display man-pages properly via man -TX75, man -TX100 etc.
In my case, a fallback fixed width font was used, which looked horrible.
I managed to solve this by haphazardly installing additional
X11 font-related Cygwin
On 11/04/2024 13:42, Jon Turney via Cygwin wrote:
On 03/04/2024 14:19, Yang Yu Lin via Cygwin wrote:
For Chinese language, the app’s default UI font is Microsoft YaHei UI.
Using MS Shell Dlg makes the UI become annoying.
Here are my changes:
diff --git a/res/zh_Hans/res.rc b/res/zh_Hans/res.rc
On 2024-04-11 06:42, Jon Turney via Cygwin wrote:
On 03/04/2024 14:19, Yang Yu Lin via Cygwin wrote:
For Chinese language, the app’s default UI font is Microsoft YaHei UI. Using
MS Shell Dlg makes the UI become annoying.
Here are my changes:
diff --git a/res/zh_Hans/res.rc b/res/zh_Hans/res.rc
On 03/04/2024 14:19, Yang Yu Lin via Cygwin wrote:
For Chinese language, the app’s default UI font is Microsoft YaHei UI. Using MS
Shell Dlg makes the UI become annoying.
Here are my changes:
diff --git a/res/zh_Hans/res.rc b/res/zh_Hans/res.rc
index 9f67a5a..da9d6e8 100644
--- a/res/zh_Hans
For Chinese language, the app’s default UI font is Microsoft YaHei UI. Using MS
Shell Dlg makes the UI become annoying.
Here are my changes:
diff --git a/res/zh_Hans/res.rc b/res/zh_Hans/res.rc
index 9f67a5a..da9d6e8 100644
--- a/res/zh_Hans/res.rc
+++ b/res/zh_Hans/res.rc
@@ -8,7 +8,7
On Fri, 08 Mar 2024 21:53:10 +0900 (JST)
Masamichi Hosoda wrote:
> Hi
>
> If I understand correctly,
> the system font cache directory setting in /etc/fonts/fonts.conf
> provided by libfontconfig-common-2.15.0-2 is wrong.
>
> In /etc/fonts/fonts.conf provided by libfontc
Hi
If I understand correctly,
the system font cache directory setting in /etc/fonts/fonts.conf
provided by libfontconfig-common-2.15.0-2 is wrong.
In /etc/fonts/fonts.conf provided by libfontconfig-common-2.13.1-2
```
/var/cache/fontconfig
```
So `fc-cache -s` creates system font cache
The following package has been added to the Cygwin distribution:
* last-resort-font 15.100
Unicode Last Resort fallback font
Unicode.org Last Resort font is a Unicode font designed as a
fallback with representative glyphs and labels to show a missing
glyph belongs to a specific:
* Unicode
On 05/02/2022 14:25, Jon Turney wrote:
On 27/01/2022 03:12, Ken Whitesell wrote:
First, the bottom line:
XWin.exe.manifest, line 21
change:
PerMonitorV2,PerMonitor
to
PerMonitor
Some details:
I managed to get to a point where I could build the packages from
source and install them. I looked
h two different
external monitors.
It seems likely that this is an unintended effect of changes in
xorg-server 21.1.0-1, trying to fix problems in this area (See [1])
Thanks for the references. I've read all the messages in the thread -
I was particularly intrigued by this comment:
wrt the fo
It seems likely that this is an unintended effect of changes in
xorg-server 21.1.0-1, trying to fix problems in this area (See [1])
Thanks for the references. I've read all the messages in the thread -
I was particularly intrigued by this comment:
wrt the font scaling issue, looking at
anges in
xorg-server 21.1.0-1, trying to fix problems in this area (See [1])
Thanks for the references. I've read all the messages in the thread - I
was particularly intrigued by this comment:
wrt the font scaling issue, looking at the source, it seems that we
don't re-consider
On 2022/01/21 10:26, L A Walsh wrote:
...
To summarize, I am not sure that the original issue
has anything to do with 2nd monitor,
nor any changes in the Xorg-sources.
In _my_ case it was a matter of how the Xserver was
started, and what dpi settings it was started with.
If server was started w
On 2022/01/19 17:01, Ken Whitesell wrote:
On 1/19/2022 2:28 PM, Jon Turney wrote:
On 19/01/2022 00:02, Ken Whitesell wrote:
On 1/17/2022 1:29 PM, Ken Whitesell wrote:
After more research and experimentation, it appears to be related to
one of xorg-server, xorg-server-common, or
o fix problems in this area (See [1])
Thanks for the references. I've read all the messages in the thread - I
was particularly intrigued by this comment:
wrt the font scaling issue, looking at the source, it seems that we
don't re-consider the display dpi after a WM_DISPLAYCHANGE messa
On 19/01/2022 00:02, Ken Whitesell wrote:
On 1/17/2022 1:29 PM, Ken Whitesell wrote:
Is there a known solution for this? (Or is it known that there is no
solution?)
Thanks for reporting this.
Any guidance, pointers, suggestions of avenues for further research,
or other information, will al
On 1/17/2022 1:29 PM, Ken Whitesell wrote:
Problem: When moving an XTerm window from the primary display to the
second monitor, characters typed into that window are "clipped" at the
top. Only about the bottom 75% is drawn. No lower-case letters taller
than the "half-height" letters render prop
Problem: When moving an XTerm window from the primary display to the
second monitor, characters typed into that window are "clipped" at the
top. Only about the bottom 75% is drawn. No lower-case letters taller
than the "half-height" letters render properly. (Letters such as "a",
"c", "m", "n",
ms to be caused by their ancient installer approach and
aggressive font replacement policy.
If something like that could be a cause of your problem, try rebooting
to see if that clears up the problem.
You could try restarting Windows, then rerunning setup to rerun the
postinstall scripts, to s
7;?
Don't do customizations. -Q doesn't help
You said in a different message that you use Courier New. How are you selecting
the font in emacs? And does the problem still occur if you just let emacs
choose the font?
If you still see the problem with 'emacs -Q', please giv
aller approach and
aggressive font replacement policy.
If something like that could be a cause of your problem, try rebooting
to see if that clears up the problem.
Used "Courier New" for years. Just a monospace font for data entry.
--
Problem reports: https://cygwin.com/pr
On 7/2/21 5:46 PM, Ken Brown via Cygwin wrote:
On 7/2/2021 5:21 PM, mcforum wrote:
The legends in the heading for emacs have turned into boxes. the text
in buffers is normal.
I'm not sure what you mean by "legends in the heading". And when you
say "have turned into boxes", are you saying tha
that decide it's a good idea to replace your existing
installed versions of Windows fonts by theirs e.g. LibreOffice updates
mess up the appearance of all my Windows, X, and Cygwin apps until I
reboot.
It seems to be caused by their ancient installer approach and aggressive
font replac
On 7/2/2021 5:21 PM, mcforum wrote:
The legends in the heading for emacs have turned into boxes. the text in
buffers is normal.
I'm not sure what you mean by "legends in the heading". And when you say "have
turned into boxes", are you saying that the problem just recently started? Or
have
The legends in the heading for emacs have turned into boxes. the text in
buffers is normal.
What interaction is causing this? The X11 emacs is unusable emacs -w32 works.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:
arious sizes and encodings
So in my "~/.Xdefaults", I have tried:
!XTerm*font: -*-lucidatypewriter-medium-*-*-*-*-*-*-*-*-*-*-*-
XTerm*font: lucidatypewriter
!XTerm*font:
-b&h-lucidatypewriter-medium-r-normal-sans-11-80-100-100-m-70-iso10646-1
full and sparse specification,
On 9/13/2020 10:16 AM, Michael Soegtrop wrote:
Dear Cygwin Team and Users,
since a few months I have issues deleting cygwin installations. In some cases
randomly the /usr/share/fonts/microsoft folder and the TTF files in it remain.
According to DOS dir the folder contains junctions to TTF file
Dear Cygwin Team and Users,
since a few months I have issues deleting cygwin installations. In some
cases randomly the /usr/share/fonts/microsoft folder and the TTF files
in it remain. According to DOS dir the folder contains junctions to TTF
files - not sure how this is possible - afaik a jun
>>>>> Steinar Bang :
> Is it possible to set the default font sizes for each application on
> the server side so that the applications look good on both laptops
> (right now the text is so small that it is hard to read on the
> 1920x1080 display).
Turns out emacs wa
resolution (1920x1080).
Is it possible to set the default font sizes for each application on the
server side so that the applications look good on both laptops (right
now the text is so small that it is hard to read on the 1920x1080
display).
Thanks!
- Steinar
--
Problem reports: https://
- Original Message -
| From: "Siegmar Gross"
| To: cygwin@cygwin.com
| Sent: Tuesday, September 26, 2017 6:09:23 AM
| Subject: "xterm -fn '...' automatically switches to an unavailable font
|
| Hi,
|
| I've updated my system to the latest package version
-bold-r-normal--15-140-75-75-c-90-iso10646-1
hermes fd1026_2 41 xterm -fn
'-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1'
xterm: cannot load font "-Misc-Fixed-medium-R-*-*-15-140-75-75-C-180-ISO10646-1"
xterm: cannot load font "-Misc-Fixed-bold-R-*-*-15-140
- Original Message -
| From: "Wouter van Doorn"
| To: "Brian Inglis" , cygwin@cygwin.com
| Sent: Thursday, July 6, 2017 5:31:42 PM
| Subject: Re: XTerm always gives out an error message concerning a font
|
| No luck with either of the fixed-medium suggestions. The on
No luck with either of the fixed-medium suggestions. The one you
mentioned as default first match on your system is the one I get it
moaning about no matter what I do.
The easiest solution (of sorts) might be to go back to xterm patch
326, but I don't know how to do that either. The installer won'
On 2017-07-06 10:58, Wouter van Doorn wrote:
> Thanks, Brian. Your link shows me a page that mentions problems in
> xterm-327 through 329, but I have 330, so although the symptom is very
> similar, it doesn't seem to be that.
Try your font name resource selections with xlsfonts unti
Thanks, Brian. Your link shows me a page that mentions problems in
xterm-327 through 329, but I have 330, so although the symptom is very
similar, it doesn't seem to be that.
Wouter
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentatio
ss of it. In fact: I never touched anything to
> do with fonts after installing. So I would not expect anything to be
> wrong, really.
> Here's the error, and it crops up every single time an term is started:
> /usr/bin/xterm: cannot load font
> "-Misc-Fixed-bold-R-*-*-18-12
fonts after installing. So I would not expect anything to be
wrong, really.
Here's the error, and it crops up every single time an term is started:
/usr/bin/xterm: cannot load font
"-Misc-Fixed-bold-R-*-*-18-120-100-100-C-180-ISO10646-1"
This happens with both of these .Xresour
On Mon, Jun 26, 2017 at 01:18:52AM -0700, Bryan Dongray wrote:
> On 06/21/2017 01:22 AM, Thomas Dickey wrote:
> > - Original Message -
> > | From: "Bryan Dongray"
> > | To: cygwin@cygwin.com
> > | Sent: Tuesday, June 20, 2017 6:52:38 PM
> >
On 06/21/2017 01:22 AM, Thomas Dickey wrote:
> - Original Message -
> | From: "Bryan Dongray"
> | To: cygwin@cygwin.com
> | Sent: Tuesday, June 20, 2017 6:52:38 PM
> | Subject: xterm 327-1 to 329-1 needs font dependency
> |
> | On an upgrade of xterm from 3
- Original Message -
| From: "Bryan Dongray"
| To: cygwin@cygwin.com
| Sent: Tuesday, June 20, 2017 6:52:38 PM
| Subject: xterm 327-1 to 329-1 needs font dependency
|
| On an upgrade of xterm from 327-1 to 329-1 starting an xterm now
| complains:
| $ xterm
| /usr
- Original Message -
| From: "Greywolf"
| To: cygwin@cygwin.com
| Sent: Tuesday, June 20, 2017 6:31:42 PM
| Subject: XTerm 329-1 throwing error on absent bold font
|
| Greetings,
|
| Whenever I start up an XTerm, even if I have the resources
|
| allowBoldFonts: fal
On an upgrade of xterm from 327-1 to 329-1 starting an xterm now complains:
$ xterm
/usr/bin/xterm: cannot load font
"-Misc-Fixed-bold-R-*-*-10-100-75-75-C-60-ISO8859-1"
/usr/bin/xterm: cannot load font
"-Misc-Fixed-medium-R-*-*-10-100-75-75-C-120-ISO10646-
Greetings,
Whenever I start up an XTerm, even if I have the resources
allowBoldFonts: false
it throws the following error:
xterm: cannot load font "-Sun-Serif-bold-R-*-*-14-140-72-72-M-80-ISO8859-1"
Never mind the font name, this is irrelevant. The fact that it wasn't
th
On 7/11/2016 9:55 AM, Duncan Roe wrote:
Hi
When upgrading to current 5.2.1 Cygwin, this message appears in the window:
Package: z/Perpetual
zp_fontconfig_cache_1.sh exit code 1
The relevant lines in /var/log/setup.log.full appear to be:
2016/07/11 22:24:30 running: C:\cygwin64\bin\bash.e
Hi
When upgrading to current 5.2.1 Cygwin, this message appears in the window:
> Package: z/Perpetual
> zp_fontconfig_cache_1.sh exit code 1
The relevant lines in /var/log/setup.log.full appear to be:
> 2016/07/11 22:24:30 running: C:\cygwin64\bin\bash.exe --norc --noprofile
> "/etc/postinst
- Original Message -
| From: "Rainer Blome"
| To: cygwin@cygwin.com
| Sent: Thursday, June 30, 2016 1:22:37 PM
| Subject: /etc/X11/app-defaults/XTerm refers to font "helvetica"
|
| Since many months (and probably several Cygwin and X11 releases),
| starting `xterm` tr
ve grepped for "helvetica" through my own config files (`.Xdefaults` etc.)
and not found such a font reference.
The mailing list archives show that at least one other Cygwin user has
encountered the same issue,
and got no answer regarding this specific issue (just for another font issue).
h
ygwin distribution.
Best,
Mark
On 18.06.2016 22:04, cygwin-digest-h...@cygwin.com wrote:
cygwin_203614.ezm
Subject:
Re: xdvipdfmx:fatal: This font using the "seac" command for accented
characters...
From:
Ken Brown
Date:
18.06.2016 13:41
To:
cygwin@cygwin.com
On 6/17/2016 5:54 PM
On 6/17/2016 5:54 PM, Mark McGregor wrote:
Ken wrote:
No, I don't think XeTeX is dying. A look at its git repository shows lots of
commits from Jonathan Kew and Arthur Reutenauer in the last few months.
The last commit was over 1 month ago: a 1-line change from JK. I'm not overly
opti
Ken wrote:
> Ken, thank you!
> (You might probably have more experience with XeTeX than me. Is XeTeX
> dying? The last bugfix was in March, months ago, and apart from A.R.
> nobody seems to work on it anyway...)
No, I don't think XeTeX is dying. A look at its git repository shows lots of
comm
On 6/13/2016 9:28 AM, Mark McGregor wrote:
Ken wrote:
Would this solution affect the compilation processes of lualatex
(which does compile the file in question) or pdflatex?
No. lualatex and pdftex don't use fontconfig.
By the way, I've filed a bug report about this problem:
https://
Ken wrote:
> Would this solution affect the compilation processes of lualatex
> (which does compile the file in question) or pdflatex?
No. lualatex and pdftex don't use fontconfig.
By the way, I've filed a bug report about this problem:
https://sourceforge.net/p/xetex/bugs/131/
Ke
On 6/13/2016 5:27 AM, Mark McGregor wrote:
References:
Ken Brown wrote:
Based on that, you can work around the problem by commenting out the type1
fonts in /usr/share/fontconfig/conf.avail/09-texlive.conf, like this:
$ cat /usr/share/fontconfig/conf.avail/09-texlive.conf
/usr/share/te
References:
Ken Brown wrote:
Based on that, you can work around the problem by commenting out the type1
fonts in /usr/share/fontconfig/conf.avail/09-texlive.conf, like this:
$ cat /usr/share/fontconfig/conf.avail/09-texlive.conf
/usr/share/texmf-dist/fonts/opentype
/usr/share/texmf-d
On 6/12/2016 8:08 PM, Mark McGregor wrote:
A more minimal non-working example:
[
\documentclass{article}
\usepackage{fontspec}
\setmainfont{CMU Serif}
%\setmainfont{cmunrm.otf}
\begin{document}
А
\end{document}
]
If you comment the first \setmainfont line and uncomment the second one, the
fi
--- Andrey wrote:
> Btw., the web page http://cygwin.com/ml/cygwin/2016-06/msg00197.html is
> displaying the cyrillic capital first letter of the cyrillic alphabet
> wrongly. The file has U+0410 internally, not a stroke D. Don't ask me why
> the web browser and web server are acting this way.
Tha
Greetings, Mark McGregor!
> Btw., the web page http://cygwin.com/ml/cygwin/2016-06/msg00197.html is
> displaying the cyrillic capital first letter of the cyrillic alphabet
> wrongly. The file has U+0410 internally, not a stroke D. Don't ask me why
> the web browser and web server are acting this w
A more minimal non-working example:
[
\documentclass{article}
\usepackage{fontspec}
\setmainfont{CMU Serif}
%\setmainfont{cmunrm.otf}
\begin{document}
А
\end{document}
]
If you comment the first \setmainfont line and uncomment the second one, the
file compiles. Rerunning /usr/bin/texlive-enabl
Btw., the web page http://cygwin.com/ml/cygwin/2016-06/msg00197.html is
displaying the cyrillic capital first letter of the cyrillic alphabet wrongly.
The file has U+0410 internally, not a stroke D. Don't ask me why the web
browser and web server are acting this way.
--
Problem reports: h
eneric/babel/xebabel.def)))
(/usr/share/texmf-dist/tex/generic/babel-english/english.ldf)) (./q.aux)
(/usr/share/texmf-dist/tex/latex/tipa/t3cmr.fd) [1] (./q.aux)
xdvipdfmx:fatal: This font using the "seac" command for accented characters...
Output file removed.
)
Error 256 (driver return c
On 08/06/16 18:55, David Stacey wrote:
Please could you check the 'noto-urdu-fonts-20160307-1.gitbdf7562'
package. The file '66-google-noto-nastaliq-urdu.conf' file contained
within appears to have an unclosed 'match' element:
...
The initial 'match' start tag (on
Please could you check the 'noto-urdu-fonts-20160307-1.gitbdf7562'
package. The file '66-google-noto-nastaliq-urdu.conf' file contained
within appears to have an unclosed 'match' element:
...
The initial 'match' start tag (on line 4) is never closed.
Many thanks i
Ken wrote:
On 5/13/2016 9:26 PM, Jaakov Jaakov wrote:
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex:
Invalid fontname `TeX Gyre Termes', contains ' '
!
! fontspec error: "font-not-found&quo
On 5/13/2016 9:26 PM, Jaakov Jaakov wrote:
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex:
Invalid fontname `TeX Gyre Termes', contains ' '
!
! fontspec error: "font-not-found"
! ! The font &q
-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/share/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex:
Invalid fontname `TeX Gyre Termes', contains ' '
!!!!
!
!
Am 12.04.2016 um 22:27 schrieb Thomas Wolff:
Am 11.04.2016 um 22:40 schrieb Thomas Wolff:
Am 11.04.2016 um 14:43 schrieb KARL BOTTS:
Perhaps related to font issues in mintty: In .minttyrc is a new
property
FontWeight=700,
which means you had configured the bold version of the font.
after
dependency on libfontconfig1
or libXft2, which means it uses these as core fonts. How those are
installed also changed at the same time.
How should I manage the postintall for this font ?
Make sure you have mkfontdir and mkfontscale, then in src_install:
fontinto tektronix
On 17/04/2016 21:01, Yaakov Selkowitz wrote:
On 2016-04-17 13:26, Marco Atzeri wrote:
Most of the postinstall font scripts are referring to
/usr/share/fonts/encodings
/usr/share/fonts/encodings/large
"Most"?
just fooled by the old postinstall files (.done)
$ cat plotuti
On 2016-04-17 13:26, Marco Atzeri wrote:
Most of the postinstall font scripts are referring to
/usr/share/fonts/encodings
/usr/share/fonts/encodings/large
"Most"?
$ cat plotutils.sh.done
/usr/bin/rm -f /usr/share/fonts/misc/encodings.dir
/usr/share/fonts/misc/fonts.{dir,scale
Most of the postinstall font scripts are referring to
/usr/share/fonts/encodings
/usr/share/fonts/encodings/large
$ cat plotutils.sh.done
/usr/bin/rm -f /usr/share/fonts/misc/encodings.dir
/usr/share/fonts/misc/fonts.{dir,scale}
/usr/bin/mkfontscale /usr/share/fonts/misc || /usr/bin/rm -f
On 15.04.2016 06:03, LLoyd wrote:
Thank you for your message, Thomas.
I can install .fon files without problem here on Win7 (by dropping them into
the fonts folder)
Window popup on all my systems:
Cannot install gohufont-14.fon
The file '...\gohufont-14.fon' does not appear to be a
Thank you for your message, Thomas.
I can install .fon files without problem here on Win7 (by dropping
them into the fonts folder)
I tried to install the ones from koemaeda, but ran into some problems:
- I can only install one at a time
- Whichever I install, I cannot set the correct font size
Hello Andrey, thank you for your answer.
What do you mean by "that explains it"?
And more importantly, what should I use instead?
Regards,
LLoyd
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.h
only one.
The first TTF archive listed on http://font.gohu.org/ is not installable
either.
But the second one (https://github.com/koemaeda/gohufont-ttf) works and
does not produce the warning.
So please use a modern font format.
Regards,
Thomas
--
Problem reports: http://cygwin.com
Hello.
I am using the .fon ones (http://font.gohu.org/gohufont-windows-2.0.zip)
I never tried to start mintty manually, I am using the standard
desktop shortcut which starts "C:\cygwin64\bin\mintty.exe -i
/Cygwin-Terminal.ico -"
I just tried this:
mintty -o Font=gohufont-14 -
which do
Am 13.04.2016 um 03:43 schrieb LLoyd:
Hello.
...
Today however, every time I start a new cygwin terminal (with Alt+F2
of using the desktop shortcut), I am met with this warning:
Font has limited support for character ranges
...
I am indeed using a font called gohufont-14 which only comes in
es I had and
> to add dos2unix, which succeeded successfully.
>
> Today however, every time I start a new cygwin terminal (with Alt+F2
> of using the desktop shortcut), I am met with this warning:
>
> Font has limited support for character ranges
>
> Here is a screenshot
), I am met with this warning:
Font has limited support for character ranges
Here is a screenshot of that warning: http://i.imgur.com/Go5vz7m.png
I am indeed using a font called gohufont-14 which only comes in size
of 14pt. I have been using this font for over a year and I am well
aware of its
Am 11.04.2016 um 22:40 schrieb Thomas Wolff:
Am 11.04.2016 um 14:43 schrieb KARL BOTTS:
Perhaps related to font issues in mintty: In .minttyrc is a new property
FontWeight=700,
which means you had configured the bold version of the font.
after I installed Cygwin 2.4.1-1 and mintty 2.3.5. (I
Am 11.04.2016 um 14:43 schrieb KARL BOTTS:
Perhaps related to font issues in mintty: In .minttyrc is a new property
FontWeight=700,
which means you had configured the bold version of the font.
after I installed Cygwin 2.4.1-1 and mintty 2.3.5. (I
noticed,
only because I have home dir files in
lled to
make fonts visible in some applications.
Another suggested checking permissions on the font directory.
A cygwin forum suggested that there might be no monospace fonts installed
and that mintty needs monospaced fonts only (make sense).
I've tried all the above, and no luck.
Somethi
Perhaps related to font issues in mintty: In .minttyrc is a new property
FontWeight=700, after I installed Cygwin 2.4.1-1 and mintty 2.3.5. (I
noticed,
only because I have home dir files in revision control.) I too use Lucida
Console.
With the 700, the font looked visibly "skinny"
Paul Ausbeck soe.ucsc.edu> writes:
>
> Cygwin setup just updated some older packages while installing a
> requested new component and now mintty does not recognize fonts
> properly. I was previously using lucinda-console but now some default
> font is being used. When I
Am 05.04.2016 um 02:40 schrieb Thomas Wolff:
Am 05.04.2016 um 01:54 schrieb Paul Ausbeck:
Cygwin setup just updated some older packages while installing a
requested new component and now mintty does not recognize fonts
properly. I was previously using lucinda-console but now some default
font
Am 05.04.2016 um 01:54 schrieb Paul Ausbeck:
Cygwin setup just updated some older packages while installing a
requested new component and now mintty does not recognize fonts
properly. I was previously using lucinda-console but now some default
font is being used. When I try to change the
Cygwin setup just updated some older packages while installing a
requested new component and now mintty does not recognize fonts
properly. I was previously using lucinda-console but now some default
font is being used. When I try to change the mintty font through the
Options... dialog, the
Am 19.03.2016 um 19:54 schrieb Andrey Tarasevich:
On Sat, Mar 19, 2016 at 11:01 AM, Thomas Wolff wrote:
Am 19.03.2016 um 18:18 schrieb Andrey Tarasevich:
...
when I attempt to start Cygwin terminal (mintty), I'm immediately
greeted with a message box saying
Lucida Console
Font
t;> updated all Cygwin components to their newest versions. However, now
>> when I attempt to start Cygwin terminal (mintty), I'm immediately
>> greeted with a message box saying
>>
>>Lucida Console
>> Font does not support ANSI character range
>>
&g
terminal (mintty), I'm immediately
greeted with a message box saying
Lucida Console
Font does not support ANSI character range
Choosing any other font available in mintty options results in the
very same error message (with a different font name, of course).
Clicking through that message box s
ssage box saying
Lucida Console
Font does not support ANSI character range
Choosing any other font available in mintty options results in the
very same error message (with a different font name, of course).
Clicking through that message box starts the Cygein terminal, which
appears to work fine.
>-Original Message-
>From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
>Yaakov Selkowitz
>Sent: Monday, March 14, 2016 10:37 AM
>To: cygwin@cygwin.com
>Subject: Re: font faq
>
>On 2016-03-14 09:54, Rockefeller, Harry wrote:
>>
On 2016-03-14 09:54, Rockefeller, Harry wrote:
I have had warnings and errors about fonts ever since - something changed.
I'm looking at the index of Cygwin FAQ and there is not a single question
matching 'font'.
Where do I need to go to match up my font issue (warning
$ uname -a
CYGWIN_NT-6.1-WOW HARRYR-PC 2.4.1(0.293/5/3) 2016-01-24 11:24 i686 Cygwin
I have had warnings and errors about fonts ever since - something changed.
I'm looking at the index of Cygwin FAQ and there is not a single question
matching 'font'.
Where do I need to go to m
The following packages have been uploaded to the Cygwin distribution:
* perl-Font-TTF-1.05-1
Perl module for TrueType font hacking. In short, you can do almost
anything with a standard TrueType font with this module.
This package has been added (from Ports) as a build-time dependency of
> From: Jon Turney [mailto:jon.tur...@dronecode.org.uk]
> Sent: Monday, October 19, 2015 7:54
>
> The dependency chain is git-gui -> gitk -> font-adobe-dpi75
>
> It doesn't look like the fonts in xorg-x11-fonts-Type1 are available to
> fontconfig, so I've cha
On 10/22/2015 12:20 PM, reinhard.ne...@fau.de wrote:
I do have the links in /etc/X11/fontpath.d
xorg-x11-fonts-75dpi:unscaled:pri=20 -> /usr/share/X11/fonts/75dpi
and they work fine within cygwin.
I tried to create corresponding links within windows by
mklink "xorg-x11-fonts-75dpi:unscaled:pri=2
why are there colon in the name of the symbolic link, which program reads
these links
and is there a way for me to change my system to use a different link name ?
Best
Reinhard
From: Ken Brown
To: cygwin at cygwin dot com
Date: Tue, 13 Oct 2015 11:31:51 -0400
Subject: Re: load
"font != NULL" failed: file
"/usr/src/ports/fontconfig/fontconfig-2.11.1-3.x86_64/src/fontconfig-2.11.1/src/fcmatch.c",
line 453, function: FcFontRenderPrepare
error: git-gui died of signal 6
cygcheck and xwin logs attached
You don't have any Fontconfig-controlled fonts
On Fri, 2015-10-16 at 17:09 +, Matt Seitz (matseitz) wrote:
> A few days ago, I ran Setup to update my currently installed package,
> including my git packages. Since then, whenever I run git gui, I get the
> following error:
>
> $ git gui
> assertion "font != NULL
1 - 100 of 316 matches
Mail list logo
