From: Simon Josefsson <jas@extundo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Fringes again
Date: Tue, 21 May 2002 22:53:01 +0200 [thread overview]
Message-ID: <ilu661hdxzm.fsf@latte.josefsson.org> (raw)
In-Reply-To: <877klyie6t.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "21 May 2002 08:37:14 +0900")
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
Miles Bader <miles@gnu.org> writes:
> Simon Josefsson <jas@extundo.com> writes:
>> I'm not sure if there was any consensus in the last discussion, but at
>> least there were some voices that wanted it to be possible to disable
>> the fringes from the menu (I remember Richard said it at least).
>>
>> So, how about if I commit this?
>
> Um, please no. You appear to have ignored most of the arguments.
Were there more than in this mail?
> The menu entries are probably uncontroversial because they allow
> choosing from a set of different styles.
OK.
> However, you've retained the simple toggling version of `M-x fringe-mode',
> and there seemed to be a reasonable concensus that the M-x command
> shouldn't just turn off the fringes, but rather should do something like
> prompt for a fringe style. There were several good ideas presented.
>
> Why not implement one of those?
I never understood exactly how the ideas were supposed to work, but
I've now implemented one approach below. It makes the user interface
of fringe.el similar as mouse-avoidance-mode.el. Is this OK?
> Another criticism is that you define a command called `toggle-fringe'
> who's distinguishing feature is (apparently) that it only affects the
> current frame -- if this is the case, it should probably reflect that in
> the command name.
>
> Granted there are plenty of functions that only affect the current frame,
> but don't have a name that says so, but it really is a bad idea to define
> two `similar' commands, one affecting all frames, and the other affecting
> only the current one, and to distinguish between them only by choosing two
> different-but-apparently-equivalent names.
It is consistent with how `toggle-scroll-bar' and `scroll-bar-mode'
already behaves. The docstring and the prompt triggered by invoking
`toggle-fringe' and `fringe-mode' should now be clear. Is this OK, or
can you suggest alternative names?
[-- Attachment #2: fringe.el --]
[-- Type: application/emacs-lisp, Size: 5321 bytes --]
next prev parent reply other threads:[~2002-05-21 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 20:03 Fringes again Simon Josefsson
2002-05-20 23:37 ` Miles Bader
2002-05-21 19:12 ` Richard Stallman
2002-05-21 20:53 ` Simon Josefsson [this message]
2002-05-21 21:40 ` Thien-Thi Nguyen
2002-05-22 8:20 ` Simon Josefsson
2002-05-22 1:24 ` Miles Bader
2002-05-22 3:21 ` Eli Zaretskii
2002-05-22 3:40 ` Miles Bader
2002-05-22 8:54 ` Simon Josefsson
2002-05-24 0:07 ` Miles Bader
2002-05-24 9:47 ` Simon Josefsson
2002-05-24 23:00 ` Kim F. Storm
2002-05-24 23:48 ` Simon Josefsson
2002-05-25 23:06 ` Kim F. Storm
2002-05-25 23:15 ` Simon Josefsson
2002-05-21 15:57 ` 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=ilu661hdxzm.fsf@latte.josefsson.org \
--to=jas@extundo.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).