emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#9770: closed (24.0.50; eshell does not recursively


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#9770: closed (24.0.50; eshell does not recursively complete directories when using Tramp)
Date: Mon, 17 Oct 2011 18:13:02 +0000

Your message dated Mon, 17 Oct 2011 20:11:43 +0200
with message-id <address@hidden>
and subject line Re: bug#9770: 24.0.50; eshell does not recursively complete 
directories when using Tramp
has caused the debbugs.gnu.org bug report #9770,
regarding 24.0.50; eshell does not recursively complete directories when using 
Tramp
to be marked as done.

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


-- 
9770: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9770
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.0.50; eshell does not recursively complete directories when using Tramp Date: Sun, 16 Oct 2011 23:09:34 +0200
Recipe:

* emacs -Q

* M-x eshell

* cd /ssh:someserver:

* Type "cd somedir/" with 'somedir' being a directory with other
  directories in it, and hit TAB

* "No completions of somedir/" appears

Expected result: eshell should be able to complete the directory names
under 'somedir' even when using Tramp. Feel free to tag this under
'wishlist' if this cannot be easily done, but since Tramp seems to
support this (e.g. when using 'find-file'), I'm hoping that there's an
easy fix.

-David



--- End Message ---
--- Begin Message --- Subject: Re: bug#9770: 24.0.50; eshell does not recursively complete directories when using Tramp Date: Mon, 17 Oct 2011 20:11:43 +0200 User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux)
Glenn Morris writes:
> This sounds like a duplicate of
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9616
>
> Your subject says 24.0.50. Please try the latest Emacs, where this
> should be fixed.

Ugh. Yes, that's the same bug and yes, it's fixed. I'm sorry for not
checking better before posting.

-David


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]