unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: paul.r.ml@gmail.com, joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Emacs inotify support?
Date: Fri, 18 Sep 2009 05:49:42 -0400	[thread overview]
Message-ID: <E1Moa62-000256-2J@fencepost.gnu.org> (raw)
In-Reply-To: <87iqfhbo6u.fsf@mail.jurta.org> (message from Juri Linkov on Thu,  17 Sep 2009 18:12:09 +0300)

    > What happens if the file whose line point is on gets renamed?  That
    > seems like a mergeable difference, but you might be a bit surprised to
    > see the line move to some other position in the buffer.

    Most file managers automatically update changed files and that
    doesn't surprise users.

The precise details of display format can have a big effect on whether
the update bothers users, and how much.

Ultimately, the only way to judge whether it bothers users too much
is to try it.  But we should POLL THE USERS before enabling it by default.




  reply	other threads:[~2009-09-18  9:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 20:34 Emacs inotify support? joakim
2009-09-11 21:28 ` Lennart Borgman
2009-09-11 22:54   ` Antoine Levitt
2009-09-11 23:00     ` Lennart Borgman
2009-09-12 13:32     ` Eli Zaretskii
2009-09-12 16:36       ` Antoine Levitt
2009-09-12 16:55         ` Eli Zaretskii
2009-09-12 17:26           ` Antoine Levitt
2009-09-12 19:45             ` Eli Zaretskii
2009-09-12 20:04               ` Antoine Levitt
2009-09-12 21:24               ` Giuseppe Scrivano
2009-09-13 16:39       ` Richard Stallman
2009-09-13 17:28         ` joakim
2009-09-13 19:42           ` Eli Zaretskii
2009-09-13 22:28             ` Lennart Borgman
2009-09-14  5:47             ` joakim
2009-09-14 18:08               ` Eli Zaretskii
2009-09-12 16:46     ` Richard Stallman
2009-09-13  2:27       ` Miles Bader
2009-09-13  9:33         ` David Kastrup
2009-09-12 16:46 ` Richard Stallman
2009-09-14  7:39   ` Paul R
2009-09-15  7:17     ` Richard Stallman
2009-09-17 15:12       ` Juri Linkov
2009-09-18  9:49         ` Richard Stallman [this message]
2009-09-18 12:10           ` David Kastrup
2009-09-18 17:14             ` Stefan Monnier
2009-09-18 18:38               ` joakim
2009-09-21 21:45           ` Dired auto-revert (was: Emacs inotify support?) Juri Linkov
2009-09-21 22:29             ` Drew Adams
2009-09-23  9:05               ` Dired auto-revert Juri Linkov
2009-12-04  0:11                 ` Proced revert (Re: Dired auto-revert) Juri Linkov
2009-12-04  2:17                   ` Stefan Monnier
2009-12-04 22:21                   ` Roland Winkler
2009-12-04  0:09               ` Dired auto-revert Juri Linkov
2009-12-04  2:15                 ` Stefan Monnier

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=E1Moa62-000256-2J@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=juri@jurta.org \
    --cc=paul.r.ml@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 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).