Re: [fossil-users] clone a repository over ssh where the path includes whitespace characters

On 2019-08-08 08:25:30, Andy Bradford wrote: > Thus said Stephan Beal on Thu, 08 Aug 2019 12:06:30 +0200: > > > fossil clone 'ssh://user@domain://path/to/"directory with > > spaces"/my.fossil' my.fossil > > Yes, that works, but it's a hack really because ... Its behaviour is consistent with

Re: [fossil-users] Turning off GCC's "helpful" ansi color escape sequences in error/warning messages

On 2018-01-09 19:27:10, The Tick wrote: > > Seems to me that most people will either use script or redirect the make > output to a file. Computers are simply too fast and the output too > (...) If you use GCC > you will probably have noticed that it inserts ansi color escape sequences > in an

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

On 03/27/17 01:55, Roy Marples wrote: Pager output disappearing with the pager (I assume when asking the pager to exit) is an issue with the pager. I disagree. Disappearing output uses the "alternate screen" of a terminal so that the pager's output does not interfere with your non-reading

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

Re: [fossil-users] Support for commonmark markdown in fossil

On 03/13/17 19:00, Warren Young wrote: On Mar 13, 2017, at 10:32 AM, Natacha Porté wrote: Or do you expect it to count parentheses and prevent you from ever linking to a URL with unbalanced parentheses? Yes. Other Markdown processors do that. It doesn't necessarily

Re: [fossil-users] Bug in "fossil branch new"

On 2017-02-07 07:59:03, Andy Bradford wrote: > Thus said "Martin S. Weber" on Tue, 07 Feb 2017 11:07:55 +0100: > > > thanks for proving my point. > > You're welcome. I never said branch names don't identify a branch, nor > that they are meaningless. drh s

Re: [fossil-users] Bug in "fossil branch new"

On 2017-02-06 23:17:00, Andy Bradford wrote: > (...) > Because it doesn't matter what the name of the branch is. > (continues to show examples where Andy, as the human, uses the branch-name to > identify the branch) thanks for proving my point. Regards, -Martin

Re: [fossil-users] Bug in "fossil branch new"

On 2017-02-06 11:13:46, Richard Hipp wrote: > (...) > Probably you are coming from a different DVCS that requires branches > to be created in advance of the commit and that also requires branch > names to be unique. Fossil has neither of these constraints, and so > it operates a little

Re: [fossil-users] Git just got shallow and sparse clones

On 2017-02-04 15:01:43, Jan Danielsson wrote: > (...) >So when you do your initial clone, it only downloads some metadata > about what files exist in the repository, but not the contents of them. > When you open a file, the vfs will fetch the file for you. > >Say a project has a doc/

Re: [fossil-users] Adding binary files to fossil

On 2017-01-03 10:08:40, Scott Doctor wrote: > What is the proper way to add binary files to a repository? Follow the following steps: (1) (fossil) add the files. (2) you're done. (3) No, really, you're done. (4) Enjoy. fossil will warn you that these files look binary. Read the warning and

Re: [fossil-users] fossil & cgi bleed (Proxy / HTTP_PROXY)

On 2016-07-18 18:07:22, Richard Hipp wrote: > On 7/18/16, Martin S. Weber <ephae...@gmx.net> wrote: > > > > But it uses the http_proxy environment variable, doesn't it, > > which a front-end web server might (or, will, according to RFC 3875,) > > set before in

Re: [fossil-users] fossil & cgi bleed (Proxy / HTTP_PROXY)

On 2016-07-18 17:27:52, Richard Hipp wrote: > On 7/18/16, Martin S. Weber <ephae...@gmx.net> wrote: > > More info e.g. at https://httpoxy.org/ > > > > suggested fix: "If you’re running PHP or CGI, you should block the Proxy > > header now." >

[fossil-users] fossil & cgi bleed (Proxy / HTTP_PROXY)

More info e.g. at https://httpoxy.org/ suggested fix: "If you’re running PHP or CGI, you should block the Proxy header now." Fossil's suggesting deployment as a CGI Fossil's using http_proxy itself (as client) wondering whether: - fossil can be convinced to be exploitable by a well crafted

