clipski (forked from ClipIt) tray-resident clipboard manager

Forum Forums General Software clipski (forked from ClipIt) tray-resident clipboard manager

  • This topic has 3 replies, 2 voices, and was last updated Dec 30-8:17 pm by Anonymous.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #48481
    Anonymous

      https://gitlab.com/skidoo/clipski

      Project rationale:

      clipski (forked from ClipIt) is a tray-resident GTK+ gui clipboard manager

      Although clipit does provide a –with-gtk3 compile option,
      its debian package has been orphaned, and debian has
      chosen to “deprecate” clipit as of the debian 11(Bullseye) release.

      Both clipit and parcellite tout their lightweighted-ness, yet both
      have become fraught with longstanding and/or recurrent bugs related to
      frilly (and proprietary, desktop environment -specific) features added along the way.
      Appatanyaindicator thingie and guh-nome ‘eggaccelerators’? Thanks, no thanks.

      Parcellite is (as of Dec 2020) still slated for inclusion in Debian 11,
      but it is ‘GTK2-only’, so will soon be be dropped from debian.
      ( ref: https://sources.debian.org/src/parcellite/1.2.1-3/debian/control/ )

      An alternative, Qt-based clipboard manager GUI utility (CopyQ), remains available
      in Debian11… but (as tested on a 64bit system) its runtime memory footprint is 50MB+ !

      Why use a “clipboard manager” ?

      * copied text (and, optionally, any selected text) remains available for immediate pasting
      even if the program you are copying from closes / exits / crashes

      * provides an option to Purge history after a configurable timeout
      (in case you are copypasting passwords)

      background reading:

      article titled “X Window selection”
      https://en.wikipedia.org/wiki/X_Window_selection

      What is the difference between Primary Selection and Clipboard Buffer?
      https://unix.stackexchange.com/questions/139191/whats-the-difference-between-primary-selection-and-clipboard-buffer

      https://askubuntu.com/questions/7769/keyboard-shortcut-for-pasting-the-primary-selection

      https://wiki.archlinux.org/index.php/clipboard

      ((( for even more background reading, websearch “linux primary selection” )))

      clipski features:

      * monitor Ctrl+C clipboard events and/or primary selection events
      * optionally, capture content of primary selection events into clipboard
      * optionally, maintain a history list of your copied snippets
      * optionally, purge history list and clipboard content after specified timeout
      * ability to edit and/or pin items (make permanent in history list)
      * as-you-type filtered history search
      * ability to selectively exclude from history (specified window names, strings, or regex)
      * optionally, trim whitespace from each newly added snippet

      ~~~~ This project repository provides a debfile,
      packaged for use with antiX 19 (and debian buster repositories): clipski_1.4.6_amd64.deb

      ________________________________________________

      How to DIY compile, create debfile, and install clipski (on an antiX or debian system)

      note: As of v1.4.6, clipski COMPILES AGAINST GTK3 ONLY (NOT GTK2 aka libgtk-2.*-dev)

      ### manually download the clipski source code, or
      sudo apt install git
      mkdir -p /path/to/holdingpen # e.g. ~/Downloads/tmp
      cd /path/to/holdingpen
      git clone https://gitlab.com/skidoo/clipski

      cd /path/to/holdingpen
      sudo apt install build-essential fakeroot debhelper intltool libgtk-3-dev
      dpkg-buildpackage -b
      sudo apt install /path/to/holdingpen/clipski_1.4.6_suffix.deb
      # ( dpkg-buildpackage places the debfie in the parent directory above your holdingpen )
      # The exact debfile name, above, varies depending on your system architecture.
      # Immediately afterward, to cleanup, you can optionally followup with:
      # cd .. && rm -rf /path/to/holdingpen

      All set. To launch the program, type: clipski

      #48503
      Member
      Xecure
        Helpful
        Up
        0
        ::

        When I am back on my main PC, I will build it for stretch/buster/bullseye i386 and ambd64, and link it so that it can be included in the antiX main repos. I think this is a good replacement for clipit for the future buster main release.

        antiX Live system enthusiast.
        General Live Boot Parameters for antiX.

        #48535
        Member
        Xecure
          Helpful
          Up
          0
          ::

          clipski 1.4.6 buster (32 and 64 bits): https://gitlab.com/nXecure/my-packages/-/tree/master/clipski/clipski-1.4.6/buster
          clipski 1.4.6 bullseye (32 and 64 bits): https://gitlab.com/nXecure/my-packages/-/tree/master/clipski/clipski-1.4.6/bullseye

          I have tested the buster build, but not the bullseye build yet.
          I cannot build for stretch (some missing dependency, and I haven’t explored the issue in detail).

          This is what I have so far.

          antiX Live system enthusiast.
          General Live Boot Parameters for antiX.

          #48543
          Anonymous
            Helpful
            Up
            0
            ::

            FWIW, at this point (debian 11 has not yet entered “freeze”) I am not yet building//testing with libraries packaged for debian 11 repos.

            For me, this project in particular was a toe-in-the-water to gauge how miserable it would be for me to convert my unsupported-upstream cherished gtk2 programs to gtk3.

            the takeaway:
            Very.
            Very miserable. The $%@!# gtk3 developer documentation mentions shite that does not (now) work because it has ALREADY been deprecated along the way ~~ across break/fix gtk3 releases. Even the basic building block for this app (“status_icon” widget) has been “deprecated”. We are now (as of gtk 3.8?) expected to learnabout and use “a notification” (sic) instead.

            What will be the gtk “version” in debian 11 stable?
            We can reasonably guess that it will be v3.24.241
            but I am unwilling to waste effort building/testing against that still unknown target.

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.