From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Drew Adams <drew.adams@oracle.com>, 29323@debbugs.gnu.org
Subject: bug#29323: kill-do-not-save-duplicate, FR
Date: Sat, 18 Nov 2017 20:06:54 +0100 [thread overview]
Message-ID: <4555a640-d432-eaad-954d-2a91078e2396@easy-emacs.de> (raw)
In-Reply-To: <9e1d4bed-fbe9-463a-afdd-031f3b9cb041@default>
On 16.11.2017 23:34, Drew Adams wrote:
>> Currently variable kill-do-not-save-duplicates checks only the (car
>> kill-ring) as docu explains: Do not add a new string to ‘kill-ring’
>> if it duplicates the last one. The comparison is done using
>> ‘equal-including-properties’. AFAIU it would be trivial replace this
>> check by a call of "member", thus checking > the whole kill-ring.
> Why do that? Why not just prevent duplicates in the first place, which
> is what the option currently does? If you for some reason get
> duplicate entries somehow, in spite of using the option to prevent
> them, you can always remove them. I don't understand how that would be
> something that would happen normally. What is the problem that this
> would try to solve/prevent? ---
Currently not a check for duplicates is implemented, but for a repeat.
When having alternating strings to copy, they go into the kill-ring one
after one. That way it ended up having just two strings in the
kill-ring, and previous content lost.
BTW implementing it would be a way more complicated as thought because
of text properties.
> BTW - it's a pain to remove all of the formatting of your mails to
> such lists.
Hmm, don't you see a formatting when sending.
> Please consider using plain text, or at a minimum not using a colored
> (i.e. non-white) background.
Switched on "Readers Default Colors", which should help.
> Just a request or suggestion.
next prev parent reply other threads:[~2017-11-18 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 19:51 bug#29323: kill-do-not-save-duplicate, FR Andreas Röhler
2017-11-16 22:34 ` Drew Adams
2017-11-18 19:06 ` Andreas Röhler [this message]
2017-11-18 19:48 ` Drew Adams
2017-11-19 18:42 ` Andreas Röhler
2019-11-11 2:14 ` Stefan Kangas
2021-11-30 14:48 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4555a640-d432-eaad-954d-2a91078e2396@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=29323@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).