[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] version aliases

From: Tom Lord
Subject: Re: [Gnu-arch-users] version aliases
Date: Mon, 5 Apr 2004 13:14:35 -0700 (PDT)

You have to be careful if you want to propose ideas but not dig into
details.   On the one hand, such input is very valuable --- it turns
up (retrospectively) easy and obvious enhancements to add.   On the
other hand, you have to watch out for getting in to "you want a pony
with that?" mode..... i.e., asking for a "colorless green leaf" or a
"room temperature solid water".   Good kibbitzing is hard.


    > Sender: address@hidden
    > Cc: address@hidden, address@hidden
    > From: Stefan Monnier <address@hidden>
    > Date: 05 Apr 2004 16:06:17 -0400
    > User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50
    > Content-Type: text/plain; charset=us-ascii
    > X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on
    > X-Spam-DCC: : mail 1182; Body=1 Fuz1=1 Fuz2=1
    > X-Spam-Status: No, hits=-1.0 required=4.5 tests=BAYES_00 autolearn=ham 
    >   version=2.63
    > X-42email-MailScanner-Information: Please contact for more information.
    > X-42email-MailScanner: Found to be clean
    > X-UIDL: 1c927db817f78a0dc44b49e83155f55b
    > >> > Is this something you want to code up or just an idle thought?
    > There's only a fixed number of hours per day last time I checked, so I'm
    > just an Arch user and not an Arch coder for now.  Sorry.
    > >> > I.e., is it worth explaining how to go about implementing it?
    > Not really.
    > > Not really.   Aliases would need a distinctive syntax -- perhaps a
    > > prefix character.   So, you wouldn't say:
    > >         tla get latest-emacs
    > > you might say:
    > >         tla get :latest-emacs
    > Well, actually given that I use `tla get' only once every blue moon, I'd
    > prefer if we used more relevant examples while thinking about it.
    > So how about `tla changes :latest-emacs' ?
    > You might think this is nitpicking, but there is a significant difference:
    > all the cases I care about are command used from within a tree.
    > > The hard part is designing how archive-wide (for all users of a
    > > certain archive),  meta-archive (archives containing aliases referring
    > > to other archives), and per-user aliases are stored, what they consist
    > > of, which take priority, where to search for a given name, etc.
    > As I said, I think they should be tree-wide rather than archive-wide or
    > user-wide.  At least, as a user, I'd like to use the same alias for
    > different purposes depending on which tree I'm in.
    > So I was thinking of storing them under the {arch} dir.  I don't know
    > whether it should be rev-controlled or not, tho.  Of course, maybe we want
    > all of those options, but it's probably not worth the trouble.
    >         Stefan

reply via email to

[Prev in Thread] Current Thread [Next in Thread]