Skip to content

Commit 7c299c3

Browse files
author
01micko
committed
fixup - better wording
1 parent ef6a84f commit 7c299c3

File tree

1 file changed

+7
-17
lines changed

1 file changed

+7
-17
lines changed

src/integration.md

Lines changed: 7 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -353,31 +353,21 @@ and set `QT_QPA_PLATFORMTHEME=qt6ct` in `~/.config/labwc/environment`.
353353

354354
# 10. Clipboard {#clipboard}
355355

356-
**Labwc** does not natively support storing of data kept on the clipboard.
356+
**Labwc** does not store clipboard contents after an application quits.
357357
For this functionality you need a _clipboard manager_.
358358

359-
Some clipboard managers to get you started are:
360-
361-
- [cliphist]
362-
- [clapboard]
363-
- [clipse]
364-
365-
They all depend on [wl-clipboard] and there are many more with various
366-
features.
367-
368-
Once you have a clipboard manager you need to have it start when starting
369-
your session, which you can do in `~/.config/labwc/autostart`.
370-
371-
You can add a line similar to this:
359+
For example, you could add a line similar to this to
360+
`~/.config/labwc/autostart`:
372361

373362
```
374363
wl-paste --watch cliphist store &
375364
```
376365

377-
You then need to access the data. You either need a `dmenu` like program
378-
for wayland such as `bemenu`, `rofi`, `wofi` or `tofi` or a dedicated clipboard
379-
application such as `nwg-clipman`.
366+
This uses [cliphist] and [wl-clipboard]. Other clipboard managers include
367+
[clapboard] and [clipse].
380368

369+
Many clipboard managers have features beyond just keeping the clipboard
370+
alive. See the documentation of the individual tools for further information.
381371

382372
# 11. Input Method {#input-method}
383373

0 commit comments

Comments
 (0)