No, I add them because they are no standard Bash chars. If I autocomplete the command line they appear. If I execute the ls command they don't. Same with the space.
$ ls Kayser-Op20-36-Estudios-Fritz Meyer-ed-Schott-Germany $ ls Kayser-Op20-36-Estudios-Fritz\ Meyer-ed-Schott-Germany/ well I have remove them now :), but the space is still there. 2013/10/19 David Kastrup <d...@gnu.org> > Marcos Press <tdy.p...@gmail.com> writes: > > > Sorry!!! > > I miss click the reply link instead of reply-to-all. > > > > These was my complete path: > > > > ~/partes/Biblioteca/Metodos-Violin/Kayser-Op20-36-Estudios-\[Fritz\ > > Meyer-ed-Schott-Germany\]/tmp/ > > > > simply removing the \[ and \] make the trick! > > Are the backslashes actually in the filenames (do they appear when you > do ls or similar) or did you just type them because that's the way you > need to write it on the command line? > > > It seams "[ ]" are not welcome as dir_names. They are, as file_name. > > And the length is not a problem since I just try adding nearly 10 char > more > > and it works perfectly. > > > > Was these known? And I miss it? > > To anybody? Maybe. But I don't think we have an issue registered for > it, and I doubt anybody already knows whether this is a problem with > LilyPond-book or something else. > > -- > David Kastrup >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user