unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: RE: Overlay insertion types, markers, etc.
Date: Sat, 16 Nov 2019 18:26:39 -0800 (PST)	[thread overview]
Message-ID: <29c934d3-712c-414e-b4aa-9ed8f3c609a2@default> (raw)
In-Reply-To: <E1iWA5m-0004Q6-TS@fencepost.gnu.org>

>   > > The design was by Richard, so he is the only one who might
> remember
>   > > why he didn't go beyond what we have.
> 
>   > Ccing Richard, in case he might want to add something.
> 
> I have not been following this thread.  What are the changes people
> propose?
> 
> It is possible that the answer is simple -- that I didn't see a need
> to do the work to add any other features in that area.  But unless
> I know what is proposed, I can't know the answer.

Thanks for replying.

No changes to anything were proposed.  I asked some
questions, trying to understand the design.  This
is all in the first message of the thread (and the
thread is short).  This the URL of that message:

https://lists.gnu.org/archive/html/emacs-devel/2019-11/msg00414.html

Eli responded to some of the questions.  I replied
with clarification questions, to understand his
reply.  But essentially everything I'm asking about
is in the initial message.

In summary, these are the questions:

1. Why, if you pass markers [to `make-overlay],
   isn't the default to use the insertion types of
   those markers?

2. Why isn't there (or is there?) a simple way to
   change the "marker insertion types" of an
   existing overlay?

3. Why, if you pass markers to `make-overlay', and
   you don't pass arg BUFFER, isn't the default to
   use the buffer of those markers?

4. Can you retrieve the markers that are "used by"
   an overlay, i.e., as markers?



  reply	other threads:[~2019-11-17  2:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<20c74b83-6272-44e9-b4ac-829fd4cd0143@default>
     [not found] ` <<<83lfsh2zvf.fsf@gnu.org>
     [not found]   ` <<a2de3d64-2fb6-41e4-aabe-0be2ec404478@default>
     [not found]     ` <<83v9rl12t1.fsf@gnu.org>
2019-11-15 17:32       ` Overlay insertion types, markers, etc Drew Adams
2019-11-17  2:15         ` Richard Stallman
2019-11-17  2:26           ` Drew Adams [this message]
2019-11-17 15:55             ` Stefan Monnier
2019-11-17 17:35               ` Drew Adams
2019-11-20 16:17             ` Richard Stallman
2019-11-20 17:33               ` Eli Zaretskii
2019-11-20 17:38               ` Drew Adams
     [not found] <<20c74b83-6272-44e9-b4ac-829fd4cd0143@default>
     [not found] ` <<83lfsh2zvf.fsf@gnu.org>
2019-11-15 16:54   ` Drew Adams
2019-11-15 17:12     ` Eli Zaretskii
2019-11-12  0:09 Drew Adams
2019-11-13 15:36 ` Drew Adams
2019-11-15 10:33 ` Eli Zaretskii

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=29c934d3-712c-414e-b4aa-9ed8f3c609a2@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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).