From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Proposal to change naming format to allow package-prefix/function-name Date: Tue, 31 Dec 2019 18:54:48 +0800 Message-ID: <87sgl0u5mv.fsf@localhost> References: <87imlxjr46.fsf@alphapapa.net> <87h81gdco8.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="25498"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen , Adam Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 31 11:57:38 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 1imFDW-0006SK-9H for ged-emacs-devel@m.gmane.org; Tue, 31 Dec 2019 11:57:38 +0100 Original-Received: from localhost ([::1]:41194 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imFDP-0000LH-UB for ged-emacs-devel@m.gmane.org; Tue, 31 Dec 2019 05:57:31 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37217) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1imFCv-0008M8-IZ for emacs-devel@gnu.org; Tue, 31 Dec 2019 05:57:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1imFCu-0006hB-2j for emacs-devel@gnu.org; Tue, 31 Dec 2019 05:57:01 -0500 Original-Received: from mail-yw1-xc2b.google.com ([2607:f8b0:4864:20::c2b]:43483) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1imFCt-0006dH-Qr for emacs-devel@gnu.org; Tue, 31 Dec 2019 05:56:59 -0500 Original-Received: by mail-yw1-xc2b.google.com with SMTP id v126so15124359ywc.10 for ; Tue, 31 Dec 2019 02:56:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=zT9TrO1NCCSkqckks9GpEEm6A9jsyuuxO3ivzkC/kV4=; b=Q408f9nC0SLCN91u+fOUdeS/BDtSvTnz2t9geIA1czUOyucug1r48yVtaYBpuKq1Sb QlknwC22U2x4aZ0mn0BGVnPlyvM5LH85MFQfszENFvHxcCtGdanyvXHf3AR0MiNI0EOu fZUPhGxsrBHxMz5MEn7YIsIq+S3nGkMawMGuTMmlBa6kHdV2jtwAI1vPzA+AvCS0vxBt dC+RMumk6Zs/hH9z6g67Te52Hcv4omGEarKEgJgu3jjVR4ak09zjQX9PVbZXRToC7rpG 9TMzrDEpXJ+7AMvgCbCaQ6pa0aRZbUZmBOgl+aitVmFUPA5vFz/YxXznr7/KQbUEHAtQ 3jgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=zT9TrO1NCCSkqckks9GpEEm6A9jsyuuxO3ivzkC/kV4=; b=lQ8VC0wLf0HsAHuVU59ecSNkVmMyW9Exk3YQnJCEugOw+JuPw1qICZTykQ9HTi5CHJ YwMdKowH0HJl8gPds6tuxkIgo28/7Z44rxd7+94eZ2YNyfoiTVumTsw/P0oGe0STeCx5 HRh9yJjPEAvXyOWOJeBGhGzXbZqjI6bO8m2+PqzYSNDytpZGT0RQttTK3JD94TFdTfWG F4yruZ/mZbTd+if8Qite/KvirkFFZHfDffzJD1xt5V6ETpz2P9M2poTi/DYu/EzjrVhJ ssmbf3htuvpNWlZQBX9qRI6m2GVjbjdWQjYx94Hq2bF+qKuTZzdzt+rLI2lQOlwXIfVi dKdA== X-Gm-Message-State: APjAAAVRgICgJbZDJOaBmV/vgzq5tUtvmNTEfaIfDHgmfR7DixbiCnDW Gci0WlZXfz1mrqrDLed8+yE= X-Google-Smtp-Source: APXvYqzVcgOpIgOlKA5gZVjPbv/+K0oSNQZzJNoyl+rO4cwRLVpJjIMKfIpyXpDVS4nVHmhHsGmuyA== X-Received: by 2002:a81:6385:: with SMTP id x127mr32333147ywb.468.1577789818821; Tue, 31 Dec 2019 02:56:58 -0800 (PST) Original-Received: from localhost ([5.226.137.4]) by smtp.gmail.com with ESMTPSA id e185sm19647775ywa.33.2019.12.31.02.56.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 31 Dec 2019 02:56:58 -0800 (PST) In-Reply-To: <87h81gdco8.fsf@gnus.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::c2b 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:243801 Archived-At: > ... I always find myself having to try all the variations to find the > correct symbol, because what my brain remembers is "foo bar zot", and > not whatever is in between those letters. > foo:bar-zot? foo-bar:zot? foo:bar/zot? I support this point. It will indeed be a problem for vanilla Emacs completion users. Let me propose an alternative solution. The proposal is trying to solve the problem of distinguishing the package name from function name. Why not just highlight the feature name in the completion buffer? Emacs knows which `provide` (if any) corresponds to every function anyway. Best, Ihor Lars Ingebrigtsen writes: > Adam Porter writes: > >> Whatever the character used, as long as it's visually distinctive and >> easy to type, I think it would be helpful to both users and developers >> to allow it to be used to separate the package/feature name from the >> rest of the symbol name. > > I don't. In Common Lisp, it's a functional thing, and it's easy to > remember that foo:bar-zot is a thing, but in Emacs Lisp, where it would > just be a character that's not sounded when you read the symbol, it's > just confounding. In the past, when working on Emacs Lisp code bases > where somebody has been creative with non-letter characters, I always > find myself having to try all the variations to find the correct symbol, > because what my brain remembers is "foo bar zot", and not whatever is in > between those letters. > > foo:bar-zot? foo-bar:zot? foo:bar/zot? > > -- > (domestic pets only, the antidote for overdose, milk.) > bloggy blog: http://lars.ingebrigtsen.no > -- Ihor Radchenko, PhD, Center for Advancing Materials Performance from the Nanoscale (CAMP-nano) State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg