From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: DWIM region (was: Re: count regexp hits) Date: Tue, 09 Jan 2018 07:20:41 +0100 Organization: Aioe.org NNTP Server Message-ID: <86373fr1s6.fsf@zoho.com> References: <86shbmcldx.fsf@zoho.com> <86d12pcvgj.fsf@zoho.com> <86d12pb988.fsf_-_@zoho.com> <86a7xqupz0.fsf@zoho.com> <86h8rxtmj3.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1515479032 30642 195.159.176.226 (9 Jan 2018 06:23:52 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 9 Jan 2018 06:23:52 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 09 07:23:48 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eYnK7-0007cF-1K for geh-help-gnu-emacs@m.gmane.org; Tue, 09 Jan 2018 07:23:47 +0100 Original-Received: from localhost ([::1]:59578 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eYnM6-0008KC-KE for geh-help-gnu-emacs@m.gmane.org; Tue, 09 Jan 2018 01:25:50 -0500 Original-Path: usenet.stanford.edu!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 75 Original-NNTP-Posting-Host: zRXoCvQ6k9fneBfYPnB6lQ.user.gioia.aioe.org Original-X-Complaints-To: abuse@aioe.org Mail-Copies-To: never Cancel-Lock: sha1:kuEwpX54X1bQK2qEFbfhuJIzZ9I= X-Notice: Filtered by postfilter v. 0.8.2 Original-Xref: usenet.stanford.edu gnu.emacs.help:221510 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:115627 Archived-At: Marcin Borkowski wrote: >>> 1. Lack of space after `let*'. This is so >>> one can change `let' into `let*' and back >>> without moving anything else. Personally, >>> I wouldn't mind just one "let" which would >>> be equal to `let*', as legend has it the >>> supposed parallelism of `let' is an urban >>> legend, however now when it is like it is >>> it would be confusing (to other people) to >>> always use `let*' when there is no reason >>> to, even tho there is equally little/as >>> much reason to use plain `let'... > > Well, for me, `let*' is an indication that > `let' is not enough. But it's a minor point, > agreed. I don't know about relative > efficiency of both. Yes, that is the indication we are used to see. So that is why it has to be used like that (it makes sense to use it like that) even tho technically it doesn't matter because there is no parallelism lost in `let' when using `let*'. So one could use `let*' all the time and not have to think about it and not have the bug/confusion when one changes something but forgets to change the asterisk. This is what I've heard; I haven't browsed the C source myself if anyone wants to look for the lost parallelism. But my bet it'll be even more difficult to find than the proverbial microchip in the supercomputer... > Well, that is really strange. Could you > explain the reason for this space being there > and not somewhere else? (yes (it is based) (on what happens on each line) ) > Well, it's not standard, I'd think. And for > me, `indentation' is at the bol, this I'd > call `alignment'. Alignment of code is a part of indentation. > And again, I do understand the reason, I just > don't like this style. It's not something I'm > accustomed to. The reason is to group items, for example artefacts, relics, treasures, wierd magical materia, and other things that are on the same level, together, to increase "seeing" and decrease "reading". PS. If anyone looking at the above example without understanding it might be you have a mail client/newsreader that messes that up. If so, this is your luckiest computer day of 2018 so far, as that should be *disabled* first thing and then never touched upon again, ever. -- underground experts united http://user.it.uu.se/~embe8573