From: Budi <budikusasi@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: How to clipboard copy emacs help text by user-made interactive function kill-ring-save
Date: Thu, 9 May 2019 11:22:33 +0700 [thread overview]
Message-ID: <CAH0GyZBWzD0J+qRtadN7bpBY6+5fVjtnPKS4KVE9HafzLKquQQ@mail.gmail.com> (raw)
I tried to clipboard copy some emacs read-only text by user-made
interactive function kill-ring-save, but fail
It's not M-w bound to kill-ring-save emacs built in function which is working
but as my preceding question, the copy :
(defun copy (b e)
(interactive "r")
(if (use-region-p) (call-interactively 'kill-ring-save)
(save-excursion
(beginning-of-line)
(set-mark (line-end-position))
(kill-ring-save (point)(mark))
))))
(global-set-key (kbd "C-c") 'copy)
cannot copy such case above,
any idea what's actually made different behavior of kill-ring-save ?
next reply other threads:[~2019-05-09 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 4:22 Budi [this message]
2019-05-09 5:36 ` How to clipboard copy emacs help text by user-made interactive function kill-ring-save Emanuel Berg
2019-05-09 23:34 ` Bruno Barbier
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=CAH0GyZBWzD0J+qRtadN7bpBY6+5fVjtnPKS4KVE9HafzLKquQQ@mail.gmail.com \
--to=budikusasi@gmail.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).