From: martin rudalics <rudalics@gmx.at>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 27243@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
antoine.levitt@gmail.com
Subject: bug#27243: another case: dired-auto-revert-buffer jumps point to beginning of buffer
Date: Fri, 28 Jul 2017 14:22:34 +0200 [thread overview]
Message-ID: <597B2C8A.9080805@gmx.at> (raw)
In-Reply-To: <8760ed7xp3.fsf@rosalinde>
> Are we waiting for feedback from Stefan (cc'd just in case)? Or should
> I go ahead and push the fix?
Go ahead and push it.
martin
next prev parent reply other threads:[~2017-07-28 12:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 23:45 bug#27243: dired-auto-revert-buffer jumps point to beginning of buffer Antoine Levitt
2017-06-05 13:37 ` Stephen Berman
2017-06-05 15:02 ` Eli Zaretskii
2017-06-05 15:15 ` Stephen Berman
2017-06-05 16:20 ` Eli Zaretskii
2017-06-10 8:24 ` Eli Zaretskii
[not found] ` <CABfD5m0==QAKYoJDkaPQxoyS1BQT-eTQJLmYZC6Z-V5A0jfeig@mail.gmail.com>
2017-06-10 8:45 ` Antoine Levitt
[not found] ` <handler.27243.D27243.14970831096548.notifdone@debbugs.gnu.org>
2017-06-17 12:16 ` bug#27243: closed (Re: bug#27243: dired-auto-revert-buffer jumps point to beginning of buffer) Antoine Levitt
2017-06-17 13:32 ` Stephen Berman
2017-07-09 17:37 ` Antoine Levitt
2017-07-14 9:56 ` Stephen Berman
2017-07-15 5:52 ` John Wiegley
2017-07-15 7:18 ` Eli Zaretskii
2017-07-17 9:22 ` Stephen Berman
2017-07-22 15:28 ` Antoine Levitt
2017-07-22 16:55 ` Glenn Morris
2017-07-22 22:48 ` Stephen Berman
2017-07-22 22:48 ` bug#27243: another case: dired-auto-revert-buffer jumps point to beginning of buffer Stephen Berman
2017-07-23 14:43 ` Eli Zaretskii
2017-07-23 18:40 ` martin rudalics
2017-07-23 18:58 ` Eli Zaretskii
2017-07-23 21:09 ` martin rudalics
2017-07-28 8:49 ` Stephen Berman
2017-07-28 9:28 ` Eli Zaretskii
2017-07-28 12:22 ` martin rudalics [this message]
2017-07-28 13:02 ` Stefan Monnier
2017-07-28 13:12 ` Eli Zaretskii
2017-07-28 13:16 ` Stefan Monnier
2017-07-28 13:41 ` Eli Zaretskii
2017-07-28 14:14 ` martin rudalics
2017-07-28 14:45 ` Eli Zaretskii
2017-07-28 14:54 ` Stephen Berman
2017-07-29 11:44 ` Stephen Berman
2020-05-25 4:21 ` Michael Heerdegen
[not found] ` <874ks4ekpg.fsf@web.de>
2020-05-25 7:26 ` Stephen Berman
2020-05-25 23:36 ` Michael Heerdegen
2020-05-27 1:23 ` Michael Heerdegen
2020-05-27 5:36 ` Michael Heerdegen
2020-05-27 14:52 ` martin rudalics
2020-05-27 17:01 ` Michael Heerdegen
2020-05-27 17:56 ` martin rudalics
2020-05-30 22:11 ` Juri Linkov
2020-05-26 8:02 ` martin rudalics
2020-05-27 1:16 ` Michael Heerdegen
2017-07-15 7:36 ` bug#27243: closed (Re: bug#27243: dired-auto-revert-buffer jumps point to beginning of buffer) martin rudalics
2017-07-15 11:14 ` Stephen Berman
2017-07-15 13:59 ` martin rudalics
2017-07-17 9:28 ` Stephen Berman
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=597B2C8A.9080805@gmx.at \
--to=rudalics@gmx.at \
--cc=27243@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stephen.berman@gmx.net \
/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).