From: Kaushal Modi <kaushal.modi@gmail.com>
To: Allen Li <vianchielfaura@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-capture-kill uses the kill ring
Date: Fri, 20 Oct 2017 03:56:51 +0000 [thread overview]
Message-ID: <CAFyQvY1GqymFs3CMs1WTBib52iKYyWo037Xm7JzcHNv+RPyRew@mail.gmail.com> (raw)
In-Reply-To: <CAJr1M6dnjKcAtHZ7+hj-4r0FDcBX6_M7Mu22-Eb8xjGSyqNP4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Thu, Oct 19, 2017 at 11:28 PM Allen Li <vianchielfaura@gmail.com> wrote:
> org-capture-kill (C-c C-k) used to abort capturing puts the contents
> of the capture buffer into the kill ring.
>
> This is obstructive when the user wants to abort a capture, but save a
> portion of the text into the kill ring to yank elsewhere. The aborted
> capture contents will replace the desired content.
>
I believe that's a good fail-safe mechanism. Imagine the joy when you
realize that Org simply saved your incomplete capture in the event you kill
it by mistake!
FWIW, I have never needed to make use of that failsafe mechanism, nor have
I ever needed to copy something from my capture and then kill it. The use
case you mention seems to be very rare IMO.
> Aborting capture should act transparently like killing a buffer. It
> shouldn't affect the kill ring. If the user wants to keep the capture
> contents, he can trivially run C-x h mark-whole-buffer M-w
> kill-ring-save
>
You can always C-y M-y to yank your second-last kill, C-y M-y M-y for the
third-last kill, and so on ..
To summarize:
- Current behavior helps users lose their incomplete captures by mistake.
- In the event you want to copy something and deliberately kill the capture
buffer, you can always paste it with C-y M-y.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1938 bytes --]
prev parent reply other threads:[~2017-10-20 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 3:27 org-capture-kill uses the kill ring Allen Li
2017-10-20 3:56 ` Kaushal Modi [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY1GqymFs3CMs1WTBib52iKYyWo037Xm7JzcHNv+RPyRew@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=vianchielfaura@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).