From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: File modes facilities.
Date: Mon, 24 Oct 2005 09:41:43 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEOJCNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87veznaveb.fsf-monnier+emacs@gnu.org>
> Yes, slightly. But if your file name starts with / or ~
> (i.e. is an absolute file name, as is the default for `load-file'
> because of its default initial value) then the difference is
minimal.
> I guess I still don't understand. I see this difference in completion
> behavior - do you not?
> Go to a directory that is not in your load-path. M-x load-library
> will not complete the name of an Emacs-Lisp file in that
> directory... M-x load-file will complete its name.
Which part of "starts with / or ~" don't you understand?
I didn't understand that you meant for the user to _type_ the absolute file
name. I thought you were somehow speaking of the default path used for
completion. Sorry.
Yes, if you type the directory explicitly and absolutely (no `../', `./',
`~/'), then `load-library' will complete in that directory. My point was
that, without doing that, they complete differently - they use different
paths (directories).
It's like saying that we can do without the use of relative file names
(chic!), because one can always type an absolute file name - IIUC.
> I see the default for `load-file' being an absolute file name
> that is in the default-directory. I see it completing to any
> file in that directory. I don't see `load-library' doing that
> at all - I see `load-library' completing only wrt the `load-path'.
As I said, the initial value (empty string for load-library,
default-directory for load-file) is the main difference.
But if you type in the default directory manually in load-library the
completion facilities will then work pretty much as they do in
load-file.
Coming back to the initial suggestion by RMS of making `load-file' just an
alias to `load-library', I repeat my preference:
I think it's good to have these two different kinds of completion
(that is, two different commands), even though the aim in both
cases is to load a Lisp file, and both will accept an absolute
file name as argument.
IOW, `load-file' offers the convenience of using the `default-directory', by
default, and inputting a relative filename. Why give up that convenience?
Why make people type an absolute filename?
It's a lot easier to navigate a directory tree using relative file names
(with, e.g., `../' and `~/'). If the user's intent is to load a file, then
the `load-file' UI is made to order, and the `load-library' UI presents an
unnecessary obstacle (= entering an absolute name). Imagine if you had no
`cd' command in shell, and had to type (even with completion, from `/') an
absolute path for each file name - that's what it would be like, IIUC.
next prev parent reply other threads:[~2005-10-24 16:41 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 20:09 File modes facilities Michael Cadilhac
2005-10-19 20:35 ` Stefan Monnier
2005-10-19 21:28 ` Michael Cadilhac
2005-10-19 22:19 ` Nick Roberts
2005-10-19 22:44 ` Michael Cadilhac
2005-10-19 22:48 ` Kim F. Storm
2005-10-19 22:57 ` Edward O'Connor
2005-10-19 23:00 ` Michael Cadilhac
2005-10-20 9:04 ` Eli Zaretskii
2005-10-20 10:41 ` Michael Cadilhac
2005-10-20 11:51 ` Romain Francoise
2005-10-20 12:41 ` Eli Zaretskii
2005-10-20 14:18 ` Michael Cadilhac
2005-10-20 16:15 ` Stefan Monnier
2005-10-20 22:16 ` Kim F. Storm
2005-10-21 3:21 ` Stefan Monnier
2005-10-21 8:44 ` Andreas Schwab
2005-10-21 12:59 ` Michael Cadilhac
2005-10-21 14:14 ` Miles Bader
2005-10-21 14:43 ` Kim F. Storm
2005-10-21 16:42 ` Michael Cadilhac
2005-10-21 22:19 ` Richard M. Stallman
2005-10-24 14:02 ` Kim F. Storm
2005-10-24 14:16 ` David Kastrup
2005-10-24 16:02 ` Andreas Schwab
2005-10-24 21:00 ` Kim F. Storm
2005-10-24 14:46 ` Stefan Monnier
2005-10-24 22:14 ` Kim F. Storm
2005-10-24 23:02 ` Stefan Monnier
2005-10-25 8:51 ` Kim F. Storm
2005-10-25 20:29 ` Richard M. Stallman
2005-10-25 15:58 ` Richard M. Stallman
2005-10-25 21:34 ` Kim F. Storm
2005-10-26 8:52 ` Kim F. Storm
2005-10-27 1:31 ` Richard M. Stallman
2005-10-27 1:29 ` Richard M. Stallman
2005-10-21 10:58 ` Kim F. Storm
2005-10-21 11:05 ` Kim F. Storm
2005-10-21 15:07 ` Stefan Monnier
2005-10-21 17:51 ` Richard M. Stallman
2005-10-21 18:43 ` Stefan Monnier
2005-10-22 4:18 ` Richard M. Stallman
2005-10-22 5:39 ` Drew Adams
2005-10-22 6:17 ` Miles Bader
2005-10-22 6:32 ` Drew Adams
2005-10-22 7:33 ` Miles Bader
2005-10-22 7:45 ` Drew Adams
2005-10-23 18:05 ` Stefan Monnier
2005-10-23 18:27 ` Drew Adams
2005-10-24 13:37 ` Richard M. Stallman
2005-10-24 13:40 ` Stefan Monnier
2005-10-24 16:41 ` Drew Adams [this message]
2005-10-24 16:59 ` Stefan Monnier
2005-10-24 17:13 ` Drew Adams
2005-10-20 23:38 ` Richard M. Stallman
2005-10-21 0:58 ` Michael Cadilhac
2005-10-21 1:06 ` Miles Bader
2005-10-21 1:24 ` Michael Cadilhac
2005-10-21 17:51 ` Richard M. Stallman
2005-10-23 23:42 ` Michael Cadilhac
2005-10-24 14:09 ` Kim F. Storm
2005-10-25 15:58 ` Richard M. Stallman
2005-10-20 1:42 ` Kevin Ryde
2005-10-20 2:01 ` Miles Bader
2005-10-20 7:12 ` Michael Cadilhac
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=DNEMKBNJBGPAOPIJOOICGEOJCNAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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).