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


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>
Cc: 35536 <at> debbugs.gnu.org, maurooaranda <at> gmail.com, monnier <at> iro.umontreal.ca
Subject: bug#35536: 27.0.50; Expose buffer's marker list to Elisp
Date: Thu, 02 May 2019 19:07:47 +0300
> From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
> Date: Thu, 02 May 2019 16:44:52 +0100
> Cc: Mauro Aranda <maurooaranda <at> gmail.com>,
> 	Stefan Monnier <monnier <at> iro.umontreal.ca>
> 
> I attach a patch implementing this based on BUF_MARKERS, as per Martin's
> suggestion.  Any reasons not to expose such a function?

I'm not yet convinced we need something like that, but in any case, is
the order important?  Because the code you propose produces a list in
reverse order.

More generally, I think we should discuss the need for this in more
detail.  Markers are used for several features, and there's internal
stuff like conversion from character to byte positions that depends on
them.  Changing markers could thus easily crash Emacs, especially if
it comes in some in-opportune moment.

It is possible that people actually need higher-level primitives that
manipulate markers internally.  We should first identify the use cases
where this could be needed, and then see how to help solving those use
cases by something like a new marker-related primitive.




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.