From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: Tag completion does not work well with org-complete-tags-always-offer-all-agenda-tags
Date: Fri, 04 May 2018 23:44:29 +0200 [thread overview]
Message-ID: <87fu37f64i.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23273.40957.997582.135225@frac.u-strasbg.fr> (Alain Cochard's message of "Wed, 2 May 2018 13:24:45 +0200")
Hello,
Alain.Cochard@unistra.fr writes:
> With variable org-complete-tags-always-offer-all-agenda-tags set to
> true, tag completion does not work as I expect. Specifically, upon
> 'C-c C-q' or 'C-c C-c', it works fine if I enter in the minibuffer
> some letter and then press <TAB>, but not if I just press <TAB>; in
> that case, a colon (:) is inserted in the minibuffer, and another
> colon for each subsequent <TAB>, ad infinitum. Is this normal?
Could you try again with master branch? Some changes related to tags
happened there recently.
> Incidentally, shouldn't this variable be documented in the manual?
> (Section "6.2 Setting tags" would seem a natural place for that.) I
> had to resort to internet search...
I don't know specifically about this one, but not all variables can be
documented in the manual, there are too many of them. An alternate way
to find about a variable is to explore Org variables with
M-x customize-group <RET> org
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-05-04 21:44 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 [this message]
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
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=87fu37f64i.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Alain.Cochard@unistra.fr \
--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).