From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Scot Becker Newsgroups: gmane.emacs.devel Subject: Re: line-move-visual Date: Fri, 10 Jul 2009 11:22:47 +0100 Message-ID: References: <200907092112.21879.jem@iki.fi> <87ws6hupsk.fsf@bzg.ath.cx> <87ocrtulzd.fsf@bzg.ath.cx> <87tz1lja6l.fsf@bzg.ath.cx> <87prc8ucfq.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1247221436 4078 80.91.229.12 (10 Jul 2009 10:23:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 10 Jul 2009 10:23:56 +0000 (UTC) Cc: Bastien , emacs-devel@gnu.org, jem@iki.fi, Kenichi Handa To: Miles Bader Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 10 12:23:49 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 1MPDGd-0002t2-MI for ged-emacs-devel@m.gmane.org; Fri, 10 Jul 2009 12:23:48 +0200 Original-Received: from localhost ([127.0.0.1]:44644 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPDGc-0000f1-V3 for ged-emacs-devel@m.gmane.org; Fri, 10 Jul 2009 06:23:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPDFp-0000JL-DN for emacs-devel@gnu.org; Fri, 10 Jul 2009 06:22:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPDFk-0000E5-19 for emacs-devel@gnu.org; Fri, 10 Jul 2009 06:22:56 -0400 Original-Received: from [199.232.76.173] (port=35036 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPDFj-0000Dp-Ag for emacs-devel@gnu.org; Fri, 10 Jul 2009 06:22:51 -0400 Original-Received: from mail-fx0-f215.google.com ([209.85.220.215]:59316) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MPDFh-0003n1-7T; Fri, 10 Jul 2009 06:22:49 -0400 Original-Received: by fxm11 with SMTP id 11so819407fxm.42 for ; Fri, 10 Jul 2009 03:22:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=qOFu2cp9A9R5bpi1TCM+KqGrjoXiC6LQKinVAxyBCsM=; b=n0gGO/Uu5+bRlzLXadKO+0sZu045nr/v8Vg/fXcN+sIzC+bwK7jIv/DEGjmw6XDdt2 5gyzNjb2UTvMLPq2vy49VPJ1EnbQ1+Uwbsk4cEMlvFyhQMgXZroTLyKaEfPiSkrMz2xe Ra96t1IJ0jQgyUgzjKAznz9ir40zDfXrzbzr8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KiFzBkup2PAJOuR+WeE2ZgSXaLAnpcTkWnEjRy5hZMuSCnBW17xhhPueNgMSi7oP2o WQi94mo4L2VlDX9uu7YaefH6Hsq2cuhGPAN2c0pBi7Ew4quPZUMtCwTwuxhOjIh3+o0H 0nWO6g2LfbMv6LdQodL4cbrp/kKn5StV3BQZU= Original-Received: by 10.204.60.133 with SMTP id p5mr1709304bkh.143.1247221368116; Fri, 10 Jul 2009 03:22:48 -0700 (PDT) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:112295 Archived-At: by Miles: ...simple themed customization groups ("get off my lawn", "windows luser", ...), which present focused groups of settings for the user to tweak at his pleasure Sure, that'd be great. And fair enough with 'coaching users through incremental changes' rather than 'changing a raft of things in one fell swoop'. A few helpful additions would be that (1) there would be a way for users to create such customization groups for distribution to other users. They wouldn't be hard-coded, like today's customization groups (apparently are). And (2) ideally there'd be the opportunity to optionally include extended user documentation in amongst the variables to give guidance beyond what one might find in the docstrings. The docstrings can be a bit minimal if what you want to do is explain the significance of various choices to a user who is only now encountering some new concept lying behind a variable. Lastly, it would be nice to have a way for such customization groups to specify: "If external library X is available, customize variable ext-lib-X-groovy, and fail gracefully if not ("If you had optional package X loaded, you would also be able to customize these variables here:") This way it would be useful for the present purpose, as well as for package writers who want to draw attention to a set of variables whose interaction with their package the user might want to consider. It could also be useful for my "Emacs for writers" config-file disto, and someone else's "Emacs for coders in functional languages" config-distro, etc. And your names are great (get off my lawn and windows luser). Scot