emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Alex Ermolov <aaermolov@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Tags completion with Helm
Date: Tue, 14 Mar 2017 12:38:07 -0400	[thread overview]
Message-ID: <CAJ51EToyxRD=ZVvzrmU7Ztg174q8H+6o9XMx7VmkirP_DQYLXw@mail.gmail.com> (raw)
In-Reply-To: <87innb4yjc.fsf@laptoptop>

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

I can't reproduce that behavior on my end. I see different behavior though.
My helm window is titled crm-complete, and the buffer is called
*helm-mode-crm-complete*

This seems to be the helm core package I am using.

helm-core-20170112.917

John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Tue, Mar 14, 2017 at 12:24 PM, <aaermolov@gmail.com> wrote:

> Hi John,
>
> no, these do not seem to fix anything. :(
>
> Namely, the following is still happens:
>
> 1) I'm pressing C-c C-q then TAB to select freeform input
> 2) then there is "org-set-tags" above candidates list and buffer title
>    is "*helm-mode-org-set-tags*"
> 3) after any input candidates list looks like "[?]<helm query chars>"
>    (initial candidates disappeared)
>
> regards,
> Alex
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > have you tried these settings:
> >
> > (setq helm-mode-fuzzy-match t
> >       helm-completion-in-region-fuzzy-match t)
> >
> > According to https://github.com/emacs-helm/helm/wiki/Fuzzy-matching, the
> > make fuzzy matching work everywhere.
> >
> > It seems to work ok for me.
> >
> > aaermolov@gmail.com writes:
> >
> >> Hi,
> >>
> >> I've spotted a problem with completing Org tags with Helm. While Helm is
> >> not at least about [fuzzy] completion, when I try to input any
> >> completion subsequence, all candidates are gone and variants are
> >> shrinked to whatever will be typed.
> >>
> >> Is there any widely known mistake, that I've stepped into with this
> >> case? Can anyone point me to some comprehensible direction?
> >>
> >> regards,
> >> Alex
> >
> >
> > --
> > Professor John Kitchin
> > Doherty Hall A207F
> > Department of Chemical Engineering
> > Carnegie Mellon University
> > Pittsburgh, PA 15213
> > 412-268-7803
> > @johnkitchin
> > http://kitchingroup.cheme.cmu.edu
>

[-- Attachment #2: Type: text/html, Size: 3354 bytes --]

  reply	other threads:[~2017-03-14 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14  9:16 Tags completion with Helm aaermolov
2017-03-14 12:54 ` John Kitchin
2017-03-14 16:24   ` aaermolov
2017-03-14 16:38     ` John Kitchin [this message]
2017-03-14 17:12       ` aaermolov
2017-03-14 17:45         ` aaermolov

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='CAJ51EToyxRD=ZVvzrmU7Ztg174q8H+6o9XMx7VmkirP_DQYLXw@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=aaermolov@gmail.com \
    --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).