[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Re: Proposal for human readable revision IDs
From: |
Bruce Stephens |
Subject: |
[Monotone-devel] Re: Proposal for human readable revision IDs |
Date: |
Thu, 08 Sep 2005 09:22:04 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
Chad Walstrom <address@hidden> writes:
[...]
> Practically speaking, I think the suggestion to add spacing every 5
> (common w/the crypto crowd) or 4/8 characters (more "natural" for
> representing hex) seems most reasonable and global. I personally like
> 4 characters/space pattern. Using a small group of characters creates
> a mnemonic device (memory aid) through rhythm, making it easier to
> recall.
That's bad because it makes cut and paste more awkward. I don't know
about Windows, but almost all Unix applications select a "word" if you
double click, so provided the hash is suitably delimited (with
whitespace, or square brackets), then it's very easy to select. So 4
characters, space separated, would be pretty horrible from that point
of view. 4 characters, underscore separated, would be much better.
[...]
> "monotone log" could also be altered to output selectors:
>
> % monotone log PATH
> -----------------------------------------------------------------
> [Ancestor]
> r:
>
> [Current]
> r:9bed b716 44a5 6862 640e 036e fc32 1fdf 7318 52be
> a:address@hidden
> d:2005-09-01T05:44:38
> b:branch.name
> t:tag1
> t:tag2
>
> [Added files]
> FILE1 FILE2 FILE3
>
> [ChangeLog]
> Example changelog entry.
> -----------------------------------------------------------------
OK, but why give hints, why not show a selector? You might show the
above as
a:address@hidden/d:2005-09-01T05:44:38/b:branch.name/t:tag1
That's not so good for cut and paste (on Unix, anyway) since it's
multiple words. But it's better than the hints.
> I'm not real fond of the "old_revision [SHA1]" output, since it can't
> immediately be used as a selector (via copy-and-paste operations).
It's just fine if a double click selects the hash.
[...]
- Re: [Monotone-devel] Proposal for human readable revision IDs, (continued)
- Re: [Monotone-devel] Proposal for human readable revision IDs, Hendrik Boom, 2005/09/07
- Re: [Monotone-devel] Proposal for human readable revision IDs, Thomas Haas, 2005/09/07
- [Monotone-devel] Re: Proposal for human readable revision IDs, Bruce Stephens, 2005/09/07
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Andy Jones, 2005/09/07
- [Monotone-devel] Re: Proposal for human readable revision IDs, Bruce Stephens, 2005/09/07
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Nathaniel Smith, 2005/09/08
- [Monotone-devel] Re: Proposal for human readable revision IDs, Bruce Stephens, 2005/09/08
Re: [Monotone-devel] Proposal for human readable revision IDs, Hendrik Boom, 2005/09/07
[Monotone-devel] Re: Proposal for human readable revision IDs, Lapo Luchini, 2005/09/09
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Andy Jones, 2005/09/09
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Jon Bright, 2005/09/12
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Andy Jones, 2005/09/12
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Florian Weimer, 2005/09/13
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Brian Downing, 2005/09/30
- Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Daniel Carosone, 2005/09/30
Re: [Monotone-devel] Re: Proposal for human readable revision IDs, Hendrik Boom, 2005/09/09