Thanks again for the quick attention. I really hate to be a bother. But I do have one concern about the latest commit. If we disable the user cache and data directories, will FontConfig write the users cache/data somewhere else? Or will the users fonts simply not show up? Some background, my application Font Manager disables loading of user configuration files so that FontConfig will give it a full listing of installed files even those that are disabled using <rejectfont>. Then it selectively loads user configuration files that don't affect rendering through Pango. So for my specific needs just stopping FontConfig from loading user configuration files when asked not to will do. If disabling user cache/data directories has no side effect then nevermind... ;-) On Mon, Jun 30, 2014 at 2:12 AM, Akira TAGOH <akira@xxxxxxxxx> wrote: > Oh, yes. you're right. fixed it again that way. > > Thanks, > > On Mon, Jun 30, 2014 at 1:18 PM, Jerry Casiano <jerrycasiano@xxxxxxxxx> wrote: >> On Mon, 2014-06-30 at 12:38 +0900, Akira TAGOH wrote: >> >> Thanks for looking into it so quickly. >> >> However, if I'm reading it right that still leaves FcConfigEnableHome >> broken, since it has no effect if the environment variable >> XDG_CONFIG_HOME is set. >> >> if (!_FcConfigHomeEnabled) >> return NULL; >> >> Right at the start of that function would restore FcConfigEnableHome, I >> believe. I realize the docs for that function state that it disables >> files specified using ~ but since that is pretty much deprecated, I >> think it should disable loading of any configuration files in the users >> home directory? >> >>> Thanks for catching this up. >>> >>> Fixed in git. >>> >>> On Sun, Jun 29, 2014 at 4:25 PM, Jerry Casiano <jerrycasiano@xxxxxxxxx> wrote: >>> > On Sun, 2014-06-29 at 01:32 -0400, Jerry Casiano wrote: >>> >> Sorry if I'm on crack, but that function no longer has any effect on my >>> >> system. Not sure when it stopped working but it was recent. >>> >> >>> >> It seems to be bypassed by FcConfigXdgConfigHome? >>> >> >>> >> There's way too much code and most of it is over my head but I'm thinking line 2037 in fccfg.c could be >>> >> >>> >> if (env && _FcConfigHomeEnabled) >>> >> >>> >> >>> >> >>> > >>> > After actually looking at the rest of that function, it would probably >>> > be better to just return NULL right off the bat from >>> > FcConfigXdgConfigHome if !_FcConfigHomeEnabled. >>> > >>> > _______________________________________________ >>> > Fontconfig mailing list >>> > Fontconfig@xxxxxxxxxxxxxxxxxxxxx >>> > http://lists.freedesktop.org/mailman/listinfo/fontconfig >>> >>> >>> >> >> > > > > -- > Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
