From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Docstring of make-symbolic-link Date: Mon, 10 Jun 2019 21:44:46 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="178103"; mail-complaints-to="usenet@blaine.gmane.org" To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 10 21:47:32 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 1haQGS-000kDt-5b for ged-emacs-devel@m.gmane.org; Mon, 10 Jun 2019 21:47:32 +0200 Original-Received: from localhost ([::1]:49282 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haQGR-00065k-7j for ged-emacs-devel@m.gmane.org; Mon, 10 Jun 2019 15:47:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59240) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haQEi-00065b-JY for emacs-devel@gnu.org; Mon, 10 Jun 2019 15:45:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1haQEb-0000Hr-SM for emacs-devel@gnu.org; Mon, 10 Jun 2019 15:45:41 -0400 Original-Received: from mail-qt1-x82d.google.com ([2607:f8b0:4864:20::82d]:33389) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1haQEb-0000By-Ns for emacs-devel@gnu.org; Mon, 10 Jun 2019 15:45:37 -0400 Original-Received: by mail-qt1-x82d.google.com with SMTP id x2so10917334qtr.0 for ; Mon, 10 Jun 2019 12:45:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=TwwvJk7vvfFQ8Uz0X0Jx/iE3ExJpmRczd9LDW/67mew=; b=TmjT9Ta3YtMsl9SsA/Xo98QpqEB8zYo5Hq/ZLFsCh0M4Nv3jJmvJsZv91c7KWzRb2W wEsjRHaWsk1vixe4I9uUzrPQEYpumuFL7IvuHEDUVBar0hr+NcWoPVRkJvd1pgdgIsB6 emF+cYNqv9PIsFHU0LTclc59RDxmJXeWRp1d788rv0UkYu+NvpZtRcI5X0Dv1AyXg1X9 PgVKK4XVjmaC57SIz0XjQ2PhPaQDvelYHysPhLbyHYaTlc9ofQFxIm6sHQdwMuEym3d3 PVZkOTDFkYn6MWqd835NdMe/aGYkwBnTZGqD8ALzGBRiC1jd2xCdQ5j0knrC6tRyzLyd 22CA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TwwvJk7vvfFQ8Uz0X0Jx/iE3ExJpmRczd9LDW/67mew=; b=NjbsMTYd2AVLM9thcW0GXAE25cs+ikN5e/PKFP/Gvh4bo9VOe/65v/DchVzvecR9Dc jznEmhAaOrjWrQOnWuxR54YcSgRFhEkANQF2VJn/cj6Y68bA0lebJN5eGrcqp/vnrxAX lKRmrImCVeWDgP6OgffbFrBxha2Zkw6BUwaVNfG9vGUrBrHBYLs7SufJepCq2G45f2Fr UhBX7M7WDDqwcKCUfsScYhX9Wr2cdr9OAlTaniMv+o78gnJM+XL85He/VEirhz9DPNWV 1EgvTnSJlkSJQrfpsgKn99TqEaH4gazPvJL02dNQzxvsudyN668KFVDyESEhcXigh3Ae ECTQ== X-Gm-Message-State: APjAAAU8coX/5ZdQyd1vZ+17R4U8wywP+vFBCEjPZ/Rsi83ZIdy13YPA Cce8EYuDbPgla/WqjyI9rFvCPaA9AmjiFbqSoDlpUxyKdKE= X-Google-Smtp-Source: APXvYqx/X9nMlRH8s3Auvar2qD/FzGG+A69HQfrQM3QLMJYai0TgbqFe4hz0ziXDK1+E7gTPRqtgnC7oGIDJN6apRJY= X-Received: by 2002:a0c:b5ad:: with SMTP id g45mr58799541qve.231.1560195922530; Mon, 10 Jun 2019 12:45:22 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::82d 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:237424 Archived-At: make-symbolic link uses NEWNAME in its docstring, but LINKNAME as the argument name: (make-symbolic-link TARGET LINKNAME &optional OK-IF-ALREADY-EXISTS) Make a symbolic link to TARGET, named NEWNAME. If NEWNAME is a directory name, make a like-named symbolic link under NEWNAME. [etc...] The easiest way to fix it is to change NEWNAME to LINKNAME in the docstring, but I think NEWNAME is the preferred name, and it is also used in the info files. The alternative is to change linkname to newname in the code, and encoded_linkname to encoded_newname (not required, but for consistency). It is a trivial change, but as it touches code in 26.2.50, better safe than sorry. So, newname everywhere, or linkname everywhere (including the info files)?