From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vivek Dasmohapatra Newsgroups: gmane.emacs.bugs Subject: bug#15362: 24.1; pcomplete unnecessarily restricts tab-completion entry points Date: Fri, 13 Sep 2013 14:50:08 +0100 (BST) Message-ID: References: <8761u5v541.fsf@noise.cbg.collabora.co.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: ger.gmane.org 1379080278 25514 80.91.229.3 (13 Sep 2013 13:51:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Sep 2013 13:51:18 +0000 (UTC) Cc: 15362@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Sep 13 15:51:20 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VKTmH-0001Ws-Dz for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Sep 2013 15:51:17 +0200 Original-Received: from localhost ([::1]:47116 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKTmH-000142-3k for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Sep 2013 09:51:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40603) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKTm8-00012M-Ky for bug-gnu-emacs@gnu.org; Fri, 13 Sep 2013 09:51:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VKTm2-0004RJ-Lr for bug-gnu-emacs@gnu.org; Fri, 13 Sep 2013 09:51:08 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:53085) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKTm2-0004RC-Iu for bug-gnu-emacs@gnu.org; Fri, 13 Sep 2013 09:51:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VKTm1-0008Ed-Vv for bug-gnu-emacs@gnu.org; Fri, 13 Sep 2013 09:51:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Vivek Dasmohapatra Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 13 Sep 2013 13:51:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15362 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15362-submit@debbugs.gnu.org id=B15362.137908021531599 (code B ref 15362); Fri, 13 Sep 2013 13:51:01 +0000 Original-Received: (at 15362) by debbugs.gnu.org; 13 Sep 2013 13:50:15 +0000 Original-Received: from localhost ([127.0.0.1]:33144 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VKTlG-0008Da-Oq for submit@debbugs.gnu.org; Fri, 13 Sep 2013 09:50:14 -0400 Original-Received: from flounder.pepperfish.net ([89.238.129.35]:43701 ident=w93mOK93uvL) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VKTlE-0008DM-6n for 15362@debbugs.gnu.org; Fri, 13 Sep 2013 09:50:13 -0400 Original-Received: from localhost ([127.0.0.1]) by flounder.pepperfish.net with esmtps (Exim 4.71 #1 (Debian)) id 1VKTlB-0005v6-EA; Fri, 13 Sep 2013 14:50:09 +0100 X-X-Sender: vivek@octopus.pepperfish.net In-Reply-To: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:78345 Archived-At: On Fri, 13 Sep 2013, Stefan Monnier wrote: >> customise the erc group, make sure erc-pcomplete is on (it >> should be) > > Ah, that's the trick. Any reason why you do that? The default should > already give you almost the same behavior. It seems to always pop a buffer rather than cycling. Haven't figured out why yet. > Also does the patch below fix your problem? Not tested yet, but it looks like it should work, yes. Will confirm shortly.