From: Richard Copley <rcopley@gmail.com>
To: Michael Maurer <maurer.michael@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: custom function getting initialized randomly
Date: Mon, 27 Mar 2023 14:56:01 +0100 [thread overview]
Message-ID: <CAPM58ohQQbNgyPBRy1V6cqsAwqNaq0+LP=c9k1HumAfaoJbeqQ@mail.gmail.com> (raw)
In-Reply-To: <CAH-0+bAgArTk3xX=+xafQJ+kGgY5O2b4=nAJZGppEQg9gQh-Qw@mail.gmail.com>
On Mon, 27 Mar 2023 at 10:21, Michael Maurer <maurer.michael@gmail.com> wrote:
>
> Hello,
>
> I wrote the following function to copy the kill-ring to the scratch
> buffer, but it only gets initialized sometimes at the start of emacs,
> sometimes not. Why?
>
> (defun copy-to-scratch-on-kill
> ()
> "Copy every kill (delete or yank) to *scratch* buffer."
> (let
> ((cur-kill-string
> (current-kill 0 t)))
> (when
> (and
> (not
> (equal cur-kill-string ""))
> (not
> (equal cur-kill-string prev-kill-string))
> (get-buffer "*scratch*"))
> (with-current-buffer "*scratch*"
> (goto-char
> (point-max))
> (insert cur-kill-string "\n")
> (goto-char
> (point-max))))
> (setq prev-kill-string cur-kill-string)))
>
> (add-hook 'post-command-hook #'copy-to-scratch-on-kill)
>
If an error propagates from the hook function (most likely "Kill ring
is empty", signalled by `current-kill`) then Emacs removes the
function from the hook. See the docstring for variable
`post-command-hook`.
next prev parent reply other threads:[~2023-03-27 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 8:22 custom function getting initialized randomly Michael Maurer
2023-03-27 13:56 ` Richard Copley [this message]
2023-03-27 14:56 ` Michael Maurer
2023-03-27 15:06 ` Richard Copley
2023-03-27 15:20 ` tomas
2023-03-27 15:30 ` Michael Maurer
2023-03-27 15:52 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 8:29 Michael Maurer
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='CAPM58ohQQbNgyPBRy1V6cqsAwqNaq0+LP=c9k1HumAfaoJbeqQ@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=maurer.michael@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.