unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
Subject: Re: Multiple people touching the same file with ange-ftp
Date: Wed, 10 Jan 2007 23:44:41 -0700	[thread overview]
Message-ID: <eo4mco$mh0$1@sea.gmane.org> (raw)
In-Reply-To: <1168469572.611178.86730@77g2000hsv.googlegroups.com>

rgb wrote:
> rgb wrote:
>> 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
> 
> I did get a little further on this.
> I see the command MDTM being attempted and the response
> 'command not understood' coming back.
> If I could intercept this, the DIR command does show the modification
> time so I should be able to find and return it.

Searching for MDTM in ange-ftp.el leads one to ange-ftp-file-modtime.

-- 
Kevin Rodgers
Denver, Colorado, USA

  reply	other threads:[~2007-01-11  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10 22:40 Multiple people touching the same file with ange-ftp rgb
2007-01-10 22:52 ` rgb
2007-01-11  6:44   ` Kevin Rodgers [this message]
     [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='eo4mco$mh0$1@sea.gmane.org' \
    --to=kevin.d.rodgers@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.
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).