From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Custom function for killing the thing at point
Date: Fri, 13 Aug 2021 22:46:00 +0000 [thread overview]
Message-ID: <877dgp6k0n.fsf@posteo.net> (raw)
In-Reply-To: <87im095682.fsf@gmail.com> (Rodrigo Morales's message of "Fri, 13 Aug 2021 17:29:17 -0500")
Hi Rodrigo,
Thanks for sharing, it seems interesting and useful. But I think this
function is missing in your post: `my/kill-new'.
Best regards,
Juan Manuel
Rodrigo Morales writes:
> I just created this function for copying the thing under the cursor (it
> works for some #+BEGIN blocks and links). I think it would be useful for
> others, so I'm creating this post for getting feedback on the Elisp code
> and sharing it to those interested.
>
> #+BEGIN_SRC elisp
> (defun my/org-kill-thing-at-point ()
> "Kill the thing at point.
>
> The following things are currently supported
>
> - #+BEGIN_SRC <<any>>
> - #+BEGIN_EXPORT <<any>>
> - #+BEGIN_EXAMPLE <<any>>
> - #+BEGIN_COMMENT
> - Org links (the description is not copied)"
> (interactive)
> (let* (content
> (element (org-element-context))
> (type (org-element-type element)))
> (cond ((or (eq type 'src-block)
> (eq type 'export-block)
> (eq type 'example-block)
> (eq type 'comment-block))
> (setq content (plist-get (cadr element) :value)))
> ((eq type 'link)
> (setq content (plist-get (cadr element) :raw-link)))
> (t
> (error "The element at point couldn't be copied.")))
> (my/kill-new content)))
> #+END_SRC
>
> #+BEGIN_SRC elisp
> (define-key org-mode-map (kbd "C-c c") 'my/org-kill-thing-at-point)
> #+END_SRC
>
next prev parent reply other threads:[~2021-08-13 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 22:29 Custom function for killing the thing at point Rodrigo Morales
2021-08-13 22:46 ` Juan Manuel Macías [this message]
2021-08-14 1:45 ` Ihor Radchenko
2021-08-14 12:33 ` John Kitchin
2021-08-14 14:09 ` Ihor Radchenko
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=877dgp6k0n.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=moralesrodrigo1100@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.