From: Allen Li <darkfeline@felesatra.moe>
To: Allen Li <darkfeline@felesatra.moe>,
Bernt Hansen <bernt@norang.ca>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Bug: Special property ITEM without stars [9.1.14]
Date: Wed, 19 Dec 2018 11:30:20 -0800 [thread overview]
Message-ID: <CADbSrJy34qLRHS0m-e0=HuSV3YuZxSH5fP9-Px3+rmHPH9oR9g@mail.gmail.com> (raw)
In-Reply-To: <87k1k5zjwu.fsf@nicolasgoaziou.fr>
On Wed, Dec 19, 2018 at 6:11 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Allen Li <darkfeline@felesatra.moe> writes:
>
> > Okay, thanks. I guess we can see how this works out with respect to users
> > like Brent using org-tags-match-list-sublevels or otherwise using
> > hierarchy.
>
> On second thought, this may not be a good idea, especially on master
> branch, which is close from being released.
>
> As suggested before, you ought to use
> `org-columns-modify-value-for-display-function' instead. This is
> probably the cleanest way to solve the current issue.
I have worked around this locally, but I hope we can revisit this later since
it makes Org mode's user interface better.
Does it make sense for Org mode to keep a separate release branch so
new features can be worked on while a release is prepared (like how I
think Emacs does it)?
>
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2018-12-19 19:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 22:19 Bug: Special property ITEM without stars [9.1.14] Allen Li
2018-12-03 22:57 ` Nicolas Goaziou
2018-12-04 10:14 ` Allen Li
2018-12-04 10:19 ` Allen Li
2018-12-06 14:35 ` Nicolas Goaziou
2018-12-07 5:26 ` Allen Li
2018-12-12 16:43 ` Nicolas Goaziou
2018-12-12 22:50 ` Allen Li
2018-12-13 14:28 ` Bernt Hansen
2018-12-14 0:52 ` Allen Li
2018-12-14 13:11 ` Nicolas Goaziou
2018-12-14 14:36 ` Bernt Hansen
2018-12-14 20:58 ` Allen Li
2018-12-18 11:18 ` Nicolas Goaziou
2018-12-19 3:12 ` Allen Li
2018-12-19 14:10 ` Nicolas Goaziou
2018-12-19 19:30 ` Allen Li [this message]
2018-12-19 20:36 ` Nicolas Goaziou
2018-12-04 10:19 ` 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='CADbSrJy34qLRHS0m-e0=HuSV3YuZxSH5fP9-Px3+rmHPH9oR9g@mail.gmail.com' \
--to=darkfeline@felesatra.moe \
--cc=bernt@norang.ca \
--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).