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: Sun, 13 May 2018 23:01:38 +0200	[thread overview]
Message-ID: <87wow7tglp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23286.35474.902070.827880@frac.u-strasbg.fr> (Alain Cochard's message of "Sat, 12 May 2018 08:32:50 +0200")

Hello,

Alain.Cochard@unistra.fr writes:

> Did you mean 'emacs -Q' with some git branch?  If so, I don't know how
> to do it...

Yes. It means "emacs -Q" and a recent Org loaded. See below.

> Emacs : GNU Emacs 24.5.1 (x86_64-redhat-linux-gnu, GTK+ Version
> 3.18.9) of 2016-04-11 on buildvm-25.phx2.fedoraproject.org Package:
> Org mode version 9.1.13 (release_9.1.13-744-g13fb6a @
> /home/cochard/Org/Coch-git/org-mode/lisp/)
>
> Is that the master branch?

It looks like so.

> With this setup, the problem remains.

Here is what I did.

I created a file "mini-init.el", containing the following lines:

--8<---------------cut here---------------start------------->8---
(add-to-list 'load-path "/path/to/org-mode/lisp/")
(setq org-complete-tags-always-offer-all-agenda-tags t)
(setq org-agenda-files '("/tmp/bug-agenda.org"))
(find-file "/tmp/bug-agenda2.org")
--8<---------------cut here---------------end--------------->8---

The file "/tmp/bug-agenda.org" contains the following:

--8<---------------cut here---------------start------------->8---
* Foo :bar:
--8<---------------cut here---------------end--------------->8---

The file "/tmp/bug-agenda2.org" is an empty file.

I then run:

    emacs -Q -l mini-init.el

When in the empty document ("bug-agenda2.org"), I type "* H", then C-c
C-q then <TAB>, I get "bar" in the minibuffer and no colon is inserted.

So, I cannot reproduce your issue.

> Are those 3 sources are supposed to provide essentially the same
> pieces of information?  If so maybe they could be
> merged/updated/coordinated?

The sole official documentation is the manual. Worg is edited by users.
Of course, it would be nice if they could be coordinated, but we need
volunteers for that.

Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2018-05-13 22:24 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 [this message]
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=87wow7tglp.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).