all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Sean McAfee <eefacm@gmail.com>
Cc: 20299@debbugs.gnu.org
Subject: bug#20299: 25.0.50; File notification is not working
Date: Sat, 18 Apr 2015 19:51:51 +0200	[thread overview]
Message-ID: <87wq19b9zc.fsf@gmx.de> (raw)
In-Reply-To: <87wq19pebr.fsf@gmail.com> (Sean McAfee's message of "Sat, 18 Apr 2015 09:54:16 -0700")

Sean McAfee <eefacm@gmail.com> writes:

> Michael Albinus <michael.albinus@gmx.de> writes:
>> Here you must apply "M-x auto-revert-mode".
>
> Ah, I didn't realize this was necessary.  I assumed Emacs would receive
> file notification events for all open files if it was built with that
> capability, since it seems an inexpensive enough operation.

Inexpensive if you have native support like inotify. If you use glib,
for example, it might be necessary to poll, which is more heavy.

> This would seem to be more of a Magit issue than an Emacs issue.  I'll
> re-report my original issue in the appropriate place (although it's hard
> to imagine that such a substantial feature being broken could have gone
> unnoticed by anyone other than me by now).

OK, so I'm closing this bug. Feel free to come back if needed.

> Thanks for the help!
>
> --Sean

Best regards, Michael.





  reply	other threads:[~2015-04-18 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11  0:39 bug#20299: 25.0.50; File notification is not working Sean McAfee
2015-04-11  7:03 ` Michael Albinus
     [not found]   ` <CANan03bo=meT7fQZ_QPxAgO69x_PBPx_H53BLMqUYk-=iqOybg@mail.gmail.com>
     [not found]     ` <87vbgyn8tr.fsf@gmx.de>
     [not found]       ` <CANan03ZDin3ZkU_=NxPa0Xyf2ouNrVYVJy7q-=Oo+Bo1Hs3KtQ@mail.gmail.com>
2015-04-16 14:25         ` Michael Albinus
2015-04-18 16:54           ` Sean McAfee
2015-04-18 17:51             ` Michael Albinus [this message]
2015-04-19  8:27               ` Michael Albinus

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=87wq19b9zc.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=20299@debbugs.gnu.org \
    --cc=eefacm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.