From: Kim Christensen <kim.christensen@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Cannot use normal save (C-x C-s) when operating over network mount
Date: Fri, 12 Jun 2009 03:31:05 -0700 (PDT) [thread overview]
Message-ID: <8879d2a2-3d9b-4256-95de-68dbb6b44d19@b9g2000yqm.googlegroups.com> (raw)
In-Reply-To: mailman.506.1244799704.2239.help-gnu-emacs@gnu.org
On Jun 12, 11:41 am, Tassilo Horn <tass...@member.fsf.org> wrote:
> Kim Christensen <kim.christen...@gmail.com> writes:
>
> Hi Kim!
>
> > I am actually mounting the Samba share via the cifs network protocol,
> > which allows me to mount it as a network file system (using "cifs" as
> > the vfstype argument to the "mount" application).
>
> Ah, then I didn't understand you correctly. If you mounted a SMB share,
> then to emacs those should be local files. Please try the following:
>
> 1. Open a file on that share and edit it
> 2. M-x toggle-debug-on-error
> 3. Save if with `C-x C-s'
> 4. Poste the contents of the *Backtrace* buffer here
>
> > Are you using tramp for accessing the files? I could try that
> > tomorrow, without mounting it at all -- just accessing it directly.
>
> You can try, but working with files on a mounted smb share should work
> anyway...
>
> Bye,
> Tassilo
Hi again,
I have enabled the debugger and receive the following trace when
trying to save ('C-x C-s'):
Debugger entered--Lisp error: (file-error "Opening output file" "no
such file or directory" "/mnt/effie/foo.bar/www/mulang/
basket_options.php")
write-region(1 4688 "/mnt/effie/foo.bar/www/mulang/
basket_options.php" nil t "/mnt/effie/foo.bar/www/mulang/
basket_options.php")
basic-save-buffer-2()
basic-save-buffer-1()
basic-save-buffer()
save-buffer(1)
call-interactively(save-buffer)
That doesn't give me much information to proceed with though...
What is the difference between saving a file with 'C-x C-s' and 'C-x C-
w', filesystem-wise? Maybe this error is related to the actual
procedure done on the filesystem; I recall gedit having some trouble
when saving files that were accessed through SMB/CIFS because of the
way it saved the file with a temporary name at first - then renaming
it to the original file. I am not sure how Emacs do this, but it could
be related.
Regards,
Kim
next prev parent reply other threads:[~2009-06-12 10:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 8:35 Cannot use normal save (C-x C-s) when operating over network mount Kim Christensen
2009-06-11 13:32 ` Tassilo Horn
[not found] ` <mailman.457.1244727146.2239.help-gnu-emacs@gnu.org>
2009-06-11 14:13 ` Kim Christensen
2009-06-11 22:01 ` Xah Lee
2009-06-11 22:49 ` Kim Christensen
2009-06-12 9:41 ` Tassilo Horn
[not found] ` <mailman.506.1244799704.2239.help-gnu-emacs@gnu.org>
2009-06-12 10:31 ` Kim Christensen [this message]
2009-06-12 11:12 ` Lennart Borgman
[not found] ` <mailman.510.1244805160.2239.help-gnu-emacs@gnu.org>
2009-06-12 11:50 ` Kim Christensen
2009-06-12 14:00 ` Lennart Borgman
2009-06-13 1:16 ` Jason Rumney
2009-06-15 7:29 ` Kim Christensen
2009-06-13 6:46 ` Tim X
2009-06-15 7:40 ` Kim Christensen
2009-06-12 11:52 ` Tassilo Horn
[not found] ` <mailman.512.1244807597.2239.help-gnu-emacs@gnu.org>
2009-06-12 14:18 ` Kim Christensen
2009-06-12 13:24 ` Xah Lee
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=8879d2a2-3d9b-4256-95de-68dbb6b44d19@b9g2000yqm.googlegroups.com \
--to=kim.christensen@gmail.com \
--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).