From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: jixiuf@qq.com, emacs-devel@gnu.org
Subject: Re: make pred customable in auto-save-visited-mode
Date: Sun, 01 Apr 2018 20:35:02 +0300 [thread overview]
Message-ID: <83d0zi7ruh.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkTK-qzfXg64v2QNTtw0OX=g+EjLei74OTPW1_B64JZ4YA@mail.gmail.com> (message from Philipp Stephani on Sun, 01 Apr 2018 17:19:38 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 01 Apr 2018 17:19:38 +0000
> Cc: jixiuf@qq.com, emacs-devel@gnu.org
>
> > Probably the second option is better because the first option would prevent PRED from running for
> > non-file-visiting buffers. Patch attached.
>
> AFAIU, this will unconditionally disable auto-saving in *ediff-merge*
> and all the similar buffers, when auto-save-visited-mode is turned
> on. Is that what we want? And if that's going to be the default, how
> are users supposed to override it if they want?
>
> I think not prompting is the right approach. It's not very user-friendly to interrupt the user every couple of
> seconds, and no other application I know that has autosave prompts the user for filenames. I think we should
> change the behavior by applying the patch; if some users do want to be interrupted, we can still add a
> customization option later.
AFAIU, you are not disabling the prompt, you are disabling the
auto-saving itself for such buffers. I'm asking if that is what we
want -- disable auto-saving for buffers like *ediff-merge* when
auto-save-visited-mode is turned on.
next prev parent reply other threads:[~2018-04-01 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 16:59 make pred customable in auto-save-visited-mode 纪秀峰
2018-03-31 8:43 ` Eli Zaretskii
2018-03-31 10:23 ` Philipp Stephani
2018-03-31 10:28 ` Philipp Stephani
2018-03-31 10:45 ` Eli Zaretskii
2018-04-01 17:19 ` Philipp Stephani
2018-04-01 17:35 ` Eli Zaretskii [this message]
2018-04-01 19:51 ` Philipp Stephani
2018-04-02 4:44 ` Eli Zaretskii
2018-04-02 10:20 ` Philipp Stephani
2018-03-31 10:42 ` 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=83d0zi7ruh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jixiuf@qq.com \
--cc=p.stephani2@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).