unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Subject: Re: file-truename, convert-standard-filename
Date: Tue, 9 Feb 2010 16:32:55 -0500	[thread overview]
Message-ID: <d2afcfda1002091332m5eb0836cid437277702490ad@mail.gmail.com> (raw)
In-Reply-To: <d2afcfda1002091330y53017b24w5e6bdf3c3d131a97@mail.gmail.com>

On Sun, Feb 7, 2010 at 11:10 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> (require 'foo)
>>
>> Which is the string of the filename referenced in the above form?
>
> As Andreas points out, rather than looking at a small portion of the
> doc string, why don't you read it in its entirety?  The answer to your
> question is there.
>

FWIW the string quoted is what appears in apropos... which is why i
referenced it as such.

None the less, the FEATURE 'foo is not a filename and does not
designate the optional arg FILENAME.
In the docstring of `require' FILENAME is an optional argument.

In the example above the feature 'foo is a quoted symbol. There is no
second arg FILENAME.

Is the second arg implicit by virtue the ``printname of FEATURE''?

(print 'foo (current-buffer))

Where is the string?

The reality is that  behind the scenes Emacs is interpolating the
symbol FEATURE to a filename string which corresponds; _not_
necessarily to FILENAME the arg. On the face of it this does not make
them one and the same. Rather the opposite actually. My point is only
that Emacs does not always make a clear distinction between files as
objects and files as strings.

Or am I misinterpreting what occurs?

/s_P\




  parent reply	other threads:[~2010-02-09 21:32 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06  3:52 file-truename, convert-standard-filename MON KEY
2010-02-06  8:28 ` Eli Zaretskii
     [not found]   ` <d2afcfda1002061814nc3e178fl5d93e21ea6bae7b5@mail.gmail.com>
2010-02-07  2:16     ` MON KEY
     [not found]     ` <83wrypelms.fsf@gnu.org>
2010-02-07 23:26       ` MON KEY
2010-02-08  0:28         ` Andreas Schwab
2010-02-08  4:10         ` Eli Zaretskii
     [not found]           ` <d2afcfda1002091330y53017b24w5e6bdf3c3d131a97@mail.gmail.com>
2010-02-09 21:32             ` MON KEY [this message]
2010-02-09 21:59               ` Andreas Schwab
2010-02-09 22:32             ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2010-02-05 17:31 Drew Adams
2010-02-05 18:15 ` Andreas Schwab
2010-02-05 18:33   ` Lennart Borgman
2010-02-05 19:45     ` Andreas Schwab
2010-02-05 19:49       ` Lennart Borgman
2010-02-05 20:14     ` Stefan Monnier
2010-02-05 20:18       ` Lennart Borgman
2010-02-06  1:10       ` Miles Bader
2010-02-05 23:51   ` Drew Adams
2010-02-05 19:04 ` Eli Zaretskii
2010-02-05 23:51   ` Drew Adams
2010-02-06  0:17     ` Lennart Borgman
2010-02-06  8:45       ` Eli Zaretskii
2010-02-06 16:55         ` Lennart Borgman
2010-02-06 19:12           ` Eli Zaretskii
2010-02-06 19:20             ` Lennart Borgman
2010-02-06  9:01     ` Eli Zaretskii
2010-02-06 15:33       ` Drew Adams
2010-02-06 19:33         ` Eli Zaretskii
2010-02-06 20:46           ` Drew Adams
2010-02-06 21:58             ` Eli Zaretskii
2010-02-06 23:12               ` Drew Adams
2010-02-07  4:01                 ` Eli Zaretskii
2010-02-08  1:38                 ` Stefan Monnier
2010-02-08  2:46                   ` Drew Adams
2010-02-26 18:33                 ` Davis Herring
2010-02-26 19:12                   ` Drew Adams
2010-02-26 19:35                     ` Davis Herring
2010-02-26 20:25                       ` Drew Adams

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=d2afcfda1002091332m5eb0836cid437277702490ad@mail.gmail.com \
    --to=monkey@sandpframing.com \
    --cc=emacs-devel@gnu.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).