From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Windows Emacs doesn't understand UNIX symbolic link?
Date: Thu, 03 Apr 2008 21:45:27 +0200 [thread overview]
Message-ID: <877ife204o.fsf@gmx.de> (raw)
In-Reply-To: <uve30kwq7.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Apr 2008 20:11:44 +0300")
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> Yes, that's what we need: to change make-symbolic-link so that only
> its native part is ifdef'ed away on systems without S_IFLNK, and the
> file-handler part is available on all systems.
The appended patch (towards the trunk) shall do the job. I have no build
environment for W32; could somebody, please, test it there?
Best regards, Michael.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1328 bytes --]
*** fileio.c.~1.609.~ 2008-03-29 20:27:38.000000000 +0100
--- fileio.c 2008-04-03 21:37:26.000000000 +0200
***************
*** 2878,2884 ****
return Qnil;
}
- #ifdef S_IFLNK
DEFUN ("make-symbolic-link", Fmake_symbolic_link, Smake_symbolic_link, 2, 3,
"FMake symbolic link to file: \nGMake symbolic link to file %s: \np",
doc: /* Make a symbolic link to FILENAME, named LINKNAME.
--- 2878,2883 ----
***************
*** 2923,2928 ****
--- 2922,2928 ----
RETURN_UNGCPRO (call4 (handler, Qmake_symbolic_link, filename,
linkname, ok_if_already_exists));
+ #ifdef S_IFLNK
encoded_filename = ENCODE_FILE (filename);
encoded_linkname = ENCODE_FILE (linkname);
***************
*** 2949,2956 ****
}
UNGCPRO;
return Qnil;
! }
#endif /* S_IFLNK */
#ifdef VMS
--- 2949,2961 ----
}
UNGCPRO;
return Qnil;
!
! #else
! UNGCPRO;
! xsignal1 (Qfile_error, build_string ("Symbolic links are not supported"));
!
#endif /* S_IFLNK */
+ }
#ifdef VMS
***************
*** 6766,6774 ****
defsubr (&Sdelete_file);
defsubr (&Srename_file);
defsubr (&Sadd_name_to_file);
- #ifdef S_IFLNK
defsubr (&Smake_symbolic_link);
- #endif /* S_IFLNK */
#ifdef VMS
defsubr (&Sdefine_logical_name);
#endif /* VMS */
--- 6771,6777 ----
next prev parent reply other threads:[~2008-04-03 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 4:01 Windows Emacs doesn't understand UNIX symbolic link? Yang
2008-04-01 15:02 ` William Xu
[not found] ` <mailman.9785.1207062149.18990.help-gnu-emacs@gnu.org>
2008-04-01 16:54 ` Yang
2008-04-01 18:57 ` Eli Zaretskii
2008-04-02 2:09 ` William Xu
[not found] ` <mailman.9816.1207102163.18990.help-gnu-emacs@gnu.org>
2008-04-02 5:06 ` Yang
[not found] ` <mailman.9824.1207116435.18990.help-gnu-emacs@gnu.org>
2008-04-02 6:33 ` Barry Margolin
2008-04-02 7:50 ` Michael Albinus
2008-04-02 17:11 ` Eli Zaretskii
2008-04-03 19:45 ` Michael Albinus [this message]
2008-04-02 17:09 ` Eli Zaretskii
2008-04-02 17:27 ` Peter Dyballa
2008-04-02 17:54 ` Eli Zaretskii
2008-04-02 22:12 ` Peter Dyballa
2008-04-03 3:12 ` Eli Zaretskii
2008-04-02 18:15 ` Michael Albinus
[not found] ` <mailman.9884.1207157251.18990.help-gnu-emacs@gnu.org>
2008-04-02 23:28 ` Jason Rumney
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=877ife204o.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).