From: Nick Roberts <nickrob@snap.net.nz>
Subject: Fringes
Date: Sun, 2 Oct 2005 22:17:01 +1300 [thread overview]
Message-ID: <17215.42381.148191.71003@kahikatea.snap.net.nz> (raw)
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. I've noticed this problem because
gdb-ui.el uses window-fringes in gdb-put-breakpoint-icon. Since the speedbar
now has no left fringe, if I expand the display of a watch expression in the
speedbar (an array, say), the breakpoint icon shifts from the fringe to the
display margin (because window-fringes uses the selected window by default,
the speedbar in this case).
Nick
Here's a suggestion/correction for the Fringes section of the lisp
manual.
(caution if applying diff - remove line with ^^^^^^)
*** display.texi.~1.188.~ 2005-10-01 00:57:51.000000000 +1200
--- display.texi 2005-10-02 21:55:21.174050936 +1300
***************
*** 2730,2752 ****
@node Fringe Size/Pos
@subsection Fringe Size and Position
! Here's how to control the position and width of the window fringes.
@defvar fringes-outside-margins
! If the value is non-@code{nil}, the frames appear outside the display
^^^^^^
! margins. The fringes normally appear between the display margins and
! the window text. It works to set @code{fringes-outside-margins}
! buffer-locally. @xref{Display Margins}.
@end defvar
@defvar left-fringe-width
This variable, if non-@code{nil}, specifies the width of the left
! fringe in pixels.
@end defvar
@defvar right-fringe-width
This variable, if non-@code{nil}, specifies the width of the right
! fringe in pixels.
@end defvar
The values of these variables take effect when you display the
--- 2730,2754 ----
@node Fringe Size/Pos
@subsection Fringe Size and Position
! The following buffer-local variables control the position and width
! of the window fringes.
@defvar fringes-outside-margins
! The fringes normally appear between the display margins and the window
! text. If the value is non-@code{nil}, they appear outside the display
! margins. @xref{Display Margins}.
@end defvar
@defvar left-fringe-width
This variable, if non-@code{nil}, specifies the width of the left
! fringe in pixels. A value of @code{nil} means to use the left fringe
! width from the window's frame.
@end defvar
@defvar right-fringe-width
This variable, if non-@code{nil}, specifies the width of the right
! fringe in pixels. A value of @code{nil} means to use the right fringe
! width from the window's frame.
@end defvar
The values of these variables take effect when you display the
next reply other threads:[~2005-10-02 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 9:17 Nick Roberts [this message]
2005-10-03 5:09 ` Fringes Richard M. Stallman
2005-10-03 5:27 ` Fringes Nick Roberts
2005-10-03 16:13 ` Fringes Richard M. 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=17215.42381.148191.71003@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
/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).