From: Dan Nicolaescu <dann@ics.uci.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@linux-m68k.org, Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: update-subdirs and lisp/term
Date: Sat, 26 Sep 2009 09:45:46 -0700 (PDT) [thread overview]
Message-ID: <200909261645.n8QGjk9R001369@godzilla.ics.uci.edu> (raw)
In-Reply-To: <83r5ttsmq0.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Sep 2009 19:19:03 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
> > Date: Sat, 26 Sep 2009 10:07:34 -0400
> >
> > >> > Does anyone know why we skip lisp/term in update-subdirs?
> > >> Because files in lisp/term are always loaded with the term/ prefix.
> > > Thanks. But why is that a good idea?
> >
> > It reduces the length of load-path and increases our namespace?
>
> But this can be said about any other subdirectory of lisp/, can't it?
>
> > Let me put it another way: why would it be a good idea to put lisp/term
> > in update-subdirs?
>
> To avoid a special case that someone could trip on. Every other
> subdirectory gets subdirs.el created in it, but term does not.
> Imagine that we will want to have subdirectories under term some day.
> Why ask maintainers to use up one more register for remembering this
> factoid, or risk strange failures/bugs?
>
> That said, I won't argue. If the above is not convincing, then so be
> it.
IMHO it's not convincing at all. Let's look at the history, the latest
files added in lisp/term:
term/common-win.el on 2008-07-20 (it's just a refactoring of existing term/*win.el files)
term/ns-win.el on 2008-07-15 -- new port, we don't get these very often, we have 4 total...
term/cygwin.el on 2005-07-22
term/linux.el on 1997-07-04
Based on the past, the probability of something dramatic happening there
is very small, and it can be dealt with at the time it happens.
next prev parent reply other threads:[~2009-09-26 16:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 9:48 update-subdirs and lisp/term Eli Zaretskii
2009-09-26 10:44 ` Andreas Schwab
2009-09-26 11:16 ` Eli Zaretskii
2009-09-26 13:24 ` Andreas Schwab
2009-09-26 16:13 ` Eli Zaretskii
2009-09-26 17:55 ` Andreas Schwab
2009-09-26 18:41 ` Eli Zaretskii
2009-09-26 18:46 ` Andreas Schwab
2009-09-26 20:14 ` Eli Zaretskii
2009-09-26 20:59 ` Andreas Schwab
2009-09-26 21:06 ` Eli Zaretskii
2009-09-26 21:07 ` Andreas Schwab
2009-09-27 7:29 ` Eli Zaretskii
2009-09-27 7:37 ` Andreas Schwab
2009-09-27 10:35 ` Eli Zaretskii
2009-09-27 11:13 ` Andreas Schwab
2009-09-27 12:39 ` Richard Stallman
2009-09-26 21:04 ` Stefan Monnier
2009-09-27 7:28 ` Eli Zaretskii
2009-09-27 18:12 ` Stefan Monnier
2009-09-27 19:09 ` Eli Zaretskii
2009-09-27 22:55 ` Stefan Monnier
2009-09-26 14:07 ` Stefan Monnier
2009-09-26 16:19 ` Eli Zaretskii
2009-09-26 16:45 ` Dan Nicolaescu [this message]
2009-09-26 16:53 ` Chong Yidong
2009-09-26 21:03 ` Stefan Monnier
2009-09-29 9:19 ` Carsten Dominik
2009-09-26 21:01 ` Stefan Monnier
2009-09-28 3:43 ` Richard Stallman
2009-09-28 6:36 ` Eli Zaretskii
2009-09-28 21:58 ` Richard Stallman
2009-09-28 22:10 ` joakim
2009-09-28 22:15 ` Chong Yidong
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=200909261645.n8QGjk9R001369@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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.