From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.devel Subject: Re: Some ideas with Emacs Date: Fri, 29 Nov 2019 12:16:28 +0100 Message-ID: <87d0dbszjn.fsf@mbork.pl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="148186"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: mu4e 1.1.0; emacs 27.0.50 Cc: emacs-devel To: Anonymous Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 29 12:55:22 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iaerq-000cO8-H9 for ged-emacs-devel@m.gmane.org; Fri, 29 Nov 2019 12:55:22 +0100 Original-Received: from localhost ([::1]:57824 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iaero-0005wB-NM for ged-emacs-devel@m.gmane.org; Fri, 29 Nov 2019 06:55:21 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57225) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iaeGR-00056h-62 for emacs-devel@gnu.org; Fri, 29 Nov 2019 06:16:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iaeGN-0001z9-PA for emacs-devel@gnu.org; Fri, 29 Nov 2019 06:16:40 -0500 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:59154) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iaeGN-0001mc-GI for emacs-devel@gnu.org; Fri, 29 Nov 2019 06:16:39 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id B059AE680E; Fri, 29 Nov 2019 12:16:35 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dCp6ftw11eER; Fri, 29 Nov 2019 12:16:32 +0100 (CET) Original-Received: from localhost (83.25.100.175.ipv4.supernova.orange.pl [83.25.100.175]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 1480AE62F7; Fri, 29 Nov 2019 12:16:32 +0100 (CET) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.110.48.8 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242865 Archived-At: On 2019-11-29, at 10:05, Anonymous wrote: > Hi, I'm a user and a fanatical fans for Emacs. I'd like to share a few id= eas for about Emacs Lisp. > Emacs Lisp is powerful, it's undeniable. But when I studied Emacs Li= sp, I found that there were too few examples of function use in the tutoria= l. Also when using Emacs Lisp for Emacs plugin development and configu= ration, Sometimes you write your own plugins will affect the configura= tion you write, so I'd like to make a few ideas for Emacs Lisp: > First, suggest to add more examples of functions in the tutorial, most fo= r Emacs Lisp Reference Manual, which can lower the learning threshold. I had a plan to write an intermediate book on Elisp, but Real Life=E2=84=A2 intervened. I still have the stuff I managed to write, and if I live long enough, I'm going to get back to this project (the current plan is late 2020 - I'm finishing work on another book now, which is long overdue, and I cannot postpone it more because it is a joint work with two other people). Would you be interested? What would you like to see in such a book? (The idea was - and is - to start approximately where Robert Chassell's "Elisp Intro" ends.) > Second, in developing the Emacs plugins, create a virtual environment, li= ke Python virtualenv, so that we can test the plugin in the virtual environ= ment so that we do not need to affect the configuration outside the virtual= environment. That's can implement plugin development environment and confi= guration isolation. > > Although my suggestion may be a little trivial and even useless. But= if my suggestions can help beginners like me go further, I think it's wort= h it. AFAIK, this is _far_ from trivial. However, you can always start a fresh Emacs instance with -Q. For more advanced configs, you may start a fresh Emacs instance with the config directory in /tmp or whatever. (Shameless plug: I blogged about it a few weeks ago, see http://mbork.pl/2019-11-04_Starting_Emacs_with_custom_configuration_directo= ry.) Now that I think of it, we could even have an Emacs command to start a fresh Emacs instance with a given file already loaded. WDYT? Hth, -- Marcin Borkowski http://mbork.pl