Lemmy Apps
A home for discussion of Lemmy apps and tools for all platforms.
RULES:
- No spamming
- Be nice and have fun
- Follow the general lemmy.world rules
Any project posted here requires an AI disclosure if any ML/LLM technology was used in any way in the development:
- Please include [AI] or [AI Assisted] as a tag at the end of your post title when sharing or discussing the project.
- In the post body, please include in what way AI was used, e.g.:
AI disclosure:
design: none
implementation: assist
testing: copilot
documentation: auto
review: pair
deployment: hint
Please consult ai-declaration.md for details how to apply about these categories. If you are posting about an app, but are not the developer, you should include the most complete information available, e.g.: " This repository lists Copilot as a contributor." or " This app shows signs of AI development such as..."
An extensive list of Lemmy apps is available here:
Visit our partner Communities!
Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. !plugins@sh.itjust.works
Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. !lemmy_integrations@lemmy.dbzer0.com
Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. !lemmy_dev@programming.dev
Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. !lemmydev@lemm.ee
view the rest of the comments
Basically when you press backspace the underline for autocorrect extends over the space before the word, then when you press backspace again it deletes that space. Every other press of backspace will delete the space before, completely messing up the text when you're just trying to make a minor correction. You then have the hassle of pixel hunting to get the cursor in the middle of the word where the space was to add it back again.
Ok my bad seems like I recalled incorrectly, your description fits exactly my experience. It's the keyboard
It's not really the keyboard though, the keyboard works fine everywhere else. It's a poor implementation from the text editor that Jerboa uses, one that other keyboards have created a workaround for. But the issue is in the text editor.
It's like when a website only works in Chrome, but doesn't work in Firefox. It isn't because Firefox is broken, it's because the website doesn't follow web standards and has only been tested in Chrome.
I see, there's the keyboard on one side and the text editor on the other, and they don't mesh well ? that makes more sense