unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
Cc: tramp-devel@mail.freesoftware.fsf.org, kai@emptydomain.de,
	emacs-devel@gnu.org
Subject: Re: New Tramp version fails with ssh.
Date: Sun, 30 May 2004 22:25:52 +0200	[thread overview]
Message-ID: <jey8n9zmpb.fsf@sykes.suse.de> (raw)
In-Reply-To: <200405301959.i4UJxe508464@raven.dms.auburn.edu> (Luc Teirlinck's message of "Sun, 30 May 2004 14:59:40 -0500 (CDT)")

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> Here is a backtrace:
>
> Debugger entered--Lisp error: (invalid-function (macro . #[(variable
> value &rest body) ".. byte-code... [variable body value if get (quote byte-obsolete-variable) quote progn let] 6 ("/usr/local/share/emacs/21.3.50/lisp/net/tramp.elc" . 226654)]))
>   tramp-let-maybe(47 47 nil "/bin/ls")

Here is a patch:

--- tramp.el.~1.44.~	2004-05-30 22:19:07.000000000 +0200
+++ tramp.el	2004-05-30 22:21:11.204987203 +0200
@@ -1885,6 +1885,16 @@ If VAR is nil, then we bind `v' to the s
 ;; To be activated for debugging containing this macro
 (def-edebug-spec with-parsed-tramp-file-name t)
 
+(defmacro tramp-let-maybe (variable value &rest body)
+  "Let-bind VARIABLE to VALUE in BODY, but only if VARIABLE is not obsolete.
+BODY is executed whether or not the variable is obsolete.
+The intent is to protect against `obsolete variable' warnings."
+  `(if (get 'byte-obsolete-variable ',variable)
+       (progn ,@body)
+     (let ((,variable ,value))
+       ,@body)))
+(put 'tramp-let-maybe 'lisp-indent-function 2)
+
 ;;; Config Manipulation Functions:
 
 (defun tramp-set-completion-function (method function-list)
@@ -6790,16 +6800,6 @@ exiting if process is running."
     (funcall (symbol-function 'process-kill-without-query)
 	     process flag)))
 
-(defmacro tramp-let-maybe (variable value &rest body)
-  "Let-bind VARIABLE to VALUE in BODY, but only if VARIABLE is not obsolete.
-BODY is executed whether or not the variable is obsolete.
-The intent is to protect against `obsolete variable' warnings."
-  `(if (get 'byte-obsolete-variable ',variable)
-       (progn ,@body)
-     (let ((,variable ,value))
-       ,@body)))
-(put 'tramp-let-maybe 'lisp-indent-function 2)
-
 
 ;; ------------------------------------------------------------ 
 ;; -- Kludges section -- 

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2004-05-30 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30 18:37 New Tramp version fails with ssh Luc Teirlinck
2004-05-30 19:59 ` Luc Teirlinck
2004-05-30 20:25   ` Andreas Schwab [this message]
2004-05-30 20:46     ` Kai Grossjohann
2004-05-30 21:28 ` Stefan Monnier
2004-05-30 21:34   ` Luc Teirlinck
2004-05-30 21:59     ` Stefan Monnier

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=jey8n9zmpb.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=emacs-devel@gnu.org \
    --cc=kai@emptydomain.de \
    --cc=tramp-devel@mail.freesoftware.fsf.org \
    /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).