On OS X (I suppose on linux too) returns wrong mount point if space used in drive's name about nodejs-disks HOT 7 OPEN

Ok, I looked closer to code and se, that trimming is performed afterwords with javascript, so, line could be just:
'df | grep ' + drive + ' | grep -oh \' /.*\''

from nodejs-disks.

Yeah. I've run into this as well. (Check out my fork.)
I switched it with this:
'df -kl | grep ' + drive + ' | awk '{ for (i = 9; i <= NF; i++) print $i}' ORS=' ''
Not the best because it assumes that the 9th is the beginning of the mount point. What if the first parameter has a space in it?
What does yours do?

from nodejs-disks.

Mine just finds row with drive and asumes that / will be last param with "/" (slash), which will be the mount point. So - it returns everything from this /. Extra space will be trimmed by javascript.

from nodejs-disks.

Does that get "/Volumes/some drive"?

from nodejs-disks.

In my case it did :D

from nodejs-disks.

A case where that would fail is if the mount point folder has a trailing space ('/Volumes /some drive'). I think that's less possible than the first field having a space in it. So, it's a better solution than mine. Do you know if it's possible?

from nodejs-disks.

Never saw such mountpoint naming, but users are geniuses and, if someone allows to do this, they will :D
I just tested on my mac (el capitan) and my solution worked on flahsdrive called " My flash " (space before "My" and after "flash"). So - need to be tested on other platforms :)

from nodejs-disks.