You can put the game into its own time namespace.
https://www.man7.org/linux/man-pages/man7/time_namespaces.7.html
Byter
joined 1 year ago
I'm not sure I understand your question.
Eat has its own major mode which is used when you open a standalone buffer via the eat function.
When it's embedded in Eshell it mostly just does the right thing whenever you invoke a command that uses terminal control codes (e.g. htop) -- and many of those can be closed with q, yes.
I assume Eat is activated for any program listed in the eshell-visual-commands variable (but I'll admit I don't really understand how that works). The notable new minor modes present when I run htop in eshell are Eat--Eshell-Local and Eat--Eshell-Process-Running.
I haven't fully moved my terminal needs to Emacs (though I'd like to) for the same little niggles you mentioned. Just wanted to recommend another option amongst the good ones already suggested here.
I play Slay the Spire or Into the Breach on my phone on every flight I take. Both are light on the battery.
Please inform yourself before diminishing others' plights.
Diarrhoea that is characteristic of coeliac disease is chronic, sometimes pale, of large volume, and abnormally foul in odor. Abdominal pain, cramping, bloating with abdominal distension (thought to be the result of fermentative production of bowel gas), and mouth ulcers[35] may be present.
Coeliac disease leads to an increased risk of both adenocarcinoma and lymphoma of the small bowel
Long-standing and untreated disease may lead to other complications, such as ulcerative jejunitis (ulcer formation of the small bowel) and stricturing (narrowing as a result of scarring with obstruction of the bowel).
Thank you for calling that out. I'm well aware, but appreciate your cautioning.
I've seen hallucinations from LLMs at home and at work (where I've literally had them transcribe dates like this). They're still absolutely worth it for their ability to handle unstructured data and the speed of iteration you get -- whether they "understand" the task or not.
I know to check my (its) work when it matters, and I can add guard rails and selectively make parts of the process more robust later if need be.
I'd love a browser-embedded LLM that had access to the DOM.
"Highlight all passages that talk about yadda yadda. Remove all other content. Convert the dates to the ISO standard. Put them on a number line chart, labeled by blah."
That'd be great UX.
I'd ask why they don't make it optional (I'm not a Brave user) but it seems it was.
Another issue is that Strict mode is used by roughly 0.5% of Brave's users, with the rest using the default setting, which is the Standard mode.
This low percentage actually makes these users more vulnerable to fingerprinting despite them using the more aggressive blocker, because they constitute a discernible subset of users standing out from the rest.
Given that, I'm inclined to agree with the decision to remove it. Pick your battles and live to fight another day.
Thanks for asking. Not sure how I toggled that on...