unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 28258@debbugs.gnu.org, Mohammed Sadiq <sadiq@sadiqpk.org>
Subject: bug#28258: 26.0.50; [PATCH] Let file-name-base succeed when buffer-file-name is nil
Date: Tue, 19 Sep 2017 08:31:29 +0000	[thread overview]
Message-ID: <CAArVCkS0MYLt+CRhauDz_iTDUmgs0gSgyvtWa06j-3Bo6XKfSQ@mail.gmail.com> (raw)
In-Reply-To: <fid16nv7sf.fsf@fencepost.gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 321 bytes --]

Glenn Morris <rgm@gnu.org> schrieb am Di., 19. Sep. 2017 um 02:41 Uhr:

>
> > I do agree that the calling convention of `file-name-base' is odd. How
> > about making the argument mandatory (initially only by changing the
> > advertised calling convention and the docstring)?
>
> Sounds good to me.
>

OK, here's a patch.

[-- Attachment #1.2: Type: text/html, Size: 620 bytes --]

[-- Attachment #2: 0001-lisp-files.el-file-name-base-Make-FILENAME-argument-ma.txt --]
[-- Type: text/plain, Size: 1311 bytes --]

From 8ab66b54afdc02aca90a4c51a426205ac024ff05 Mon Sep 17 00:00:00 2001
From: Philipp Stephani <phst@google.com>
Date: Tue, 19 Sep 2017 10:29:42 +0200
Subject: [PATCH] * lisp/files.el (file-name-base): Make FILENAME argument
 mandatory.

---
 etc/NEWS      | 3 +++
 lisp/files.el | 4 ++--
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/etc/NEWS b/etc/NEWS
index 371cdf686c..de93ae84fa 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -43,6 +43,9 @@ When you add a new item, use the appropriate mark if you are sure it applies,
 \f
 * Incompatible Lisp Changes in Emacs 27.1
 
+** The FILENAME argument to 'file-name-base' is now mandatory and no
+longer defaults to 'buffer-file-name'.
+
 \f
 * Lisp Changes in Emacs 27.1
 
diff --git a/lisp/files.el b/lisp/files.el
index c55c8097c1..fe7cb1a8a9 100644
--- a/lisp/files.el
+++ b/lisp/files.el
@@ -4479,8 +4479,8 @@ file-name-extension
             "")))))
 
 (defun file-name-base (&optional filename)
-  "Return the base name of the FILENAME: no directory, no extension.
-FILENAME defaults to `buffer-file-name'."
+  "Return the base name of the FILENAME: no directory, no extension."
+  (declare (advertised-calling-convention (filename) "27.1"))
   (file-name-sans-extension
    (file-name-nondirectory (or filename (buffer-file-name)))))
 
-- 
2.14.1


  reply	other threads:[~2017-09-19  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28  2:22 bug#28258: 26.0.50; [PATCH] Let file-name-base succeed when buffer-file-name is nil Mohammed Sadiq
2017-08-29 15:54 ` Glenn Morris
2017-08-29 16:10   ` Mohammed Sadiq
2017-08-29 17:02     ` Glenn Morris
2017-09-18 17:12       ` Philipp Stephani
2017-09-19  0:41         ` Glenn Morris
2017-09-19  8:31           ` Philipp Stephani [this message]
2017-09-19  8:46             ` Philipp Stephani
2017-09-24  8:07               ` Philipp Stephani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAArVCkS0MYLt+CRhauDz_iTDUmgs0gSgyvtWa06j-3Bo6XKfSQ@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=28258@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    --cc=sadiq@sadiqpk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).