From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Julian Scheid Newsgroups: gmane.emacs.devel Subject: Re: python-try-complete Date: Sat, 12 Apr 2008 22:00:58 +1200 Message-ID: <4800885A.1090402@gmail.com> References: <47F62CE4.7070903@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1207994500 21077 80.91.229.12 (12 Apr 2008 10:01:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Apr 2008 10:01:40 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 12 12:02:13 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JkcYm-00061m-Q9 for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 12:02:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JkcY8-0003gz-Ss for ged-emacs-devel@m.gmane.org; Sat, 12 Apr 2008 06:01:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JkcY1-0003f0-4f for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:01:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JkcXy-0003d1-2H for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:01:23 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JkcXx-0003cr-RJ for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:01:21 -0400 Original-Received: from wa-out-1112.google.com ([209.85.146.180]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JkcXx-0003IC-Nj for emacs-devel@gnu.org; Sat, 12 Apr 2008 06:01:21 -0400 Original-Received: by wa-out-1112.google.com with SMTP id k34so814704wah.10 for ; Sat, 12 Apr 2008 03:01:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:from; bh=+a7TSstHS81bs1x/t2bn648f5fayLicW4sSKE3Dfjio=; b=YIvlj1hVDYVZRKYmcHm1Nsc5X7ElF3Frqy4+j/mVhbvCwiMccnkI0Oo+fcffjgbb70PhZYaMhQzSFviCA4F1YAxdLyu867yn/tnH3gksMVWT5Dd1ERHukNi1hHHPswh09XxtcGWgwx3UYWvR7MNCURNoKo0NvM4mUhSBLELQlMo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=WnQQV55bkltM28WwQ3xlqIaXbQsqLIYe6+wdvpB7E8biVw/NsYELftCZ4qyZkzMn3EgTIr7wlfqcEUkWk12W2poruFtmY7L2u0AX1PeH1KK/xlKRgvgRlt8Wm5s7cbyvsASJy6O3QU8lDamaFLDfJiptXylf1+YYCl9cNoSsVXk= Original-Received: by 10.141.163.12 with SMTP id q12mr2114409rvo.190.1207994477950; Sat, 12 Apr 2008 03:01:17 -0700 (PDT) Original-Received: from ?192.168.1.3? ( [210.86.66.147]) by mx.google.com with ESMTPS id l31sm6240011rvb.2.2008.04.12.03.01.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 12 Apr 2008 03:01:17 -0700 (PDT) User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) In-Reply-To: X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:95030 Archived-At: >> I take issue with one of its design decisions however: sneaking in >> python-try-complete into hippie-expand-try-functions-list. > > Agreed, it should be fixed on the EMACS_22_BASE branch now, Thanks for that, Stefan. Did you have any thoughts about the second problem I described in the same mail - python-try-complete locking up when used in a remote buffer? To quote from my previous mail, Either python-try-complete should refrain from launching the process remotely by looking at (file-remote-p default-directory), or the scripts it launches need to be prepared (e.g. in terms of quoting) for being run remotely via ssh. I am not using python-try-complete anymore but this is a bug and I would be happy to help fix it. Julian