Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • F fontconfig
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 181
    • Issues 181
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fontconfig
  • fontconfig
  • Issues
  • #171
Closed
Open
Issue created Jul 29, 2019 by Lawrence D'Oliveiro@ldo

[PATCH] Rework Reporting Of Config Parse Errors To Use Callback

This patch ldo_config_parse-20190729.patch reworks the FcConfigMessage routine in fcxml.c to pass all messages through a callback action. The idea is that it becomes easy to add alternate versions of the FcConfigParseAndLoadxxx routines that specify a caller-specified callback for capturing the messages, rather than sending them direct to stderr.

Initially I had the callback details stored as fields in the _FcConfigParse structure. Then I discovered that messages could be reported in situations where such a structure did not exist. So I put them in a separate _MessageCallback structure. So this structure has to be passed as a separate arg to every FcConfigMessage call.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking