unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 26973@debbugs.gnu.org, eggert@cs.ucla.edu,
	michael.albinus@gmx.de, dgutov@yandex.ru
Subject: bug#26973: 26.0.50; sleep-for behavior changes with global-auto-revert-mode enabled
Date: Sun, 28 May 2017 18:13:31 +0300	[thread overview]
Message-ID: <83efv9ggkk.fsf@gnu.org> (raw)
In-Reply-To: <87h905wd7u.fsf@luca> (message from Andreas Politz on Sun, 28 May 2017 11:19:17 +0200)

> From: Andreas Politz <politza@hochschule-trier.de>
> Date: Sun, 28 May 2017 11:19:17 +0200
> Cc: 26973-done@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>,
> 	Dmitry Gutov <dgutov@yandex.ru>
> 
> 
> It just occured to me that the other back-ends may exhibit the same
> behavior, when used outside of filenotify.el . For example w32notify
> provides the flag
> 
>   'last-access-time'   -- report changes in last-access time

Sorry, I've lost track of the discussion -- could you please tell what
"same behavior" did you refer to, and what could be the problem with
the last-access-time flag provided by w32notify.c?

Thanks.





  reply	other threads:[~2017-05-28 15:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 23:57 bug#26973: 26.0.50; sleep-for behavior changes with global-auto-revert-mode enabled Dmitry Gutov
2017-05-20 11:36 ` Eli Zaretskii
2017-05-20 12:45   ` Dmitry Gutov
2017-05-20 13:38     ` Eli Zaretskii
2017-05-21 22:38       ` Dmitry Gutov
2017-05-22  4:06         ` Eli Zaretskii
2017-05-24  0:58           ` Dmitry Gutov
2017-05-24 18:33             ` Eli Zaretskii
2017-05-22  7:52       ` Michael Albinus
2017-05-22 18:24         ` Eli Zaretskii
2017-05-25  8:12           ` Michael Albinus
2017-05-25  9:45             ` Andreas Politz
2017-05-26 14:45               ` Michael Albinus
2017-05-27  0:45                 ` Dmitry Gutov
2017-05-27  7:33                   ` Michael Albinus
2017-05-26 18:06 ` Paul Eggert
2017-05-27 16:36   ` Andreas Politz
2017-05-27 18:19     ` Paul Eggert
2017-05-27 21:13       ` Andreas Politz
2017-05-27 21:29         ` Paul Eggert
2017-05-27 21:56           ` Andreas Politz
2017-05-28 18:21             ` Paul Eggert
2017-05-28 21:18               ` Andreas Politz
2017-05-28  9:19           ` Andreas Politz
2017-05-28 15:13             ` Eli Zaretskii [this message]
2017-06-04 11:49             ` Michael Albinus
2017-06-04 14:00               ` Eli Zaretskii
2017-06-04 15:30                 ` Andreas Politz
2017-06-04 16:20                   ` Eli Zaretskii

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=83efv9ggkk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26973@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eggert@cs.ucla.edu \
    --cc=michael.albinus@gmx.de \
    --cc=politza@hochschule-trier.de \
    /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).