GNU bug report logs - #9663
23.2; feature wish: put priority on vcursor overlay

Previous Next

Package: emacs;

Reported by: Hendrik Tews <hendrik <at> askra.de>

Date: Mon, 3 Oct 2011 20:05:02 UTC

Severity: normal

Tags: fixed, patch

Found in version 23.2

Fixed in version 24.2

Done: Lars Magne Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Hendrik Tews <tews <at> os.inf.tu-dresden.de>
To: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
Cc: Kevin Rodgers <kevin.d.rodgers <at> gmail.com>, Stefan Monnier <monnier <at> IRO.UMontreal.CA>, 9663 <at> debbugs.gnu.org
Subject: bug#9663: 23.2; feature wish: put priority on vcursor overlay
Date: Wed, 11 Apr 2012 13:54:40 +0200
Lars Magne Ingebrigtsen writes:
   Date: Wed, 11 Apr 2012 13:35:18 +0200
   Subject: Re: bug#9663: 23.2; feature wish: put priority on vcursor overlay
   
   Hendrik Tews <tews <at> os.inf.tu-dresden.de> writes:
   
   >    same priority. Which makes me wonder: why other overlay have
   >    you bumped into which has either higher priority than nil, or
   >    nil priority but is not larger than vcursor.
   >
   > As I wrote in the feature wish: the locked region in Proof
   > General (proof-locked-span). It has priority 100, see the call to
   > span-raise inside proof-init-segmentation in
   > generic/proof-script.el.
   
   So perhaps this is a bug in Proof General and doesn't really require an
   overlay priority in Emacs?

Could you explain why using a non-deprecated feature (priorities
of overlays) is a bug?

I really don't understand this discussion about a very simple
feature wish with a very simple patch. Overlay priorities do
exist, so vcursor better should work in the presence of overlays
with non-zero priorities, shouldn't it?

Bye,

Hendrik




This bug report was last modified 13 years and 102 days ago.

Previous Next


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