Get Info in Yosemite no longer displays file path with slashes

[redheeler]

I have noticed a rather annoying change in Yosemite. When I Get Info on a file, instead of displaying the actual path with slashes like in Mavericks it places ▸ characters between the folders. Although it looks more stylish, this becomes especially annoying when I want to copy the path into "Go to Folder", as I have to replace these characters with slashes for it to work.

Does anyone now of a way to revert it back to the Mavericks method of displaying the path, or is it like most of the behavior changes made in Yosemite and there isn't a way to revert back?

 

[redheeler]

On the left is Mavericks, and on the right is Yosemite.

 

[GreyOS]

Can't add anything other than just to say I noticed this the other day and found it annoying too

 

[Ritsuka]

You can drag the file on the go to folder textfield.

 

[KALLT]

File path in Finder info window
OS X Yosimte: Get Info 'Where' section now shows ▸ instead of forward slashes

 

[pickaxe]

this is the epitome of style over substance.

 

[b0fh666]

retarded.

 

[KALLT]

this is the epitome of style over substance.

But at least it’s more consistent now and easier to understand. A UNIX path is something not everyone understands, let alone uses (how many people would readily know that “/Library/Desktop Pictures” is located in your system root rather than your own user folder?). When you enable the path bar in Finder, you will get the same arrows. Developers can obtain the paths in other ways: files and folders dragged into Terminal or any code editor will be transformed into a file path and, as shown above, it’s also trivial to add a shortcut with a workflow using Automator.

It’s certainly annoying for people that do need them, and I wished Apple would have added an option for this, but I kind of understand the reason for changing it.

 

[Weaselboy]

File path in Finder info window
OS X Yosimte: Get Info 'Where' section now shows ▸ instead of forward slashes

[Mod Note]

Please continue the discussion in one of the existing threads linked by KALLT.