From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: "Johannes Thrän"
<johannes.thraen-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: vim reports file having changed
Date: Thu, 1 Dec 2011 10:44:17 -0500 [thread overview]
Message-ID: <20111201104417.4b3ce577@barsoom.rdu.redhat.com> (raw)
In-Reply-To: <CAFbNW2Fv58h_r1rmtk0rHg+uJ0C9i1Rtoy2DEDm-Hxw-ZtK_mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 30 Nov 2011 15:25:01 +0100
Johannes Thrän <johannes.thraen-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:
> Hi all,
>
> I reported this before here, it somehow went under. So I'll try again:
>
> When I open a file which is located on a cifs-mounted windows share
> with vim, vim will after some time always report the file as having
> changed upon saving, regardless whether it has actually changed or
> not.
>
> I reported this also to the vim maintainer who told me, there he
> doesn't know of a similar problem with samba. Ergo it's probably a
> problem with cifs.
> I work on a daily basis with mentioned setup, so I would be vary glad
> to help resolve it.
>
> mount.cifs -v gives 4.5, I use kubuntu 11.04 and vim 7.2
>
Unfortunately, this sort of report doesn't help us to help you very
much. I have no idea what vim is actually complaining about when it
says that the file has changed.
As it's a kernel filesystem, it primarily deals with userspace code via
system calls. If you can phrase your problem in that context then
that would help. We'd need to know what vim is actually looking at to
detect that the file has changed. Is it the mtime?
--
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
next prev parent reply other threads:[~2011-12-01 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 14:25 vim reports file having changed Johannes Thrän
[not found] ` <CAFbNW2Fv58h_r1rmtk0rHg+uJ0C9i1Rtoy2DEDm-Hxw-ZtK_mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-01 1:42 ` Shirish Pargaonkar
[not found] ` <CADT32eKDtm0sGk8TWp9zvELaK+Fw_PSinSpGR2S_epw7_pXu9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-01 5:24 ` Steve French
[not found] ` <CAH2r5mszHcu5XKTsTtQeEVd-jCMCOnNvucZTe=p2PAfAA9vAmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-01 9:34 ` Johannes Thrän
2011-12-01 15:44 ` Jeff Layton [this message]
[not found] ` <20111201104417.4b3ce577-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2011-12-01 15:56 ` Shirish Pargaonkar
[not found] ` <CADT32eJT=J+Jip_LFTX8SKZcEYUgdP7k=3PkE=q5UeH1rL2Ehg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-01 18:22 ` Johannes Thrän
[not found] ` <CAFbNW2EQC5d506pXTzJUMtHGUL-76Wz9CoVTJkf0WAdb5VQX1w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-02 17:27 ` Johannes Thrän
[not found] ` <CAFbNW2FJuRQMLspnSqGcvNRfCT=2zsVO+x0eQJ6mTFKJTQkdBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-02 19:24 ` Shirish Pargaonkar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111201104417.4b3ce577@barsoom.rdu.redhat.com \
--to=jlayton-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=johannes.thraen-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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