unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: reveal-filename
Date: Tue, 21 May 2013 05:52:47 +0300	[thread overview]
Message-ID: <83mwrpujr4.fsf@gnu.org> (raw)
In-Reply-To: <jwv61ydnlia.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Mon, 20 May 2013 22:02:31 -0400
> 
> >> Could we find some other name for this function?
> > You are welcome to suggest any name you like.  The only semi-important
> > consideration I had in mind was not to have too long a name, so as not
> > to require reformatting of too many lines in Makefile.in files.
> 
> How 'bout `unmsys--filename'?

Fine with me.

> >> "Produce the real file name for FILE" isn't sufficiently descriptive
> >> to decide when it's buggy and when it's not.
> > That's unfair: the doc string does explain what this function does.
> > You quoted only the first line of the doc string.
> 
> I didn't mean to criticize, sorry.  I just mean that a function with
> such a "clean" name should have a "clean" specification of what it
> should do, at a higher level than describing its current behavior under
> various OSes.  I don't think coming up with such a description is easy,
> but I suspect it's not needed either and a less clean name (such as the
> one O suggested above) would work just fine.

The description that's already there is all there is to tell:

    "Produce the real file name for FILE.

  On systems other than MS-Windows, just returns FILE.
  On MS-Windows, converts /d/foo/bar form of file names
  passed by MSYS Make into d:/foo/bar that Emacs can grok.

  This function is called from lisp/Makefile."

What did you find missing from this description?



  reply	other threads:[~2013-05-21  2:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 21:28 reveal-filename Stefan Monnier
2013-05-18  8:11 ` reveal-filename Eli Zaretskii
2013-05-21  2:02   ` reveal-filename Stefan Monnier
2013-05-21  2:52     ` Eli Zaretskii [this message]
2013-05-21  5:26       ` reveal-filename Stefan Monnier
2013-05-21  6:28         ` reveal-filename Stephen J. Turnbull
2013-05-21 16:22           ` reveal-filename Eli Zaretskii
2013-05-22  2:46             ` reveal-filename Stephen J. Turnbull
2013-05-21 16:19         ` reveal-filename Eli Zaretskii
2013-05-21 16:20         ` reveal-filename Eli Zaretskii
2013-05-21 19:37           ` reveal-filename Stefan Monnier
2013-05-25  7:21           ` reveal-filename Eli Zaretskii
2013-05-26  4:49             ` reveal-filename Richard Stallman

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=83mwrpujr4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).