unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joakim Verona <joakim@verona.se>
Subject: how to work with unreliable filesystems?
Date: Thu, 12 Jan 2006 11:58:31 +0100	[thread overview]
Message-ID: <m3ek3dr9uw.fsf@kurono.home> (raw)

I have a smb filesystem mounted over a shaky vpn connection.
Much of the time this works, but if the share hangs for some reason,
emacs also stops responding, waiting for the share to come back.

I currently solve this by unmounting/remounting the filesystem, but
its all very inconvenient.

It would be neat if a directory hierarchy could be marked "unstable"
and using copying instead of direct writes, much as Tramp works. 

I guess this would ideally be handled at the os level, but I have
twiddled mount paramters back and forth to no avail. 

Any hints are apreciated. 

-- 
Joakim Verona
www.verona.se

             reply	other threads:[~2006-01-12 10:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 10:58 Joakim Verona [this message]
     [not found] <mailman.819.1137074824.26925.help-gnu-emacs@gnu.org>
2006-01-12 17:55 ` how to work with unreliable filesystems? Pascal Bourguignon

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=m3ek3dr9uw.fsf@kurono.home \
    --to=joakim@verona.se \
    /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).