[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: toggling a minor mode should not tell Customize that the value has b
From: |
Richard Stallman |
Subject: |
Re: toggling a minor mode should not tell Customize that the value has been set |
Date: |
Sun, 06 Jan 2008 05:46:51 -0500 |
This means that if you so much as toggle a global minor mode, and you later
use `customize-customized' to see which options you have edited and set, the
minor mode variable shows up in the list of customized options.
I think this was done deliberately to make the interaction with Custom
smoother. Otherwise Custom would say it was "changed outside of
Custom" and it would make users worry.
- Re: toggling a minor mode should not tell Customize that the value has been set, (continued)
- Re: toggling a minor mode should not tell Customize that the value has been set, Stefan Monnier, 2008/01/06
- RE: toggling a minor mode should not tell Customize that the value has been set, Drew Adams, 2008/01/06
- Re: toggling a minor mode should not tell Customize that the value has been set, Stefan Monnier, 2008/01/06
- RE: toggling a minor mode should not tell Customize that the value has been set, Drew Adams, 2008/01/06
- Re: toggling a minor mode should not tell Customize that the value has been set, Stefan Monnier, 2008/01/06
- Re: toggling a minor mode should not tell Customize that the value has been set, martin rudalics, 2008/01/06
- RE: toggling a minor mode should not tell Customize that the value has been set, Drew Adams, 2008/01/06
- Re: toggling a minor mode should not tell Customize that the value has been set, Stefan Monnier, 2008/01/06
- Re: toggling a minor mode should not tell Customize that the value has been set, martin rudalics, 2008/01/07
- Re: toggling a minor mode should not tell Customize that the value has been set, Richard Stallman, 2008/01/07
Re: toggling a minor mode should not tell Customize that the value has been set,
Richard Stallman <=