From: Mike McLean <mike.mclean@pobox.com>
To: Bastien <bzg@gnu.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Mike McLean <mike.mclean@pobox.com>
Subject: Re: Bug: Tag Completion Not Prompting for all tags
Date: Tue, 10 Apr 2012 14:40:26 -0400 [thread overview]
Message-ID: <CANid5Q44=_fjdj0SoiAC2VEAmN-pmjWRn-HKe=Mf=AN50aPCHw@mail.gmail.com> (raw)
In-Reply-To: <87iph7iltn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Interesting
The very first report I submitted (
http://comments.gmane.org/gmane.emacs.orgmode/53824 ) showed the historic
behavior correct (the two tags defined in org-tag-alist show up in the fast
tag completion window). The "bug" was after shifting to free tag selection
mode, the tags defined in org-tag-alist are not available for completion.
The behavior that Matt Lundin reported was/is a side effect of the fix
(implementation). I think that the idea of the fix is valid, e.g. the free
tag entry should autocomplete tags defined in org-tag-alist to match the
behavior of the fast tag completion window.
On Tuesday, April 10, 2012, Bastien wrote:
> Hi Mike,
>
> I just reverted the commits I pushed for fixing this "issue".
>
> Mike McLean <mike.mclean@pobox.com <javascript:;>> writes:
>
> > The expected result is a completion list of tag_a and tag_b, this
> > does not work and the Minibuffer prompts [No match]
>
> I cannot do any better than to quote Matt Lundin on this:
>
> "Historically, only tags explicitly defined in org-tag-alist or via an
> in-buffer heading show up in the fast tag completion window."
>
> So, let's stick to the current behavior.
>
> Thanks for your patience!
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1719 bytes --]
next prev parent reply other threads:[~2012-04-10 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 15:50 Bug: Tag Completion Not Prompting for all tags Mike McLean
2012-03-24 16:03 ` Bastien
2012-03-24 16:43 ` Mike McLean
2012-03-27 10:31 ` Bastien
2012-03-30 0:43 ` Mike McLean
2012-03-31 9:17 ` Bastien
2012-04-02 15:26 ` Mike McLean
2012-04-02 15:27 ` Mike McLean
2012-04-02 15:45 ` Bastien
2012-04-02 15:50 ` Bastien
2012-04-02 19:19 ` Mike McLean
2012-04-02 19:19 ` Mike McLean
2012-04-04 1:00 ` Mike McLean
2012-04-04 17:38 ` Mike McLean
2012-04-06 4:38 ` Matt Lundin
2012-04-10 18:48 ` Mike McLean
2012-04-10 16:38 ` Bastien
2012-04-10 18:40 ` Mike McLean [this message]
2012-04-11 8:08 ` Bastien
2012-04-11 11:57 ` Mike McLean
2012-04-11 12:11 ` Mike McLean
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='CANid5Q44=_fjdj0SoiAC2VEAmN-pmjWRn-HKe=Mf=AN50aPCHw@mail.gmail.com' \
--to=mike.mclean@pobox.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
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).