all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Overlay insertion types, markers, etc.
Date: Wed, 20 Nov 2019 11:17:04 -0500	[thread overview]
Message-ID: <E1iXSfA-0003iI-SE@fencepost.gnu.org> (raw)
In-Reply-To: <29c934d3-712c-414e-b4aa-9ed8f3c609a2@default> (message from Drew Adams on Sat, 16 Nov 2019 18:26:39 -0800 (PST))

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

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

I don't think I ever thought about the question back then.

Did pointers even have insertion types, back when overlays were first
introduced?

However, the function calling convention would have to bec omplex
to give you three options: yes, no, or inherit from the marker.

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

I never thought of adding it.

  > 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?

I never thought about it.

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

If you could get at them, you could change their buffer positions.
I think that would mess up the overlay sort order and cause bugs.
You could also put them in another buffer  and cause even worse trouble.

-- 
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2019-11-20 16:17 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
2019-11-17 15:55             ` Stefan Monnier
2019-11-17 17:35               ` Drew Adams
2019-11-20 16:17             ` Richard Stallman [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1iXSfA-0003iI-SE@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.