From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs and Everything (~ locate) on Windows 8
Date: Thu, 17 Jan 2013 18:28:59 +0200 [thread overview]
Message-ID: <83622v93jo.fsf@gnu.org> (raw)
In-Reply-To: <86ehhkgc4o.fsf@somewhere.org>
> From: "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com>
> Date: Thu, 17 Jan 2013 14:41:43 +0100
>
> Another tool such as locate could certainly work, though it's not
> straightforward to set up under Cygwin
There is a native Windows port here:
http://sourceforge.net/projects/ezwinports/files/findutils-4.2.30-4-w32-bin.zip/download
although I never tried this on Windows 8, so caveat emptor. I do use
this on Windows 7, and there are even 64-bit (as well as 32-bit)
binaries in the pack, which should be significantly faster on a 64-bit
OS.
> and locate's contents is only updated every once in a while.
You could set up a scheduled task that will run every hour, if you
really need the DB to be so up-to-date. (I have such a task run once
a week, and I never had any problems with files I couldn't find.)
> Everything, on the other hand, is always fully up-to-date. You move a file, it
> already knows about that. Very practical.
If this is more important to you than get rid of the UAC prompts, then
you are already set up.
In any case, the list of measures I know of that might help you not to
get into trouble with UAC is:
. Never run "as administrator", except for very rare and specific
jobs. Windows treats such users inherently dangerous and will pop
up UAC prompts where it doesn't for other users.
. If you possibly can, don't use a user who is "local admin";
instead, use a "normal" user and grant that user all the necessary
privileges via the Local Security Policy.
. Take ownership on the entire hierarchy under C:\Users\YOUR-USERNAME;
that will fix the ownership problems that Emacs might not like,
because it doesn't always know that ownership by "Administrators"
group is OK when the user FOO is a local admin.
. Take ownership on any directory tree where you happen to work a
lot, if that tree is not owned by you.
. If you must run programs that write into C:\Program Files, take
ownership on that directory and its subdirectories as well.
. Some utilities might need a manifest where you tell Windows to run
them at "asInvoker" level, to avoid the UAC prompts, because
Windows in its infinite wisdom considers certain program names and
even certain symbols inside them as evidence that the program
might be "dangerous". One example is the GNU Patch utility, but
the exact rules by which Windows decides whether a program belongs
to the dangerous lot are unpublished, so any program which pops up
the UAC prompts should have a manifest created for it, before you
conclude that it's something in the program's code that triggers
that.
Not sure this will help you; I don't use Everything. You may wish to
try Findutils anyway before you embark on the above adventure, who
knows, you might even like it.
next prev parent reply other threads:[~2013-01-17 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 12:51 Emacs and Everything (~ locate) on Windows 8 Sebastien Vauban
2013-01-17 13:13 ` Jason Rumney
2013-01-17 13:41 ` Sebastien Vauban
2013-01-17 14:05 ` Valentin Baciu
2013-01-17 16:28 ` Eli Zaretskii [this message]
[not found] ` <mailman.17712.1358440166.855.help-gnu-emacs@gnu.org>
2013-01-18 16:32 ` Sebastien Vauban
2013-01-18 7:44 ` Yuri Khan
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=83622v93jo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).