From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Emacs Survey: Toolbars Date: Thu, 17 Dec 2020 09:06:02 -0800 (PST) Message-ID: <81fd6785-f9b5-4926-9363-1d63f8672599@default> References: <87o8iv3ac3.fsf@gnus.org> <838s9zavcx.fsf@gnu.org> <87im92nmd6.fsf@gnus.org> <83y2hx91u1.fsf@gnu.org> <87czz9enc6.fsf@gmail.com> <83sg858yjr.fsf@gnu.org> <878s9wetdb.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20149"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Robert Pluim , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 17 18:26:21 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kpx2h-00055k-TT for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Dec 2020 18:26:19 +0100 Original-Received: from localhost ([::1]:44456 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpx2g-0002ki-Pl for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Dec 2020 12:26:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36502) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpwjH-0001jI-Rb for emacs-devel@gnu.org; Thu, 17 Dec 2020 12:06:16 -0500 Original-Received: from aserp2120.oracle.com ([141.146.126.78]:48662) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpwjD-0004k2-WB; Thu, 17 Dec 2020 12:06:15 -0500 Original-Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 0BHGxxEZ141453; Thu, 17 Dec 2020 17:06:05 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2020-01-29; bh=AdCPXxc7Xyxs21Nvv4DpY1a0jAXkUg5y40GYhv5+SJM=; b=Z0t4ihU40/1mX57m+W1ik+r/VU0whYv2JllhFobagJvZcE/LtWScVAaViyEe6NxiQPs2 BNsycZ/feSh7RR2UCl9l3rxwkYHQ5vnLwYgKLz7oiQBT8kAUIPeGixb0hJnTF1x15cu1 EOrTMkvuiGrNMVeT05sBTkd04u8rPgREmk5fEp9ugcu6z8mECq10RzPjLzyFPImIyztj f/A1kLNGfqZiEKgAmZOUeVJKH8xYvFEhVL3QcQDokCCBNPDnU+JAYqZLj5kBEA3lsxQx Z0rpkKg7wAenLkVnI0nEJPCX5Z6R859hSQUcJMyXgEaqQw85BTheWdNWlIYYRITjvs6E Fg== Original-Received: from aserp3020.oracle.com (aserp3020.oracle.com [141.146.126.70]) by aserp2120.oracle.com with ESMTP id 35cntmeekr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 17 Dec 2020 17:06:05 +0000 Original-Received: from pps.filterd (aserp3020.oracle.com [127.0.0.1]) by aserp3020.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 0BHH5D4c097280; Thu, 17 Dec 2020 17:06:05 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserp3020.oracle.com with ESMTP id 35e6etjv07-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 17 Dec 2020 17:06:05 +0000 Original-Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id 0BHH63j0028941; Thu, 17 Dec 2020 17:06:03 GMT In-Reply-To: <878s9wetdb.fsf@gmail.com> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.5071.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9838 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 mlxscore=0 phishscore=0 bulkscore=0 suspectscore=0 malwarescore=0 mlxlogscore=999 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2012170118 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9838 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 phishscore=0 mlxscore=0 lowpriorityscore=0 spamscore=0 adultscore=0 malwarescore=0 suspectscore=0 mlxlogscore=999 impostorscore=0 priorityscore=1501 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2012170117 Received-SPF: pass client-ip=141.146.126.78; envelope-from=drew.adams@oracle.com; helo=aserp2120.oracle.com X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:261125 Archived-At: > >> Should we take this opportunity to either auto-save config changes > >> made via the menus, or put a big red button somewhere saying 'click > >> here to save settings', or prompt the user to save them when exiting? > > > > What's wrong with Options->Save Options? >=20 > Nothing, except that people have been conditioned to expect that > changes in options get saved automatically,=20 I assume you mean _some_ people. > so we could do that for > them if they make the changes via the menus. On a related note, perhaps > 'save options' should be the last entry in the Options menu, to make > it stand out more. If some more than a few people really do expect setting (option) changes to be saved automatically, then we could add an option (!) (or a minor mode) that does that. Turn on that option, and thereafter all changes you make to options, faces, themes, etc. get saved automatically. Note that that behavior can get in the way of user experimentation. Not that it's necessarily limiting - it's just a different approach. In sum, if we want to support automatic saving of every setting change then we should do so optionally (and opt-in), not just switch to that for everyone.