In theory. The frontend is curre tly unaware of encodings, and the choice between UTF-8, UTF-8 w/BOM, SBCS, and hexdump is hardcoded for each language.
No, the frontend byte counter cannot rely on the backend. In the way it is set up right now, it would have to query the backend once for each keystroke.
Actual byte counters would have to get implemented in the frontend. I plan to do that eventually, but to make sense, you'd also have to be able to pick and encoding.
@MDXF I'm not sure I'll be able to add Eiffel. The compiled interpreter takes up 1.1 GiB of disk space, which is a huge chunk out of TIO's 20 GiB for a language I haven't even heard of.
Anonymous
06:54
@Dennis I can help you with some iPad debugging tomorrow (so in ~12 hours), hopefully.
Anonymous
I just need to bug my wife and have her leave her iPad at home tomorrow
@Dennis If I am using the search box but I have Practical unticked and I type "Java", there are no results which is perfectly correct. Request: If there are no results but you have filters enabled, can you provide a little tip to check the filters if the same search would return results without them?
so like in my example, you would still return 0 results but since you would have >0 results if Practical was ticked, a message is displayed
@Poke I'd suggest a message that says e.g. "showing 0 of 4 results", but even for the general case: "showing 8 of 20 results", "showing 5 of 5 results"
@StepHen I was thinking about that, but I'm not sure if transparently reordering the results would help or confuse people. I agree that searching for c isn't exactly useful as is though.
@Dennis Hm. Are you currently separating the compiler " (compiler)" and the name of the lang? If you are, a direct hit on the lang name could elevate it to the top of the list