search

cdown / clipmenu

Clipboard management using dmenu
MIT License
1.14k stars 91 forks source link

Tiny panel on Hidpi #90

Closed tareefdev closed 6 years ago

tareefdev commented 6 years ago

On Hidpi screen (4k) the clipmenu seems tiny, Although I used throw Rofi which run faultlessly with -dpi 192 parameter. Any suggestions?

kaihendry commented 6 years ago

Set your CM_LAUNCHER env to use rofi?

tareefdev commented 6 years ago

I put this: export CM_LAUNCHER=rofi in .bash_profile, isn't the right way?

kaihendry commented 6 years ago

Clipmenud is usually run by systemd user, hence the setting goes into /.config/systemd/user/clipmenud.service.d/override.conf 

[Service]
Environment=CM_LAUNCHER=rofi
tareefdev commented 6 years ago

I deleted that line in .bash_profile, and created the following one: ~/.config/systemd/user/clipmenud.service.d/clipmenud.service.conf:

[Unit]
Description=Clipmenu daemon

[Service]
ExecStart=
ExecStart=/usr/bin/clipmenud
Restart=always
RestartSec=0
Environment=DISPLAY=:0
Environment=CM_LAUNCHER=rofi

MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
ProtectControlGroups=yes
ProtectKernelTunables=yes
RestrictAddressFamilies=
RestrictRealtime=yes

[Install]
WantedBy=default.target

Then I restart my system, when I'm checking systemctl --user status clipmenud.service it's running but typing printenv CM_LAUNCHER didn't return anything.

Another trying, I execute clipmenu -i -fn Terminus:size=22 and finally it seems great on Hidpi, but I think it's still don't uses Rofi, because its colors and positions different from Rofi's settings.

Thanks.

cdown commented 6 years ago

Then I restart my system, when I'm checking systemctl --user status clipmenud.service it's running but typing printenv CM_LAUNCHER didn't return anything.

That's not how environment variables work -- they're propagated by process hierarchy, printenv isn't going to help you here. In your last comment you don't mention whether it works, just that you can't see the environment variable.

On Hidpi screen (4k) the clipmenu seems tiny

This is a question to pose to current dmenu developers, since clipmenu is menu program agnostic.

tareefdev commented 6 years ago

I found the proper way in Arch Linux wiki: "Environmental variables needed for applications should instead be added to /etc/environment", so I put there CM_LAUNCHER=rofi and finally clipmenu now uses rofi, and when I type printenv CM_LAUNCHER I got rofi.

Thanks.

cdown commented 6 years ago

I found the proper way in Arch Linux wiki: "Environmental variables needed for applications should instead be added to /etc/environment", so I put there CM_LAUNCHER=rofi and finally clipmenu now uses rofi, and when I type printenv CM_LAUNCHER I got rofi.

This isn't really the ideal way since now this pollutes every single application you use :-)

It will work, but there's no reason to make it system-global. Again, you should really look at how environment variables work -- working or not working with printenv really has nothing to do with your problem. Environment variables propagate downwards.