unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Copying a list for insertion
Date: Sat, 22 Oct 2022 14:34:38 +0300	[thread overview]
Message-ID: <Y1PVTn1klBN6HyDo@protected.localdomain> (raw)
In-Reply-To: <87wn8sd5xx.fsf@dataswamp.org>

* Emanuel Berg <incal@dataswamp.org> [2022-10-22 14:17]:
> Jean Louis wrote:
> 
> > (defun rcd-kill-new (kill)
> >   (cond ((stringp kill) (progn 
> > 			  (kill-new kill)
> > 			  (rcd-message "Killed: %s" kill)))
> > 	 (t (rcd-message "😧 WARNING: Nothing to kill."))))
> 
> ;; (advice-add    #'kill-new :after (lambda (&rest str) (message "%s" str)))
> ;; (advice-remove #'kill-new        (lambda (&rest str) (message "%s" str)))

WYMINWYS - What you mean is not what you see.

Purpose of my function `rcd-kill-new' is not to send message what was
killed, but in general to be able to intercept information and
eventually record it, track it, or generate statistics out of it,
which in turn gives information how to shorten workflows or which new
functions to make. Imagine many programming lines, without direct
`kill-new' function and much of killing activity. Inspection of what
was killed leads to improvements.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2022-10-22 11:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 14:16 Copying a list for insertion Heime via Users list for the GNU Emacs text editor
2022-10-21 14:35 ` Manuel Giraud
2022-10-21 15:03   ` Heime
2022-10-21 15:46 ` Teemu Likonen
2022-10-21 15:57 ` Jean Louis
2022-10-21 16:12   ` Heime
2022-10-21 17:26     ` Heime
2022-10-21 17:32       ` Jean Louis
2022-10-21 19:26     ` Heime
2022-10-21 20:32       ` Jean Louis
2022-10-21 22:00       ` Heime
2022-10-22  0:28         ` Jean Louis
2022-10-22  0:48           ` Emanuel Berg
2022-10-22 11:23             ` Jean Louis
2022-10-24 20:58               ` Emanuel Berg
2022-10-22  1:02           ` Heime
2022-10-22  1:20             ` Emanuel Berg
2022-10-22  6:43             ` Jean Louis
2022-10-22  6:52               ` Heime
2022-10-22 10:09                 ` Jean Louis
2022-10-22  7:07               ` tomas
2022-10-22  1:04           ` Emanuel Berg
2022-10-22 11:34             ` Jean Louis [this message]
2022-10-24 20:57               ` 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=Y1PVTn1klBN6HyDo@protected.localdomain \
    --to=bugs@gnu.support \
    --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).