unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: 24980@debbugs.gnu.org
Cc: Dave Abrahams <dave@boostpro.com>
Subject: bug#24980: Fwd: tramp (2.2.13.25.1); ido virtual buffer interaction
Date: Mon, 21 Nov 2016 19:47:36 +0100	[thread overview]
Message-ID: <87a8cs4qlz.fsf@gmx.de> (raw)
In-Reply-To: <87mvgs4r2d.fsf@gmx.de>


[-- Attachment #0: Type: message/rfc822, Size: 1449 bytes --]

From: Michael Albinus <michael.albinus@gmx.de>
To: Dave Abrahams <dave@boostpro.com>
Cc: tramp-devel@gnu.org
Subject: Re: tramp (2.2.13.25.1); ido virtual buffer interaction
Date: Mon, 21 Nov 2016 19:34:04 +0100
Message-ID: <87vavg4r8j.fsf@gmx.de>

Dave Abrahams <dave@boostpro.com> writes:

Hi Dave,

> Voilà:

Thanks. And here is the story:

>   expand-file-name("/wingy:tmp" nil)
>   apply(expand-file-name ("/wingy:tmp" nil))
>   tramp-completion-run-real-handler(expand-file-name ("/wingy:tmp" nil))
>   tramp-completion-file-name-handler(expand-file-name "/wingy:tmp" nil)
>   get-file-buffer("/wingy:tmp")
>   ido-add-virtual-buffers-to-list()

ido-add-virtual-buffers-to-list calls get-file-buffer. This calls
expand-file-name, and Tramp becomes active. "/wingy:tmp" seems to be the
file name related to the (still existing) buffer with the dead connection.

There is no obvious solution, I will forward your report as Emacs bug,
therefore.

Best regards, Michael.





  parent reply	other threads:[~2016-11-21 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 18:37 bug#24980: Fwd: tramp (2.2.13.25.1); ido virtual buffer interaction Michael Albinus
2016-11-21 18:46 ` Michael Albinus
2016-11-21 18:47 ` Michael Albinus [this message]
2016-11-21 21:33   ` Dave Abrahams
2016-11-24 11:03     ` bug#24980: " Michael Albinus
2016-12-05 15:13       ` Michael Albinus
2016-12-19  1:59         ` Dave Abrahams
2016-12-19  2:10           ` Dave Abrahams
2016-12-19  8:36             ` Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8cs4qlz.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=24980@debbugs.gnu.org \
    --cc=dave@boostpro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).