emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gustavo.barros@ufjf.edu.br>
To: "Michaël Cadilhac" <michael@cadilhac.name>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Scheduling in a narrowed subtree: Bug?
Date: Mon, 09 Sep 2019 19:13:04 -0300	[thread overview]
Message-ID: <87ftl5rudr.fsf@ufjf.edu.br> (raw)
In-Reply-To: <CADt3fpN2pLynn+ZpWgJ7ZUjafcyZ1_QmecPvw3VweC_iVXzthg@mail.gmail.com> (=?utf-8?Q?=22Micha=C3=ABl?= Cadilhac"'s message of "Mon, 9 Sep 2019 15:17:06 -0500")

On Mon, Sep 09 2019, Michaël Cadilhac wrote:

> Is this the expected behavior?
> 1. Create an empty org file
> 2. Insert
> * Test
> * Test 2
> 3. With the cursor at Test, hit C-x n s to narrow the view to the Test subtree
> 4. Hit C-c C-s to schedule the line at any date.
> As a result, the SCHEDULED keyword is _not_ included in the narrow view, and inserting things after the Test heading
> moves the SCHEDULED keyword away from its second-line position.

This is likely related to


  reply	other threads:[~2019-09-09 22:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 20:17 Scheduling in a narrowed subtree: Bug? Michaël Cadilhac
2019-09-09 22:13 ` Gustavo Barros [this message]
2019-09-10  7:53 ` Fraga, Eric
2019-09-10 21:10 ` Gustavo Barros
2020-05-06  0:44 ` 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:

  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=87ftl5rudr.fsf@ufjf.edu.br \
    --to=gustavo.barros@ufjf.edu.br \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael@cadilhac.name \


* 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


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