From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: Re: line-move-visual Date: Fri, 10 Jul 2009 11:13:24 +0200 Message-ID: References: <200907092112.21879.jem@iki.fi> <87ws6hupsk.fsf@bzg.ath.cx> <87ocrtulzd.fsf@bzg.ath.cx> <87tz1lja6l.fsf@bzg.ath.cx> <83ocrsykx7.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1247217236 24626 80.91.229.12 (10 Jul 2009 09:13:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 10 Jul 2009 09:13:56 +0000 (UTC) Cc: handa@m17n.org, emacs-devel@gnu.org, bastienguerry@googlemail.com, jem@iki.fi, Scot Becker , miles@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 10 11:13:48 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MPCAs-0006oW-FF for ged-emacs-devel@m.gmane.org; Fri, 10 Jul 2009 11:13:46 +0200 Original-Received: from localhost ([127.0.0.1]:33415 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPCAr-0000us-P8 for ged-emacs-devel@m.gmane.org; Fri, 10 Jul 2009 05:13:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPCAn-0000uk-C7 for emacs-devel@gnu.org; Fri, 10 Jul 2009 05:13:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPCAj-0000si-SF for emacs-devel@gnu.org; Fri, 10 Jul 2009 05:13:41 -0400 Original-Received: from [199.232.76.173] (port=60152 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPCAj-0000sZ-Lp for emacs-devel@gnu.org; Fri, 10 Jul 2009 05:13:37 -0400 Original-Received: from iwfs.imcode.com ([82.115.149.64]:54324 helo=gate.verona.se) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MPCAg-00053H-BJ; Fri, 10 Jul 2009 05:13:34 -0400 Original-Received: from localhost.localdomain (IDENT:1005@localhost [127.0.0.1]) by gate.verona.se (8.13.4/8.11.4) with ESMTP id n6A9DODs009972; Fri, 10 Jul 2009 11:13:24 +0200 In-Reply-To: <83ocrsykx7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jul 2009 11:57:56 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:112288 Archived-At: Eli Zaretskii writes: >> Date: Fri, 10 Jul 2009 09:43:37 +0100 >> From: Scot Becker >> Cc: miles@gnu.org, emacs-devel@gnu.org, jem@iki.fi, >> Kenichi Handa >> >> Discoverability is key. This could be done through a customize >> interface, as Stephen suggests or simply through a piece of startup >> documentation called "Things you might want to tweak." > > We already have a feature that is close to that: > > Options->Customize Emacs->New Options > > It asks for an old version, and presents a Customize buffer with all > options changed or introduced since that version. > It would be nice to have something similar to the "skinnability feature" some other applications have. It would make use of Custom, and would allow to group together Customizable features in a coherent theme. So, the default for "line visual" would be nil in the "emacs oldtimer" skin, and t in "emacs newbie" skin. There would also be a "Windoze for the w*n" skin that would have cua defaults, etc. Just as the "emacs->new options" feature, the skin feature would keep track of defaults that are new in this particular emacs for this particular skin. It would also keep track of for which options the user has decided to diverge from the customize options from the default. The feature could also support trying out different themes. Also purely cosmetical options like those supported by "color-theme" should be provided. -- Joakim Verona