all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: vidagabor@gmail.com, 14030@debbugs.gnu.org
Subject: bug#14030: 24.3; expand-file-name expands remote file name on Windows incorrectly
Date: Sun, 24 Mar 2013 19:32:00 +0100	[thread overview]
Message-ID: <877gkwfy3j.fsf@gmx.de> (raw)
In-Reply-To: <83mwts3dm9.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 24 Mar 2013 19:35:10 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Albinus <michael.albinus@gmx.de>
>> Cc: vidagabor@gmail.com,  14030@debbugs.gnu.org
>> Date: Sun, 24 Mar 2013 18:21:48 +0100
>> 
>> > So, somehow, compiling tramp-sh.el on Unix replaces the call to
>> > tramp-drop-volume-letter with nothing.  Perhaps the condition, viz.
>> 
>> Yes, that is intended. tramp-drop-volume-letter is not needed on GNU/Linux.
>
> ??? But byte-compiled files are supposed to be platform-independent.
> The release tarball includes all of the *.elc files, which were
> compiled on Unix when the release was tarred, and they are not
> recompiled when Emacs is built on Windows (or on any other platform).
> Now you seem to be saying that all the *.elc files need to be compiled
> as part of the build on the target platform.  I think this isn't a
> good thing.

Yes, you are right.

>> Does this mean, this declaration requests Tramp to be compiled on MS
>> Windows?
>
> No, it means tramp-drop-volume-letter has a bug that needs to be
> fixed, IMO.

The problem seems to be, that defalias is evaled during
byte-compilation. So I will revert the definition of
tramp-drop-volume-letter, that is is decided at runtime how it is
defined.

>> We shall repackage Emacs 24.3 for MS Windows then.
>
> Lisp files are not supposed to be recompiled on the target platform.
> They are architecture-independent, and are installed in a directory
> which can be shared among different architectures.
>
> Sorry, but I think this is a grave bug.

Yes. Unfortunately, all pretests for MS Windows were compiled on MS
Windows. So this hasn't been detected earlier.

What shall we do with Emacs 24.3 for MS Windows? I still believe, that
we must repackage it, and compile tramp.el on MS Windows.

Alternatively there could be an Emacs 24.3a with a changed tramp.el. But
this sounds too heavy to me.

Best regards, Michael.





  reply	other threads:[~2013-03-24 18:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 15:17 bug#14030: 24.3; expand-file-name expands remote file name on Windows incorrectly Vida Gábor
2013-03-22 16:02 ` Eli Zaretskii
2013-03-23 12:13   ` Michael Albinus
2013-03-23 20:23     ` Eli Zaretskii
2013-03-23 21:37       ` Michael Albinus
2013-03-24 16:10         ` Eli Zaretskii
2013-03-24 17:21           ` Michael Albinus
2013-03-24 17:35             ` Eli Zaretskii
2013-03-24 18:32               ` Michael Albinus [this message]
2013-03-24 19:23                 ` Eli Zaretskii
2013-03-25  8:36                   ` Michael Albinus
2013-03-25  9:01                     ` Eli Zaretskii
2013-03-25  9:20                       ` Michael Albinus
2013-03-25  9:55                         ` Eli Zaretskii
2013-03-25 10:06                           ` Michael Albinus
2013-03-27  0:11                     ` Wolfgang Jenkner
2013-03-27  2:24                       ` Stefan Monnier
2013-03-27  6:59                         ` Eli Zaretskii
2013-03-26  0:35                 ` Wolfgang Jenkner
2013-03-25 14:28               ` Stefan Monnier
2013-03-25 18:49                 ` Stefan Monnier
2013-03-25 19:28                   ` Michael Albinus
2013-03-25 20:32                   ` Eli Zaretskii
2013-03-26  0:23                     ` Stefan Monnier
2013-03-26  6:11                       ` Eli Zaretskii
2013-03-24 16:11 ` Eli Zaretskii
2013-03-25  8:53   ` Vida Gábor
2020-09-09 13:56     ` Lars Ingebrigtsen

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

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

  git send-email \
    --in-reply-to=877gkwfy3j.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=14030@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=vidagabor@gmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.