[Nix-dev] fontconfig with vim sumo

Jeevakan Suresh Jeevakan.Suresh at macquarie.com
Fri Oct 10 00:27:45 CEST 2008


I saw this as well, and fixed it via setting the FONTCONFIG_FILE variable.

It seemed like a bit of a hack? I'm sure there is a better way to do all of this without leaving nix land :) 

-----Original Message-----
From: nix-dev-bounces at cs.uu.nl [mailto:nix-dev-bounces at cs.uu.nl] On Behalf Of Pjotr Prins
Sent: Wednesday, October 08, 2008 11:24 PM
To: nix-dev at cs.uu.nl
Subject: [Nix-dev] fontconfig with vim sumo

When I build vim vim-7.2-huge-X11-python-tcl I get the following error on starting gvim:

Fontconfig warning: line 26: empty font directory name ignored No fonts found; this probably means that the fontconfig library is not correctly configured. You may need to edit the fonts.conf configuration file. More information about fontconfig can be found in the fontconfig(3) manual page and on http://fontconfig.org

when I set

  export FONTCONFIG_FILE=/etc/fonts/fonts.conf
	
it works, but obviously my Debian fonts get loaded. Using

  ls ~/.nix-profile/etc/fonts/fonts.conf

I see:

  <!-- Font directory list -->

  <dir></dir>
  <dir>/usr/X11R6/lib/X11/fonts</dir>
  <dir>~/.fonts</dir>

The first one is erroneous. But what about the second one? And how does one use fontconfig with the Nix fonts?

Pj.


On Wed, Oct 08, 2008 at 10:09:42AM +0200, Ludovic Courtès wrote:
> Hi,
> 
> Armijn Hemel <armijn at uulug.nl> writes:
> 
> > hiya,
> >
> >> Log:
> >> Add libupnp, a UPnP implementation.
> >
> > Urgh. I suggest we add a meta.pkgCrapLevel for this one.
> >
> > Seriously, you want to replace it with pupnp (the forked and
> > *maintained* version of this library): pupnp.sourceforge.net
> 
> Can you provide a bit of explanation?  Is pupnp API-compatible?  The 
> thing is software (aMule in this case) actually uses libupnp.
> 
> > UPnP security is a bit of a hobby horse for me:
> > http://www.upnp-hacks.org/
> 
> I see.  :-)
> 
> It's not clear from the front page whether the security issues you are 
> concerned about stem from implementation flaws (such as buffer 
> overflows, which you mention on another page) or protocol flaws (which 
> you mention in the paragraph that starts with "In May 2006").  If the 
> latter, it would be great to emphasize it after "very little has 
> changed", IMO.
> 
> Thanks,
> Ludo'.
> 
> _______________________________________________
> nix-dev mailing list
> nix-dev at cs.uu.nl
> https://mail.cs.uu.nl/mailman/listinfo/nix-dev
_______________________________________________
nix-dev mailing list
nix-dev at cs.uu.nl
https://mail.cs.uu.nl/mailman/listinfo/nix-dev

NOTICE
This e-mail and any attachments are confidential and may contain copyright material of Macquarie Group Limited or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Group Limited does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Group Limited.




More information about the nix-dev mailing list