Re: [fossil-users] problems with links in embedded documents

On 23 November 2015 at 22:59, Ron W wrote: > > > On Mon, Nov 23, 2015 at 2:19 PM, Richard Hipp wrote: >> >> That's all well and good, but Joerg is right - it would be convenient >> to be able to specify the root of the repository in a hyperlink. I've >> pondered making that possible with some bi

Re: [fossil-users] problems with links in embedded documents

Thus said Warren Young on Mon, 23 Nov 2015 14:43:53 -0700: > Yes. It already has a legal meaning, at least on POSIX-based web > servers. Basically, multiple slashes are suppressed, so that you can > do things like: In some parts of Fossil, // has a different meaning than / in a URL. S

Re: [fossil-users] problems with links in embedded documents

On Mon, Nov 23, 2015 at 2:19 PM, Richard Hipp wrote: > > That's all well and good, but Joerg is right - it would be convenient > to be able to specify the root of the repository in a hyperlink. I've > pondered making that possible with some bit of magic like > "[$ROOT/wcontent]" or "". But it se

Re: [fossil-users] problems with links in embedded documents

On Nov 23, 2015, at 2:43 PM, Warren Young wrote: > > It already has a legal meaning, at least on POSIX-based web servers. Hmmm…apparently Fossil’s internal web server doesn’t know that rule: http://fossil-scm.org/index.html/info//565d1b0a3880421e gives a 404. There’s also no rule that say

Re: [fossil-users] problems with links in embedded documents

On Nov 23, 2015, at 2:09 PM, j. van den hoff wrote: > > from these, I would choose FOSSIL_ROOT. I like “THIS” better, but maybe that’s just my C++ speaking. > would a single slash be out of the question Yes. It already has a legal meaning, at least on POSIX-based web servers. Basically, mul

Re: [fossil-users] problems with links in embedded documents

On 11/23/15, j. van den hoff wrote: >> >> What should the magic symbol be? Some ideas: >> >> FOSSIL_ROOT >> $ >> THIS >> THIS_REPO > > from these, I would choose FOSSIL_ROOT. spontaneous idea: would a single > slash be out of the question, so that the link relative to repo-root w

Re: [fossil-users] problems with links in embedded documents

On Mon, 23 Nov 2015 22:04:07 +0100, Richard Hipp wrote: On 11/23/15, j. van den hoff wrote: On Mon, 23 Nov 2015 20:19:28 +0100, Richard Hipp wrote: That's all well and good, but Joerg is right - it would be convenient to be able to specify the root of the repository in a hyperlink. I've p

Re: [fossil-users] problems with links in embedded documents

On 11/23/15, j. van den hoff wrote: > On Mon, 23 Nov 2015 20:19:28 +0100, Richard Hipp wrote: > >> That's all well and good, but Joerg is right - it would be convenient >> to be able to specify the root of the repository in a hyperlink. I've >> pondered making that possible with some bit of magi

Re: [fossil-users] problems with links in embedded documents

On Mon, 23 Nov 2015 20:19:28 +0100, Richard Hipp wrote: That's all well and good, but Joerg is right - it would be convenient to be able to specify the root of the repository in a hyperlink. I've pondered making that possible with some bit of magic like "[$ROOT/wcontent]" or "". But it seems

Re: [fossil-users] problems with links in embedded documents

On Mon, 23 Nov 2015 20:13:40 +0100, Warren Young wrote: On Nov 23, 2015, at 9:42 AM, j. van den hoff wrote: You could still serve multiple Fossil repositories via your web server’s name-based virtual hosting feature I will have to look into this, thank you for this tip. I was curious,

Re: [fossil-users] problems with links in embedded documents

On 11/23/15, Warren Young wrote: > > I was curious, so I looked into it. The Fossil docs only talk about nginx, > but I’m more familiar with name-based virtual hosting on Apache, so I worked > out how to configure it: That's all well and good, but Joerg is right - it would be convenient to be ab

Re: [fossil-users] problems with links in embedded documents

