From: Eli Zaretskii <eliz@gnu.org>
To: Hendrik Tews <tews@os.inf.tu-dresden.de>
Cc: larsi@gnus.org, kevin.d.rodgers@gmail.com, 9663@debbugs.gnu.org
Subject: bug#9663: 23.2; feature wish: put priority on vcursor overlay
Date: Wed, 11 Apr 2012 17:14:05 +0300 [thread overview]
Message-ID: <837gxm5paq.fsf@gnu.org> (raw)
In-Reply-To: <20357.34394.201790.771032@blau.inf.tu-dresden.de>
> From: Hendrik Tews <tews@os.inf.tu-dresden.de>
> Date: Wed, 11 Apr 2012 15:25:46 +0200
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> larsi@gnus.org,
> kevin.d.rodgers@gmail.com,
> 9663@debbugs.gnu.org
>
> > Could you explain why using a non-deprecated feature (priorities
> > of overlays) is a bug?
>
> It isn't.
>
> I still don't understand why you suggest this is a bug in Proof
> General?
But I just said it was NOT a bug, not in Proof General, not anywhere.
> However, if, as you say, vcursor should always be visible,
> why not make its default priority most-positive-fixnum?
>
> I agree, most-positive-fixnum would be a reasonable choice.
> However, some day there might be a package with an overly that
> should hide the vcursor.
We can bother about that when that day comes, if it ever does.
> A large but not maximal number might be a better choice.
Any other value is arbitrary, and I don't like arbitrary values.
But since it sounds like I'm the only one, I will have to live with
that.
next prev parent reply other threads:[~2012-04-11 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 19:48 bug#9663: 23.2; feature wish: put priority on vcursor overlay Hendrik Tews
2011-10-06 4:10 ` Kevin Rodgers
2011-11-01 8:57 ` Hendrik Tews
2011-11-01 19:59 ` Stefan Monnier
2011-11-01 21:23 ` Hendrik Tews
2011-11-02 1:19 ` Stefan Monnier
2011-11-02 7:37 ` Hendrik Tews
2012-04-11 11:35 ` Lars Magne Ingebrigtsen
2012-04-11 11:54 ` Hendrik Tews
2012-04-11 12:22 ` Eli Zaretskii
2012-04-11 13:25 ` Hendrik Tews
2012-04-11 13:43 ` Stefan Monnier
2012-04-11 14:14 ` Eli Zaretskii [this message]
2012-04-11 14:27 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837gxm5paq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9663@debbugs.gnu.org \
--cc=kevin.d.rodgers@gmail.com \
--cc=larsi@gnus.org \
--cc=tews@os.inf.tu-dresden.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.