From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-orgmode@gnu.org
Subject: Emacs bug 37890; killing capture buffer
Date: Fri, 13 Dec 2019 22:48:12 +0100 [thread overview]
Message-ID: <87r217lwwz.fsf@web.de> (raw)
Hi,
I want to speak about my Emacs bug report 37890 about org-capture.
Seems my main point:
| I want to capture an APPT with `org-capture'. I the pop-up buffer to
| edit the item I move the date to the second line and add text after the
| date (personal preference). That loses the final newline in
| CAPTURE-todo.org. As a result, the headline of the item following the
| item to be inserted gets appended to the last line of the text:
|
| ** APPT Abc
| <2019-10-23 Mi>
| text... ** APPT 8:30 Important Appointment
|
| breaking the whole item. The user should somehow be prevented from that
| happening.
has been resolved with the latest merge into Emacs master - is that
correct? Then I will close that report.
The report also included a feature request which I now want to tell
here: I often kill the capture buffer instead of hitting C-c C-k. Just
by habit. It's wrong and I now it but I guess it happens to others.
I guess the capture buffer is just a narrowed indirect buffer copy of
the buffer visiting the according org file. Because of this, when you
kill the capture buffer, the original buffer reflects the partial and
uncomplete entry one tried to add. This may damage your file. But such
internals are not known to all, so it would be good if killing the
capture buffer, or even just closing the window, would warn the user and
offer to undo the partial changes. Or (really better IMHO) consider a
different implementation where the original buffer is not modified until
the user explicitly confirms the stuff to capture with C-c C-c.
TIA,
Michael.
next reply other threads:[~2019-12-13 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 21:48 Michael Heerdegen [this message]
2019-12-14 5:05 ` Emacs bug 37890; killing capture buffer Adam Porter
2019-12-15 22:31 ` Michael Heerdegen
2019-12-16 23:00 ` Michael Heerdegen
2019-12-17 17:40 ` Adam Porter
2019-12-17 18:24 ` Michael Heerdegen
2019-12-17 18:53 ` Adam Porter
2019-12-20 0:10 ` Michael Heerdegen
2019-12-18 1:20 ` Kyle Meyer
2019-12-18 2:16 ` Ihor Radchenko
2019-12-20 0:40 ` Michael Heerdegen
2019-12-18 0:07 ` Samuel Wales
2019-12-18 6:17 ` Fraga, Eric
2019-12-20 0:17 ` Michael Heerdegen
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=87r217lwwz.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-orgmode@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.
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).