Bug 16122 - make fc-match err on too many cmdline args
Summary: make fc-match err on too many cmdline args
Status: RESOLVED WONTFIX
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.4
Hardware: Other All
: medium normal
Assignee: Keith Packard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-27 12:05 UTC by Behdad Esfahbod
Modified: 2008-08-13 00:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Behdad Esfahbod 2008-05-27 12:05:34 UTC
I have to try a couple times to see which of:

  fc-match : lang=fa

or

  fc-match :lang=fa

is the correct syntax.  fc-match simply takes one non-option argument.  It should err if more args are passed.

Also the man for fc-list should be changed, such that instead of:

       fc-list [ -vV? ] [ --verbose ] [ --version ] [ --help ] [ pattern ] [ element ]

it says:

       fc-list [ -vV? ] [ --verbose ] [ --version ] [ --help ] [ pattern [ element... ] ]

something like that. (more than one elements allowed, and that pattern is not optional if elements are to be given).
Comment 1 Behdad Esfahbod 2008-08-12 13:49:07 UTC
Fixed in my tree, though in a more user-friendly way:
Created commit ee1f404: [fc-match] Join all cmd-line arguments using : to use as pattern str (#16122)
Comment 2 Behdad Esfahbod 2008-08-12 13:50:18 UTC
Not sure how to fix the fc-list thingy.  It's not that important.
Comment 3 Behdad Esfahbod 2008-08-12 16:57:39 UTC
(In reply to comment #1)
> Fixed in my tree, though in a more user-friendly way:
> Created commit ee1f404: [fc-match] Join all cmd-line arguments using : to use
> as pattern str (#16122)

Humm, this conflicts with bug 13017.  I'd rather that bug be fixed.  In the mean time fc-match should just err if extra arguments given.
Comment 4 Behdad Esfahbod 2008-08-13 00:16:27 UTC
I'm closing this bug in favor of the other one.


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.