From: MarcWeber <MarcWeber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: urxvt keeps asking to verify paste
Date: Fri, 24 Nov 2023 14:48:49 +0100 [thread overview]
Message-ID: <20231124134849.EIwCXHnwsaGfQoA3DP0O83SIQ8r-F3DCjcVvDTIQPV8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34442@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
New comment by MarcWeber on void-packages repository
https://github.com/void-linux/void-packages/issues/34442#issuecomment-1825703027
Comment:
My view:
- urxvt is not a default of user friendly distros anyway, is it?
- open source should be getting out of the way, not into the way. Cause not getting your job done has a cost, too.
- When it matters (eg irssi) they have their own checks
- I am aware of copying from the net could be dangerous (so is loosing time). So maybe it should be the responsibility of providing/receiving sides to step into the way.
Pasting 3 lines into a shell is a common pattern.
Have you ever seen a PC "Do you want to switch on the speakers could be loud?" ;-)
But maybe a link to this issues would be enough to have people find the solution fast and control their own ~/.X11defaults file.
But the most annoying thing is that if you copy paste 3 lines from an urxvt terminal you get one line instead then ! So the behavior might even change in an unexpected way. I have been using version 9.31.
next prev parent reply other threads:[~2023-11-24 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 13:14 [ISSUE] " zlice
2021-12-09 19:39 ` loreb
2021-12-09 19:49 ` [ISSUE] [CLOSED] " zlice
2021-12-09 19:49 ` zlice
2022-05-15 7:09 ` xlotlu
2022-05-15 7:29 ` paper42
2022-05-15 12:28 ` zlice
2023-11-24 13:48 ` MarcWeber [this message]
2023-11-24 14:12 ` loreb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231124134849.EIwCXHnwsaGfQoA3DP0O83SIQ8r-F3DCjcVvDTIQPV8@z \
--to=marcweber@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).