Feature Request: Infer language from title/file property

[acarlson1029]

Example:

```file:some_file.json
{
  "some_key": "some_value"
}
\```

It seems silly to have to repeat the language and the extension in the parameter list.

[mugiwara85]

It depends what you want. You could also write file:"this is a sample json block".
But in that case you could use title. Currently file and title are aliasses. Maybe title should just display the specified text, and file also adds the extension? But still, the extension is nost always the same as the language. If you define powershell as a language then the extension is powershell but rather ps1. Also one language can have multiple extensions.
Maybe an option that does that what you want for file only? That way people could enable it, and would not always do that. Would that help?

[acarlson1029]

I'm thinking mostly with respect to code editors which automatically syntax highlight based on extensions, so following that approach makes the most sense. There should be existing Extension -> Language mappings out there.

The plugin should always use the language specified by the code block if it's provided.

I think splitting 'file' and 'title' would be helpful.