nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't see a comparison between PS1 files stored in stash, but can see the source

spence leighton

We are evaluating Stash and tried storing some PowerShell script files in a repository. When browsing the repository, you can view the PS1 file but Stash won't show the differences between commits of that file. Anybody run into this or is there a fix out there in the works? ()

Accepted answers

seb

It is likely that your files are not "simple" text files, where they may be UTF16LE for example. Try diff them using the git client directly.

All comments

seb

Are you able to provide more thorough instructions on how to reproduce this issue, or can you attach some screenshots?

Cheers

spence leighton

Well, I don't have enough Karma to upload screen shots but I can say that after doing some more research the files are not strictly text files as Git GUI can't display the differences between them saying that they are binary files.

The file contents do show in the file source view in Stash but when I click Diff to Previous it says the files cannot be rendered in your browser.

I had originally thought the files were just text but it seems the tool used to create them stores more than just text. Still, it is odd that I can see the contents in one view but not in another.

The files were created with Sapien Technologies PrimalScript and came from another department so I don't have access to the tools themselves.

Thanks.

seb

It is likely that your files are not "simple" text files, where they may be UTF16LE for example. Try diff them using the git client directly.

Justin Johnson8

If you create PS1 files using the PowerShell ISE it saves the files in UTF-16 encoding. This causes problems for Subversion as well. Search for utf-16 at http://serverfault.com/questions/2071/hidden-features-of-powershell for a work around.