-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.12.1 default file format assignment, new file not working as expected #2297
Comments
@harshad1 Seems like the todo.txt detection not takes priority over plaintext .txt with new registry @michibr81 Use the top file menu and change the format to todo.txt. |
Actually I tried this but forgot to switch off Auto-Format before. After doing so the solution you mention works. Thanks. |
New file - todo.txt example is not making the right contents either currently |
I believe a similar issue is happening with the Wikitext format. After the v2.12.1 update, my Zim wiki files are now detected as Plain Text (no formatting). If I manually change the format of individual files, the formatting comes back, but the auto-detection doesn't seem to be working. And, since you mentioned the new file issue, I just noticed that creating a new file using the zim-wiki-empty.txt template crashes the app. Maybe it's also related. Should I open a new issue with more details about the crash? Cheers, |
No its OK. Dont need new one.
|
Hi @gsantner, creating a new file using the zim-wiki-empty.txt template is still crashing the app for me in v2.12.2. Can you reproduce this as well? |
There are numerous dicscussions here. |
Description
Updated to Version 2.12.1 and no have no syntaxhighlighting in Todo.txt format (no categories, no topics, no priority, checkecd or unchecked not visible). No buttons available any more for categories. No sorting possible.
Steps to reproduce
Information
Android version: 14
Device: Zenfone 10
App Version: 2.12.1
Source
Google Play
Format / File type
todo.txt
Additional info / Log
The text was updated successfully, but these errors were encountered: