all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 6931@debbugs.gnu.org
Subject: bug#6931: 24.0.50; fringe-mode
Date: Thu, 28 Apr 2016 00:48:27 +0200	[thread overview]
Message-ID: <87lh3yr7lw.fsf@gnus.org> (raw)
In-Reply-To: <1222E80F95BD4AF9835A8848BC30F17D@us.oracle.com> (Drew Adams's message of "Fri, 27 Aug 2010 15:50:32 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> Command `fringe-mode' is not normal.  It does not act as a normal mode
> command.  And its variable, `fringe-mode', does not act as a normal mode
> variable.  This is not good for users or for Lisp coders.  If you are
> going to keep this behavior, then do not use "-mode" in the name at all
> - call it `fringe-mess' or something instead.
>
> Code that tests a mode variable should be able to treat a value of nil
> as meaning that the mode is turned off.  In this case, that would mean
> there is no fringe.  Not so, however.
>
> If you want the value of variable `fringe-mode' to provide the fringe
> width also, then 0 and nil should give the same info: fringe is not
> shown.  If you want a special value that means "the default width", then
> use the symbol `default' or something - do not use nil to mean a default
> width of 8.
>
> This command and its variable are a mess.

Yes, it's pretty confusing.  Perhaps the `fringe-mode' command should be
renamed to `choose-fringe-state' or something?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2016-04-27 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 22:50 bug#6931: 24.0.50; fringe-mode Drew Adams
2016-04-27 22:48 ` Lars Ingebrigtsen [this message]
2021-06-03  8:20   ` Lars Ingebrigtsen

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=87lh3yr7lw.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=6931@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.