Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos and markdowns #73

Merged
merged 1 commit into from Aug 8, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/test.yml
Expand Up @@ -16,7 +16,7 @@ jobs:
override: true
components: rustfmt
- uses: actions/checkout@v2
- name: Check formating
- name: Check formatting
uses: actions-rs/cargo@v1
with:
command: fmt
Expand Down
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -10,7 +10,7 @@ This is a cross-platform library for interacting with the clipboard. It allows t

The Linux implementation uses the X protocol by default for managing the clipboard but *fear not* because Wayland works with the X11 protocol just as well. Furthermore this implementation uses the Clipboard selection (as opposed to the primary selection) and it sends the data to the clipboard manager when the application exits so that the data placed onto the clipboard with your application remains to be available after exiting.

There's also an optional wayland data control backend through the `wl-clipboard-rs` crate. This can be enabled using the `wayland-data-control` feature. When enabled this will be prioritized over the X11 backend, but if the initialization fails, the implementation falls back to using the X11 protocol automatically. Note that in my tests the wayland backend did not keep the clipboard contets after the process exited. (Although neither did the X11 backend on my Wayland setup).
There's also an optional wayland data control backend through the `wl-clipboard-rs` crate. This can be enabled using the `wayland-data-control` feature. When enabled this will be prioritized over the X11 backend, but if the initialization fails, the implementation falls back to using the X11 protocol automatically. Note that in my tests the wayland backend did not keep the clipboard contents after the process exited. (Although neither did the X11 backend on my Wayland setup).

## Example

Expand Down
2 changes: 1 addition & 1 deletion src/platform/linux/x11.rs
Expand Up @@ -242,7 +242,7 @@ impl Inner {
let mut guard = selection.mutex.lock();

// Notify any existing waiting threads that we have changed the data in the selection.
// It is important that the mutex is locked to prevent this notication getting lost.
// It is important that the mutex is locked to prevent this notification getting lost.
selection.data_changed.notify_all();

if wait {
Expand Down