unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	schwab@linux-m68k.org, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: update-subdirs and lisp/term
Date: Tue, 29 Sep 2009 11:19:15 +0200	[thread overview]
Message-ID: <78026BA0-5349-4399-9FF5-BD48E08F8638@gmail.com> (raw)
In-Reply-To: <jwvocoxe7y4.fsf-monnier+emacs@gnu.org>


On Sep 26, 2009, at 11:03 PM, Stefan Monnier wrote:

>>>> 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.
>> The CEDET subdirectories will also lack subdirs.el.  In fact, you  
>> agreed
>> to it yourself, as a solution to the 8+3 filename restriction for  
>> CEDET,
>> remember?
>
> BTW, if the Org people want to use a similar trick, I'd be happy to  
> add
> `org' to the list of exceptions that aren't added to load-path (so all
> the files lisp/org/org-foo.el can be renamed lisp/org/foo.el and then
> loaded via (require 'org/foo)).

Nice.  I wish I had known this 2 year ago when I was really
struggling with some of those 8+3 filenames.

For now we are fine, but thanks for the offer.

- Carsten





  reply	other threads:[~2009-09-29  9:19 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
2009-09-26 16:53         ` Chong Yidong
2009-09-26 21:03           ` Stefan Monnier
2009-09-29  9:19             ` Carsten Dominik [this message]
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

  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=78026BA0-5349-4399-9FF5-BD48E08F8638@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=cyd@stupidchicken.com \
    --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 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).