xcmenu - lightweight clipboard manager for X (formerly loliclip)

Cloudef · 2012-10-21 16:28:10

Šaran wrote:

My config.h isn't modified and it works with CLEAR_SELECTIONS.

Can you compile loliclip with the DEBUG variable set to 1, run the loliclip on terminal, reproduce the bug and pastebin the output somewhere. Thanks.

Last edited by Cloudef (2012-10-21 16:28:24)

karabaja4 · 2012-10-21 16:30:00

I managed to reproduce it too with Geany. Output of the line:

~ >>> for i in $(loliclip -h | grep -o "text/.*"); do loliclip -b "$i"; echo -e "\n--$i--"; done

--text/uri-list--

--text/plain--

--text/richtext--
ÿþBeginners' subforum for general Arch issues. Please consult the 
excellent Arch wiki and web before posting. Also try the forum search 
function at the upper left.
--text/html--

(I copied aaaaaaaaaaaaaaaa... in Geany and it pastes aaaaaaaaaaaaaaaa... everywhere else except in Gmail but that line from above doesn't list it).

EDIT: debug output coming soon.

Last edited by karabaja4 (2012-10-21 16:35:27)

Šaran · 2012-10-21 16:38:05

Output of loliclip &> lolilog without CLEAR_SELECTIONS.
http://ompldr.org/vZnlzaw

After pasting I have selected aaaaaaaaaaaaaaa in lolictrl and pasted again.

Cloudef · 2012-10-21 16:47:57

Since, I still can't reproduce this.. I take shot in the dark.
Can you give me output of the latest git again. I added some verbose to myself.

karabaja4 · 2012-10-21 17:08:48

Could it be that Geany is using some different selection type?

Šaran · 2012-10-21 17:21:20

It works with 2.4-4! Thank you!

http://ompldr.org/vZnl0YQ

Cloudef · 2012-10-21 18:17:21

It works with 2.4-4! Thank you!

Great to know! My code was just broken

karabaja4 · 2012-10-22 18:23:43

Can I use this new reset bit feature to avoid the libreoffice paste issue and if so, how?

Cloudef · 2012-10-22 19:58:03

You could put the reset bit to every selection.. But that would give same effect as CLEAR_SELECTIONS flag.
Putting images and text/ stuff (expect from text/uri-list, I don't think libreoffice uses it) to same data index, could work.
Not sure though.

karabaja4 · 2012-10-22 21:49:32

Heh. Too bad. As you wrote before, maybe it would be a good idea to make CLEAR_SELECTIONS default, so unsuspecting new users aren't scared away by strange behaviour (just IMHO).

Cloudef · 2012-10-23 14:41:26

karabaja4 wrote:

Heh. Too bad. As you wrote before, maybe it would be a good idea to make CLEAR_SELECTIONS default, so unsuspecting new users aren't scared away by strange behaviour (just IMHO).

Done.

karabaja4 · 2013-03-12 22:08:23

Hey Cloudef,

sorry to bother you, but if and when you have free time... could you check why loliclip doesn't play nice with suckless st terminal?

Basically anything you highlight (select) gets unselected very quickly inside the terminal, sometimes the selection doesn't even start because it is cancelled too quickly.

Thanks!

P.S: This is the st terminal package: https://aur.archlinux.org/packages/st/

Last edited by karabaja4 (2013-03-12 22:11:11)

Cloudef · 2013-03-12 22:21:16

It's propably related to the way PRIMARY selection is queried..
There might be no easy solution for this.

For now it might be possible to workaround it by commenting out line 51 in config.h (REGISTER_CLIPBOARD("PRIMARY" ...)
Anyways, I'll take a look when I've got time.

karabaja4 · 2013-03-12 22:36:39

Cloudef wrote:

For now it might be possible to workaround it by commenting out line 51 in config.h (REGISTER_CLIPBOARD("PRIMARY" ...)
Anyways, I'll take a look when I've got time.

Commenting out line 51 didn't help. Anyway, it's just a minor annoyance, no need to rack your brain over this.

loliclip rocks

Cloudef · 2013-03-12 22:42:22

Commenting out line 51 didn't help. Anyway, it's just a minor annoyance, no need to rack your brain over this.

I see. I'll try to check it out tomorrow.

loliclip rocks

Thanks, it's something I use daily as well.

Cloudef · 2013-03-13 16:29:50

It seems when you select stuff in st, it also copies the the stuff to CLIPBOARD, and since loliclip by default postprocess immediatly everything that goes to CLIPBOARD, it needs to grab the ownership of the selection which as side effect causes X to unselect the text in whichever application had the selection before.

karabaja4 · 2013-03-13 17:03:18

Cloudef wrote:

It seems when you select stuff in st, it also copies the the stuff to CLIPBOARD, and since loliclip by default postprocess immediatly everything that goes to CLIPBOARD, it needs to grab the ownership of the selection which as side effect causes X to unselect the text in whichever application had the selection before.

st copies selection into CLIPBOARD? lol. I'll try to workaround this in st code.

Thanks.

karabaja4 · 2013-03-13 17:30:53

Fixed Simple replacing "CLIPBOARD" with "PRIMARY" did the trick.

Army · 2013-03-13 18:08:35

Wanna mention this upstream? I use st too and frankly, I don't really like this behavior (fixed it with a sed line in the PKGBUILD).

Last edited by Army (2013-03-13 18:08:59)

karabaja4 · 2013-03-19 19:36:50

Hey Cloudef,

a problem again with 2.4-7 to 2.4-8 upgrade This commit:

https://github.com/Cloudef/PKGBUILDS/co … 69527d2c8e

caused a problem when running loliclip in the background using a shortcut (Openbox).

I have this script.sh

#!/bin/bash

loliclip -p | loliclip -c
aplay /usr/share/etracer/sounds/fish_pickup1.wav

binded on Super-C. loliclip does nothing when the command is run (and the sound is played).

I also tested a bit. This works:

echo test | loliclip -c

but this doesn't:

loliclip -c > hello.txt

The weird thing is, when piping is ran from the command prompt (terminal) everything works like it should.

Cheers!

Cloudef · 2013-03-20 07:56:30

Seems like the isatty is not good for checking this case.
I'll propably just add seperate command switch for input/output for simplicity sake.

Atm, my GPU broke, so I'm waiting for new one. Will take a while.

karabaja4 · 2013-03-20 21:52:08

Cloudef wrote:

Seems like the isatty is not good for checking this case.
I'll propably just add seperate command switch for input/output for simplicity sake.
Atm, my GPU broke, so I'm waiting for new one. Will take a while.

Can you please explain, what is the purpose of isatty command? As I can read from your comments, it blocks the piping of data if the pipe is open, is that limitation there just for robustness?

Because if it is and doesn't really change anything, I don't think it's worth it... new people will probably assume loliclip isn't working and discard it.

Cloudef · 2013-03-21 07:12:21

karabaja4 wrote:

Can you please explain, what is the purpose of isatty command? As I can read from your comments, it blocks the piping of data if the pipe is open, is that limitation there just for robustness?
Because if it is and doesn't really change anything, I don't think it's worth it... new people will probably assume loliclip isn't working and discard it.

I tried to preserve similar functionality as xsel. They used isatty, but in this case it won't work since there is no tty when forking and piping.
But looking back again. Even xsel has seperate commands for output/input.

The added isatty there is related to github issue reported few days back. (When pipe has no data, it dumps the output to stdout).

Cloudef · 2013-04-05 20:48:20

karabaja4, I've added --pipe/-i switch to the git. This tells loliclip to always wait input from pipe and ignore what isatty tells. Also, instead of loliclip -p | loliclip -c, I suggest using lolictrl -spc.
That way you syncing from primary to clipboard is quarnteed to work in future as well.

I'll update loliclip on aur, if no other regression is found.

karabaja4 · 2013-04-05 21:43:17

Thanks.

I've been looking at the code and I've been trying to figure this out:

-      if (!isatty(fileno(stdin))) return 1;
+      if (!isatty(fileno(stdin)) || PIPE_MODE) return 1;

It's not exactly clear to me how this works.

Before, if isatty() would return false (we are not in terminal), the function would return 1 and do nothing.

Now, if isatty() returns false (we are not in terminal) or we are using PIPE_MODE switch the function will return 1 and do nothing.

I guess this would seem more logical:

if (!isatty(fileno(stdin)) && !PIPE_MODE) return 1;

Please if you would explain... it could be that I'm too tired and talking stupid... I haven't tried loliclip yet though, I will as soon as I have the chance.

Arch Linux

#151 2012-10-21 16:28:10

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#152 2012-10-21 16:30:00

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#153 2012-10-21 16:38:05

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#154 2012-10-21 16:47:57

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#155 2012-10-21 17:08:48

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#156 2012-10-21 17:21:20

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#157 2012-10-21 18:17:21

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#158 2012-10-22 18:23:43

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#159 2012-10-22 19:58:03

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#160 2012-10-22 21:49:32

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#161 2012-10-23 14:41:26

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#162 2013-03-12 22:08:23

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#163 2013-03-12 22:21:16

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#164 2013-03-12 22:36:39

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#165 2013-03-12 22:42:22

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#166 2013-03-13 16:29:50

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#167 2013-03-13 17:03:18

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#168 2013-03-13 17:30:53

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#169 2013-03-13 18:08:35

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#170 2013-03-19 19:36:50

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#171 2013-03-20 07:56:30

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#172 2013-03-20 21:52:08

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#173 2013-03-21 07:12:21

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#174 2013-04-05 20:48:20

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

#175 2013-04-05 21:43:17

Re: xcmenu - lightweight clipboard manager for X (formerly loliclip)

Board footer