On Mon, Aug 27, 2012 at 10:19 PM, Peter Spjuth wrote:
> Expanding on the bash completion script previously published in this list
> by Stuart Rackham, this would give you tab completion on branch names:
>
+1!
Very cool :).
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gp
> On Mon, Aug 27, 2012 at 12:35 PM, Stephan Beal
> wrote:
>
>> On Mon, Aug 27, 2012 at 6:07 PM, wrote:
>>
>>> I'd be very happy if I could just type:
>>>
>>> $ fossil co vim-7.3.154
>>>
>>> I'd be even happier if I could just type:
>>>
>>> $ fossil co 154
>>>
>>
>> Not to sound too pessimistic, bu
On Mon, Aug 27, 2012 at 6:07 PM, wrote:
> I have a fossil repository where I keep my vim settings in different
> branches. Here is an example output of branch listing:
>
> $ fossil branch
> * trunk
> vim-7.3.000-i486-1-custom
> vim-7.3.000-i486-1-default
> vim-7.3.154-x86_64-1-custom-big
>
The essence of my suggestion was to not do it by default but to provide a
simple way for the user to say "yes, I really want you to search for this
substring anywhere" rather than forcing it on everyone.
SDR
On Mon, Aug 27, 2012 at 11:24 AM, Stephan Beal wrote:
> On Mon, Aug 27, 2012 at 7:18 PM,
On Mon, Aug 27, 2012 at 7:18 PM, Scott Robison wrote:
> fossil co --glob 154
>
> Though I'm not personally looking for this functionality myself so not
> having it as an official feature doesn't bother me.
FWIW: as Richard said, it's _technically_ easy, but brings with it both
philosophical and
Just throwing out a couple of ideas:
fossil globco 154
Or perhaps slightly less bad:
fossil co --glob 154
Though I'm not personally looking for this functionality myself so not
having it as an official feature doesn't bother me.
SDR
On Mon, Aug 27, 2012 at 11:00 AM, Richard Hipp wrote:
>
>
This sounds like something you could put in a shell script wrapper -- just
use "fossil sqlite3".
On Mon, Aug 27, 2012 at 11:07 AM, wrote:
> I have a fossil repository where I keep my vim settings in different
> branches. Here is an example output of branch listing:
>
> $ fossil branch
> * trunk
On Mon, Aug 27, 2012 at 12:35 PM, Stephan Beal wrote:
> On Mon, Aug 27, 2012 at 6:07 PM, wrote:
>
>> I'd be very happy if I could just type:
>>
>> $ fossil co vim-7.3.154
>>
>> I'd be even happier if I could just type:
>>
>> $ fossil co 154
>>
>
> Not to sound too pessimistic, but...
>
>
Yeah. I
On Mon, Aug 27, 2012 at 6:07 PM, wrote:
> I'd be very happy if I could just type:
>
> $ fossil co vim-7.3.154
>
> I'd be even happier if I could just type:
>
> $ fossil co 154
>
Not to sound too pessimistic, but...
How is fossil supposed to be able to know that 154 is supposed to mean
abcdef154
I have a fossil repository where I keep my vim settings in different
branches. Here is an example output of branch listing:
$ fossil branch
* trunk
vim-7.3.000-i486-1-custom
vim-7.3.000-i486-1-default
vim-7.3.154-x86_64-1-custom-big
Now, to checkout the last branch in this list, I have to c
10 matches
Mail list logo