unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Strange behavior editing a file from Dired
Date: Fri, 09 Dec 2016 09:46:46 +0200	[thread overview]
Message-ID: <8337hxily1.fsf@gnu.org> (raw)
In-Reply-To: <E1cF5Pz-0001Ef-Jl@fencepost.gnu.org> (message from Richard Stallman on Thu, 08 Dec 2016 15:35:51 -0500)

> From: Richard Stallman <rms@gnu.org>
> Date: Thu, 08 Dec 2016 15:35:51 -0500
> 
> When I review mails before sending them out, I move down through
> a Dired buffer typing C-o.  Sometimes I switch to the other window
> and type C-x 1, edit that message file, and save it.  Then I switch
> back to the Dired buffer.
> 
> Occasionally I find that point has moved up some number of lines in
> the Dired buffer.  The number of lines varies.
> 
> This has been happening for months.
> 
> When I notice it, I type C-h l, but I have not noticed anything
> significant in the output.  And I have not been able to reproduce it.
> 
> Has anyone else seen something like this?

I haven't, but I don't use Dired much with this paradigm.

I would suggest to define some appropriate hook (pos-command-hook, if
nothing better exists) that watches the value of point in that buffer,
and signals an error when it changes.  Then you might be able to catch
the villain red-handed.



  reply	other threads:[~2016-12-09  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 20:35 Strange behavior editing a file from Dired Richard Stallman
2016-12-09  7:46 ` Eli Zaretskii [this message]
2016-12-09 15:06   ` Richard Stallman
2016-12-09  9:24 ` Andreas Schwab
2016-12-09 15:06   ` Richard Stallman
2016-12-09 15:53   ` Drew Adams
2016-12-09 21:56     ` Richard Stallman
     [not found]   ` <<6f523b1f-71ab-4147-8d9d-7e7f1cb2b07d@default>
     [not found]     ` <<E1cFT9O-0001ky-7m@fencepost.gnu.org>
2016-12-09 22:32       ` Drew Adams
2016-12-11  9:32         ` Richard Stallman
2016-12-11 15:11 ` Simen Heggestøyl

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=8337hxily1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
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).