ediff pause after finishing session

ediff pause after finishing session

[Sam Halliday]

Hi all,

When I use ediff to merge conflicts between two files, I will finish the session by typing 'q' and then 'y' to confirm that I am finished.

But then there is a 3 second wait before asking for confirmation to save the buffer (which in itself is superfluous at this stage).

The pause is frustrating (especially when I have lots of trivial file merges to make).

Does anybody have any experience in skipping the pause? (or at least explain why it happens and why it cannot be disabled).

Best regards,
Sam

Re: ediff pause after finishing session

[Sam Halliday]

On Tuesday, 29 April 2014 17:47:44 UTC+1, Sam Halliday  wrote:
> When I use ediff to merge conflicts between two files, I will finish the session by typing 'q' and then 'y' to confirm that I am finished.

(actually there are three questions:

* quit (y/n)
* overwrite (y/n)
* (3 second pause)
* kill buffer (y/n)

I'd really like to get that down to

* save and quit (y/n)

(with no pause)

> Does anybody have any experience in skipping the pause? (or at least explain why it happens and why it cannot be disabled).

Re: ediff pause after finishing session

[Michael Heerdegen]

Sam Halliday <sam.halliday@gmail.com> writes:

> * quit (y/n)
> * overwrite (y/n)
> * (3 second pause)
> * kill buffer (y/n)

Looks like `ediff-write-merge-buffer-and-maybe-kill' is the culprit.

> > Does anybody have any experience in skipping the pause? (or at least
> > explain why it happens and why it cannot be disabled).

In Ediff, lots of such stuff is hardcoded - including the behavior you
see.  The pause was probably added to make the user see the feedback
from writing the file.

I too find the behavior irritating, but there's probably no easy way to
fix it on a user basis.  You can try a bug report, but I doubt it will
be treated soon.


Michael.

Re: ediff pause after finishing session

[Dan.Espen]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Sam Halliday <sam.halliday@gmail.com> writes:
>
>> * quit (y/n)
>> * overwrite (y/n)
>> * (3 second pause)
>> * kill buffer (y/n)
>
> Looks like `ediff-write-merge-buffer-and-maybe-kill' is the culprit.

sit-for is supposed to respond as soon as you hit a key.
Maybe type a space after "overwrite (y/n)"?

-- 
Dan Espen

Re: ediff pause after finishing session

[Michael Heerdegen]

despen@verizon.net (Dan.Espen) writes:

> > Looks like `ediff-write-merge-buffer-and-maybe-kill' is the culprit.
>
> sit-for is supposed to respond as soon as you hit a key.
> Maybe type a space after "overwrite (y/n)"?

But AFAIK this event would not be discarded, and the following y-or-n-p
would grasp it and barf.  But just hitting y y y (blindly) in fast
succession should be fine, I think.

Michael.