all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: dhruva <dhruvakm@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Build failure on M$ (using MSVC): Patch enclosed
Date: Thu, 22 May 2008 09:32:50 +0200	[thread overview]
Message-ID: <85d4nelrod.fsf@lola.goethe.zz> (raw)
In-Reply-To: <e3f230850805220010i5a7e5804jedda4ac23e19d9e9@mail.gmail.com> (dhruva's message of "Thu, 22 May 2008 12:40:59 +0530")

dhruva <dhruvakm@gmail.com> writes:

> Hi,
> On 5/22/08, David Kastrup <dak@gnu.org> wrote:
>> There is no necessity whatsoever to use the settings file mechanism for
>>  global defaults.  Just set the appropriate variables in site-start.el.
>
> The locate-dominating-file restricts me to see in folders that are in
> the hierarchy of my HOME folder only.

No, it doesn't.

> At work, I have my home folder at a different mount point and
> development tree in a different mount point. They do not share the
> same tree apart from the root '/'. If I (and other users) need to have
> default settings for the build tree, I would put it in the mount
> folder of the build tree. With the recent changes, it will never see
> is as the tree does not share my HOME.

Have you actually _tried_ it?

> Ex:
> Build dir:
> /mnt/dev/build/users/dhruva/branch/...
> Home:
> /u/users/dhruva
>
> Using "site-start.el" will affect all users, this will not provide me
> the fine grained control that I will get using the folder structure.

Your previous example was about affecting all users, and
locate-dominating-file works perfectly well with the current example.

locate-dominating-file stops the traversal when it would pass from
within $HOME to outside, or when the traversal would change the owner of
the directory.  But it does not require the traversal to start within
$HOME or elsewhere.

> I use a similar thing for my BASH shell. Every directory I need to
> change some values (like CVSROOT for different projects) will have a
> local.bashrc which gets sources once I visit it. I use this traversal
> back to find the most appropriate local.bashrc and find it quite
> useful.

Could you _please_ provide a test case which you actually tried out and
which does not work as desired before complaining?

I can't see this to be the case right now.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum




  reply	other threads:[~2008-05-22  7:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  4:58 Build failure on M$ (using MSVC): Patch enclosed dhruva
2008-05-20  6:10 ` dhruva
2008-05-20  8:26   ` dhruva
2008-05-20  8:58     ` dhruva
2008-05-20  9:46       ` Jason Rumney
2008-05-20 10:21         ` David Kastrup
2008-05-20 11:57           ` dhruva
2008-05-20 12:01             ` dhruva
2008-05-20 18:26       ` Eli Zaretskii
2008-05-20 12:11     ` Herbert Euler
2008-05-20 18:30       ` Eli Zaretskii
2008-05-20 18:12 ` Eli Zaretskii
2008-05-21  3:13   ` dhruva
2008-05-21 17:28     ` Stefan Monnier
2008-05-22  3:51       ` dhruva
2008-05-22  4:46         ` Stefan Monnier
2008-05-22  5:03           ` dhruva
2008-05-22  6:52             ` David Kastrup
2008-05-22  7:10               ` dhruva
2008-05-22  7:32                 ` David Kastrup [this message]
2008-05-22 15:49                 ` Stefan Monnier
2008-05-22 15:45               ` Stefan Monnier
2008-05-22  6:56             ` dhruva
2008-05-23  8:30               ` Eli Zaretskii
2008-05-23  9:15                 ` Jason Rumney
2008-05-22  8:32         ` Jason Rumney
2008-05-22  9:10           ` dhruva
2008-05-22  9:29             ` dhruva
2008-05-22 12:31               ` Jason Rumney
2008-05-22 13:10                 ` Jason Rumney
2008-05-22 13:33                   ` Miles Bader

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=85d4nelrod.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=dhruvakm@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.