From: Miles Bader <miles@gnu.org>
Subject: Re: Customize fringe
Date: 10 May 2002 03:48:37 +0900 [thread overview]
Message-ID: <87helh5f96.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <ilu3cx1jk9z.fsf@extundo.com>
Simon Josefsson <jas@extundo.com> writes:
> Either you have a fringe or you don't. Same as menubar and toolbar.
> Size, content, color etc is additional configuration. IMHO. But I
> see your point.
My point was that, unlike menus or toolbars, people will _usually_ want to
do something besides turning fringes entirely on or off (presuming they
want to do anything at all), and that as a result, having `fringe-mode' +
adjustments is the wrong user-interface to this functionality.
Note that this is unlike the closest analogue (I think), scrollbars --
it's common for people to want to simply turn scrollbars on or off, but
the scrollbar location is merely a detail.
I expect a common case for the fringes, though will to be to want to
toggle between full-fringes and right-side-only. This simply doesn't map
well to the name `fringe-mode'.
As to what the right interface is, I'm not really sure; I guess it depends
a lot on what people want to do with the fringes (personally, I think
they're fine, though I might want to use half/half if we could get it to
use some alternate bitmaps for that case).
> Of course, the Options->Show/Hide submenu should have a "Fringe"
> submenu similar to the scroll-bar, with common choices.
That's a much better user-interface than `fringe-mode'.
> If I didn't preload it, my fringes didn't go away when I started
> emacs. I had to (require 'fringe). Maybe I did something wrong? It
> looks similar to tool-bar-mode, scroll-bar-mode etc though.
That sort of detail should be taken care of by the dependencies in your
defcustoms. [e.g., with the :require parameter]
-Miles
--
97% of everything is grunge
next prev parent reply other threads:[~2002-05-09 18:48 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 [this message]
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
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=87helh5f96.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@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).