On Nov 23, 2015, at 9:42 AM, j. van den hoff wrote: > >> You could still serve multiple Fossil repositories via your web server’s >> name-based virtual hosting feature > > I will have to look into this, thank you for this tip. I was curious, so I looked into it. The Fossil docs only talk abou

Re: [fossil-users] problems with links in embedded documents

On Mon, 23 Nov 2015 16:10:02 +0100, Warren Young wrote: On Nov 22, 2015, at 6:47 AM, j. van den hoff wrote: my (obviously wrong/incomplete understanding so far is that `/wcontent' is an absolute path relative to the repository root… I think the problem is that you’re serving a collection

Re: [fossil-users] problems with links in embedded documents

On Nov 22, 2015, at 6:47 AM, j. van den hoff wrote: > > my (obviously > wrong/incomplete understanding so far is that `/wcontent' is an absolute > path relative to the repository root… I think the problem is that you’re serving a collection of Fossils, instead of just one. I don’t use the CGI

[fossil-users] problems with links in embedded documents

I am currently giving embedded docs and the wiki another try (never had much need for it till now) and am having some difficulties regarding cross-linking between an embedded doc and any of the default wiki pages, e.g. `wcontent' in a way that it works on a cgi-served repo and its local clone. con

Re: [fossil-users] Problems with /doc/

> Please try again now. Fixed in 31c3c599ffb1b449, thank you. However I still believe that someday the following would be fixed too: http://localhost:8080/doc (and doc/) should search for tip/index.html and tip/index.md in addition to index.wiki. Same with 404.md. http://localhost:8080/doc/cko

Re: [fossil-users] Problems with /doc/

On 7/15/15, Sergey Sfeli wrote: > http://www.fossil-scm.org/fossil/info/c99b4e34dd1db2cc does not fix an > issue 1 completely: http://localhost:8080/doc//index.md still crashes. > Please try again now. -- D. Richard Hipp d...@sqlite.org ___ fossil-user

Re: [fossil-users] Problems with /doc/

http://www.fossil-scm.org/fossil/info/c99b4e34dd1db2cc does not fix an issue 1 completely: http://localhost:8080/doc//index.md still crashes. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman

[fossil-users] Problems with /doc/

Hello. I've noticed a few issues with an embedded documentation: 1) http://localhost:8080/doc/ crashes a request handler, because zCheckin gets initialized with an empty string in doc_page(), which makes name_to_typed_rid() to return 0 instead of calling fossil_fatal() and this 0 crashes fociFilt

Re: [fossil-users] Problems with the tkt-change-hook branch

2013/10/12 Justin Forest : > Hello. > > I wanted to use the ticket change hooks, and found a problem with the > current code . > I fixed this by replacing the last return TH_OK in submitTicketCmd with > return TH_RETURN. Thank you very much! Your fix is committed now:

[fossil-users] Problems with the tkt-change-hook branch

Hello. I wanted to use the ticket change hooks, and found a problem with the current code. This is how I get the code: 1. fossil update trunk 2. fossil merge tkt-change-hook 3. ./configure && make I'm new to the Fossil code, so I'd appreciate an advice if I did that wrong. The problem wit

Re: [fossil-users] Problems with Fossil 1.26 for Windows

On Tue, Jun 18, 2013 at 9:53 PM, Edward Berner wrote: > > Ugh. I compiled it using a "VS2012 x86 Native Tools Command Prompt" on >> Win8. Anybody have a guess what might have gone wrong? >> >> > It looks like the initial release of Visual Studio 2012 did not support > targeting XP and that Upda

Re: [fossil-users] Problems with Fossil 1.26 for Windows

On 6/18/2013 5:53 PM, Richard Hipp wrote: On Tue, Jun 18, 2013 at 8:05 PM, Richie Adler > wrote: Trying to run the Windows version in Windows XP SP3 gives the error "Not a valid Win32 application". Ugh. I compiled it using a "VS2012 x86 Native Too

Re: [fossil-users] Problems with Fossil 1.26 for Windows

On Tue, Jun 18, 2013 at 9:25 PM, og wrote: > Maybe: > > > Project->Application Properties->Compile > > Set Target CPU to *x86* > > The build was done from the *Command Line Prompt* not from a MSVC GUI, so there is no Project->Application Properties->Compile menu. If I update to http://www.fossil

Re: [fossil-users] Problems with Fossil 1.26 for Windows

Maybe: Project->Application Properties->Compile Set Target CPU to *x86* https://blogs.msdn.com/b/vcblog/archive/2012/10/08/10357555.aspx?Redirected=true t+ og On Tue, Jun 18, 2013 at 9:53 PM, Richard Hipp wrote: > > > On Tue, Jun 18, 2013 at 8:05 PM, Richie Adler wrote: > >> Trying to r

Re: [fossil-users] Problems with Fossil 1.26 for Windows

On Tue, Jun 18, 2013 at 8:05 PM, Richie Adler wrote: > Trying to run the Windows version in Windows XP SP3 gives the error "Not a > valid Win32 application". > > Ugh. I compiled it using a "VS2012 x86 Native Tools Command Prompt" on Win8. Anybody have a guess what might have gone wrong? -- D

[fossil-users] Problems with Fossil 1.26 for Windows

Trying to run the Windows version in Windows XP SP3 gives the error "Not a valid Win32 application". -- o-=< Marcelo >=-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossi

Re: [fossil-users] Problems with renames (patch included)

On Fri, Feb 10, 2012 at 10:32:00AM -0500, Richard Hipp wrote: > 2012/2/10 Lluís Batlle i Rossell > > > > > So, as I said, the patch solves that situation for us. I hope someone can > > review > > the patch. > > > > > A simpler change which accomplishes the same thing has been checked in at > >

Re: [fossil-users] Problems with renames (patch included)

2012/2/10 Lluís Batlle i Rossell > > So, as I said, the patch solves that situation for us. I hope someone can > review > the patch. > > A simpler change which accomplishes the same thing has been checked in at http://www.fossil-scm.org/fossil/ci/f0359882c9?sbs=1 Please let me know if this

[fossil-users] Problems with renames (patch included)

Hello, we found the source of error of our renames. It is not related to what I mentioned on whether we changed the file + rename, or only renamed. It's related to the lack of information in the manifests, when a checkin has multiple parents, about where the rename comes from: the primary, or ano

Re: [fossil-users] problems........

To start with someone must place a note that in windows paths must be treated differently (WITHOUT BEEN A 100% SURE) c:/P/prg1.fossil and not c:\P\prg1.fossil Your Path should point to fossil.exe not to the repository. On Windows Path must not be treated differently, but apparently like the OS

Re: [fossil-users] problems........

On Mon, Jan 16, 2012 at 05:42:59PM +0200, android devkit wrote: > Dear all > I didn’t like to start this email in a negative manner but unfortunately I > will. I have spent 2 days trying to make fossil run in my windows xp > machine. I think troubles like yours are on discussion already. Those inv

Re: [fossil-users] problems........

Looks like you still have a stray _FOSSIL_ file in your C:\. From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of android devkit Sent: maandag 16 januari 2012 16:43 To: fossil-users@lists.fossil-scm.org Subject: [fossil-users

[fossil-users] problems........

Dear all I didn’t like to start this email in a negative manner but unfortunately I will. I have spent 2 days trying to make fossil run in my windows xp machine. To start with someone must place a note that in windows paths must be treated differently (WITHOUT BEEN A 100% SURE) c:/P/prg1.fossil an

[fossil-users] Problems with annotate

Hello, I have problems with annotate giving misleading information. I wrote a ticket: http://fossil-scm.org/index.html/info/f0f9aff371 Maybe asking for a mass 'please try to reproduce it', we can get a public repository which shows the same problem. Regards, Lluís. (Copy of the ticket text belo

[fossil-users] Problems merging with renames

Hello, we had a bad merge, using the latest released fossil (2010-01-01). The merge was removing files it should not remove. Hence I write to the list alerting on the problem. We tracked the problem, and attached proposed patches, in two tickets: http://fossil-scm.org/index.html/info/c9d454153e h

Re: [fossil-users] Problems cloning Repository

Thanks for you answers > Hello, > > I had already sent this mail to the list. But as I did not see it > come back to > me, I am not sure whether it has reached the list or not. So I sent > it again, > this time to you directly. > > Sorry if you get double mail now ... > > > On Fri, 05 Feb 2010

[fossil-users] Problems cloning Repository

Hi, I have a server where I have to run an older version of fossil (Fossil version [0eb08b860c] 2009-09-16 21:29:18). This is part of the distribution running there. I cannot distribute a newer version of fossil to this server. I build a Fossil repository on my local system and copied it

Re: [fossil-users] Problems with server

D. Richard Hipp wrote: > fossil clone http://projecs.theingots.org/cgi-bin/awards.cgi > awards.fossil Server Error: not authorized to clone fossil: server says: not authorized to clone Also, this command seems needlessly redundant. My first reaction was to ask myself why I had to specify "awa

Re: [fossil-users] Problems with server

D. Richard Hipp wrote: > Why did you change the URL? > > fossil clone http://projecs.theingots.org/cgi-bin/awards.cgi > awards.fossil Because that is how I interpreted the documentation. Look: fossil clone http://www.fossil-scm.org/ myclone.fossil Do you see a "project.cgi" anywhere in

Re: [fossil-users] Problems with server

On Jan 20, 2010, at 6:13 PM, Daniel Carrera wrote: > Hello, > > Ok, I've set up a server, and it seems to work: > > http://projects.theingots.org/cgi-bin/awards.cgi > > I created a user name and password. Then on my local computer I did: > > fossil clone http://projects.theingots.org/awards.fossi

[fossil-users] Problems with server

Hello, Ok, I've set up a server, and it seems to work: http://projects.theingots.org/cgi-bin/awards.cgi I created a user name and password. Then on my local computer I did: fossil clone http://projects.theingots.org/awards.fossil awards.fossil This gave some errors: Bytes

Re: [fossil-users] Problems with proxy settings in client server mode with autosync

On 10.11.2009, at 16:14, Franz Brummer wrote: > Sorry for the useless traffic. I've found out what my problem was. I > had the wrong name for the cgi script in the URL of some previous push > or sync action and didn't recognize that I should have specified the > right URL once more. Now it works!

Re: [fossil-users] Problems with proxy settings in client server mode with autosync

On 10.11.2009, at 16:14, Franz Brummer wrote: > Sorry for the useless traffic. I've found out what my problem was. I > had the wrong name for the cgi script in the URL of some previous push > or sync action and didn't recognize that I should have specified the > right URL once more. Now it works!

Re: [fossil-users] Problems with proxy settings in client server mode with autosync

Sorry for the useless traffic. I've found out what my problem was. I had the wrong name for the cgi script in the URL of some previous push or sync action and didn't recognize that I should have specified the right URL once more. Now it works! But anyway I had to look in the apache logs on the ser

Re: [fossil-users] Problems with proxy settings in client server mode with autosync

On Nov 10, 2009, at 7:50 AM, Franz Brummer wrote: > > New_Version: d7edf74845e393a3e3ed4328889f06940ddb1d52 > Autosync: http://icends.his.de/cgi-bin/fossil-server.cgi >Bytes Cards Artifacts Deltas > Send: 27196 16 1 1 > Received:

Re: [fossil-users] Problems with proxy settings in client server mode with autosync

>On Nov 9, 2009, at 8:11 AM, Franz wrote: > >> Hello, >> >> this is my first post on this list so please bear with me! ;-) >> >> I want to set up a central fossil server in our company network. So >> I've created a local repository on my desktop machine, worked there >> for some time and decided it

Re: [fossil-users] Problems with proxy settings in client server mode with autosync

On Nov 9, 2009, at 8:11 AM, Franz wrote: > Hello, > > this is my first post on this list so please bear with me! ;-) > > I want to set up a central fossil server in our company network. So > I've created a local repository on my desktop machine, worked there > for some time and decided it was tim

[fossil-users] Problems with proxy settings in client server mode with autosync

Hello, this is my first post on this list so please bear with me! ;-) I want to set up a central fossil server in our company network. So I've created a local repository on my desktop machine, worked there for some time and decided it was time to make it "public". Like it is recommended in the f