Re: [fossil-users] Skin almost finished.

On 2015-05-01 11:58:30, John Found wrote: (...) Well, maybe it is a bad practice, but my browser is always maximized. Also, all people I know maximize their browsers... Which is why I was saying, one keystroke and you're ready for prose-reading-mode, but the other way around, there's no way

Re: [fossil-users] Select specific changes within files

On 2015-03-20 13:04:44, Richard Hipp wrote: (...) The way I deal with this in SQLite is: (1) Make logically separate changes in separate check-outs so that they are easy to test and commit separately. (...) That's the sort of flow-interrupting context switch I was referring to on one hand,

Re: [fossil-users] Select specific changes within files

On 2015-03-20 09:02:32, Richard Hipp wrote: (...) I'm still having trouble understanding how the partial commit would be *useful*, though. Some people like their metadata (i.e. fossil's commit message log) to match up with what they were doing in the files. You go to your file, you begin to

Re: [fossil-users] possible error

On 2015-03-17 17:06:33, Ramon Ribó wrote: fossil version This is fossil version 1.32 [302052d30b] 2015-02-20 08:30:51 UTC fossil sync Usage: c:\other\binutils\fossil.exe sync URL is it not possible to use sync without URL? It is, after you've stored your sync settings (i.e. who is to be

Re: [fossil-users] Timeline graph display options

On 2015-03-09 21:42:51, Andy Bradford wrote: Thus said Richard Hipp on Mon, 09 Mar 2015 23:06:59 -0400: Which timeline graph do you prefer: (1) https://www.fossil-scm.org/fossil/timeline?y=cinomo=0 (2) https://www.fossil-scm.org/fossil/timeline?y=cinomo=1 (1) because the

Re: [fossil-users] Horror story about git - Forever Alone

On 2014-09-25 08:44:04, Gour wrote: Morning, just read it today on Reddit: http://www.reddit.com/r/programming/comments/2hctgh/horror_story_about_git_forever_alone/ Article is at: http://thedailywtf.com/Articles/Forever-Alone.aspx What about Fossil in the same scenario? What's

Re: [fossil-users] Please improve documentation for the checkout command

On 2014-03-20 12:46:15, Stephan Beal wrote: (...) # f help Usage: f help COMMAND Common COMMANDs: (use f help -a|--all for a complete list) add changes gdiff openrss ui addremove clean helppraise settingsundo all clone

Re: [fossil-users] Please improve documentation for the checkout command

On 2014-03-20 12:47:35, David Mason wrote: Are branches easier to deal with in fossil? Using hg at work, I completely understand why one would stay away from branches. Using fossil at home, I completely fail to understand why one would work on trunk. Can't really tell you much about the why

Re: [fossil-users] Version 1.28 release?

On Thu, Jan 09, 2014 at 11:19:45AM -0500, Richard Hipp wrote: On Thu, Jan 9, 2014 at 11:12 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2014/1/9 Richard Hipp d...@sqlite.org: Jan - would you like to start the branch-1.28 containing the SQLite 3.8.2 release?

Re: [fossil-users] Version 1.28 release?

more info: test-out @ http://phaeton.sdf-eu.org/fossil-1f10199a09724a50-test-out -M ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Version 1.28 release?

On Thu, Jan 09, 2014 at 09:31:59AM -0500, Richard Hipp wrote: On Thu, Jan 9, 2014 at 9:17 AM, Jan Nijtmans jan.nijtm...@gmail.com wrote: The latter has the advantage that no new Fossil binary has to be built when SQLite 3.8.3 is released. Fossil will always follow the latest stable

Re: [fossil-users] survey: your top 5 most-used fossil CLI commands?

On Mon, Sep 02, 2013 at 06:36:42PM +0200, Stephan Beal wrote: (...) So... which fossil CLI commands do you use most often, NOT counting the following (which are more or less required for any real work): (...) changes add/addremove/rm/mv stash merge (settings? remote-url?) would be what

Re: [fossil-users] survey: your top 5 most-used fossil CLI commands?

