Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Can you remove the space in the dropbox folder name ("Dropbox (Company-Name)")?
I'm using my companies business dropbox account. And it created a folder called "Dropbox (my companies name here)".
Is there a way to remove the space between "Dropbox" and "("? I don't want to ha...
Hi all,
Unfortunately, it's not possible to change the name of Dropbox folder, as many of you have discovered.
If you are using it for scripts then the best thing would firstly to parse the info.json and grab the path from there. The JSON is located:
Mac/Linux:
~/.dropbox/info.json
Windows will be one of these two paths:
%APPDATA%\Dropbox\info.json
%LOCALAPPDATA%\Dropbox\info.json
I say this as if you were to move your Dropbox folder at anytime then this would, of course, break any paths that explicitly referenced an exact folder path.
On a side note, spaces within file paths shouldn't cause issues within scripts, it's fairly normal to have some spaces in there, just ensure your path string is correctly formatted and your script should be fine.
Ross_S
Dropbox Staff
Dropbox StaffFor those having issue performing a specific routing task:
If you were to outline what you are doing, and the error you are hitting, then the community here may be able to help you resolve the issue. The space shouldn't stop you performing the task you are doing.
Again I would advise; there is a space in our folder name, but this is incredibly standard in computing and in no way unusual.
OK -- one very annoying example is that a number of node modules won't install correctly using 'npm install' with a space in the path. An example is better-sqlite3; everytime I need to install it, I need to copy the entire source directory to a different path without the space character, then copy it back after installing.
Yes, I could ask the package maintainers to fix their install scripts, but that is not the only package that has the issue and asking for a fix from the developer could take days or weeks -- so not a practical solution in the middle of a development project.
Why can't you simply recognize that this is causing significant problems for some of your most sophisticated users (and influencers) and address the core problem rather than trying to excuse the flaw?
