From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.help Subject: Re: Diagnosing a curious minibuffer problem (proliferating, weird initial contents) Date: Wed, 21 Jan 2015 05:26:44 +0100 Message-ID: <878ugw21yz.fsf@web.de> References: <87r3uptmbj.fsf@bertrandrussell.Speedport_W_723V_1_36_000> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1421814437 28795 80.91.229.3 (21 Jan 2015 04:27:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2015 04:27:17 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 21 05:27:12 2015 Return-path: Envelope-to: geh-help-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 1YDmso-0004g0-Q1 for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Jan 2015 05:27:10 +0100 Original-Received: from localhost ([::1]:46486 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDmsn-0005Nr-Ul for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Jan 2015 23:27:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35445) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDmsd-0005Nl-Lh for help-gnu-emacs@gnu.org; Tue, 20 Jan 2015 23:27:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YDmsZ-0003Mf-Er for help-gnu-emacs@gnu.org; Tue, 20 Jan 2015 23:26:59 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:57506) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDmsZ-0003MU-7G for help-gnu-emacs@gnu.org; Tue, 20 Jan 2015 23:26:55 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YDmsX-0004cw-KZ for help-gnu-emacs@gnu.org; Wed, 21 Jan 2015 05:26:53 +0100 Original-Received: from ip-90-187-16-104.web.vodafone.de ([90.187.16.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Jan 2015 05:26:53 +0100 Original-Received: from michael_heerdegen by ip-90-187-16-104.web.vodafone.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Jan 2015 05:26:53 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 21 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip-90-187-16-104.web.vodafone.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:8PEaFsnBGxPTXaWRRKz07BaO/no= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:102185 Archived-At: florian@fsavigny.de (Florian v. Savigny) writes: > I have no idea how to get to the root of the problem. I cannot edebug > completing-read, in any case. (That is what I would try otherwise, > anyway.) I would try trace-function-background on completing-read and check with which args it is called when the problem appears. Especially check the INITIAL-INPUT arg. In any case, using the normal debugger (not edebug) is useful, e.g. debug-on-entry completing-read, check how it is called etc. Check elements of minibuffer-setup-hook whether there could be the culprit. Finally, the mysterious initial inputs must be stored somewhere. Try to find out with `apropos-value'. Michael.