clipboardcopies
clipnotify
clipboardcopies | clipnotify | |
---|---|---|
1 | 6 | |
5 | 217 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | 2 months ago | |
Swift | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clipboardcopies
-
“This project will only take 2 hours”
https://github.com/owenfi/clipboardcopies
The article does strike me as "scope creep" or missing the point of the question...I've taken this super crappy version and added it to my startup items, I think I might find it useful, and if I do it might grow over time. The polish can happen later if needed. I was able to accommodate a bit of the polish out of the gate by saving to individual files based on the time. The granularity roughly corresponds with the polling frequency. (Turns out there isn't a clipboard did change notification?)
To me the "complexities" are those things lurking beneath the surface, that a newbie doesn't know how to resolve, and an expert forgets to even point out. In this case the complexities I saw were:
clipnotify
-
Clipboards, Terminals, and Linux
The common xclip utility can be used to get or set clipboards. And, there's a tiny little utility script called clipnotify that I found really useful for debugging this. I cloned and built it, then ran it in a loop:
-
My first “useful” Go app
I rewrote this app for learning purposes, personal use and why not for sharing with other people to use as well.
-
xfocusnotify: X11-tool which exits when a window is focused and prints the respective window-id
Credit: I took inspiration from clipnotify.
-
Take My App Ideas
I don't think time to learn bash or programming intuition can reasonably be included in the timeframe to build a product. It's assumed that time starts after you come up with the idea to do something, and retroactively saying "this project took me a year" for something you created in a few hours is ... odd.
I agree that the time spent to find the libraries and their documentation should be factored in, so I'd like to note that that part of the process took ... 3 ddg searches (so +a few mins).
?where does parcellite store clipboard data -> https://www.mankier.com/1/parcellite -> `clipboard -c`
?regex for url -> https://gist.github.com/securibee/f15f8c7aaa0593cc32fc30f585...
?get notified when something has been copied to clipboard linux -> https://askubuntu.com/questions/1167026/detect-clipboard-cop... -> https://github.com/cdown/clipnotify -> `while clipnotify;do`
:)
- Run script on clipboard change, need help
-
“This project will only take 2 hours”
Using clipnotify[0], one could fix the busy-wait issue pretty easily.
[0] https://github.com/cdown/clipnotify
What are some alternatives?
WebOmni - Clipboard manager in the cloud
Simba - Simba is a program used to repeat certain (complicated) tasks. Typically these tasks involve using the mouse and keyboard. Simba is programmable, which means you can design your own logic and steps that Simba will follow, based upon certain input such a colours on the screen.
clipstory
WinOmni - Windows client for the device API
xfocusnotify - X11-tool which exits when a window is focused and prints the respective window-id.
DroidOmni - Clipboard manager in the cloud for Android
software-ideas