Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Custom file types

Monday, March 24, 2008 Daniel Peñalba 3 Comments

Plastic SCM handles two different file types: binaries and text files. By default, Plastic tries to identify a newly added file by using an internal algorithm and a built-in list of known extensions. But sometimes a file that should be binary is identified as text or viceversa.

When a file type is interpreted by Plastic SCM as binary, it is not possible to show the differences in text mode. This is not a problem because it is possible to change the type of a revision. When you change the type of a revision, future revisions of the item will be of the same type.

But now, with Plastic SCM 2.0, users can associate file extensions to file types.

For example, if you want to specify that the files with the extension .cpx are text revisions, you must add a line to the filetypes.conf file which is placed together with your client.conf file.

  • On Windows, the filetypes.conf file is located in C:\Users\user\AppData\Local\plastic4.
  • On Linux, the filetypes.conf file is located in $HOME/.plastic4.

This file will look like this:

# PlasticSCM custom file types. 
# Syntax: <extension>:<type> 
# Type can be 'txt' or 'bin'.
# Examples:
#     .cpp:txt
#     .jpg:bin
Dani Peñalba
Yes! I was the first employee to join Codice!
I own the record in number of check-ins to the Plastic repository. And you can find me working on every single area of Plastic.
I'm also a professional guitar player and I like scuba diving, too. You can reach me at @danipen00.


  1. It doesn't work? I have added exceptions to the list, using both ".extension txt" and ".extension:txt" syntax and I still get "Unsupported file types for binary diff" error message.

  2. did not work for me either, common practice of saving react components as .jsx comes up as binary, I changed in my filetypes.conf -> .jsx:txt but still comes up as binary :-(

  3. If the file was already under version control you'll have to change the type manually (using the context menu on the items view).

    But new files being added will take this setting into account.