From: "rgb" <rbielaws@i1.net>
Subject: Multiple people touching the same file with ange-ftp
Date: 10 Jan 2007 14:40:58 -0800 [thread overview]
Message-ID: <1168468857.210422.271210@i39g2000hsf.googlegroups.com> (raw)
I'm reading in the manual where it says:
Every time Emacs saves a buffer, it first checks the last-modification
date of the existing file on disk to verify that it has not changed
since the file was last visited or saved.
This doesn't happen when I visit a file via ange-ftp.
I'm accessing an unusual host so most of the support I've had to write
myself. But I don't see anything related to modification timestamps
begin called when I trace the ange-ftp calls so I'm not sure how/what
to modify to make this work.
Does anyone have even the slightest idea where to start looking in
order to add support for this.
Thanks
next reply other threads:[~2007-01-10 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 22:40 rgb [this message]
2007-01-10 22:52 ` Multiple people touching the same file with ange-ftp rgb
2007-01-11 6:44 ` Kevin Rodgers
[not found] ` <mailman.2958.1168497899.2155.help-gnu-emacs@gnu.org>
2007-01-11 17:34 ` rgb
2007-01-12 8:00 ` Kevin Rodgers
[not found] ` <mailman.2987.1168588869.2155.help-gnu-emacs@gnu.org>
2007-01-12 18:40 ` rgb
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=1168468857.210422.271210@i39g2000hsf.googlegroups.com \
--to=rbielaws@i1.net \
/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).