[Xquartz-dev] The 'official' 2.7.5 still acts the same as _rc3 and _rc4 here.

[Peter Dyballa]

Am 11.11.2013 um 20:01 schrieb Jeremy Huddleston Sequoia:

> $ /opt/X11/bin/fc-cache -v

This command is faulty! (I know that it knows only one level of verbosity. But sometimes I want to force something. Then I think I better do not hide my intentions. When it's not a faulty itself.)

I ran it privately and also with elevated privileges. Privately I got:

	pete 82 /\ /opt/X11/bin/fc-cache -vvv
	/opt/X11/share/fonts: caching, new cache contents: 0 fonts, 10 dirs
	/opt/X11/share/fonts: failed to write cache
	/opt/X11/share/fonts/100dpi: caching, new cache contents: 398 fonts, 0 dirs
	/opt/X11/share/fonts/100dpi: failed to write cache
	...
	/opt/X11/var/cache/fontconfig: not cleaning unwritable cache directory
	/Users/pete/.cache/fontconfig: cleaning cache directory
	/Users/pete/.fontconfig: cleaning cache directory
	/opt/X11/bin/fc-cache: failed

With elevated privileges I got:

	pete 83 /\ sudo /opt/X11/bin/fc-cache -vvv
	Password:
	/opt/X11/share/fonts: caching, new cache contents: 0 fonts, 10 dirs
	/opt/X11/share/fonts: failed to write cache
	/opt/X11/share/fonts/100dpi: caching, new cache contents: 398 fonts, 0 dirs
	/opt/X11/share/fonts/100dpi: failed to write cache
	...
	/opt/X11/var/cache/fontconfig: cleaning cache directory
	/Users/pete/.cache/fontconfig: cleaning cache directory
	/Users/pete/.fontconfig: cleaning cache directory
	/opt/X11/bin/fc-cache: failed

Every time the same output is generated. It plays no role whether the private or the privileged command comes first.

--
Greetings

  Pete

Don't force it; get a larger hammer. 
				– Anthony's Law of Force