From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: kill ring questions, #emacs
Date: Sun, 15 Apr 2018 06:06:15 +0200 [thread overview]
Message-ID: <86vact5d1k.fsf@zoho.com> (raw)
I just posted this on #emacs but I don't see
why I can't post it here as well. They say in
the topic "No public logging! What happens in
#emacs stays in #emacs" but surely that doesn't
refer to 100% on-topic Q&As, right? (Or, for
that matter, the topic itself :))
<incal> hello, is there a setting to inhibit
the kill ring from filling up with
several back-to-back instances of the
same string?
<incal> also why is the kill ring fontified?
why not let that be determined by the
mode/context of the new place, where it
is yanked?
--
underground experts united
http://user.it.uu.se/~embe8573
next reply other threads:[~2018-04-15 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 4:06 Emanuel Berg [this message]
2018-04-15 4:28 ` kill ring questions, #emacs Emanuel Berg
2018-04-15 5:36 ` Marcin Borkowski
2018-04-15 6:40 ` Teemu Likonen
[not found] ` <mailman.12417.1523770740.27995.help-gnu-emacs@gnu.org>
2018-04-15 14:17 ` Emanuel Berg
[not found] ` <mailman.12418.1523774421.27995.help-gnu-emacs@gnu.org>
2018-04-15 14:18 ` Emanuel Berg
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=86vact5d1k.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).