From: dhruva <dhruvakm@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Build failure on M$ (using MSVC): Patch enclosed
Date: Thu, 22 May 2008 10:33:40 +0530 [thread overview]
Message-ID: <e3f230850805212203i565b90r931d539761c43342@mail.gmail.com> (raw)
In-Reply-To: <jwvlk23kky6.fsf-monnier+emacs@gnu.org>
On 5/22/08, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > Well, I was not aware of that function. Looking a little deeper into
> > it, it does not traverse above the current user $HOME (~/ or %HOME%).
> > This code needs to go all the way till the top. Since it does a
> > username comparison, it apprears a bit more expensive (based on gut
> > feel though).
>
>
> Indeed, it doesn't go up past the home directory and it doesn't lookup
> past a directory with a different owner. It's all done on purpose to
> try and avoid pathological cases.
> I don't see that as a problem at all.
Though I do not see a practical use case, here is a case where it can fail:
1. As a system wide policy, I put some settings file in the root
folder or the parent folder of every user folder which has a bunch of
defaults
2. I allow the use to over ride it by adding their own in which case
your changes will find the user modified file (as it resides under the
user HOME folder on UNIX because users will not have permission to
create anywhere above that. But not true on M$ as I have local admin
privilege and hence I can keep it anywhere in the tree).
3. Not all users might want to over ride the default settings and
would like to rely on the system wide policy where the current code
fails.
-dhruva
--
Contents reflect my personal views only!
next prev parent reply other threads:[~2008-05-22 5:03 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 [this message]
2008-05-22 6:52 ` David Kastrup
2008-05-22 7:10 ` dhruva
2008-05-22 7:32 ` David Kastrup
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=e3f230850805212203i565b90r931d539761c43342@mail.gmail.com \
--to=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.