unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: 13921@debbugs.gnu.org
Subject: bug#13921: 24.2; Misbehavior of expand-file-name on Cygwin with Emacs 24.2
Date: Wed, 13 Mar 2013 05:52:58 +0200	[thread overview]
Message-ID: <838v5sj6qt.fsf@gnu.org> (raw)
In-Reply-To: <CAFM41H1SUBd_tpWmctEMjzNCKqs+EFn=6R-jc3PczCWzMcVgNg@mail.gmail.com>

> Date: Tue, 12 Mar 2013 20:45:45 -0400
> From: Barry OReilly <gundaetiapo@gmail.com>
> Cc: 13921@debbugs.gnu.org
> 
>    source-directory is a variable defined in `lread.c'.
>    Its value is "d:/devel/emacs/release/emacs24/emacs-24.2/"
> 
>    Documentation:
>    Directory in which Emacs sources were found when Emacs was built.
>    You cannot count on them to still be there!
> 
> I did not find this /devel/emacs/release/emacs24/emacs-24.2/ on my system,
> nor is it the kind of path I would create.

source-directory is where Emacs was built.  And since you didn't build
it yourself, this reflects the directory where whoever built it did
that.

And since Cygwin passes to Emacs a file name without a drive letter,
the logic in autoload.el causes the D: drive letter be added to
/home/epich/sw/cedet/lisp/cedet, because it doesn't expect a
semi-absolute file name like that, it expects either a relative file
name or a fully-qualified absolute one.

So this is a direct result of launching a native w32 Emacs from a
Cygwin Bash.





  reply	other threads:[~2013-03-13  3:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11  2:03 bug#13921: 24.2; Misbehavior of expand-file-name on Cygwin with Emacs 24.2 Barry OReilly
2013-03-11 16:30 ` Eli Zaretskii
2013-03-11 17:21   ` Barry OReilly
2013-03-11 17:43     ` Eli Zaretskii
2013-03-11 17:54       ` Eli Zaretskii
2013-03-13  0:45         ` Barry OReilly
2013-03-13  3:52           ` Eli Zaretskii [this message]
2013-03-13 17:54             ` Eli Zaretskii
2013-03-14 12:16               ` Barry OReilly
2013-03-14 16:38                 ` Eli Zaretskii

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=838v5sj6qt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13921@debbugs.gnu.org \
    --cc=gundaetiapo@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 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).