unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: how to tell what's in the fringe?  (lazy fringe)
Date: Fri, 19 Jun 2009 11:45:02 +0900	[thread overview]
Message-ID: <buoocslt00h.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <23168F61416544D98791D6E70AFF9027@us.oracle.com> (Drew Adams's message of "Thu, 18 Jun 2009 11:30:25 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:
> So my thought was to code up some lazy fringe: a fringe that would not show,
> except when there is some non-blank glyph in it. But I don't know how to test
> whether that condition is satisfied (e.g. in Lisp).
>
> Is that even logical? Perhaps if a fringe is not shown then its
> content is empty or undefined? I was thinking in terms of it having
> content that is simply not shown, but maybe that's incorrect.

Many of the fringe indicators are very dynamic, and only known in
relation to a particular redisplay.  Morever, the presence of the fringe
can change the physical dimensions of the area available for redisplay.

If there's a particular less-dynamic indicator you're interested in,
then perhaps it reflects a condition that can be tested for more easily
in lisp code.

-Miles

-- 
Inhumanity, n. One of the signal and characteristic qualities of humanity.




  reply	other threads:[~2009-06-19  2:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 18:30 how to tell what's in the fringe? (lazy fringe) Drew Adams
2009-06-19  2:45 ` Miles Bader [this message]
2009-06-19 16:24   ` Drew Adams
2009-06-19 20:52     ` Miles Bader
2009-06-19 21:39       ` Drew Adams
2009-06-19 22:24         ` Miles Bader
2009-06-19 22:42           ` Drew Adams
2009-06-19 23:29             ` Miles Bader
2009-06-19 23:33               ` Drew Adams

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=buoocslt00h.fsf@dhlpc061.dev.necel.com \
    --to=miles@gnu.org \
    --cc=drew.adams@oracle.com \
    --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).