From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Brad Knotwell <bknotwell@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-note-abort
Date: Sat, 21 Apr 2018 15:23:57 +0200 [thread overview]
Message-ID: <87d0ysd76a.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <371527828.1457872.1523396932915@mail.yahoo.com> (Brad Knotwell's message of "Tue, 10 Apr 2018 21:48:52 +0000 (UTC)")
Hello,
Brad Knotwell <bknotwell@yahoo.com> writes:
> Good day all--
> Earlier, I had written about the unreliability of adding
> a table-line. Well, I ran into a similar problem with the
> (significantly simpler) entry capability. Unlike the table-line, this
> was an easier debug and I determined that org-note-abort was set to
> t which ensures capture will always fail.
> While I don't know exactly how I did it, I suspect it was something
> like the following:* edit a template, test it and find it isn't quite
> what you want* make an (incorrect) change that sets breaks on
> insertion, sets org-note-abort to t and you're stuck until you reset
> it to nil by hand (remarkably, I've had to do the same thing with
> inhibit-trace as well).
> Searching the mailing list and looking at Google hasn't been any more
> illuminating on this. It's important to note that while
> org-capture-kill sets org-note-abort to t, it's reset correctly when
> used in the normal way.
> Version: 9.1.7
> Thx and I'm guessing something similar happened with the table-line
> issue.
I pushed a fix in maint. Could you test it and report if it solves your
issue ?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-04-21 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <371527828.1457872.1523396932915.ref@mail.yahoo.com>
2018-04-10 21:48 ` org-note-abort Brad Knotwell
2018-04-21 13:23 ` Nicolas Goaziou [this message]
2018-04-22 16:12 ` org-note-abort Brad Knotwell
2018-04-29 22:54 ` org-note-abort Nicolas Goaziou
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=87d0ysd76a.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bknotwell@yahoo.com \
--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).