The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: "Michael Kjörling" <michael@kjorling.se>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] A question about ls(1)
Date: Mon, 29 Apr 2019 14:37:26 -0600	[thread overview]
Message-ID: <CANCZdfoO4392-fQqgaHm7Ape=dnvww0m5X2h1b7C_jz_rBB0eg@mail.gmail.com> (raw)
In-Reply-To: <20190429180512.q2jrlsyhvb7cx4ev@h-174-65.A328.priv.bahnhof.se>

[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]

On Mon, Apr 29, 2019 at 12:14 PM Michael Kjörling <michael@kjorling.se>
wrote:

> On 28 Apr 2019 13:00 -0700, from bakul@bitblocks.com (Bakul Shah):
> > b) a standardized plain text format
>
> I'm not sure about that; different applications have very different
> needs, and trying to shoehorn one into another would be ugly; quite
> possibly even more ugly than just having different formats. Imagine
> trying to write mail sorting recipies (think procmail) in a file with
> the same format as that of one holding word processor settings or an
> image metadata store. I guess that's half-way tolerable on Windows
> because next to nobody edits the settings directly anyway, but on a
> system where many such files are sometimes, or often, edited directly
> by the user, it might well hinder more than it helps. I guess you
> _could_ go with something like XML or JSON, but that's a bit like
> saying "all cars should have an engine and a refillable fuel store",
> in that it doesn't actually standardize anything _meaningful_ (in both
> of those cases, the magic is in the schema, not the format). Lists of
> examples not intended to be exhaustive.
>

The only thing that .profile and .Xdefaults share is a leading '.'. While
the latter could be XML or JSON (almost, neither of those formats has
conditional expressions and .Xdefaults is run through cpp), the former
never could be XML or JSON in any sane universe.

So while some config stuff is stored in the dot files, its nature is
somewhat different.

Also, to use git as an example. my repo has a .git/config in it. For work
repos I put my work email and preferred spelling of my name. those go in
repo/.git/config. But for everything else, I have some global settings in
$HOME/.git/config. There are from time to time other reasons to tweak the
settings of a repo and have it be local to that repo only.

It's a tricky problem...

Warner

[-- Attachment #2: Type: text/html, Size: 2470 bytes --]

  reply	other threads:[~2019-04-29 20:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 16:54 Norman Wilson
2019-04-28 19:45 ` Jon Forrest
2019-04-28 20:00   ` Bakul Shah
2019-04-29 18:05     ` Michael Kjörling
2019-04-29 20:37       ` Warner Losh [this message]
2019-04-29 20:44       ` Christopher Browne
2019-04-30  6:44         ` Michael Kjörling
2019-04-30  7:24           ` Kurt H Maier
2019-04-30 10:35             ` Wesley Parish
2019-04-29 22:32       ` Bakul Shah
2019-04-30 11:52         ` Theodore Ts'o
2019-04-28 22:16   ` Thoma Paulsen
2019-04-29  0:53     ` John P. Linderman
  -- strict thread matches above, loose matches on Subject: below --
2019-04-27 23:03 Noel Chiappa
2019-04-27 20:11 Norman Wilson
2019-04-27 14:16 Anthony Martin
2019-04-27 15:38 ` Warner Losh
2019-04-27 15:42   ` Larry McVoy
2019-04-28 23:59   ` Warner Losh
2019-04-28 11:47 ` Dan Cross
2019-04-28 12:00   ` arnold
2019-04-28 14:44   ` jcs
2019-04-28 16:15   ` Bakul Shah

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='CANCZdfoO4392-fQqgaHm7Ape=dnvww0m5X2h1b7C_jz_rBB0eg@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=michael@kjorling.se \
    --cc=tuhs@minnie.tuhs.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 NNTP newsgroup(s).