From: Mauro Aranda <maurooaranda@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 35536@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#35536: 27.0.50; Expose buffer's marker list to Elisp
Date: Fri, 3 May 2019 20:01:18 -0300 [thread overview]
Message-ID: <CABczVweRE2J_Bh7NOt_4L_gLDQHtc=UEqvfdVp7L6At5abxFNA@mail.gmail.com> (raw)
In-Reply-To: <87imusztof.fsf@tcd.ie>
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
>>> I have yet to see a use-case for marker-list which can't be engineered
>>> in a different way (other than as a replacement for the obsolete
>>> buffer-has-markers-at, FWIW).
>>
>> Well, the discussions you cited did express requirements whose
>> implementation with the existing facilities was either inconvenient or
>> restricted. If these problems are still relevant, then why not try
>> providing some primitives to help them?
>
> A save+restore primitive like the one you suggested in your other
> message sounds like it might do the trick without having to expose a
> buffer's marker list to Lisp.
Indeed. I thought Martin was talking about something like this in his post
in bug#18. Given a region where text is going to be replaced, save the
positions of markers that would be affected because of the delete+insert,
and then restore them.
>> IOW, let me turn the table and ask: why would a Lisp program want to
>> get a list of all the markers in a buffer, especially those not
>> created from Lisp?
>
> As I say above, I don't have any use-cases which specifically need to
> expose a buffer's marker list to Lisp, as opposed to using some other
> approach. The main call for marker-list in bug#18 could probably be
> better solved with a different primitive.
>
When I said I didn't find anything at the Lisp level to get the markers,
that didn't fully express my thoughts. I didn't mean it as a call for a
function to get that information (and certainly, I don't see a use for
getting information about markers created internally). What I meant was
that I thought about that way of restoring markers, but had no way of
working on it (at least not with my current knowledge of C).
Best regards,
Mauro.
[-- Attachment #2: Type: text/html, Size: 2137 bytes --]
next prev parent reply other threads:[~2019-05-03 23:01 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 [this message]
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
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='CABczVweRE2J_Bh7NOt_4L_gLDQHtc=UEqvfdVp7L6At5abxFNA@mail.gmail.com' \
--to=maurooaranda@gmail.com \
--cc=35536@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=monnier@iro.umontreal.ca \
/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).