You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ wl-paste >~/carlsen-kaidanov-2023.pgnClipboard content is not available as inferred output type "application/vnd.chess-pgn"Use "wl-paste --list-types" to view available types. Use "--type" to explicitly specify a type.
$
With this output it's not clear if the file has been created (it has) or if this error is fatal (it's not). Something like this might be better:
$ wl-paste >~/carlsen-kaidanov-2023.pgnWarning: Clipboard content is not available as inferred output type "application/vnd.chess-pgn"Use "wl-paste --list-types" to view available types. Use "--type" to explicitly specify a type.
$
The text was updated successfully, but these errors were encountered:
thanks for the suggestion, but I don't think I'm following why you'd want that:
it's not clear if the file has been created (it has)
Well, the (empty) file is created by your shell, not by wl-clipboard, before wl-paste even starts running. So the file will be created whether or not wl-clipboard does anything or runs into any errors.
if this error is fatal (it's not)
Depending on what you call fatal, I guess? It certainly means we could not paste; wl-paste exits with code 1 right after printing this error. But it's not fatal, as in nothing's crashed, your computer is not on fire, you should probably just re-run wl-paste with an explicit --type option.
In your specific case, you're trying to paste to a PGN file, so wl-clipboard looks for application/vnd.chess-pgn in the clipboard, but apparently it doesn't contain that. Since PGN is (apparently) a textual format, perhaps the source app thought it was copying plain text? Try wl-paste --type text > ~/carlsen-kaidanov-2023.pgn then.
I see. If I'm wrong in thinking this is a warning and not fatal, then can illustrate the point: users are prone to confusion about which messages are for fatal errors without being hit over the head with it. :)
For example:
With this output it's not clear if the file has been created (it has) or if this error is fatal (it's not). Something like this might be better:
The text was updated successfully, but these errors were encountered: