Jean-Marc Lasgouttes wrote:
> Angus> I seem to remember Bennett saying that LyX refused to allow him
> Angus> to load a filename into a dialog using the Browse button if the
> Angus> filename (file path?) contained spaces.
> 
> Yes, this is due to frontends/controllers/helper_funcs.C:browseFile,
> which does
> 
> if (result.second.find_first_of("#~$% ") == string::npos)
> break;
> 
> Alert::alert(_("Filename can't contain any "
> "of these characters:"),
> _("space, '#', '~', '$' or '%'."));
> 
> I am not sure what we shall do there. Obviously this test only makes
> sense for file names that are going to be passed to LaTeX. Currently
> it also applies to bind files, for example. This is silly.
> 
> I tend to think that we should just remove this code. How useful is it
> really?

I don't think that it is useful at all. The warning, if any, should come
when the user tries to compile the LaTeX:

    No compilation is possible.
    Your version of LaTeX is insufficiently smart to be able to
    handle file paths containing spaces.
      <list of offending paths>

-- 
Angus

Reply via email to