GNU bug report logs - #63318
Variable ediff-auto-refine doesn't always default to "on"

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#63318: closed (Variable ediff-auto-refine doesn't always
 default to "on")
Date: Sat, 13 May 2023 14:03:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 13 May 2023 17:02:14 +0300
with message-id <83o7mo9vo9.fsf <at> gnu.org>
and subject line Re: bug#63318: Variable ediff-auto-refine doesn't always default to "on"
has caused the debbugs.gnu.org bug report #63318,
regarding Variable ediff-auto-refine doesn't always default to "on"
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
63318: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63318
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Peter Oliver <p.d.oliver <at> mavit.org.uk>
To: bug-gnu-emacs <at> gnu.org
Subject: Variable ediff-auto-refine doesn't always default to "on"
Date: Fri, 5 May 2023 21:21:50 +0100 (BST)

[Message part 3 (text/plain, inline)]

Severity: minor
Tags: patch

Document that variable ediff-auto-refine doesn't always default to "on".

-- 
Peter Oliver

[0001-Variable-ediff-auto-refine-doesn-t-always-default-to.patch (text/plain, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Peter Oliver <p.d.oliver <at> mavit.org.uk>
Cc: 63318-done <at> debbugs.gnu.org
Subject: Re: bug#63318: Variable ediff-auto-refine doesn't always default to
 "on"
Date: Sat, 13 May 2023 17:02:14 +0300

> Date: Mon, 8 May 2023 11:26:47 +0100 (BST)
> From: Peter Oliver <p.d.oliver <at> mavit.org.uk>
> cc: 63318 <at> debbugs.gnu.org
> 
> > Why doesn't Ediff turn on ediff-auto-refine for all terminals?
> > AFAICT, it only needs faces (basically, colors), and we support that
> > on all terminals nowadays?  So I think we should simply change the
> > default value (which will also solve bug#63317).  Or what am I
> > missing?
> 
> I assumed that this complication was present because there exist displays on which auto-refinement isn’t desirable.
> 
> If that’s no-longer the case, then great, simplifying the default to always be “on” certainly sounds like the best way to go to me.  Attached is a patch to do that instead.

Thanks, installed on the master branch (after applying the necessary
fix).

Closing the bug.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.