On Mon, Sep 02, 2013 at 07:30:01PM +0200, Stephan Beal wrote: @All: Your answers surprise me a bit, guys. addremove, really? i've never used that one, either. I find it easy to bring my checkout to the state I want the DB to reflect and then just go ahead and do so in a single swoop. Getting

Re: [fossil-users] survey: your top 5 most-used fossil CLI commands?

On Mon, Sep 02, 2013 at 07:54:35PM +0200, Stephan Beal wrote: On Mon, Sep 2, 2013 at 8:41 PM, Martin S. Weber ephae...@gmx.net wrote: I find it easy to bring my checkout to the state I want the DB to reflect and then just go ahead and do so in a single swoop. Getting (all) files in place

Re: [fossil-users] sqlite errors after reinstalling fossil

On 01/17/13 16:46, Joseph Mingrone wrote: One change I made when I upgraded the box was that I set home directories to be nfs mounted from a storage server. I'm using the automount daemon to do the mounting. Before home directories were local. To test if this was causing a problem I created a

Re: [fossil-users] anything speaking against fossil add --commit ?

On 07/10/12 10:30, Benoit Mortgat wrote: What do you want the command to do in this case: * edit foo.txt (versioned) * fossil add --commit bar.txt Do you want the commit to just add bar.txt to the version control, or to also include foo.txt changes? Given that fossil add is a no-op when

Re: [fossil-users] anything speaking against fossil add --commit ?

On 07/10/12 12:13, Richard Hipp wrote: Why do you think you will be more likely to type --commit after fossil add than you would be to type ; fossil commit? Well, assuming there's a shorthand for the option, I find it more natural to add these extra three characters on the 'add' line than

Re: [fossil-users] Prototype JSON wiki editor demo online

On 09/22/11 18:14, Baptiste Daroussin wrote: So there's the markdown support some of you have been asking for. :) Sorry for stupid question but does that mean that you bundled a markdown library? if yes which one? Or how do you render the markdown? You should have quoted one more sentence

Re: [fossil-users] any interest in integrating jimtcl w/fossil?

