unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: bojohan+news@dd.chalmers.se (Johan Bockgård)
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Lisp manual issues regarding overlays, display properties, margins, etc.
Date: Mon, 08 Oct 2007 14:04:15 -0400	[thread overview]
Message-ID: <E1Iewxj-0004V5-8N@fencepost.gnu.org> (raw)
In-Reply-To: <yoijbqbhh551.fsf@gamma02.me.chalmers.se> (bojohan+news@dd.chalmers.se)

    > That seems like a bug to me.  It seems to me that a property that puts
    > something in the margin should not alter the appearance of the text
    > it is on.
    >
    > Does anyone think the current behavior is desirable?

    In any case, it follows the documentation

Two parts of the Lisp manual seem to conflict with each other.  It
would be straightforward to fix the one that doesn't agree with the
code.  I will do that.  But is there a good reason for the current
behavior?

    Maybe there should be a margin property (distinct from the current
    margin display spec) which specifies material to go in the margin
    (like the way the overlay before-string property works).

We don't want to make another property, because each kind of property
that display needs to check for slows it down.

But we could make another kind of margin display specification
that combines the effect of before-string and margin.
That would do what users would naturally expect.

  reply	other threads:[~2007-10-08 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86d4w2y1ej.fsf@macs.hw.ac.uk>
2007-10-02 15:29 ` Emacs Lisp manual issues regarding overlays, display properties, margins, etc Richard Stallman
2007-10-02 16:07   ` Johan Bockgård
2007-10-08 18:04     ` Richard Stallman [this message]
2007-10-02 16:23   ` Joe Wells
2007-10-02 19:20     ` Stefan Monnier
2007-10-03 18:38       ` Richard Stallman

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=E1Iewxj-0004V5-8N@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bojohan+news@dd.chalmers.se \
    --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 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).