-
Search Results
-
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_selectionWhat is the difference between Primary Selection and Clipboard Buffer?
https://unix.stackexchange.com/questions/139191/whats-the-difference-between-primary-selection-and-clipboard-bufferhttps://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/clipskicd /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/holdingpenAll set. To launch the program, type: clipski
User approved, EDIT BY Moddit: PROBLEM WAS USER ERROR GRUB NOT INSTALLED
I’m new to Linux and am trying to install AntiX on a HTPC. After some effort, I was finally able to install it to an old SSD with no apparent issues. However, when I try to actually boot from that drive, the computer gets stuck at “verifying DMI pool data”. I did some Googling, and I think that means there’s a problem with how I formatted the drive in some way that’s preventing the OS from being able to boot. But I have no clue what I did wrong.
Not sure what information you need, but here’s the fdisk output for the drive in questionn. I formatted it as ext4 and was able to run sudo cli-installer with no issues. I changed the boot flag afterwards because I didn’t realize that was needed.
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2a06df21Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 488397167 488395120 232.9G 83 Linux- This topic was modified 2 years, 5 months ago by ModdIt.
- This topic was modified 2 years, 4 months ago by ModdIt.