💾 Archived View for bbs.geminispace.org › s › Bubble › 1860 captured on 2024-07-09 at 04:29:07. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-06-16)
-=-=-=-=-=-=-
Re: "Editing quirk: if a post contains more than one 'line' (..."
Do you really dislike 'Paste Selected Text' as a possible solution?
2023-06-12 · 1 year ago
🕹️ skyjake [mod...] · 2023-06-12 at 13:26:
You mean pasting the marked selection without touching the clipboard?
🚀 stack [OP] · 2023-06-12 at 14:55:
That's what I was thinking, although pasting the clipboard also works. I don't know why I didn't think of that!
🍵 michaelnordmeyer · 2023-06-12 at 15:02:
Pasting the clipboard automatically would trigger a privacy warning on iOS each time the clipboard is being accessed.
🚀 stack [OP] · 2023-06-12 at 15:05:
michaelnordmeyer: even if pasting into the same application? That is really nuts.
🍵 michaelnordmeyer · 2023-06-12 at 17:45:
@stack Depends on the circumstances. There are always edge cases like you copy some text to the clipboard, then switch to another app, then switch back to Lagrange and select to upload text.
Bottom line: if an app queries the clipboard, the user is notified.
🚀 stack [OP] · 2023-06-12 at 18:46:
@michaelnodmeyer: while I appreciate the attempt to keep the user aware of potential privacy loss, it seems really wrong for a company with infinite resources to not keep track of the process id for the data in the clipboard. Annoying the user with pointless warnings makes it likely the user will ignore important warnings!
(added another reason to dislike Apple)
Editing quirk: if a post contains more than one 'line' (shift-cr is used to start a new line), it is no longer possible to edit anything but the final line using the Lagrange 'copy prev. line' prompt feature. Having posts that are not editable is a bit harsh. I realize this is more of a Lagrange issue (perhaps there should be a second option to copy anything highlighted into the prompt?), and those using standard browsers have to retype the whole post. As a possible work-around, you could...