From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Adam Porter Newsgroups: gmane.emacs.devel Subject: Re: Do shorthands break basic tooling (tags, grep, etc)? (was Re: Shorthands have landed on master) Date: Thu, 30 Sep 2021 08:18:33 -0500 Message-ID: <87h7e2qk0m.fsf@alphapapa.net> References: <16338bdc2497fc51c6fb6d54ab370bfb@webmail.orcon.net.nz> <831r59kyhf.fsf@gnu.org> <834ka4k15m.fsf@gnu.org> <83y27gijmz.fsf@gnu.org> <87sfxmgqvd.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17664"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 30 15:21:15 2021 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 1mVvzu-0004KL-CA for ged-emacs-devel@m.gmane-mx.org; Thu, 30 Sep 2021 15:21:14 +0200 Original-Received: from localhost ([::1]:41092 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mVvzs-0004RQ-Sh for ged-emacs-devel@m.gmane-mx.org; Thu, 30 Sep 2021 09:21:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33016) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVvxU-0001V7-RT for emacs-devel@gnu.org; Thu, 30 Sep 2021 09:18:44 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:57134) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVvxT-0001g3-FD for emacs-devel@gnu.org; Thu, 30 Sep 2021 09:18:44 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mVvxR-0000ua-LS for emacs-devel@gnu.org; Thu, 30 Sep 2021 15:18:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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:275892 Archived-At: Joost Kremers writes: > As Gregory points out, there is a package that does this already. It actually > has another issue, which is that indentation is sometimes wrong. If the second > argument of a function is on a separate line, it's indented to align with the > first argument. This position depends on the length of the prefix of the > function name: > > ``` > (somelongprefix-do-something arg1 > arg2) > ``` > > The nameless package can align `arg2` so that it matches up with `arg1`, but > unlike the shortening of the prefix, that indentation is saved to the file. > Not dramatic, but it can occasionally be annoying. FWIW, this is a dramatically annoying problem that has prevented me from using Nameless. :) Either the code is indented incorrectly while I'm editing it with Nameless activated, or it's indented incorrectly in the saved file. And having incorrect indentation is more annoying than longer symbols, for me. Since I usually use aggressive-indent-mode for my Elisp projects, I once tried to use hooks to automatically reindent a file with full symbol names before saving, and restore the abbreviated view and indentation afterward, but I couldn't make it work smoothly (IIRC, buffers always indicated that they were modified after having saved them and reactivated the mode, which was an even bigger problem for usability). If this issue could be solved, it could be as Phil said: user-local symbol abbreviations that are transparent to everything else.