From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 35536@debbugs.gnu.org, Mauro Aranda <maurooaranda@gmail.com>
Subject: bug#35536: 27.0.50; Expose buffer's marker list to Elisp
Date: Fri, 03 May 2019 13:09:15 -0400 [thread overview]
Message-ID: <jwvbm0jlbow.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r29fcza7.fsf@tcd.ie> (Basil L. Contovounesios's message of "Fri, 03 May 2019 16:50:56 +0100")
> Given a sufficiently sufficient save+restore primitive as per Eli's
> suggestion, it's not looking worth the trouble.
FWIW, I think exposing some new opaque "set of markers" plus primitives
to manipulate such objects is likely a lot more work, so I think from
a purely pragmatic point of view, `markers-in` might be a better option
*assuming* we can make it safe-enough (i.e. it can cause weird behaviors
if mis-used but no hard-crashes, and not if used "reasonably", e.g. if
it's not used to change the markers's buffers nor their relative ordering).
In Emacs, we're generally pretty happy to provide tools powerful enough
to shoot yourself in the foot, as long as such mishaps only happen when
you're clearly using the tool in a dangerous way.
Stefan
prev parent reply other threads:[~2019-05-03 17:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 15:44 bug#35536: 27.0.50; Expose buffer's marker list to Elisp Basil L. Contovounesios
2019-05-02 16:07 ` Eli Zaretskii
2019-05-02 16:51 ` Basil L. Contovounesios
2019-05-02 17:41 ` Eli Zaretskii
2019-05-03 15:50 ` Basil L. Contovounesios
2019-05-03 16:38 ` Drew Adams
2019-05-03 17:22 ` Basil L. Contovounesios
2019-05-03 17:31 ` Drew Adams
2019-05-03 17:39 ` Stefan Monnier
2019-05-03 17:53 ` Drew Adams
2019-05-03 18:13 ` Stefan Monnier
2019-05-03 20:05 ` Drew Adams
2019-05-04 21:25 ` Richard Stallman
2019-09-16 21:07 ` Lars Ingebrigtsen
2019-05-03 23:01 ` Mauro Aranda
2019-05-04 17:34 ` martin rudalics
2019-05-02 19:59 ` Stefan Monnier
2019-05-02 20:05 ` Eli Zaretskii
2019-05-03 15:50 ` Basil L. Contovounesios
2019-05-03 17:09 ` Stefan Monnier [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbm0jlbow.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=35536@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=maurooaranda@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).