emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Derek Chen-Becker <derek@chen-becker.org>
Cc: Emacs-orgmode@gnu.org
Subject: Re: [BUG] Effort range format broken [9.5.5 (release_9.5.5 @ /usr/local/share/emacs/28.2/lisp/org/)]
Date: Fri, 03 Mar 2023 16:04:13 +0000	[thread overview]
Message-ID: <87o7p94y9u.fsf@localhost> (raw)
In-Reply-To: <CAMbmz5=nsVRPvRhXUQ_h-xKExtMxWwgboepJVXj-d_regFOh1g@mail.gmail.com>

Derek Chen-Becker <derek@chen-becker.org> writes:

> Here is the minimal org file to repro:
> ========================================
> #+COLUMNS: %ITEM(Task) %Effort(Estimate){est+}
> * Table
> #+BEGIN: columnview :id input
> #+END
> ...

With point at #+BEGIN, pressing C-c C-c works just fine for me.
Using Org 9.6.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  reply	other threads:[~2023-03-03 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 14:43 [BUG] Effort range format broken [9.5.5 (release_9.5.5 @ /usr/local/share/emacs/28.2/lisp/org/)] Derek Chen-Becker
2023-03-03 16:04 ` Ihor Radchenko [this message]
2023-03-03 20:03   ` Derek Chen-Becker

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=87o7p94y9u.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=Emacs-orgmode@gnu.org \
    --cc=derek@chen-becker.org \


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