#726 fails with filenames with a "*"

Usability
open
None
5
2013-02-21
2012-12-18
Felix Sipma
No

mediainfo fails with filenames with a "*" (it just outputs a newline character).

Please don't repeat that non-paid bugs are set to low priority, you don't know when you have time to handle it.

Discussion

  • Felix Sipma
    Felix Sipma
    2012-12-18

    Oops, I should have put Milestone to "Incorrect_result" :(

     
    • milestone: Crash --> Usability
     
  • With new sourefroge system, I don't have anymore the templates so it is longer to write it, so I don't write it ;). But it does not change the priority for me (any patch is welcome).

    More seriously, it is related to also the question mark issue

     
  • Felix Sipma
    Felix Sipma
    2012-12-18

    OK :-)
    Do you know where could the "?" and "*" issues come from? Is it just from the command line parsing?
    I would be happy to help if mediainfo was written in python, but C++ is a different deal... :-)

     
  • I think it is due to how I manage wildcards (on Windows, theses characters are forbidden, so I did not care about files with such characters in the filenames), 100% in my code.

     
    • assigned_to: Jerome Martinez