Closed 0xInfection closed 3 years ago
Hi!
The issue (should) be resolved in the latest commit, thanks for reporting! As far as I know, I've caught all of the unicode characters, and "converted" them in similar-looking ascii chars. Please let me know if you find more of them, since I can't reproduce the error due to my environment supporting UTF 8 :+1:
Thanks, great work man. Keep it up!
Also @VainlyStrain, we should merge the dev branch into master and let people know that a new release is upcoming. What do you say?
I'm for it! I'll take care of it tomorrow*
*(basically, in some hours :wink: Nights have been rather short due to CTF)
Traceback (most recent call last):
File "/root/tidos-framework/tidconsole.py", line 779, in
Salut a tous j'ai ce soucis lorsque j'essaie d'executer TIDoS-Framework comment resoudre le soucis cordialements....
So I started to manually test TIDoS v2 on the
dev
branch, and found a few bugs (more possibly upcoming). This is the first one that I hit while trying to runsudo ./tidconsole.py
.Possible cause:![image](https://user-images.githubusercontent.com/39941993/97099726-4571ae80-16b2-11eb-9047-90b1b0e3b291.png)
Another place where I encountered this is right after adding a site using
vicadd
command.I would suggest that we should stick with strict ASCII. This is because for terminals that don't support unicode, the tool will just spew illegible characters. Since these arts have been curated by you, so I would let you decide what to do with these.
I agree that unicode makes it look good, but they are an unnecessary cause of these troubles. Let me know what you think! :) P.S.: Great work with the ASCII arts!