dirname returns whitespace instead of an escaped whitespace

[mathias-goebel]

in
exist / bin / functions.d / eXist-settings.sh
you are using dirname that can't handle whitespaces very well.
see for example:

$ dirname /some_path\ with_space/somefile
/some_path with_space

in my case this causes an error when executing startup.sh, but starting with run.sh works just fine. strange.

[dizzzz]

I had similar issues in the past, but I am not sure if/how we fixed it. @ljo could you check ?

@mathias-goebel what exist version, operating system, shell etc are you using?

[mathias-goebel]

I am using some Ubuntu and Debian systems pretty new stable versions.
eXist is some pre 2.2RC2 build from github within a Jetty and Java 7.
But I guess these facts are obsolete, the error occurs shortly after executing the startup.sh with an output like Error in line 14 at eXist-settings.sh. Probably run.sh uses the same function called get_exist_home(), but it goes on - that what I mean with "strange".
I think two quotation marks will solve this problem:

(cd "$(/usr/bin/dirname "$p")" ; /bin/pwd)

Quoted folder names are treated correct, even with unescaped withespaces.
But you have to be aware of the following output treatment, /bin/pwd gives you unescaped whitespaces again!

[duncdrum]

a lot has changed with scripts since exist2.2RC2. Is this still an issue, otherwise i m going to close this. Please open a new issue, if whitespaces are still misbehaving.

[mathias-goebel]

i can not start eXist on linux when the path to eXist contains a whitespace. but is not related to the function mentioned above.
will continue at #3101