-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
making repositioning of context tag and project tag optional #68
Comments
Hi @Tobida . I'm totally with you on this topic and would prefer it the way you describe it too. But this is actually not up to me, as I use a JavaScript library to do the parsing of the text into proper todo.txt objects. And while it does a great job in general, it doesn't persist the position of projects and contexts after generating the object, but sorts these attributes in it's own way. But in fact there is a feature request for exactly that feature at the project: jmhobbs/jsTodoTxt#5 You can give it a push over there and as soon as they implement it, I will include it into sleek. |
A similar repositioning request: is it possible to have a function to sort the projects/contexts inside the todo alphabetically?
running the function makes it
|
+1, super important imho |
Agree here - I am never likely to use to use Slick seriously if it messes with the Todo file and changing the order of the words is a serious problem. One if the points if the protocol is to be be able to use natural text. |
I'm closing here, the issue will further discussed in #68 |
Hello @ransome1 , since jmhobbs/jsTodoTxt#5 has been getting some attention lately, I wondered if the matter could be addressed in Sleek again. You closed #68 in September, but I didn't find an open issue with that problem (#92, #183, #216, #220, #306, #370 and #411 are all closed). Things have been getting better, since ticking of a box now only changes that very line, and not the whole file any more. But the resorting on the ticked todo is still happening unfortunately. Sleek is getting better and better every week, I am really hoping to be able to use it to tick off todos as well soon : ) Please let me know what you think. Thanks! |
Yes, as soon as jsTodoTxt is finishing the rewrite, sleek will adapt to it and hopefully this will solve these issues. But for now the latest version of jsTodoTxt is alpha and for almost two weeks there has been no progress. I will start implementing as soon as a stable version has been released and the documentation is complete :) |
Wow, that's a swift response, thanks @ransome1 ! Also thanks for reopening. You have no idea how much I am looking forward to using Sleek as my daily driver. |
Hey @ransome1 using the now new
Yeah I saw that. Folder
This is sleek using file
This is sleek using file
Both files The difference between I hope that helps? Thanks again for your effort! |
Funny you just posted this... But I did use dev7 above, phew 😇 |
Hehe :) The good news is, I can reproduce the issue with the non working file in my working environment. Let's see if I can find the root cause here. |
PERFECT!!! Looking at how you've handled issues in the past, I think it is safe to say that sleek will become my daily driver very soon 😊🥳 You have no idea how long I've been hoping for this to happen! Thank you so much! |
So then, the issue is being caused by the
I cannot find anything in that line, which looks unusual. What I found though is, that if I manually pass a line break That's something I will pass on to the As for now I added an error handling, which, will catch errors, when I don't know if you already mentioned it, but can you tell me what other apps (Todo apps, editors, or anything which manipulates the files) you use to work on your todo files? |
Thank you for looking into it! That's so weird, I can't be the only one having this problem...
That's what I mean... Nothing special to the file :(
Thanks. So that's nothing you can fix on our side, right?
I'll try my "real" todo-file in dev8 and will let you know how many lines are skipped.
On Windows I am using todotxt.net (https://github.com/jdckr/todotxt.net), Sublime Text portable, a self-made batch to add todos, a self-made ahk-script to add todos, Obsidian and Windows notepad.exe. On Android I am using Simpletask and Obsidian |
I think if I find out what exactly it is, that is making jsTodoTxt throw the error, I can intercept it. If it's some hidden character, I can cut it out. I will investigate it. |
Okay, thanks! |
@dnngll although it won't really help you, you can try out the latest developer preview: https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev8 If a line in the file contains something, which But I assume, that all the lines in your file will contain this mysterious character and it might cut out all your todos :/ |
Hey @ransome1 , thank you for your reply. I just got back and tried something new, which will address your point in #68 (comment) . I created a new file through the Windows context menu "New | Text Document" and named it
Or as a screenshot, cursor on end: Then I duplicated that file, renamed it into
Or again as a screenshot, cursor on end: These are the results of Powershell on
These are the results of Powershell on
That's so weird, isn't it? You could simply create these files yourself, however I uploaded then just in case you want to check them out: https://filetransfer.io/data-package/EjleeshY I used dev7 ( Also, I always deleted the userfolder before. I hope you can make any sense of this? I will try the same with the current dev now - just in case! Will get back to you asap... |
That took forever, since I'm on a very slow connection currently :( Using dev9 ( These are the results of Powershell on
Plus, a screenshot: These are the results of Powershell on
Plus, a screenshot again: Does that help? |
TLDR: IT'S WORKING!!! 🎉 I see you just released dev10 - wow! Here are the results using dev10 ( These are the results of Powershell on
These are the results of Powershell on
I'm really curious - what was the issue? Again, thank you so much. I am really looking forward to using Sleek now 😁 |
I just deleted the Dev10 again, because it wasn't working as expected. But thanks to your input here I now found the root cause: In Windows a line break is being represented as I will implement a multi platform compatible solution and push this into the new Dev10. |
I see! I find it really weird that I am the only one who was complaining about this. Seems no one else is on Windows... Or trying out the dev-versions... I am just playing around with the (broken) dev10 ( |
Totally disregard my last message. After playing around with that version for a bit, I realized that hardly anything is working yet. I should have considered your info about the nightlies: "This is an early developer preview with some basic functionality implemented, although many features are still missing." Looking forward to all the new features making it into the stable 👐 and will of course keep on testing future dev-versions. Thanks |
We are at a point where a lot of stuff is working already. What do you mean with |
I hope I didn't offend you by saying this, sorry if I did, didn't mean to. Here's what did not work:
So it was not really usable for me right now, which is why I thought that not everything has been implemented in these builds... Hope I could help! |
It is not suppose to be usable for production use: #501 I updated the release description texts to further clear up, what is happening in this project right now. Also let me close this thread for now, since we more or less hijacked it a little bit for something not related to the initial requirement. The line break issue should be resolved in the upcoming developer preview 10 and if it is not we should rather open a separate bug task. |
Yeah, my bad. I was so excited that you fixed #68 and wanted to use Sleek as my daily driver right away. So in my fantasy it was more of a "test new features in an upcoming version", than a complete rewrite. I know better now 😊 Really looking forward to "Once this foundational work is complete, there is room for new features. Hopefully developed not just by me. I sincerely hope that this endeavor will attract a broader range of contributors who will support me in achieving these goals." from your #501
Definitely, thanks
Yes, it was already resolved in the defective dev10 that I was able to download before you deleted it. I think however, the CRLF / LF problem after Sleek touches the file (first point from my #68 (comment) ) might be related, but I'm sure you've got it covered. Which brings me to my last point: I suppose I will not create new issues about what I mentioned in #68 (comment) (using the defective dev10), until the new dev10 comes out? To save you some time and to not hijack this thread any more, please only reply, if you want me to create new issues right away. If I don't hear anything from you here, I would wait for the final dev10. Thanks again @ransome1 ! |
I hadn't seen this particular issue on my side, but I would propose once the Dev 10 uploaded, you give it another try on your system. And if anything weird happens, I would appreciate a separate bug report. |
@dnngll I tested the latest implementation on a Windows machine and couldn't reproduce the error any more. So please feel free to test it out yourself and if it still throws the error or shows some other unwanted behavior, let's open a dedicated bug report for it. |
Hey @ransome1 last week I did test all 4 files from above plus my 3 main todo-files, using I am on dev-13 still, but will test dev-14 ( |
@dnngll the |
Yeah I know, thanks. I've been using it since last week. I got the link through the email GitHub sends automatically when subscribed. I just wanted to point out that dev-14 (still) can't be found on the official release-page https://github.com/ransome1/sleek/releases for some reason. Very much looking forward for the final 🙌 |
I love to use todo.txt in a natural way of language:
This is in consensus with the todo.txt rules i read: "Contexts and Projects may appear anywhere in the line after priority/prepended date"
In my sleek this will show up like this, the sentence is destroyed
I fully respect that in your perspective this is not a bug but a feature.
I would like to use it without the feature of putting tags at the and of the line - perhaps there could be an option to switch this behaviour off?
Thanks!
The text was updated successfully, but these errors were encountered: