The most popular clipboard manager for GNOME, with over 2M downloads. Check the Github page for a full list of features.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 69 | Active |
| 68 | Active |
| 67 | Rejected |
| 66 | Active |
| 65 | Active |
| 64 | Active |
| 63 | Active |
| 62 | Active |
| 61 | Active |
| 60 | Active |
| 59 | Active |
| 58 | Inactive |
| 57 | Active |
| 56 | Active |
| 55 | Active |
| 54 | Active |
| 53 | Active |
| 52 | Active |
| 51 | Active |
| 50 | Active |
| 49 | Rejected |
| 48 | Rejected |
| 47 | Active |
| 46 | Rejected |
| 45 | Active |
| 44 | Active |
| 43 | Active |
| 42 | Active |
| 41 | Rejected |
| 40 | Rejected |
| 39 | Inactive |
| 38 | Active |
| 37 | Active |
| 36 | Active |
| 35 | Inactive |
| 34 | Active |
| 33 | Active |
| 32 | Active |
| 31 | Inactive |
| 30 | Active |
| 29 | Active |
| 28 | Active |
| 27 | Active |
| 26 | Active |
| 25 | Active |
| 24 | Active |
| 23 | Active |
| 22 | Active |
| 21 | Active |
| 20 | Active |
| 19 | Active |
| 18 | Active |
| 17 | Active |
| 16 | Active |
| 15 | Active |
| 14 | Active |
| 13 | Active |
| 12 | Rejected |
| 11 | Active |
| 10 | Active |
| 9 | Active |
| 8 | Active |
| 7 | Active |
| 6 | Active |
| 5 | Active |
| 4 | Rejected |
| 3 | Rejected |
| 2 | Active |
| 1 | Rejected |
- the new prettyPrint() function calls the (no longer existent) dbPrintObj() - some nits: - forgot to delete convenience.js? - stat() (as called by g_file_info_query) may block as well, so if you want to avoid this, you'd have to use g_file_info_query_async() (yeah, nested async gets quite nasty fairly quickly :-/ ) - if your timeout handler returns false, the source is removed automatically; trying to remove it again in disable() will then result in a warning (harmless, but easily fixable by correctly resetting _clipboardTimeoutId) (none of this should block the extension though, so approving)
What do you mean by 'resetting _clipboardTimeoutId'? Do you think maybe I can set some global variable from inside the 'disable()' function, and the timeout handler will return false once that variable has been set?
No, I meant exactly what you did in the new extension version.