Summary: | Enhancing the output of "fc-cache -v" | ||
---|---|---|---|
Product: | fontconfig | Reporter: | sworddragon2 |
Component: | fc-cache | Assignee: | Akira TAGOH <akira> |
Status: | RESOLVED MOVED | QA Contact: | Behdad Esfahbod <freedesktop> |
Severity: | enhancement | ||
Priority: | medium | CC: | akira, fontconfig-bugs |
Version: | 2.11 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
sworddragon2
2016-06-06 22:39:50 UTC
(In reply to sworddragon2 from comment #0) > On executing "fc-cache -v" I'm a bit wondering about some of the output: > > - I'm seeing many things being skipped like "/usr/share/fonts: skipping, > existing cache is valid: 0 fonts, 3 dirs" but I'm wondering what has > actually been skipped. Skipping updating caches - what you are going to do with fc-cache is to update caches. so it is obvious thing, isn't it? > - Even on repeated executions I'm seeing the same directories getting > cleaned like "/home/sworddragon/.cache/fontconfig: cleaning cache > directory". Since something can be skipped as sayed above I'm wondering if > the directories are really cleaned and if not maybe they should also say > that they skip the cleaning as nothing would be to do. That makes sense. let me take a look how it can be improved. (In reply to Akira TAGOH from comment #1) > Skipping updating caches - what you are going to do with fc-cache is to > update caches. so it is obvious thing, isn't it? Updating caches with fc-cache includes different subtasks like the cleaning process of old caches. Maybe that makes it not so super obvious for every user. Or maybe the summerly temperatures here are already getting just too high. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/79. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.