unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Two new entries in menu-bar's Tools menu
Date: Sat, 16 Feb 2002 14:56:00 -0700 (MST)	[thread overview]
Message-ID: <200202162156.g1GLu0x09942@aztec.santafe.edu> (raw)
In-Reply-To: <rjbserq943.fsf@ssv2.dina.kvl.dk> (message from Per Abrahamsen on Fri, 15 Feb 2002 12:26:20 +0100)

    >     Also note, that flyspell-mode is not customizable option. 
    >
    > That seems like a bug to me.  Could you make it customizable?

    It is already an option for text-mode-hook, like turn-on-auto-fill
    is. 

turn-on-auto-fill is a function, not an option, so I am confused
and not sure what you meant to say.

    It is very conceptually very similar to auto-fill-mode as it only
    makes sense in text-mode derivatives.  

Auto Fill mode can be used in programming language modes; it is not
for Text mode derivatives only.  Maybe Flyspell mode makes sense in
some other modes, too.  But you are right that they are similar cases
and both mainly used in text modes.

So I think the Options menu should probably have an item that controls
use of Flyspell mode in Text derivatives, just as it has one that
controls use of Auto Full in Text derivatives.

    Hmm.. Should toggle-text-mode-auto-fill be made a customize option?
    And maybe rename it to global-auto-fill-mode?  It could be implemented
    with custom :get and :set methods.

Maybe, but I wonder: is it possible to provide a more general
customization facility for controlling minor mode enablement
in various major modes?  That might provide a very clean way
to customize where you do or don't want Auto Fill, or Flyspell,
or whatever.


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  parent reply	other threads:[~2002-02-16 21:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 19:46 Two new entries in menu-bar's Tools menu Eli Zaretskii
2002-02-13 21:32 ` Kim F. Storm
2002-02-14  7:22   ` Pavel Janík
2002-02-14  9:49     ` Per Abrahamsen
2002-02-15 10:36       ` Richard Stallman
2002-02-15 11:26         ` Per Abrahamsen
2002-02-15 22:33           ` Stefan Monnier
2002-02-16 21:56           ` Richard Stallman [this message]
2002-02-17 10:10             ` Per Abrahamsen
2002-02-17 22:50               ` Richard Stallman
2002-02-15 10:36     ` Richard Stallman
2002-02-14 10:17   ` Eli Zaretskii
2002-02-14 12:46 ` Richard Stallman
2002-02-14 15:33   ` Eli Zaretskii
2002-02-14 16:24     ` Per Abrahamsen
2002-02-14 16:27       ` Eli Zaretskii
2002-02-14 16:56         ` Per Abrahamsen
2002-02-14 17:08           ` Eli Zaretskii
2002-02-14 16:31       ` Eli Zaretskii
2002-02-15  1:31         ` Miles Bader
2002-02-15 20:27       ` Richard Stallman
2002-02-17 12:20         ` Per Abrahamsen
2002-02-17 22:50           ` 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=200202162156.g1GLu0x09942@aztec.santafe.edu \
    --to=rms@gnu.org \
    --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).