Weird Win7

Ok so I'm guessing most people have realized that since so many programmers whinged about windows uses spaces in folder names they decided to do something about it in vista and they changed "My Documents" to "Documents". Which bravo is sooo much better. In fact I cannot find anything on my vista machine called "My Documents". Additionally My Pictures was changed to Pictures and My Favorites to Favorites etc..

However then on my Win7 machine when I first installed it seemed to be exactly the same as Vista only, the context menu (the left sidebar of an open folder)
is slightly different in Win7 it has a (Favorite, Computer, Library, Homegroup, Network) view instead of the Vista "Favorite Links" view. In 7 you can expand each one which contains sub-categories, this was even a better improvement IMO, and I love it. However recently something happened, when I used to expand the Documents, it would show up 2 subs, "Public" and "My Documents", my docs was slightly different to Documents, and didn't seem to reside in the typical directory structure: C:\Users\Me\Documents.(instead it would go to Documents if you clicked it, but the public docs wouldn't show up) In this directory structure everything seemed to be as Vista was. However Documents was the combined 2.

Recently I shared a folder that resided in Documents and now all of a sudden I don't have Documents, Pictures, or anything, now everything in the directory are named My docs, My pics etc.
Can anyone second this, I mean about the Documents folder called "Documents" in the directory C:\User\name\*, all is it all in my imagination?

Also the shared folder doesn't exist in the dir struct, I have searched for it using the search, it's not in MyDocs, the only way I can access it is if I go to Network and view it that way. If I try to make a shortcut to it the path simply show up as:
\\DESKTOP-PC\Sync

DESK.. being my computer and Sync is the name of the folder.
Last edited on
so many programmers whinged about windows uses spaces in folder names
Huh? Maybe when using a crap debugger like gdb. Otherwise I can't see what the problem is with spaces.
It is not a bug. Windows 7 has something called "libraries." The Documents for Libraries is the current user's documents and the public documents combined.

Say you have two users, foo and bar. In foo's Documents folder, he has two files:
how-does-eat-food_a-tutorial.wmv
text.txt

bar has a directory in his Documents folder:
NOTporn/

In the Public documents is a note from foo to bar:
readme.txt

When foo looks in the libaries thing, he sees
how-does-eat-food_a-tutorial.wmv
text.txt

readme.txt

bar sees
NOTporn/
readme.txt

Get me?

Huh? Maybe when using a crap debugger like gdb

Protip: "filenames with spaces can be surrounded with quotes"
$ gdb
[...]
(gdb) file "my file with spaces"
"/home/chris/my file with spaces": not in executable format: File truncated
(gdb) quit

"my file with spaces" was a blank text file, btw. That's why it complains about it not being executable
Last edited on
So I guess I was loosing my mind, I created another user to check and was the same scenario.
Dammit, I still prefer the no spaces folders makes things look cleaner.

How is "My Documents" more intuitive than "Documents"...

or "My Computer" as apposed to "Computer" WHO ELSE IS GOING TO OWN IT!
Vista was on to a good thing IMO. I'm not saying spaces shouldn't be allowed, simply that having "My" in front of everything looks retarded.

edit: and not just GDB, using any shell under Cygwin you have to use quotes for folders with spaces, or escape:

cd /cygdrive/c/Users/Me/My\ Documents/My\ Folder\ which\ is\ mad\ with\ spaces/
Last edited on
I agree.
Oh and I found the Sync folder, it was in user directory instead of Documents like on my laptop. So that post was completely pointless! yay for me, I have a habit of making useless threads. :)
PROTIP: The novice doesn't PROTIP the master.

gdb has problems with spaced paths even when the command line arguments are quoted. I have seen this myself and it's a known issue. You can look it up if you want.
I don't say gdb is crap because I feel like it. It is crap and the FSF should be ashamed of itself.
gdb has problems with spaced paths even when the command line arguments are quoted


What if it's escaped?
It has problems with the fact that the path contains spaces. It has nothing to do with how you passed the path.
I can't find anything on it except this post which is more to do with an eclipse/windows PATH inclusion issue than anything:

http://markmail.org/message/qwratv6lawzcnrta

What search string did you use? "gdb spaces paths" gives me over two million results, and "gdb spaces paths problems" over two hundred thousand.

EDIT: I just remember exactly what the problem was. If the executable is in a path that contains spaces, setting brakpoints fails utterly.
Last edited on
PROTIP: The novice doesn't PROTIP the master.

Don't PROTIP me then. >:)
PROTIP: Don't ask not to be PROTIP'd.
Can we stop this now? It's lost it's lustre.
Topic archived. No new replies allowed.