On Wed, May 7, 2014 at 8:15 AM, Stephan Beal wrote:
> The lock you're seeing is almost certainly your dropbox and "should" be
> harmless. sqlite locks the db as needed, and Dropbox "should" recognize
> that and not touch the file as long as it's locked (but posix locks are
> advisory locks, not r
On Wed, May 7, 2014 at 10:56 PM, Michai Ramakers wrote:
> On 7 May 2014 22:51, Stephan Beal wrote:
> > Maybe output the list and confirm for Y/n as it does now for certain
> > scenarios?
>
> I don't think I understand... I meant undo/redo as per editor
> features, within a single select-files-to-
On 7 May 2014 21:15, Stephan Beal wrote:
>
> For diff i was thinking first show the list of all names, select one or more
> files, then show the diff. Maybe repeat the list/input after that, allowing
> views of multiple individual files. Pipe them through the $PAGER, maybe. Or:
> diff --interactiv
On 7 May 2014 22:51, Stephan Beal wrote:
> On Wed, May 7, 2014 at 10:32 PM, Michai Ramakers
> wrote:
>>
>> Right. Perhaps one issue is the stack-like nature of undo/redo; when a
>> user changes his/her mind, he/she has to undo up to the point where
>> the incorrectly removed filename appears agai
On Wed, May 7, 2014 at 10:32 PM, Michai Ramakers wrote:
> Right. Perhaps one issue is the stack-like nature of undo/redo; when a
> user changes his/her mind, he/she has to undo up to the point where
> the incorrectly removed filename appears again.
>
Maybe output the list and confirm for Y/n as i
Hello,
On 7 May 2014 21:15, Stephan Beal wrote:
> On Wed, May 7, 2014 at 9:03 PM, Michai Ramakers
> wrote:
>>
>> I've been thinking about this a bit as well. Perhaps a nice idea would
>> be to fire up $EDITOR...
>>
> ...
> Maybe just delete the lines you don't want? That would
> be relatively ea
On Wed, May 7, 2014 at 9:03 PM, Michai Ramakers wrote:
> One drawback of using explicit screendrawing like you suggested might
> be long lists (when implementing 'diff-interactive' for instance). Or
> perhaps lists are typically not long, I don't know. One idea there
> might be an interface like G
On Wed, May 7, 2014 at 9:03 PM, Michai Ramakers wrote:
> I've been thinking about this a bit as well. Perhaps a nice idea would
> be to fire up $EDITOR like with 'commit', and allow the user to prefix
> wanted files with some char (i.e. grep -v '^ ' on the resulting
> tempfile would yield the
Hello,
On 7 May 2014 19:34, Stephan Beal wrote:
> Hi, all,
>
> i'm looking for ideas and implementation strategies for a new feature:
>
> fossil add -interactive
>
> (snip)
I've been thinking about this a bit as well. Perhaps a nice idea would
be to fire up $EDITOR like with 'commit', and allow
Hi, all,
another fossil trick i like to tinker with sometimes...
this CTE query provides a timeline-like overview of commits, starting at a
specific checkin version and optionally limiting the results to the
previous N Julian Days:
-- All ancestors (direct or merged!) of the checkin
-- RID given
On Wed, May 7, 2014 at 10:18 AM, Stephan Beal wrote:
> Hi, all,
> Anyway...
>
> The script:
>
> http://fossil.wanderinghorse.net/repos/cwal/index.cgi/finfo?name=vgLastFewVersions.sh
>
> Of course it could be refactored into a generic (repo-independent) script
> which then calls a repo-specific scr
On Wed, May 7, 2014 at 7:18 PM, Stephan Beal wrote:
> for the Unix-like OS users out there (who know how to write shell
> scripts), this might be a tiny bit interesting (possibly too special-case,
> but maybe conceptually useful as a basis for one's own script)...
>
And now the fatal flaw reveal
Hi, all,
i'm looking for ideas and implementation strategies for a new feature:
fossil add -interactive
Here's basically what it would do:
a) recurse into the current dir/subdirs and build a list of files...
b) exclude any files which match the appropriate ignore globs (TBD) and
any files whi
Hi, all,
for the Unix-like OS users out there (who know how to write shell scripts),
this might be a tiny bit interesting (possibly too special-case, but maybe
conceptually useful as a basis for one's own script)...
Here's a bash script which uses the various f-* tools (from libfossil):
http://f
Thus said Richard Hipp on Wed, 07 May 2014 11:02:55 -0400:
> We might be talking about different hooks. I'm concerned about the
> verify_before_commit hook implemented here:
>
> http://www.fossil-scm.org/fossil/artifact/615e25ed6?ln=94-104
Yes, it does appear that we were talking abou
On Wed, May 7, 2014 at 9:46 AM, Baruch Burstein wrote:
> On Wed, May 7, 2014 at 8:03 AM, Gerald Gutierrez <
> gerald.gutier...@gmail.com> wrote:
>
>>
>> I have a fossil repository that I use on two machines, one at work and
>> one at home. For this one, I'd rather not host it at an online location
On Wed, May 7, 2014 at 5:02 PM, Richard Hipp wrote:
>
> On Wed, May 7, 2014 at 10:32 AM, Andy Bradford
> wrote:
>
>>
>> http://www.fossil-scm.org/index.html/artifact/05e0e4bec391ca300d1a6fc30fc19c0a12454be1?ln=1506,1518
>>
>
> We might be talking about different hooks. I'm concerned about the
>
On Wed, May 7, 2014 at 10:32 AM, Andy Bradford wrote:
> Thus said Richard Hipp on Wed, 07 May 2014 07:06:31 -0400:
>
> > The purpose of the hooks is to verify that all of the content in the
> > repository is still accessible. Before each commit, the hooks run to
> > verify that all of the
Thus said Richard Hipp on Wed, 07 May 2014 07:06:31 -0400:
> The purpose of the hooks is to verify that all of the content in the
> repository is still accessible. Before each commit, the hooks run to
> verify that all of the artifacts can still be un-deltaed and
> uncompressed and t
On Wed, May 7, 2014 at 1:59 AM, Andy Bradford wrote:
>
> Basically it does a commit each round trip and defers execution of hooks
> until the last round-trip happens.
>
That is scary.
The purpose of the hooks is to verify that all of the content in the
repository is still accessible. Before eac
On Wed, May 7, 2014 at 8:03 AM, Gerald Gutierrez wrote:
>
> I have a fossil repository that I use on two machines, one at work and one
> at home. For this one, I'd rather not host it at an online location. So I
> tried to to put the fossil file on Dropbox instead so that Dropbox will
> automatica
21 matches
Mail list logo
