emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Tag completion does not work well with org-complete-tags-always-offer-all-agenda-tags
Date: Mon, 14 May 2018 16:43:14 +0200	[thread overview]
Message-ID: <87po1yxpq5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23289.39754.230850.819664@frac.u-strasbg.fr> (Alain Cochard's message of "Mon, 14 May 2018 16:20:58 +0200")

Hello,

Alain.Cochard@unistra.fr writes:

> Thank you for not giving up on me!  Turned out that the problem was
> due to a "::" in one of my tag lists in one of my agenda files...
>
> Specifically, doing as you did above, I don't have the problem, while
> I do get it if replacing ":bar:" by "::bar:" or ":foo::bar:" in
> "/tmp/bug-agenda.org".
>
> I should note, however, that org-lint does not complain about the "::"
> occurrence.

Could you describe exactly the context where that happened? I.e., what
is exactly "a "::" in one of my tag lists in one of my agenda
files...":

    * This :tag::tag2:

or that:

    #+TAGS: tag1 :: tag2


Regards,

-- 
Nicolas Goaziou                                                0x80A93738

  reply	other threads:[~2018-05-14 14:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 11:24 Tag completion does not work well with org-complete-tags-always-offer-all-agenda-tags Alain.Cochard
2018-05-04 21:44 ` Nicolas Goaziou
2018-05-08  8:17 ` Bastien
2018-05-12  6:32   ` Alain.Cochard
2018-05-12  8:20     ` Gregor Zattler
2018-05-12 14:20       ` Alain.Cochard
2018-05-13 21:01     ` Nicolas Goaziou
2018-05-14 14:20       ` Alain.Cochard
2018-05-14 14:43         ` Nicolas Goaziou [this message]
2018-05-14 14:52           ` Alain.Cochard
2018-05-14 15:42             ` 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=87po1yxpq5.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=Alain.Cochard@unistra.fr \
    --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).