GNU bug report logs - #35536
27.0.50; Expose buffer's marker list to Elisp

Previous Next

Package: emacs;

Reported by: "Basil L. Contovounesios" <contovob <at> tcd.ie>

Date: Thu, 2 May 2019 15:46:01 UTC

Severity: wishlist

Tags: patch, wontfix

Found in version 27.0.50

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

Bug is archived. No further changes may be made.

Full log


Message #29 received at 35536 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 35536 <at> debbugs.gnu.org, maurooaranda <at> gmail.com, monnier <at> iro.umontreal.ca
Subject: RE: bug#35536: 27.0.50; Expose buffer's marker list to Elisp
Date: Fri, 3 May 2019 09:38:02 -0700 (PDT)
> When asked for a list of markers between BEG and END, it makes sense to
> me to return a list which ascends from BEG to END.
                            ^^^^^^^^^^^^^^^^^^^^^^^
IOW, in buffer-position order.

> If it really matters, we could either return the
> order of BUF_MARKERS unchanged,

Unchanged from what?

> or accept an additional argument which tells the
> function how to sort.

Have not really been following this thread, and
not weighing in on whether such a function is
needed or whether users need access to markers
created by C.

But as for the order of such a list: It's trivial
for users (any Lisp code) to sort by buffer position
or anything else, so why would the default order
be by buffer position?

What's _not_ available to users or Lisp code, I
think, is the order of marker creation or even the
order of last setting.  I'd think that
marker-creation order (either direction) would be
a better default sort order for this, no?




This bug report was last modified 5 years and 253 days ago.

Previous Next


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