Earlier quoted context omitted.
Why can't a Go program fork into the background?
Because go uses threads.
Makes me wonder if there is a way at all that you could implement a Go fork yourself.
How the clipboard works
151–160 of 160 posts
Re: How the clipboard works
#152> The majority of the implementations out there are broken and only handle text. Copy/paste are the biggest neglected operations in computing, considering that they are the only universal mechanism for transferring data between applications that is accessible to end users. Mobile intents do help somehow, but they are not universal or available on desktop or web environments.
In Windows-land I'm more annoyed that lots of applications default to pasting rich-text, when in 95% of cases I only want the text and not the formatting. Otoh, copy-pasting images or entire files works great, as does drag-and-drop all over the place (dragging things from Firefox's download popup, or from E-Mail attachments).
There are several clipboard apps that let you clean format and keep just the text by pasting with a hotkey like CTRL+SHIFT+V.
Re: How the clipboard works
#153Earlier quoted context omitted.
You'd expect the Wayland design to improve on that to allow clipboard managers to work 100% reliably and efficiently by only being able to take over the clipboard just before the previous owner closes - just like how Windows does it. Better yet would be to integrate that behavior into the server.
You don’t want to integrate it into the server, because that limits choice. There are a lot of features that you could put into a clipboard manager that not everyone would want, and you don’t want to force everyone to just have the least common denominator of those features. For example, one commenter pointed out that he uses one that keeps a permanent database of everything he has ever copied. Maybe you want to sync…
I'd want the server to provide the baseline functionality to keep up the illusion that Ctrl+C copies into the clipboard, even accross application restarts. That doesn't preclude additional clipboard managers that do more (e.g. history) on top of that.
Re: How the clipboard works
#154Earlier quoted context omitted.
You don’t want to integrate it into the server, because that limits choice. There are a lot of features that you could put into a clipboard manager that not everyone would want, and you don’t want to force everyone to just have the least common denominator of those features. For example, one commenter pointed out that he uses one that keeps a permanent database of everything he has ever copied. Maybe you want to sync…
I'd want the server to provide the baseline functionality to keep up the illusion that Ctrl+C copies into the clipboard, even accross application restarts. That doesn't preclude additional clipboard managers that do more (e.g. history) on top of that.
The protocol doesn’t support that feature. No wayland server or clipboard manager can add it. Applications don’t support it either.
Re: How the clipboard works
#155This design has the really annoying situation that applications closing down can't leave stuff in the clipboard. This results in a quite a frustrating behavior for users and also makes command line tools tricky. wl-clipboard lets you pipe text into the command to copy. The way it works is that it daemonizes in the background to fulfill the copy request. It either cancels on the first paste (command) or until some oth…
> This design has the really annoying situation that applications closing down can't leave stuff in the clipboard.
Some programs on Windows will present you with this dialog when closing the program:
There is a large amount of information on the Clipboard. Do you want to be able to paste this information into another program later?
Re: How the clipboard works
#156This contradicts how I as a user think of the clipboard. The clipboard is the most important feature of end user computing that is ignored by OS designers. I should be able to open a window and see all things in my clipboard. Also with password managers like 1Password using the clipboard as a means to xmit sensitive data it seems to me like the API needs to be updated. An interesting solution to the problem discussed…
> I should be able to open a window and see all things in my clipboard.
In Windows, pressing Win+V does exactly that.
Re: How the clipboard works
#157I'm surprised there was no mention of copy/paste that existed BEFORE ctrl+c/ctrl+v ctrl + INS (copy) shift + INS (paste) IIRC this is a hardware interrupt in much the same way as ctrl+alt+del is. My memory is damn hazy about this (I've used DOS since MS-DOSv3.3) but I think I used that combination back in the DOS days. {instead of using the mouse to select things, shift+CURSOR would do the trick} This might even be a…
Well I'll be. You learn a new hotkey every day. Certainly feels like it predates the mouse, considering the innate right-handedness of the key combo.
I've always thought of Ctrl+Ins/Shift+Del/Shift+Ins as an accessibility feature for left-handed people like me.
Re: How the clipboard works
#158Earlier quoted context omitted.
That's generally true of most things in Wayland. It's poorly designed and then badly implemented, by multiple different compositors in different ways, leading to endless bug reports and broken software.
What's so frustrating is that this is my Linux desktop experience since I have been using it. Clipboards not surviving shutdown where at one point not working, then a bunch of people got together to fix it up and now it's broken again. My Wayland experience is a massive flashback to 2004.
Yes, I know. I remember several years ago being super excited about Wayland. But every time I have tried it, it just falls over in so many different ways. I have given up.
About copy/paste in particular, I have solved it for myself because I work almost exclusively in the terminal and the browser, both of which stay running all the time and therefore acts as a clipboard manager for any copy/paste that happens in it. I am just waiting for my terminal of choice to get support for copy/pasting arbitrary mime types, which its maintainer has said he is going to implement.
Re: How the clipboard works
#159Earlier quoted context omitted.
Well I'll be. You learn a new hotkey every day. Certainly feels like it predates the mouse, considering the innate right-handedness of the key combo.
I've always thought of Ctrl+Ins/Shift+Del/Shift+Ins as an accessibility feature for left-handed people like me.
You use the mouse left handed, then? I'm left handed myself and briefly tried that back as a youngster in computer lab but never really adjusted to it well enough to continue doing so.
Re: How the clipboard works
#160Earlier quoted context omitted.
So... selecting some text by accident clears what you previously had in the clipboard?
Well, of course; why would you want to keep the initial clipboard forever? This is exactly the same behavior as for ^C/^V. I don't understand the purpose of your question.
> by accident
Imagine you install a 'clapper' in your bedroom to control the lights. You say "works great for me, let's install this everywhere". Someone responsible for an auditorium then says "so clapping turns the lights on and off?"
That said, I frequently use text selection as a highlighter. I will highlight lines as I'm reading text to help me keep track of which line I'm on. I also need to select text to apply formatting such as bold or add link.