From: Miles Bader <miles@gnu.org>
To: eric@siege-engine.com
Cc: Eli Zaretskii <eliz@gnu.org>,
zappo@gnu.org, cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Filename problem in CEDET merge
Date: Fri, 28 Aug 2009 20:27:38 +0900 [thread overview]
Message-ID: <buoocq0w53p.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <1251458160.31028.44.camel@projectile.siege-engine.com> (Eric M. Ludlam's message of "Fri, 28 Aug 2009 07:16:00 -0400")
"Eric M. Ludlam" <eric@siege-engine.com> writes:
>> > (provide 'hack/fooble)
....
>> > (require 'hack/fooble)
>> >
>> > and Emacs finds it and loads it. This could be a magic way to have
>> > "long" file names on DOS. Just providing 'fooble won't work.
>>
>> This might work for `require', but I don't think it will work for
>> `load' (e.g., in ~/.emacs).
>
> Load still works with my example, as:
>
> (load "hack/fooble")
This is excellent -- it seems to work great when I tried it for
load/require/provide. It seems a _much_ better method for shortening
filenames than the "painfully contrived cryptic abbreviations" method
we've used previously.
In addition, it actually makes the source tree look better: Redundant
prefixes on every file in a package are ugly even when the filesystem
can deal with the extra length, but I thought they were required to make
require/provide work -- but as you point out, maybe not...!
If we're going to group all the files for a package in a subdirectory
anyway, why not take advantage of that structure?
-Miles
--
o The existentialist, not having a pillow, goes everywhere with the book by
Sullivan, _I am going to spit on your graves_.
next prev parent reply other threads:[~2009-08-28 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 22:50 Filename problem in CEDET merge Chong Yidong
2009-08-28 2:26 ` Eric M. Ludlam
2009-08-28 9:45 ` Eli Zaretskii
2009-08-28 11:16 ` Eric M. Ludlam
2009-08-28 11:27 ` Miles Bader [this message]
2009-08-28 13:33 ` Eli Zaretskii
2009-08-28 13:55 ` Eric M. Ludlam
2009-08-28 14:06 ` Eli Zaretskii
2009-08-28 14:58 ` Chong Yidong
2009-08-28 15:23 ` Chong Yidong
2009-08-28 15:46 ` Andreas Schwab
2009-08-28 15:26 ` Stefan Monnier
2009-08-28 9:42 ` Eli Zaretskii
2009-08-28 15:23 ` Stefan Monnier
2009-08-28 12:14 ` Leo
2009-08-28 13:44 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buoocq0w53p.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
--cc=zappo@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.