[debbugs-tracker] bug#140: closed (python-try-complete)

[GNU bug Tracking System]

Your message dated Sun, 25 Nov 2012 13:45:18 +0800
with message-id <address@hidden>
and subject line Re: bug#140: python-try-complete
has caused the debbugs.gnu.org bug report #140,
regarding python-try-complete
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
140: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=140
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: python-try-complete
>
>
>
>
> Date: 
>
> Sat, 12 Apr 2008 22:00:58 +1200
>
>
>
>
> User-agent: 
>
> Thunderbird 2.0.0.12 (Macintosh/20080213)
>
>
>
>
> > > 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
>
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#140: python-try-complete
>
>
>
>
> Date: 
>
> Sun, 25 Nov 2012 13:45:18 +0800
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.2.90 (gnu/linux)
>
>
>
>
> Julian Scheid <address@hidden> writes:
>
> > 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 think Michael Albinus finally fixed this in June (r108500).  Closing.
>
>
> --- End Message ---