From: Bastien <bzg@gnu.org>
To: "Christoffer Stjernlöf" <a@xkqr.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-drill-entry-empty-p should use outline-forward-same-level and not outline-next-heading [9.1.6 (9.1.6-48-gfe7619-elpaplus @ /Users/christoffer/.emacs.d/elpa/org-plus-contrib-20180212/)]
Date: Mon, 03 Feb 2020 21:55:32 +0100 [thread overview]
Message-ID: <87wo93l7az.fsf@gnu.org> (raw)
In-Reply-To: <m2y30ub8ct.fsf@xkqr.org> ("Christoffer Stjernlöf"'s message of "Fri, 19 Jul 2019 12:56:50 +0200")
Hi,
a@xkqr.org (Christoffer Stjernlöf) writes:
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> https://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org mailing list.
> ------------------------------------------------------------------------
>
> I have noticed that some of my drill entries are skipped by org-drill,
> and only
> recently took the time to try to troubleshoot why – apparently
> org-drill-entry-empty-p returns t for my entries, because they look like
> the
> following:
org-drill is not in Org's repository anymore, you can try to contact
Paul Sexton from this repository:
https://bitbucket.org/eeeickythump/org-drill/src/default/
Best,
--
Bastien
prev parent reply other threads:[~2020-02-03 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 10:56 Bug: org-drill-entry-empty-p should use outline-forward-same-level and not outline-next-heading [9.1.6 (9.1.6-48-gfe7619-elpaplus @ /Users/christoffer/.emacs.d/elpa/org-plus-contrib-20180212/)] Christoffer Stjernlöf
[not found] ` <WM!6459e2a8e0f34a4538738dadf66f2587cc46f8eb3ba97abfa40c92bbc5a1c3edc0be21c82dc04dbc95c8871ec704862a!@mailhub-mx3.ncl.ac.uk>
[not found] ` <87h87eb4tt.fsf@newcastle.ac.uk>
2019-07-22 13:02 ` Phillip Lord
2020-02-03 20:56 ` Bastien
2020-02-03 20:55 ` Bastien [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=87wo93l7az.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=a@xkqr.org \
--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).