[fossil-users] Extra code in autosetup/local.tcl

Hi Joe, I was just looking at autosetup/local.tcl and I see back in 2014 you committed 3a5c9b34f39be09b contain a bunch of extra code. It looks like this is copied from jim local.tcl I suggest deleting everything from '# The complex extension checking is done here.' onwards to avoid

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Hi all: In message <787dd2f8-edf8-4caf-5d8c-b63cac39a...@marples.name>, Roy Marples writes: >On 26/03/2017 22:19, Joerg Sonnenberger wrote: >> On Sun, Mar 26, 2017 at 07:49:30PM +0200, Tomasz Konojacki wrote: >>> For someone with a different background, there is *nothing* nice about >>> fossil

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On 26/03/2017 22:19, Joerg Sonnenberger wrote: On Sun, Mar 26, 2017 at 07:49:30PM +0200, Tomasz Konojacki wrote: For someone with a different background, there is *nothing* nice about fossil dumping thousands of lines to the terminal. In fact, I think it scares off newbies who only used git

Re: [fossil-users] Endless loop in fossil merge (legacy version)

2017-03-26 20:02 GMT+02:00 Francois Vogel: > So it works with fossil-1.33 but not with 1.35. > > Is this problem known? It looks fixed with 2.1 (but it's much slower than > with 1.33): Yes, this was a known bug fixed here:

[fossil-users] Newbie Fossil Hosting and Culture

>... > Date: Sun, 26 Mar 2017 13:18:08 -0400 > From: Richard Hipp >... > Subject: [fossil-users] GitLab v. Fossil. Was: Eric Raymond (a.k.a. > ESR) haspublished an SCM > Message-ID: >

[fossil-users] Push transfer script

I’m working on setting up my Fossil server so that certain tasks are kicked off after someone pushes changes to it. Push transfer scripts seem like the right tool for this. Because of the nature of the work that needs to happen after a push, I have my TH1 script ‘tclInvoke exec’ an external

Re: [fossil-users] Fossil Captchas

On Sun, Mar 26, 2017 at 9:06 PM, Richard Hipp wrote: > I am also now reminded that there is an option on the Setup/Access > page that adds a button to the CAPTCHA that completes the captcha > automatically. That would nicely facility access via screen readers. > i was about to

Re: [fossil-users] Fossil Captchas

On 3/26/17, Damien Sykes-Lindley wrote: > Hi Richard, > Forgive me if I'm mistaken, but I think the anonymous password shows itself > as a captcha. The following quote from the antibot article would seem to > confirm this: > > "The "anonymous" user is also available

Re: [fossil-users] Fossil Captchas

Hi Richard, Forgive me if I'm mistaken, but I think the anonymous password shows itself as a captcha. The following quote from the antibot article would seem to confirm this: "The "anonymous" user is also available for humans who do not wish to identify themselves. The difference is that

Re: [fossil-users] fossil 1.2->2.1 - hash policy "auto" doesn't seem to work and gives SQL error.

On 3/26/17, arnoldemu wrote: >>fossil update > Autosync: http:///arnold > Autosync failed. > This fossil repository is not compatible with the version of your client. > You need version 2.1 or later. Please visit http://www.fossil-scm.org and > download a new

Re: [fossil-users] GitLab v. Fossil. Was: Eric Raymond (a.k.a. ESR) has published an SCM

On 03/26/17 19:18, Richard Hipp wrote: [---] > (i) With Fossil, one can click on two nodes of the graph to see a > diff between those two nodes. With GitLab, you apparently have to go > to the separate "Compare" screen, then many type in (or paste in) hash > name prefixes of the two check-ins

Re: [fossil-users] fossil 1.2->2.1 - hash policy "auto" doesn't seem to work and gives SQL error.

Hi Richard, >The "auto" hash-policy automatically flips to "sha3" as soon as Fossil >sees one or more SHA3 artifacts in the repo.  Since your repo contains >SHA3 artifacts, you won't be able to set the policy to "auto" because >it will immediately and automatically flip to "sha3". > >That is the

Re: [fossil-users] Fossil Captchas

On 3/26/17, Damien Sykes-Lindley wrote: > Hi there, > Is there any chance an option can be added in Fossil whereby, when/where a > captcha is required, the task is to answer a question instead? That could be done, in theory, but augmenting a few routines in the

[fossil-users] Endless loop in fossil merge (legacy version)

Hi, FYI, this is on Windows in the Tk repository: http://core.tcl.tk/tk/ I get an endless loop in fossil as follows: C:\Users\francois\Documents\Development\tcltk-fossil\tk>fossil version This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Sun, 26 Mar 2017 19:25:25 +0200 Christophe Gouiran wrote: > I see that most of you complain about this proposed feature. TBH, many members of this list live in the UNIX greybeard bubble, and that's why there is so much opposition to this feature. They're used to the

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Mar 26, 2017 11:25 AM, "Christophe Gouiran" wrote: Please find as attached file another patch which: 1. First test for a real terminal before spawning the pager command. 2. No more paginate json command. I see that most of you complain about this proposed

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Please find as attached file another patch which: 1. First test for a real terminal before spawning the pager command. 2. No more paginate json command. I see that most of you complain about this proposed feature. It was only a proposition, if it is not accepted I won't care. However, it

Re: [fossil-users] fossil 1.2->2.1 - hash policy "auto" doesn't seem to work and gives SQL error.

On 3/26/17, arnoldemu wrote: > > So it seems that hash-policy of auto is not working? > The "auto" hash-policy automatically flips to "sha3" as soon as Fossil sees one or more SHA3 artifacts in the repo. Since your repo contains SHA3 artifacts, you won't be

[fossil-users] GitLab v. Fossil. Was: Eric Raymond (a.k.a. ESR) has published an SCM

On 3/26/17, Stephan Beal wrote: > It seems that ESR has published his own SCM: > > http://esr.ibiblio.org/?p=7448 > http://www.catb.org/esr/src/ Thanks for pointing this out, Stephan. What intrigues me most here is not ESR's python-script wrapper around RCS/SCCS, but

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Sergei Gavrikov decía, en el mensaje "Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager" del 25/3/2017 14:09:57: > My 2 cents. Many of us use f-alias to deal with fossil in a terminal, > right? Then why not f-function? Maybe because not everybody uses Unix-like

[fossil-users] fossil 1.2->2.1 - hash policy "auto" doesn't seem to work and gives SQL error.

Hi All, i downloaded windows version of fossil 2.1 - after initial problems crashing when I ran it (see other thread) and rebuilding it was fine. I used fossil hash-policy to set it to sha3 and forced a commit to the server because I didn't have files in my changes at that time. From then on

[fossil-users] Fossil Captchas

Hi there, Is there any chance an option can be added in Fossil whereby, when/where a captcha is required, the task is to answer a question instead? I say this because, as a totally blind screen reader user, captchas are generally inaccessible to us. Ordinarily, most sites have an audio captcha

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Sun, 26 Mar 2017 16:00:11 +0200, Scott Robison wrote: On Mar 26, 2017 7:13 AM, "Christophe Gouiran" wrote: Hi all, First of all many thanks for all your feedback. I come back to you with an implemented solution. After many thinking,

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Sun, Mar 26, 2017 at 4:00 PM, Scott Robison wrote: > their amount of output, perhaps based on some extra parameter. DRH > suggested that it should be based on any output, which would avoid the > worry about how fossil changes over time. > corner case: json output

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Mar 26, 2017 7:13 AM, "Christophe Gouiran" wrote: Hi all, First of all many thanks for all your feedback. I come back to you with an implemented solution. After many thinking, for me not all commands need to send their outputs to a pager. Only ones which may output

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On 2017-03-26 15:13:53, Christophe Gouiran wrote: > I come back to you with an implemented solution. > Your solution doesn't check whether stdout is actually pointing to a terminal. You should never invoke a pager if it's not. I also think this is a horrible idea in general. Regards, -Martin

[fossil-users] Eric Raymond (a.k.a. ESR) has published an SCM

It seems that ESR has published his own SCM: http://esr.ibiblio.org/?p=7448 http://www.catb.org/esr/src/ "Simple Revision Control is RCS/SCCS reloaded with a modern UI, designed to manage single-file solo projects kept more than one to a directory. Use it for FAQs, ~/bin directories, config

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Hi all, First of all many thanks for all your feedback. I come back to you with an implemented solution. After many thinking, for me not all commands need to send their outputs to a pager. Only ones which may output a big amount of lines in a bunch. Therefore, I selected only some of them to be

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

On Sat, 25 Mar, Andy Bradford wrote: > Thus said Roy Keene on Thu, 23 Mar 2017 17:36:37 -0500: > > > I vote that the pagination be off by default to preserve the > > existing behaviour -- terminals have been able to scroll for > > decades now so I don't know why systemd/git like to do this by