From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: <cygwin@cygwin.com>
Subject: RE: /dev/registry
Date: Mon, 04 Feb 2002 18:50:00 -0000 [thread overview]
Message-ID: <NCBBIHCHBLCMLBLOBONKEEBPCKAA.g.r.vansickle@worldnet.att.net> (raw)
In-Reply-To: <014a01c1acc9$7324cc80$0100a8c0@advent02>
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Chris January
> Sent: Sunday, February 03, 2002 9:43 AM
> To: cygwin@cygwin.com
> Subject: /dev/registry
>
>
> How about adding a /dev/registry fhandler to Cygwin? Registry keys would be
> directories and values in the registry files. I'm willing to try coding this
> if people think it's a good idea. It allows shell scripts to easily access
> registry keys as well as programs.
>
Well, it looks like I'll be the only one, but this sounds to me like an insanely
*BAD* idea. It seems to me to be hard enough to keep the Windows registry in
one piece even if you don't dink with it; I shudder to think what horrors await
sombody with fat fingers and an itchy TAB finger (i.e. me):
cat HundredsOfMBsOfCrap > /dev/r[TAB-oops-I-meant...well-something-else-anyway]
I'm trying to think where this would actually be useful, but I'm drawing a
blank. It seems to me that the registry should have at least a slightly higher
barrier to entry than the command line.
--
Gary R. Van Sickle
Brewer. Patriot.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-02-05 2:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 12:07 /dev/registry Chris January
2002-02-03 10:49 ` /dev/registry Gerald Villemure
2002-02-03 11:02 ` /dev/registry Daniel Adams
2002-02-03 11:14 ` /dev/registry Charles Wilson
2002-02-03 12:00 ` /dev/registry Christopher Faylor
2002-02-03 12:07 ` /dev/registry roland
2002-02-03 23:15 ` /dev/registry Gerald Villemure
2002-02-04 0:36 ` /dev/registry Corinna Vinschen
2002-02-04 14:43 ` /dev/registry Greg Mosier
2002-02-04 14:53 ` /dev/registry Michael A Chase
2002-02-05 5:28 ` /dev/registry Lapo Luchini
2002-02-05 9:28 ` /dev/registry Christopher Faylor
2002-02-05 13:46 ` /dev/registry Ralf Habacker
2002-02-05 14:03 ` /dev/registry Larry Hall (RFK Partners, Inc)
2002-02-05 14:07 ` /dev/registry Michael A Chase
2002-02-03 12:07 ` /dev/registry Lapo Luchini
2002-02-03 12:07 ` /dev/registry Jon Foster
2002-02-03 12:07 ` /dev/registry Michael F. March
2002-02-04 18:50 ` Gary R. Van Sickle [this message]
2002-02-10 0:18 ` /dev/registry Robert Collins
2002-02-04 19:57 /dev/registry Gareth Pearce
2002-02-06 3:23 ` /dev/registry Barubary
2002-02-06 8:56 ` /dev/registry Randall R Schulz
2002-02-08 23:42 ` /dev/registry Robert Collins
2002-02-09 10:43 ` /dev/registry Christopher Faylor
2002-02-09 13:17 ` /dev/registry Robert Collins
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=NCBBIHCHBLCMLBLOBONKEEBPCKAA.g.r.vansickle@worldnet.att.net \
--to=g.r.vansickle@worldnet.att.net \
--cc=cygwin@cygwin.com \
/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).