From: Richard Stallman <rms@gnu.org>
To: Rocky Bernstein <rocky@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: relative load-file
Date: Sun, 22 Nov 2009 21:29:56 -0500 [thread overview]
Message-ID: <E1NCOge-0000Rl-Jk@fencepost.gnu.org> (raw)
In-Reply-To: <6cd6de210911212045q21a4080bxdb1073b64a4cc5cb@mail.gmail.com> (message from Rocky Bernstein on Sat, 21 Nov 2009 23:45:14 -0500)
First, it seems like a little more work that isn't strictly needed - adding
that file.
That is one file in your entire program, which we assume is so many
files that you have decided to split it into multiple directories.
It is negligible work.
Second, as files move over the course of the lifetime of a project, this
scheme will *always* require changing files more often than what I proposed
. Here is an example based on experience so far.
With file-relative references, any time you move one file,
you have to change all its references to other files,
as well as all other files' references to it.
With main-directory-relative references, when you move a file
between subdirectories, you don't have to change its references
to other files. You only change the way other files refer to it.
Thus, when moving one file, the main-directory-relative approach
always requires less change.
You present a scenario of moving many files together. Indeed, in that
scenario, the file-relative approach avoids the need to change the way
these files refer to each other. But it still requires changing the
way they refer to all other files.
I can't fully follow your scenario because
For now, I find it convenient to split the parts of the Ruby
debugger *rbdgr* into several of files: *rbdbgr-core*, *rbdbgr-track-mode*and
*rbdbgr*
I don't understand the significance of the *'s. Do you write *'s in
file names, or are they wildcards, or what?
Emacs convention is not to use *'s in any names, except for names
of special buffers.
next prev parent reply other threads:[~2009-11-23 2:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 17:01 relative load-file Rocky Bernstein
2009-11-11 18:35 ` Tassilo Horn
2009-11-11 19:26 ` Rocky Bernstein
2009-11-11 19:54 ` Tassilo Horn
2009-11-11 20:17 ` Stefan Monnier
2009-11-11 21:21 ` Rocky Bernstein
2009-11-11 23:06 ` Stefan Monnier
2009-11-12 1:01 ` Rocky Bernstein
2009-11-12 1:20 ` Stefan Monnier
2009-11-12 2:09 ` Rocky Bernstein
2009-11-12 4:22 ` Stefan Monnier
2009-11-12 13:01 ` Rocky Bernstein
2009-11-12 13:52 ` spedrosa
2009-11-12 14:11 ` Andreas Schwab
2009-11-12 15:34 ` Stefan Monnier
2009-11-13 4:34 ` Rocky Bernstein
2009-11-13 14:22 ` Stefan Monnier
2009-11-13 15:03 ` Rocky Bernstein
2009-11-13 16:17 ` Stefan Monnier
2009-11-13 16:39 ` Rocky Bernstein
2009-11-14 11:24 ` Richard Stallman
2009-11-14 15:44 ` Rocky Bernstein
2009-11-15 21:59 ` M Jared Finder
2009-11-18 3:20 ` Stefan Monnier
2009-11-15 22:38 ` Richard Stallman
2009-11-15 23:50 ` Rocky Bernstein
2009-11-18 12:10 ` Richard Stallman
2009-11-18 13:39 ` Rocky Bernstein
2009-11-21 22:52 ` Richard Stallman
2009-11-22 4:45 ` Rocky Bernstein
2009-11-23 2:29 ` Richard Stallman [this message]
2009-11-23 15:04 ` Rocky Bernstein
2009-11-24 14:11 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2009-11-13 5:24 grischka
2009-11-13 5:59 ` Rocky Bernstein
2009-11-13 14:26 ` Stefan Monnier
2009-11-13 15:06 ` Rocky Bernstein
2009-11-09 14:54 rocky
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=E1NCOge-0000Rl-Jk@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rocky@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.