all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Yang Zhang" <fz15@cse.msstate.edu>
To: "Michael Albinus" <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tramp 2.1.13-pre messed up symbolic link?
Date: Tue, 24 Jun 2008 00:24:06 -0500	[thread overview]
Message-ID: <8d61170c0806232224r324a4b0gb1f22fa28ac78e36@mail.gmail.com> (raw)
In-Reply-To: <nq1w2oa1mm.fsf@alcatel-lucent.de>

Hi Michael,

Thank you for your patch. It worked fine with emacs 23 on Ubuntu 8.04.
I've also tried the patched tramp 2.1.13 with emacs 22.1 on Windows
Vista. It seems that this also allowed the Windows emacs to read and
save symbolic link files correctly on the remote Solaris 10 machine,
except for some initial warning and interactions (I have to type some
"yes" to proceed). In the Windows Vista emacs 22.1, for symbolic links
that point to cvs controlled file, it directly opened the target file
(which is fine).

There is one small issue (that I've noticed for a long time). After
saving, the target file's permission is always set to be "-rwxrwxrwx"
regardless of the original one. For example, the target file is
"test.cc (-rw-------)" the symbolic link is "test_link.cc (always
lrwxrwxrwx)"  After opening "test_link.cc" through tramp and saving
something, "test.cc" now has a permission of "-rwxrwxrwx".  It there a
way to retain the target file's original permission after saving
through the symbolic link file?

Thanks
--Yang


On Mon, Jun 23, 2008 at 5:26 AM, Michael Albinus <michael.albinus@gmx.de> wrote:
>> Hello Michael,
>
> Hi,
>
>> Thank you for your attention and help. The pre-installed tramp
>> 2.1.13-pre with my emacs 23.0.60.1 is also having the symbolic
>> problem. Here I attached the tramp debug buffer output. The other
>> buffer "tramp /scp host*" is empty.
>
> Thanks for the traces, they have been helpful. Please try the appended
> patch (towards 2.1.14-pre), it shall fix the problem.
>
>> Thank you very much,
>>
>> --Yang
>
> Best regards, Michael.
>
>




  reply	other threads:[~2008-06-24  5:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19  7:56 tramp 2.1.13-pre messed up symbolic link? Yang Zhang
2008-06-19 10:19 ` Peter Dyballa
     [not found] ` <mailman.13566.1213870789.18990.help-gnu-emacs@gnu.org>
2008-06-20  4:50   ` Yang Zhang
2008-06-21  8:37     ` Michael Albinus
     [not found]       ` <8d61170c0806220203h75885df3nf6283e13c6d3732c@mail.gmail.com>
2008-06-23 10:26         ` Michael Albinus
2008-06-24  5:24           ` Yang Zhang [this message]
2008-06-24 15:10             ` Michael Albinus
2008-06-25 11:35             ` Michael Albinus
2008-06-26  4:31               ` Yang Zhang
     [not found]             ` <mailman.13825.1214393802.18990.help-gnu-emacs@gnu.org>
2008-06-26 17:20               ` Thr4wn
2008-06-26 20:43                 ` Yang Zhang
2008-06-27  7:05                 ` 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

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

  git send-email \
    --in-reply-to=8d61170c0806232224r324a4b0gb1f22fa28ac78e36@mail.gmail.com \
    --to=fz15@cse.msstate.edu \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.