From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Usability for tags in master branch [9.1.12 (release_9.1.12-646-gb08245 @ c:/D-Drive/bin/org-mode/lisp/)]
Date: Sat, 28 Apr 2018 02:25:01 +0200 [thread overview]
Message-ID: <87604ctbxe.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87muxoiwbv.fsf@norang.ca> (Bernt Hansen's message of "Fri, 27 Apr 2018 09:59:48 -0400")
Hello,
Bernt Hansen <bernt@norang.ca> writes:
> With the below org file tags handling behaves in a surprising way.
>
>
> * TODO Test Parent :PRODUCTION:MISC:
> ** TODO foo :BAR:
> ** keys to reproduce
>
>
> 1) At beginning of line 2 on TODO foo
> 2) M-ret to insert a new heading before foo
> 3) S-ret to get TODO keyword
> - auto fills :PRODUCTION:MISC: tags ?
> 4) SPC now does not work to insert a space after the TODO so I can type my headline
> I have to use C-f
> 5) C-c C-q on this line now removes both tags
> I thought this was a bug but it seems to be removing tags that are defined
> by the parent tasks and maybe that is intentional
> 6) When I enter a parent tag C-c C-q MISC RET it is displayed and then removed if I do another C-c C-q
> This was surprising to me and I thought tag handling was completely broken
> Until I tried a tag not in a parent task
> try C-c C-q TAB MISC RET
> C-c C-q TAB PRODUCTION RET
I think this is now fixed. Could you confirm it?
Thank you!
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-04-28 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 13:59 Bug: Usability for tags in master branch [9.1.12 (release_9.1.12-646-gb08245 @ c:/D-Drive/bin/org-mode/lisp/)] Bernt Hansen
2018-04-27 17:06 ` Bastien
2018-04-27 17:22 ` Bernt Hansen
2018-04-28 6:20 ` Bastien
2018-04-28 0:25 ` Nicolas Goaziou [this message]
2018-04-28 13:10 ` Bastien
2018-04-28 22:54 ` Nicolas Goaziou
2018-04-29 8:26 ` Bernt Hansen
2018-04-29 8:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87604ctbxe.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.