emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Scheduling capture with a single line capture template [9.2.4 (9.2.4-10-g3b006f-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20190715/)]
Date: Tue, 04 Feb 2020 08:28:39 -0300	[thread overview]
Message-ID: <87imkmsiag.fsf@gmail.com> (raw)
In-Reply-To: <87v9om22tf.fsf@gnu.org>

Hi Bastien,

thanks for looking into this.

On Tue, Feb 04 2020, Bastien wrote:

> I cannot reproduce this issue with latest stable Org and emacs -q.
>
> Can you check and report if this still needs a fix?

Yes, I can still reproduce this as described in the original report with 
current version (Org mode version 9.3.2 (9.3.2-24-g5c72d6-elpaplus @ 
/home/gustavo/.emacs.d/elpa/org-plus-contrib-20200203/)).

As the recipe for the ECM starts with "emacs -Q", I don't know what else 
I could isolate in my environment.

One possibility I can think of. It's been some time since I reported, 
but if I recall correctly, the existence of a headline *after* the one 
in which the capture is being placed was critical to the 
effect. Rereading the report, it is there in the ECM, but I haven't 
emphasized this in the analysis. Did you try the recipe with that file 
structure?

But anyway, if you have any other ideas, I'm at your disposal to try 
things out and try to pin this further down.

Best,
Gustavo.

next prev parent reply	other threads:[~2020-02-04 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 19:36 Bug: Scheduling capture with a single line capture template [9.2.4 (9.2.4-10-g3b006f-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20190715/)] Gustavo Barros
2020-02-04  8:07 ` Bastien
2020-02-04 11:28   ` Gustavo Barros [this message]
2020-02-04 16:06     ` Bastien
2020-02-05 11:06       ` Gustavo Barros
2020-02-05 12:30         ` Bastien

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=87imkmsiag.fsf@gmail.com \
    --to=gusbrs.2016@gmail.com \
    --cc=bzg@gnu.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

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).