From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Fringes
Date: Mon, 03 Oct 2005 01:09:35 -0400 [thread overview]
Message-ID: <E1EMIZz-0005gM-3e@fencepost.gnu.org> (raw)
In-Reply-To: <17215.42381.148191.71003@kahikatea.snap.net.nz> (message from Nick Roberts on Sun, 2 Oct 2005 22:17:01 +1300)
If a buffer uses the default left fringe width, the variable
left-fringe-width is nil while the function window-fringes returns
information about the fringes of a window. So there appears to be
no way to determine the fringe width of a buffer that is not
currently displayed.
What does it mean to speak of the "fringe width of a buffer that is
not currently displayed"?
If it means the fringe width that would be in effect if that buffer is
displayed in a window, then if left-fringe-width is nil in that
buffer, it should use the default. So couldn't you just use the
default value?
That ought to be easy, so if you think this problem is hard, perhaps I
have missed the point.
Anyway, your changes in the Lisp Manual look good.
Please install them.
next prev parent reply other threads:[~2005-10-03 5:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 9:17 Fringes Nick Roberts
2005-10-03 5:09 ` Richard M. Stallman [this message]
2005-10-03 5:27 ` Fringes Nick Roberts
2005-10-03 16:13 ` Fringes Richard M. Stallman
[not found] <72A87F7160C0994D8C5A36E2FDC227F501FB5475@txnexc01.americas.cpqcorp.net>
2002-05-17 17:35 ` fringes Chuck Bernard
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 21:11 fringes Bingham, Jay
2002-05-16 21:36 ` fringes Chuck Bernard
2002-05-15 22:08 fringes Chuck Bernard
2002-05-16 12:51 ` fringes G Anna
2002-05-17 17:04 ` fringes Oliver Scholz
2002-05-17 16:12 ` fringes Chuck Bernard
2002-05-17 16:57 ` fringes Greg Hill
2002-05-17 17:32 ` fringes Eli Zaretskii
2002-05-18 11:35 ` fringes Luis O. Silva
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=E1EMIZz-0005gM-3e@fencepost.gnu.org \
--to=rms@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.