Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: ding@gnus.org
Subject: Bug when using address completion from bbdb
Date: Sat, 28 Jul 2012 16:22:39 +0200	[thread overview]
Message-ID: <874nost174.fsf@free.fr> (raw)

The headers get all mixed up when I try to complete an adress. More
precisely :

* I type some characters in the From field
* I press TAB (bound to message-tab)
* bbdb proposes several completion
* I middle click on the one I want
* some (not all) part of the address is copied in the *Subject* header
* resulting in something like :

To: 
Subjecsomename@mit: 

notice that Subject is cut, and the complete adress should be
somename@mines.org

Has anyone else seen something like that ?

Also, is there a way to get TAB (message-tab) to focus on the newly
created bbdb frame, and to select the address with a key (RET for
example) without using the mouse ?

Thanks for your help,

Julien.




             reply	other threads:[~2012-07-28 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28 14:22 Julien Cubizolles [this message]
2012-07-28 23:45 ` Adam Sjøgren
2012-07-29 20:20   ` Julien Cubizolles

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=874nost174.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --cc=ding@gnus.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.
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).