Text: Text vs files_texteditor

Created on 14 May 2019  Â·  7Comments  Â·  Source: nextcloud/text

In the create menu in Files, there are 2 entries now:

  • "New text file" → defaulting to .txt
  • "New text document" → defaulting to .md

text file vs text document difference not clear

Seeing this is a bit confusing, and the difference is not really clear and not really relevant either to regular people. The .txt files are still opened by files_texteditor, and the .md files by Text.

Proposal (all this only for when the Text app is installed):

  • There is only one entry, saying "New text document" → defaulting to .md
  • The Text app should be able to open .txt files too, overriding the files_texteditor app
  • The files_texteditor app should basically be phased out, as I thought was the plan?

What do you think @juliushaertl?

enhancement

Most helpful comment

The Text app should be able to open .txt files too, overriding the files_texteditor app

While this should be possible in general, I have not looked into how to achieve that. Right now we only support one schema (markdown) in the editor, so for plain text files we need a separate schema and also disable all the formating options.

The files_texteditor app should basically be phased out, as I thought was the plan?

Not sure, files_texteditor is not only about plain text but also any text based file format, like source code files with syntax highlighting.

There is only one entry, saying "New text document" → defaulting to .md

:+1: As a first step we could just move this to one entry which creates a .md file by default, but the user can change it to any file extension. For the first iteration we would open .md files in the text app and the rest in the files_texteditor. Later on once a plain text schema is developed we can also open .txt files in the text app.

All 7 comments

The Text app should be able to open .txt files too, overriding the files_texteditor app

While this should be possible in general, I have not looked into how to achieve that. Right now we only support one schema (markdown) in the editor, so for plain text files we need a separate schema and also disable all the formating options.

The files_texteditor app should basically be phased out, as I thought was the plan?

Not sure, files_texteditor is not only about plain text but also any text based file format, like source code files with syntax highlighting.

There is only one entry, saying "New text document" → defaulting to .md

:+1: As a first step we could just move this to one entry which creates a .md file by default, but the user can change it to any file extension. For the first iteration we would open .md files in the text app and the rest in the files_texteditor. Later on once a plain text schema is developed we can also open .txt files in the text app.

Right, your plan makes sense! :+1: minimally invasive and the default is not confusing, and uses the Text app. :)

13 is about opening plain text files.

@juliushaertl is that one ready? Doesn’t seem a pull request is open yet?

@jancborchardt I wanted to wait with the pr until we publish. :wink:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

juliushaertl picture juliushaertl  Â·  3Comments

jeyca picture jeyca  Â·  5Comments

feutl picture feutl  Â·  3Comments

Klakla2 picture Klakla2  Â·  5Comments

csantosb picture csantosb  Â·  5Comments