unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reinhard Tartler <siretart@tauware.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 1529@emacsbugs.donarmstrong.com, Romain Francoise <romain@orebokech.com>
Subject: bug#1529: [emacs-snapshot/master] Changelog entry for 20090411-1
Date: Tue, 14 Apr 2009 15:08:26 +0200	[thread overview]
Message-ID: <87r5zvv0vp.fsf@faui44a.informatik.uni-erlangen.de> (raw)
In-Reply-To: <nq1vrv2zvd.fsf@alcatel-lucent.de> (Michael Albinus's message of "Tue, 14 Apr 2009 14:17:42 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> Reinhard Tartler <siretart@tauware.de> writes:
>
>>> I can reliably reproduce it with the package 'emacs-goodies-el'
>>> installed. Tramp works fine with 'emacs-goodies-el' uninstalled.
>>>
>>> Perhaps that helps you to further track down the issue?
>>
>> It seems that color-theme.el is causing the issue. I'm attaching the
>> lisp file for your convenience. Can someone else confirm that
>> color-theme.el breaks tramp?
>
> Could you, please, tell me the steps how to reproduce? I cannot
> reproduce, doing
>
> ~/src/emacs/src/emacs -Q 
> C-x C-f ~/lisp/color-theme.el
> M-x eval-current-buffer
> [Tools] -> [Color Themes] -> [Classic]
> C-x C-f /ssh::

sorry, no. This way I cannot reproduce it either :(

However during my tests, I discovered the following:

when pressing C-x C-f /ssh:
                          ^
                          at that point, tramp gets loaded. I notice
                          that in the minibuffer by a flashing message.

In a "clean" environment (running emacs with -Q), this happens only the
first time I do that in my emacs session. in my "unclean" session (that
is with my customisations), this happens every time.

Any clue how to debug these automatic loadings?

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4






  reply	other threads:[~2009-04-14 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1LsheJ-0002FW-1P@alioth.debian.org>
     [not found] ` <87r5zwudbv.fsf@faui44a.informatik.uni-erlangen.de>
     [not found]   ` <87ljq49a42.fsf@elegiac.orebokech.com>
2009-04-13 16:37     ` bug#1529: [emacs-snapshot/master] Changelog entry for 20090411-1 Reinhard Tartler
     [not found]       ` <87tz4sscn3.fsf@faui44a.informatik.uni-erlangen.de>
2009-04-14 12:17         ` Michael Albinus
2009-04-14 13:08           ` Reinhard Tartler [this message]
2009-04-14 13:14             ` Michael Albinus
2009-04-14 15:27               ` Reinhard Tartler
2009-04-14 16:03                 ` Romain Francoise
     [not found]                   ` <87eivu70ec.fsf@faui44a.informatik.uni-erlangen.de>
2009-04-15  9:24                     ` Michael Albinus
2009-04-15 14:51                       ` Reinhard Tartler
2009-04-15 15:04                         ` 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=87r5zvv0vp.fsf@faui44a.informatik.uni-erlangen.de \
    --to=siretart@tauware.de \
    --cc=1529@emacsbugs.donarmstrong.com \
    --cc=michael.albinus@gmx.de \
    --cc=romain@orebokech.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).