From: storm@cua.dk (Kim F. Storm)
Subject: Re: Customize fringe
Date: 12 May 2002 01:44:41 +0200 [thread overview]
Message-ID: <5xk7qa45cm.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <ilu3cwzqc8c.fsf@latte-eth2-dhcp128.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> storm@cua.dk (Kim F. Storm) writes:
>
> > Simon Josefsson <jas@extundo.com> writes:
> >
> >> What do you think of this?
> >
> > I would like you to wait implementing anything like this.
> > It is on my TODO list to make fringe configurable
> > per buffer/window rather than per frame.
> >
> > Something like variables left-margin-width / right-margin-width
> > and functions set-window-margin / window-margin.
> >
> > Once that is in place, various modes may fine-tune their
> > use of the fringe (e.g. gdb may explicitly enable the left
> > fringe for the arrow, and speedbar may turn off both fringes
> > by default).
>
> Hm. Aren't these separate issues? Fine tuning for each mode would
> require per buffer fringes. But the overall customization by the user
> to disable fringes works if default-frame-alist and all existing
> frames are modified. If the fine tuning exist, it can override the
> frame wide decision not to have fringes.
Can it? Should it?
If you think of this as similar to the menu-bar, I don't think we
have any major modes which turns on the menu bar if the user has
turned it off (and likewise with the scroll-bar).
So will it be acceptable to have a non-standard behaviour for fringes
where major (or minor) modes override the user's choice?
I would prefer to have per-buffer fringes controlled by a per-mode
alist -- then you (as a user) will be able to add e.g. fundamental-mode
and text-mode to that alist with option "no fringes".
That's less intrusive than simply turning off the fringe for all modes.
IMO it is a bad idea to remove the left fringe in e.g. C buffers, as
it is used by gdb-mode if you debug that C program/module.
However, I don't object to adding "Fringe" to the Show/Hide menu -- as
long as it is understood that it only controls the default settings
for the fringes. I think the options should be: Both/Left/Right/None.
>
> My main goal is that it should not be very difficult for the user to
> just disable fringes everywhere, much like you can disable the toolbar
> and menubar everywhere today. Fine tuning is useful for re-enabling
> fringes in those modes where the user wants them, but couldn't that be
> added to fringe.el later?
>
Yes.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-05-11 23:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 12:05 Customize fringe Simon Josefsson
2002-05-09 12:28 ` Miles Bader
2002-05-09 17:36 ` Simon Josefsson
2002-05-09 18:48 ` Miles Bader
2002-05-09 19:46 ` Simon Josefsson
2002-05-10 1:32 ` Miles Bader
2002-05-10 6:52 ` Eli Zaretskii
2002-05-10 7:23 ` Miles Bader
2002-05-10 9:40 ` Kim F. Storm
2002-05-10 11:07 ` Robert J. Chassell
2002-05-10 11:08 ` Robert J. Chassell
2002-05-10 10:44 ` Robert J. Chassell
2002-05-10 12:17 ` Eli Zaretskii
2002-05-10 13:37 ` Robert J. Chassell
2002-05-13 2:16 ` Miles Bader
2002-05-11 6:31 ` Richard Stallman
2002-05-11 8:04 ` Simon Josefsson
2002-05-09 18:07 ` Eli Zaretskii
2002-05-09 18:35 ` Stefan Monnier
2002-05-09 19:39 ` Simon Josefsson
2002-05-09 21:18 ` Stefan Monnier
2002-05-09 22:13 ` Simon Josefsson
2002-05-09 22:24 ` Simon Josefsson
2002-05-11 8:16 ` Pavel Janík
2002-05-11 9:14 ` Simon Josefsson
2002-05-11 10:13 ` Eli Zaretskii
2002-05-11 12:24 ` Simon Josefsson
2002-05-11 23:28 ` Kim F. Storm
2002-05-11 6:31 ` Richard Stallman
2002-05-09 23:31 ` Kim F. Storm
2002-05-11 9:12 ` Simon Josefsson
2002-05-11 23:44 ` Kim F. Storm [this message]
2002-05-11 23:11 ` Simon Josefsson
2002-05-12 4:49 ` Eli Zaretskii
2002-05-12 9:51 ` Simon Josefsson
2002-05-12 10:06 ` Eli Zaretskii
2002-05-12 10:30 ` Simon Josefsson
2002-05-12 12:37 ` Eli Zaretskii
2002-05-13 14:18 ` Richard Stallman
2002-05-10 0:29 ` 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=5xk7qa45cm.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
/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).