-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/17/2014 9:40 PM, Doug Franklin wrote:
> On 2014-06-17 22:00, Andy Goth wrote:
>
>> This almost works in csh (which I am regrettably forced to use).
>> Yes, the command is not executed but is still stuffed in the
>> history buffer,
>
> Maybe I'm
On 2014-06-17 22:00, Andy Goth wrote:
This almost works in csh (which I am regrettably forced to use). Yes,
the command is not executed but is still stuffed in the history buffer,
Maybe I'm OCD or something, but if I have to do it more than twice, it
gets embodied as a script. :)
--
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/16/2014 3:24 PM, Stephan Beal wrote:
> 1) Move your cursor to the beginning of the line. In Bash-like
> shells that's normally Ctrl-A, but many terminals support the Home
> key as well.
>
> 2) Type the '#' character (shift-3 on a US keyboard). Th
On Tue, Jun 17, 2014 at 4:54 PM, Andy Goth wrote:
>
> At this moment, http://www.sqlite.org/cgi/src/timeline?y=ci shows
> these two checkins (others too, of course):
>
> [b500f2a097] Leaf: Fix a missing space in a "wheretrace" comment. No
> changes to production code. (user: drh, tags: trunk)
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Right now, ambiguous artifact IDs are handled by showing a page
listing all (*) the artifacts with the prefix.
I suggest jumping straight to the oldest artifact with the prefix, but
showing the alternatives on the page. Perhaps it would be easier to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At this moment, http://www.sqlite.org/cgi/src/timeline?y=ci shows
these two checkins (others too, of course):
[b500f2a097] Leaf: Fix a missing space in a "wheretrace" comment. No
changes to production code. (user: drh, tags: trunk)
[38965484199153e]
On Jun 17, 2014 10:47 AM, "Stephan Beal" wrote:
>
> On Tue, Jun 17, 2014 at 7:24 PM, B Harder wrote:
>>
>> Nice! As a BSD user though, I feel compelled to point out this looks
>> like a readline[1] feature, and not an editline[2] feature. So it
>> works with bash (and likely other readline linked
On Tue, Jun 17, 2014 at 7:24 PM, B Harder wrote:
> Nice! As a BSD user though, I feel compelled to point out this looks
> like a readline[1] feature, and not an editline[2] feature. So it
> works with bash (and likely other readline linked progs), it doesn't
> work w/ (e.g.) NetBSDs /bin/sh.
>
i
On Tue, 17 Jun 2014 17:39:45 +0200
Stephan Beal wrote:
> On Tue, Jun 17, 2014 at 5:30 PM, Eduardo Morras
> wrote:
>
> > git fast-export > xz -vv --lzma2=preset3,dict=256MiB git.xz
> > xzcat -vv git.xz > fossil import git.fossil
> >
>
> That is a _very_ interesting trick.
You can pause it, vi
On 6/17/14, Stephan Beal wrote:
> On Tue, Jun 17, 2014 at 6:49 AM, B Harder wrote:
>
>> Remember that the buffer is only one level deep, though. A subsequent ^W,
>> ^K , etc will clobber the previous contents.
>>
>
> Almost: try 2x (NON-consecutively) ctrl-k (or ctrl-w, or whatever), then 1x
> ct
I'll be able to tell you if ever this conversion finishes :)
right now 88H and still running
@eduardo at the time iirc the git export did not contain the full
history but a small part of it, right now for sure it contains the
full history
2014-06-17 17:39 GMT+02:00 Stephan Beal :
> On Tue, Jun 17
On Tue, Jun 17, 2014 at 5:30 PM, Eduardo Morras wrote:
> git fast-export > xz -vv --lzma2=preset3,dict=256MiB git.xz
> xzcat -vv git.xz > fossil import git.fossil
>
That is a _very_ interesting trick.
Question to you both: do you know if fossil has generated any delta
manifests in the import?
On Mon, 16 Jun 2014 23:08:22 +0200
Baptiste Daroussin wrote:
> Hi,
>
> I just want to share some feedback, for fun I tried to convert some of
> the FreeBSD repositories to fossil to see how it performs
>
> I first tried the FreeBSD Documentation repository, to go the easy way
> I took the FreeB
On Jun 17, 2014 8:42 AM, "Eric Rubin-Smith" wrote:
>
> This thread is hilarious. I thought I was pretty old-school -- I use
> vi, xterm, fvwm2, and other tools written by my forebears around the
> time when I was born. I get made fun of by people twice my age for my
> dev toolkit.
>
> But even *
This thread is hilarious. I thought I was pretty old-school -- I use
vi, xterm, fvwm2, and other tools written by my forebears around the
time when I was born. I get made fun of by people twice my age for my
dev toolkit.
But even *I* will have two terminals up concurrently -- so that I can
On Tue, 17 Jun 2014, Nico Williams wrote:
> On Mon, Jun 16, 2014 at 11:49 PM, B Harder wrote:
> > Remember that the buffer is only one level deep, though. A subsequent ^W, ^K
> > , etc will clobber the previous contents.
> >
> > Along lines of Stephan Beals method, I use ":" preceding the fossil c
On Tue, Jun 17, 2014 at 6:49 AM, B Harder wrote:
> Remember that the buffer is only one level deep, though. A subsequent ^W,
> ^K , etc will clobber the previous contents.
>
Almost: try 2x (NON-consecutively) ctrl-k (or ctrl-w, or whatever), then 1x
ctrl-y, then Esc-y. Esc-y acts upon the previo
17 matches
Mail list logo
