From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "N. Raghavendra" <raghu@hri.res.in>
Cc: info-gnus-english@gnu.org
Subject: Re: Define "Group" of mail recipients in Gnus?
Date: Thu, 10 Nov 2016 13:49:25 +0100 [thread overview]
Message-ID: <m2d1i3a4a2.fsf@charm-wifi.irisa.fr> (raw)
In-Reply-To: <m2fumzk2uh.fsf@hri.res.in> (N. Raghavendra's message of "Thu, 10 Nov 2016 16:40:14 +0530")
[-- Attachment #1.1: Type: text/plain, Size: 1408 bytes --]
Hello,
On 2016-11-10 16:40, "N. Raghavendra" <raghu@hri.res.in> writes:
>> This might be an org 9 problem, then. I'll have to investigate further.
I found out it's not an org problem, but a completion problem. If I use
ivy or helm, I get the bug, but if I use the default completion, things
work. I've asked for help on the emacs-devel mailing list on how to fix
this:
https://lists.gnu.org/archive/html/emacs-devel/2016-11/msg00269.html
> If you aren't using helm, this is irrelevant to you, but just in case it
> is, I have the following also in my emacs configuration:
>
> ;; Don't use helm for org capture. It gives an error if there is a
> ;; PROMPT in the capture template. See
> ;; https://github.com/emacs-helm/helm/issues/1494
> (setcdr (assoc 'org-capture helm-completing-read-handlers-alist) nil)
>
> ;; Don't use helm in message mode. It leaves white space at the end
> ;; when I complete a name with org-contacts.
> (add-to-list 'helm-mode-no-completion-in-region-in-modes 'message-mode)
This is very interesting, thanks for sharing. Unfortunately I use ivy
and there does not seem to be any equivalent setting. But now I
understand why things work for you: you actually use the default
completion in message mode.
Thanks again,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2016-10: 401.57, 2015-10: 398.29
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2016-11-10 12:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 9:58 Rainer M Krug
2016-11-08 10:53 ` B.V. Raghav
2016-11-08 11:54 ` Rainer M Krug
2016-11-08 13:39 ` Dan Christensen
2016-11-08 17:11 ` Rainer M Krug
2016-11-08 21:58 ` Dan Christensen
2016-11-08 11:25 ` Rasmus
2016-11-08 11:54 ` N. Raghavendra
2016-11-09 12:28 ` B.V. Raghav
2016-11-09 12:42 ` Alan Schmitt
2016-11-09 13:39 ` N. Raghavendra
2016-11-10 8:09 ` Alan Schmitt
2016-11-10 8:19 ` N. Raghavendra
2016-11-10 8:21 ` Alan Schmitt
2016-11-10 11:10 ` N. Raghavendra
2016-11-10 12:49 ` Alan Schmitt [this message]
2016-11-08 11:41 ` Enrico Schumann
2016-11-08 13:34 ` Alan Schmitt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2d1i3a4a2.fsf@charm-wifi.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=info-gnus-english@gnu.org \
--cc=raghu@hri.res.in \
/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.
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 NNTP newsgroup(s).