For what it's worth, I've now seen JSONC files (with comments) stored in
`.json` multiple times, e.g. the launch settings in any VS Code project. So
while technically a different file type, I do wonder how you'd want to detect
it based on the file ending, making the idea of two different parsers
To make a concrete UI suggestion, I think the file menu could be changed to:
```
New File
New File (with template) >...
Open Folder as Project...
Open File...
Open Selected File
Recent Files
```
... and the `Properties` entry expanded to a sub menu:
```
Properties > Current File
Properties > Proje
Sounds good! Although I'd call it "JSON (strict)" & "JSON (with comments)",
because that is how most people seem to refer to the looser interpretation on
the web. But that's just my personal preference, obviously
--
You are receiving this because you are subscribed to this thread.
Reply to this
I would recommend to ship a `JSON with comments` filetype from the start
because it does seem to be somewhat common to me (mostly due to MS's VS Code
which popularized). Being able to extend it is always cool, but obviously the
user experience is better if the right file mode is already availabl
> Changing a filetype setting during editing is simply not usable.
For what it's worth, I think that is what VS Code does: it attempts to
auto-detect (not sure if just based on file extension or actually content) but
t the docs suggest it shows the resulting filetype somewhere prominent, I thi
I think the best way could be to have a JSON with comments file type for the
lenient parsing if the core JSON type to allow it. A global option as you
suggest will basically force anyone to disable strict mode if they have just
have just 1+ files that rely on the expanded syntax, which IMHO turn
@eht16 just google "JSON for comments", apart from posts telling you it's not
allowed you'll find quite a bunch of different parsers to enable this. And
Visual Studio Code (which is pretty popular) uses this style for all its
configs, too. I don't have proper statistics, but I think it should be
Isn't it common that JSON parsers accept comments as an extension? I know many
also don't, but unless you want to split up into two separate JSON-pure and
JSON-with-comments file types it might be better to keep in the comment
highlighting
--
You are receiving this because you are subscribed t
This is *the* major reason why I personally don't use geany :cry: I love the
new fancy "open folder" concept where the folder just magically is shown as a
complete file tree, but Geany only allows me to open single files or a project
file by default. It just feels clumsy and inflexible, in parti
