emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Tag completion does not work well with org-complete-tags-always-offer-all-agenda-tags
Date: Sat, 12 May 2018 08:32:50 +0200	[thread overview]
Message-ID: <23286.35474.902070.827880@frac.u-strasbg.fr> (raw)
In-Reply-To: <877eoewoha.fsf@gnu.org>

Bastien writes on Tue  8 May 2018 10:17:
 > Hi Alain,
 > 
 > 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?
 > 
 > I could not reproduce this problem from Org 9.1.12 and the master
 > branch.  Can you try with a bare emacs -Q and report against maint
 > or master branch?

Hello.  Sorry for the late feedback.  Since Nicolas' answer I have
been trying to get acquainted with getting Org from git. I made some
progress, but am not sure I am there yet.  So there is the initial
issue and there is the git issue, hence the probably
poorly-ordered/poorly-thought points which follow.

* Since 9.1.13 appeared, I have updated to it:

(Fedora 23) 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 (9.1.13-elpa @
/home/cochard/.emacs.d/elpa/org-20180507/)

and the problem remains.

* I have been able to test on another machine:

(Fedora 26) Emacs : GNU Emacs 25.3.1 (x86_64-redhat-linux-gnu, GTK+
Version 3.22.19) of 2017-09-12 Package: Org mode version 9.1.13
(9.1.13-elpa @ /root/.emacs.d/elpa/org-20180507/)

and the problem is /not/ there.

* In all cases above I used command 'emacs' with a void .emacs,
setting variables org-agenda-files and
org-complete-tags-always-offer-all-agenda-tags using 'M-x
eval-expression'.

* You ask "Can you try with a bare emacs -Q and report against maint
or master branch?"

Sorry, your question is not explicit enough for me (one or two
questions?).  For sure, with emacs -Q, it gives:

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 8.2.10 (release_8.2.10 @
/usr/share/emacs/24.5/lisp/org/)

and the problem is there.

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

* I have learned about master and maint at

https://orgmode.org/worg/dev/index.html

* I have tried to install a git repository.  For this I have tried to
follow

https://orgmode.org/worg/org-tutorials/org4beginners.html

section "Running the latest version of Org mode"

It might be for beginners, but it was not easy for me, so I am not
sure I did it right.  [In particular I had to hide my .emacs.d
directory, and was not sure about (require 'org-install) vs (require
'org) vs no require at all, in the .emacs file.]

I got:

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?

With this setup, the problem remains.

* About getting git:

In addition to section "Running the latest version of Org mode" at
https://orgmode.org/worg/org-tutorials/org4beginners.html, I also read
https://orgmode.org/worg/org-faq.html#keeping-current-with-Org-mode-development,
as well as section "1.2 Installation" of the manual (v9.1.13),
subsection "Using Org's git repository".

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


-- 
EOST (École et Observatoire des Sciences de la Terre) 
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 106] | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France    | Fax:   +33 (0)3 68 85 01 25     

  reply	other threads:[~2018-05-12  6:33 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 [this message]
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=23286.35474.902070.827880@frac.u-strasbg.fr \
    --to=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).