From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: David Reitter <david.reitter@gmail.com>
Cc: aquamacs Bugs <aquamacs-bugs@aquamacs.org>,
bug-gnu-emacs@gnu.org, Bill McGonigle <bill@bfccomputing.com>
Subject: Re: *emacs vs. MacFUSE/sshfs
Date: Fri, 27 Jul 2007 08:54:13 +0900 [thread overview]
Message-ID: <wl6446g1qy.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <53099B2E-2D42-43A0-92D7-E81DA62B053E@gmail.com>
>>>>> On Thu, 26 Jul 2007 16:07:33 +0100, David Reitter <david.reitter@gmail.com> said:
> I think this would have to be addressed on the Emacs level. I'm
> cc'ing the Emacs Bugs list.
> PS.: You could use Tramp for the time being.
> On 26 Jul 2007, at 15:23, Bill McGonigle wrote:
> Just sending along a pointer to a bug report at Google that affects
> Aquamacs:
> http://code.google.com/p/macfuse/issues/detail?id=214#c7
> There appears to be a work-around that can be implemented in
> MacFUSE, but it also appears emacs is aggressive/optimistic, and
> this might affect other filesystems, not just MacFUSE-based ones.
Could you explain more about "it appears emacs is
aggressive/optimistic"? In the Carbon port, the SIGALRM duration is 2
seconds by default and it's not too frequent. If some file operation
takes much more time than that period, then it is desirable that it
works with signals so users/applications can interrupt the long
operation, IMO.
> A different duration for the alarm signal might make sense on the
> Mac.
You can set it via `polling-period' if you need.
What kind of change on the Emacs side are the MacFUSE developers
suggesting?
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2007-07-26 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0C7ECE52-6318-4F24-98D9-9A7A75FB0521@bfccomputing.com>
2007-07-26 15:07 ` *emacs vs. MacFUSE/sshfs David Reitter
2007-07-26 23:54 ` YAMAMOTO Mitsuharu [this message]
2007-07-27 7:11 ` Bill McGonigle
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=wl6446g1qy.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=aquamacs-bugs@aquamacs.org \
--cc=bill@bfccomputing.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=david.reitter@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).