On 09/21/11 14:12, Ingo Koch wrote: On 09/20/11 15:53, Martin S. Weber wrote: On 09/20/11 19:20, Steve Bennett wrote: It is the interface to fossil which is important. Yep. That's where step #1 comes in - librarization of fossil. Luckily I'll have time for that (at least rounding up an API

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 11:19, Stephan Beal wrote: Hi, all, i'm just curious - is there any interest out there in integrating jimtcl with fossil, e.g. as a replacement for th1? While i'm not currently a tcl user, binding C/C++ code to scripting languages is a hobby of mine (e.g.

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 11:52, Stephan Beal wrote: On Tue, Sep 20, 2011 at 5:44 PM, Martin S. Weber martin.we...@nist.gov mailto:martin.we...@nist.gov wrote: Yes. It is one of my plans, the reasons I joined here, to extend fossil with tcl. Whether that's ought to be jimtcl (for size

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 12:07, Konstantin Khomoutov wrote: Not that I ever had any need to touch either th1 or jimtcl, but I'd like to ask an obligatory question: what are the current th1's shortcomings so that replacing it with something else is needed? It's no general programming language. It is modeled

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 12:49, Konstantin Khomoutov wrote: Well, my question was actually a veiled uneasy feeling about possible code bloat and feature creep. If you look at the top feature request for fossil I wouldn't say that's bloat or feature creep. It's a necessity for fossil to be considered in

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 12:55, Andreas Kupries wrote: On 9/20/2011 9:01 AM, Martin S. Weber wrote: On a side note, fossil should grow something to import artifacts-with-history from other projects/databases. How would the proposed command (extension) differ from the existing fossil import

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 12:58, Joe Mistachkin wrote: Has you looked at the tcl-integration branch in Fossil? It has experimental changes to allow full-blown Tcl to be used in Fossil. It allows Tcl and TH1 to call into each other. I've seen it, but I disagree with the approach. Tcl is a superset of Th1.

Re: [fossil-users] any interest in integrating jimtcl w/ fossil?

On 09/20/11 13:00, Stephan Beal wrote: On Tue, Sep 20, 2011 at 6:49 PM, Konstantin Khomoutov flatw...@users.sourceforge.net mailto:flatw...@users.sourceforge.net wrote: While I *am* a Tcl aficionado, for me, one of the Fossil's selling points is its self-containment and a minimal set of

Re: [fossil-users] any interest in integrating jimtcl w/fossil?

On 09/20/11 13:38, Steve Havelka wrote: Excuse my bluntness: that sounds like a terrible idea. Tcl is huge compared to fossil, and certainly not installed everywhere by default. Which is why it would have to be integrated in the fossil source, built from source, and attached to fossil at

Re: [fossil-users] any interest in integrating jimtcl w/fossil?

On 09/20/11 14:53, Eric wrote: I agree entirely. I think Fossil is in danger of becoming some sort of Swiss Army Knife, rather than a finely honed specialised tool. Actually fossil IS a swiss army knife. It combines a DVCS with tickets, wiki, http UI, user-mgmt embedded doc. Its

Re: [fossil-users] JSON/wiki: what info needs to be returned for...

On 09/17/11 08:35, Richard Hipp wrote: (Aside: Should we create a new fossil-dev mailing list for this kind of thing, and preserve fossil-user for use by people who just want to use Fossil and don't really care what is happening behind the scenes?) Yes please :) -Martin

Re: [fossil-users] fossil code style question...

On 09/16/11 14:26, Stephan Beal wrote: To be clear: i'm not going to argue either way, i just want to conform. Which reminds me, try building your code with either c89 as compiler or pass -ansi to gcc. There's still a fix necessary for fossil's sha1 computation (see previous thread starting

[fossil-users] fossil: numerous open trunk leaves

Hey fellow archaeologists, I was just wondering: how did fossil end up with all these distinct open leaves of the same branch? If you look at our leaves display here: http://fossil-scm.org/index.html/leaves And do a search for tags: trunk, you should find six instances of trunk leaves:

Re: [fossil-users] JSON API and WSDL

On 09/14/11 11:21, Stephan Beal wrote: Hi, all, It would be cool if the JSON API had a way to serve a WSDL of its API. i'm looking to pick someone's brain about WSDL, namely regarding: a) Is WSDL intended only for SOAP (in which case it is not interesting here)? See section 4 [1] of the WSDL

Re: [fossil-users] Presentation slides for Fossil?

On 09/10/11 15:54, Ron Wilson wrote: On Thu, Sep 8, 2011 at 4:08 PM, Ingo Kochingo.k...@gmx.de wrote: Take a look at http://arnebachmann.pytalhost.de/pdf/integrated-version-control-with-fossil-scm.pdf Good presentation. I noted it said that configuration is not shared. Actually, it is

Re: [fossil-users] sqlite3_prepare_v2() is generating output to stderr?

On 09/09/11 12:31, Stephan Beal wrote: Maybe this is a bug, maybe not, but i've certainly never seen it before... i'm intentionally introducing SQL errors to test my JSON-side error handling, and i found that this: rc = sqlite3_prepare_v2(g.db, zSql, -1, pStmt-pStmt, 0); outputs to stderr

Re: [fossil-users] sqlite3_prepare_v2() is generating output to stderr?

On 09/09/11 12:34, Martin S. Weber wrote: Really? I'm assuming the JSON output goes to stdout, and the error message goes to stderr. In that case it wouldn't interfere with the JSON output at all. Just pipe the output to your json reader without a 21...there'll be no problem. That being said

Re: [fossil-users] Draft doc for JSON/REST Fossil interface

On 09/09/11 13:52, Stephan Beal wrote: (...) While there is arguably little use for JSON in CLI mode, i'm trying to keep it all structured so that i can use the same code/commands in both CLI and CGI/server modes (...) Actually, if the complete CLI functionality was available as JSON output,

[fossil-users] coding style guidelines: c89

Hi, fossil currently does not build in a ANSI C-89 environment - a requirement of the coding style guidelines ([1], point 16). There's an obvious build error in http_ssl.c (C++ style comments), but there's something more in sha1.c... When adding a -std=c89 to the generated Makefile with gcc as

Re: [fossil-users] cannot push or commit

Try setting the autosync URL (fossil remote-url) to http://user@host:port/path. Note the presence of user in the URL. -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] cannot push or commit

On 09/01/11 12:30, Stephan Beal wrote: On Thu, Sep 1, 2011 at 6:23 PM, Martin S. Webermartin.we...@nist.govmailto:martin.we...@nist.gov wrote: Try setting the autosync URL (fossil remote-url) to http://user@host:port/path. Note the presence of user in the URL. To expand on that a bit: if

[fossil-users] Merge two repositories... not.

So, I'm aware of drh's message from 2010-03-06 [1]. Is merging repositories this way still supposed to work? If so, I'll open a ticket with the information below. -Martin [1] http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg01641.html # background: two teams working on some

Re: [fossil-users] Merge two repositories... not.

On 08/24/11 18:14, Martin Gagnon wrote: May be fossil export of one piped on a fossil import of the other one will work!! I never tried but it might work I don't know how would look like the timeline when doing that... Actually I did try fossil deconstruct'ing both repositories into

Re: [fossil-users] Bug: errant operations don't cause exit(EXIT_FAILURE).

On 08/09/11 15:14, Martin S. Weber wrote: I stumbled over this while I had a network outage... ...so what's the new workflow now that I as anonymous cannot create a ticket to capture that problem. Will I get an ACK on this list? Will a ticket be silently created by someone

Re: [fossil-users] Bug: errant operations don't cause exit(EXIT_FAILURE).

On 08/11/11 17:39, Richard Hipp wrote: There are 47 people on this list who have the appropriate credentials to write a ticket and/or make changes to the code. All you have to do is convince 1 out of those 47 people that the problem is worth their time and effort. Or, failing that, you can

[fossil-users] Bug: errant operations don't cause exit(EXIT_FAILURE).

I stumbled over this while I had a network outage... $ until fossil configuration pull all fossil sync ; do echo; echo; date; echo; echo; sleep 5 ; done Bytes Cards Artifacts Deltas Sent: 58 1 0 0 fossil: cannot connect to host

[fossil-users] X-Frame-Options http header

So I wanted to use javadoc/scaladoc style documentation and take advantage of fossils embedded documentation -- I put the scaladoc under repo/docco and happily was going to http://server:port/repo/doc/trunk/docco/index.html - but there noscript was already waiting for me, saying No, no!. I

Re: [fossil-users] database locked on sync

On 08/06/11 12:47, Kevin Quick wrote: $ fossil sync PATH-TO-REPO Bytes Cards Artifacts Deltas Sent:3897 82 0 0 Error: Database error: database is locked DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private) Received:

Re: [fossil-users] database locked on sync

On 08/08/11 16:16, Stephan Beal wrote: 2011/8/8 Lluís Batlle i Rossell virik...@gmail.com mailto:virik...@gmail.com I have fossil repositories opened in multiple directories each, and I only hit database locked troubles if I'm really running at the same time two fossil

[fossil-users] Problem with shunning: files reappear

Hello there! Recently I accidentally added some files that are automatically generated, changing quite often and which I generally don't want under version control at all. So I deleted them (I used show files on the timeline, followed the view links on the files I wanted to get rid of, used

Re: [fossil-users] Problem with shunning: files reappear

On 07/13/11 17:05, Richard Hipp wrote: On Wed, Jul 13, 2011 at 5:02 PM, Martin S. Weber martin.we...@nist.gov mailto:martin.we...@nist.gov wrote: Hello there! Recently I accidentally added some files that are automatically generated, changing quite often and which I

Re: [fossil-users] Version 1.18

On 07/13/11 19:27, Richard Hipp wrote: I have tagged the release of Fossil version 1.18. You can pickup a copy at http://www.fossil-scm.org/download.html Comments on the download page enumerate the changes in this release. This is no compelling reason to upgrade - it just had been a long