[fossil-users] fossil help set no longer provides essential information

Older versions of fossil would provide some very helpful information from "fossil help set": gmerge-command   A graphical merge conflict resolver command operating                  on four files.               Ex: kdiff3 "%baseline" "%original" "%merge" -o "%output"               Ex: xxdiff "%orig

Re: [fossil-users] fossil help set no longer provides essential information

On Fri, 2018-01-05 at 13:42 -0500, Richard Hipp wrote: > On 1/5/18, Matt Welland wrote: > > > > Older versions of fossil would provide some very helpful > > information > > from "fossil help set": > > > > gmerge-command   A graphi

Re: [fossil-users] fossil help set no longer provides essential information

On Fri, 2018-01-05 at 13:06 -0700, Andy Bradford wrote: > Thus said Richard Hipp on Fri, 05 Jan 2018 13:42:29 -0500: > > > > > Maybe  I just  need to  improve the  "fossil help  setting" > > output  to > > provide some clue about how to get help on individual settings? > That would be an  improve

[fossil-users] Thank you developers for the unversioned feature...

I'm finding the unversioned files to be extraordinarily useful. Thanks you all for implementing it. The most recent use case I found was to solve the annoying problem of having some changes that are not quite ready to commit and needing to move to another computer. By storing a patch as an unversi

[fossil-users] 3-way merge likely to happen anytime soon?

I saw a prior thread on this topic but I am not clear on if any action was planned. Not sure yet why but I'm getting a lot more merge conflicts than I did with Monotone. If nothing is being worked on I'll make a perl script helper as fixing merges by editing the files with markers is really tedious

Re: [fossil-users] 3-way merge likely to happen anytime soon?

Hipp wrote: > Just to clearify, by "3-way merge", you mean a graphical merging tool? I > ask because Fossil always has done a 3-way merge behind the scenes - it just > doesn't show you what it is doing or give you the opportunity to intervene. > > On Sun, Feb 20, 2011 a

Re: [fossil-users] 3-way merge likely to happen anytime soon?

I tested [691fccbaf7] and it seems to work great! I still get conflicts where I suspect I would not have in the past (i) but they are no big deal with a little help from xxdiff. Thanks!! (i) I have no defensible evidence for this claim. If anyone

[fossil-users] symlinks to directories are traversed by fossil extras?

What is the plan for handling symlinks for fossil? My preference would be for fossil to treat links as a file. Storing the pointer would be great. Just ignoring links would also be fine by me. But actually traversing the links is not a good idea IMHO and is a real fossil killer. It is also not easy

Re: [fossil-users] Work flow with fossil (understanding conflict resolution)

For a very nice (IMHO) model on how to handle forks take a look at monotone. Forking is natural, you just want to take precautions to keep your data safe. A fork is just a branch you haven't given a name to and didn't necessarily intentionally create. In the case of monotone it just lets you know y

[fossil-users] A crazy idea, but perhaps it has merit ...

I don't have a lot of public stuff out there yet (my fossils are at www.kiatoa.com/fossils/opensrc) but there have been several times where I made a typo or minor mistake and it would have saved some embarrassment *and* been really cool to be able to browse to the file and make a change and check i

[fossil-users] ignore-glob behavior - fossil extras taking inordinate amount of time

Does fossil descend into directories filtered out by ignore-glob? I have a repo which contains a directory with links to a large (hundreds of megs) amount of data and "fossil extras" takes over fifteen minutes to complete. I added a pattern to prevent those files from showing up in the listing in t

Re: [fossil-users] ignore-glob behavior - fossil extras taking inordinate amount of time

On Wed, Apr 13, 2011 at 8:57 PM, Joshua Paine wrote: > On 4/13/2011 11:41 PM, Matt Welland wrote: >> "fossil extras" takes over fifteen minutes >> to complete. > > Any chance you're running an older fossil? I had similar problems with > an old fossil almost

Re: [fossil-users] SharpFossil/WinFossil

Rather than changing the terminal user interface (it will be slightly less nice IMHO due to the extra newline on a prompt) I suggest considering the approach used on the monotone project. A separate interface for automation. Make the human friendly interface friendly to humans and make the automati

Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!

You have no trunk. I can reproduce what you saw by cloning mongrel, opening it, then doing the update. If you have no trunk you probably want to add the branch you want to your open "fossil open ../mongrel.fossil ws-hybi-7" The fix in fossil would be to have a real branch selected on open if one i

Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!

One correction, you do have a "trunk" but fossil is not recognizing it: fossil branch /tmp/mongrel proxymustdie * ws-hybi-7 That looks like a fossil bug to me since "trunk" is not marked as closed as far as I can tell. On Sat, May 21, 2011 at 9:29 AM,

Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!

Hi Zed, Please confirm if you really lost local changes. That would be a big concern for me. I haven't lost any non-checked in work and would like to keep it that way. No tool is perfect and if there is a bug in fossil that causes local changes to be inadvertently discarded we'd all like to know

Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!

On Sat, May 21, 2011 at 11:13 AM, Zed A. Shaw wrote: > On Sat, May 21, 2011 at 10:57:45AM -0700, Matt Welland wrote: >> Hi Zed, >> >> Please confirm if you really lost local changes. That would be a big >> concern for me. I haven't lost any non-checked in work a

Re: [fossil-users] Partial commit after merge

===Remigiusz Modrzejewski wrote:=== "What is exactly the design idea that prohibits merging only a few files? It would certainly be useful in this kind of untangling mess that I have to do now. Which I have to do by having two open local copies and manual copying :/" ==

Re: [fossil-users] Needed: volunteer to autoconf Fossil

All of these alternative build systems are a PITA on one system or another. If it requires jam, cmake or anything that requires installing prerequisites 9 times out of 10 I won't even try that software unless there is a binary install available somewhere or a pre-assembled Makefile. I thought that

Re: [fossil-users] Can't make gdiff work

Are you using fossil compiled for cygwin or fossil compiled for windows? If the later then internally it will not know about cygwin paths and may not be able to launch cygwin binaries (not sure on that one, haven't tested it). On Tue, Jun 28, 2011 at 8:34 AM, Brian Cottingham wrote: > I'm using F

Re: [fossil-users] Needed: volunteer to autoconf Fossil

As an end user this appears to the best alternative I've seen so far. The fact that autosetup presents a familiar ./configure && make interface is fantastic - if it really works as advertised. Does the cross compilation really work? I'd really like to put fossil on my n900 but I don't want to set

Re: [fossil-users] Needed: volunteer to autoconf Fossil

Worked great for me on two Ubuntu machines. One mildly unusual thing, "make install" uses mv to put the binary in /usr/local/bin. Normally I think autoconf generated Makefiles will use install or a sh script to emulated install and keeps the executable in the build dir. Probably no big deal but why

Re: [fossil-users] Converting from mercurial

Lack of hooks is a hassle for me too. Wrapper scripts don't meet the need - especially on the server side. Part of the power of hooks is that you don't have to replicate the effort of parsing the command line to know what is being done. An example: I have a regression system running and when co

[fossil-users] Any way to create a branch *not* derived from any other branch?

I'm in the habit of keeping a good number of completely independent projects in a single fossil db. This is a hold over from how I used to use monotone. These are all very small projects that would be annoying to keeping in separate fossil files. When I imported from monotone everything worked as I

Re: [fossil-users] Any way to create a branch *not* derived from any other branch?

On Sun, Aug 7, 2011 at 11:47 AM, Richard Hipp wrote: > On Sun, Aug 7, 2011 at 1:21 PM, Matt Welland wrote: > >> I'm in the habit of keeping a good number of completely independent >> projects in a single fossil db. This is a hold over from how I used to use >> monot

Re: [fossil-users] Why do people create branches as a separate step? Was: Unable to sign manifest

I often am planning a change or thinking ahead and will create the branch to record my intentions before I've started coding. I do like the ability to checkin changes to a branch but would generally not intentionally use it out of the risk of forgetting that my changes are intended for a branch and

Re: [fossil-users] Why do people create branches as a separate step? Was: Unable to sign manifest

On Tue, Aug 9, 2011 at 9:25 AM, Ron Wilson wrote: > On Tue, Aug 9, 2011 at 10:58 AM, Richard Hipp wrote: > > The way I've *always* done things is: > > > > (1) ... edit files > > (2) fossil commit -branch new-branch > > > > But I see many people want to do a 4-step process: > > > >

Re: [fossil-users] New features for merging

2011/8/15 Lluís Batlle i Rossell > On Mon, Aug 15, 2011 at 02:41:48AM +, altufa...@mail.com wrote: > > Me too like fossil because of simplicity of one file / less file clutter. > Why can't versionable settings be treated like a wiki or ticket page and > versioned inside the repository itself

Re: [fossil-users] Broken when checkout on root filesystem (/)

Hi Martin, I think fixing the bug of fossil having trouble running in / should be a very low priority. It just seems like a bad idea to me in general to try to run a scm out of / and spending time fixing bugs with respect to that ability is not time well spent. But that is just my $0.02. In case

[fossil-users] symlink causes problems - how to debug?

To work around a tool issue in one of our repositories we need to have a symlink that points to "/". Yes, we know this is bad but it works and we can't fix the root cause of the problem. Running fossil extras never comes back. I assume because fossil traverses the link and then tries to read though

Re: [fossil-users] Testing for a release

I have switched to the new "trunk" and I think it address the issue I had with symlinks (sent in separate mail). Thanks! The empty-dirs works as advertised but I have an enhancement request. If I specify a multilevel directory and the upper levels do not exist the directory is silently skipped. Ei

[fossil-users] .svg files in .wiki, could one of embed, object or iframe be safely added to the allowed html in .wiki files?

The following when loaded directly by firefox showed the LaTeX_logo.svg but when accessed as http://localhost:8081/doc/ckout/www/AnotherExample.wiki none of the embed, object or iframe tags were recognized. % cat AnotherExample.wiki AnotherExample This is to test that HTML is working Could one

Re: [fossil-users] .svg files in .wiki, could one of embed, object or iframe be safely added to the allowed html in .wiki files?

2011 at 4:03 PM, Matt Welland wrote: > The following when loaded directly by firefox showed the LaTeX_logo.svg but > when accessed as > http://localhost:8081/doc/ckout/www/AnotherExample.wiki none of the embed, > object or iframe tags were recognized. > > % cat AnotherE

Re: [fossil-users] .svg files in .wiki, could one of embed, object or iframe be safely added to the allowed html in .wiki files?

- Venkat > > > -Original Message- From: Matt Welland > Sent: Monday, August 29, 2011 21:40:44 Subject: Re: [fossil-users] > .svg files in .wiki, could one of embed, object or iframe be safely > added to the allowed html in .wiki files? > > On further researching th

Re: [fossil-users] Is it possible to edit a ticket's submission time?

How many tickets are we talking about? If it is only a few then perhaps try the following: # Set your system date to the date for the ticket sudo date -s "08/11/2011" # create the ticket fossil ui # repeat for remaining tickets Maybe do it in a virtualbox instance just be sure to put the date b

[fossil-users] fossil performance testing and is it possible to increase the sqlite3 timeout?

We are revisiting fossil for use in our team and I've been doing a little performance testing. One thing that we've seen is when two people access the central repo simultaneously sometimes sync can fail and you get the "continue without sync: y/N" question. This is benign enough and recovery is eas

Re: [fossil-users] Is it possible to edit a ticket's submission time?

s to make a backup of the fossil, set the date and add ticket, 2 minutes to reboot (slow netbook) and sync. On Sat, Sep 3, 2011 at 1:27 AM, Remigiusz Modrzejewski wrote: > > On Sep 2, 2011, at 10:40 PM, Stephan Beal wrote: > > > On Fri, Sep 2, 2011 at 9:48 PM, Matt Welland > wr

[fossil-users] Pushing the limits; SQL error: string or blob too big

I am continuing to test the limits of fossil and I've run into an interesting case where I can't merge. I'd like to know how I could recover from this. Note, this is from running the scripts (two in parallel) that I put at :http://chiselapp.com/user/kiatoa/repository/testfossil with more and larger

Re: [fossil-users] new fossil docs: is the wiki or embedded docs preferred?

On Thu, Sep 15, 2011 at 3:50 AM, Richard Hipp wrote: > > > On Thu, Sep 15, 2011 at 5:11 AM, Stephan Beal wrote: > >> Hi, all, >> >> When adding new docs (for the up-coming json bits), which is the currently >> preferred approach: wiki or embedded docs ? >> > > I've grown to prefer embedded docs,

[fossil-users] Pseudo file locking using a wiki page to transport lock information.

Hi All, I started writing a proof of concept for this idea but have a time crunch and won't be working on it again for a few weeks so I'm putting it out here in case it sparks interest/debate. Definition of "binary": File for which no automatic merging is viable. Motive: concurrent editing of bi

Re: [fossil-users] Pseudo file locking using a wiki page to transport lock information.

One qualification to what I wrote below. The "setuid wrapper" and "special user id" is to address other requirements unique to my situation (access control to branches) and is not relevant to the locking idea. Please disregard it. Thanks. On Sat, Sep 24, 2011 at 8:41 AM,

Re: [fossil-users] Listing artifact IDs for shunning?

On Tue, Oct 4, 2011 at 2:24 PM, Steve Havelka wrote: > On 10/4/11 4:11 PM, Dmitry Chestnykh wrote: > >> Found it. In the UI, go to the "Files" section, select a file, click on "Shun" in the menu bar, and finalize with "Rebuild". As has already been said, you don't really want to d

Re: [fossil-users] Listing artifact IDs for shunning?

On Wed, Oct 5, 2011 at 12:19 AM, Eric wrote: > > On Wed, October 5, 2011 6:14 am, Matt Welland wrote: > ... > > Every time pragmatism loses to philosophy someone, somewhere, is gonna > get > > screwed. > > But "pragmatic" decisions made by someone

[fossil-users] fossil should know to open up perms on a file prior to update if no write access.

Here is the sequence of events. A developer accidentally (and naively) checked in a file with no write permissions. On changing the file and checking it in others could not do an update and would get something like this: > fossil update UPDATE foo.txt fossil: unable to open file "/tmp/mrwellan/t

Re: [fossil-users] fossil should know to open up perms on a file prior to update if no write access.

My description was a bit off. The developer who initially checked in the file without write permission is the one who cannot do the update. The problem is not that fossil is storing or handling the perms wrong. The issue is that a controlled file with no write permission causes fossil to barf on an

Re: [fossil-users] fossil should know to open up perms on a file prior to update if no write access.

On Thu, Oct 6, 2011 at 12:07 AM, Stephan Beal wrote: > On Wed, Oct 5, 2011 at 11:20 PM, Matt Welland wrote: > >> "fossil: unable to open file "/tmp/mrwellan/testing/test/foo.txt" for >> writing" >> >> The remainder of the message confused the de

Re: [fossil-users] fossil should know to open up perms on a file prior to update if no write access.

On Thu, Oct 6, 2011 at 9:32 AM, Stephan Beal wrote: > On Thu, Oct 6, 2011 at 6:28 PM, Matt Welland wrote: > >> Of course it is easy to fix. But why expose your users to all the >> distracting and irrelevant junk in the error message? If possible report the >> fact that

Re: [fossil-users] fossil should know to open up perms on a file prior to update if no write access.

Ah, cool!! I assumed the SQLITE error was somehow related to the non-writablitiy of the file. I'll read more carefully and dig a little deeper next time so the feedback can be of higher quality. On Thu, Oct 6, 2011 at 10:27 AM, Richard Hipp wrote: > > > On Wed, Oct 5, 2011 at

Re: [fossil-users] fossil should know to open up perms on a file prior to update if no write access.

tes received UPDATE foo.txt ./fossil: unable to open file "/tmp/mrwellan/testing/test/foo.txt" for writing Rolling back prior filesystem changes... UNDO foo.txt chlr11723> On Thu, Oct 6, 2011 at 10:34 AM, Matt Welland wrote: > Ah, cool!! I assumed the SQLITE error was somehow rela

Re: [fossil-users] Honor REMOTE_USER by default?

Or at least make the setting controllable from "fossil settings" so it can be scripted up. If it is already I wasn't able to figure out how to do it On Tue, Oct 11, 2011 at 1:59 PM, Richard Hipp wrote: > If you are using .htaccess style authentication for a Fossil instance on a > website, yo

[fossil-users] locking down tags, or at least capturing their state at a point in time ...

As far as I can tell if a tag is moved (added to another commit and deleted from the old commit) there is no easily accessible history kept as to where it pointed to in the past, is that correct? I couldn't see any option for getting the history of a tag in the ui. Since accidentally moving a tag

Re: [fossil-users] locking down tags, or at least capturing their state at a point in time ...

On Sun, Oct 16, 2011 at 1:46 PM, Richard Hipp wrote: > > > On Sun, Oct 16, 2011 at 4:01 PM, Matt Welland wrote: > >> As far as I can tell if a tag is moved (added to another commit and >> deleted from the old commit) there is no easily accessible history kept as >>

Re: [fossil-users] Opinions on some changes out of trunk (Was: Merging my two branches into trunk)

2011/10/15 Lluís Batlle i Rossell > On Sat, Oct 15, 2011 at 06:32:53AM -0400, Richard Hipp wrote: > > I will entertain arguments to move the merge-conflict reporting changes > back > > into trunk. But I need to hear some arguments in favor of that change > > before moving forward with it. > > In

Re: [fossil-users] adding empty directory to repository

On Mon, Oct 17, 2011 at 5:00 AM, Jiri Navratil wrote: > Hello, > > How I can add empty directory to repository? fossil add is not doing that > for me. > You can use the empty-dirs setting if you like. Create a directory .fossil-settings and a file in it called empty-dirs. Put the dirs you want

Re: [fossil-users] Veracity (was: Fwd: suggestion on fossil)

I sent out a description of how I think light weight "locks" could be implemented on top of fossil in a past email. In fact I'm making some good progress on implementing what I want in a wrapper around fossil (implement locks in addition to some other things). I can look into making the wrapper ava

Re: [fossil-users] Veracity (was: Fwd: suggestion on fossil)

awesomeness of Fossil itself. :-) > Agreed :) > > On Wed, Oct 19, 2011 at 4:24 PM, Matt Welland wrote: > >> I sent out a description of how I think light weight "locks" could be >> implemented on top of fossil in a past email. In fact I'm making some goo

Re: [fossil-users] Veracity (was: Fwd: suggestion on fossil)

On Wed, Oct 19, 2011 at 8:46 PM, Mike Meyer wrote: > On Wed, 19 Oct 2011 16:24:17 -0700 > Matt Welland wrote: > > > I sent out a description of how I think light weight "locks" could be > > implemented on top of fossil in a past email. In fact I'm making some

Re: [fossil-users] More thoughts on locks

2011/10/20 Lluís Batlle i Rossell > Thinking as if we had to implement locks some day... > > I just thought that we could have locks working not on > file-paths-in-branch, but > on artifacts. That would expand well to multiple branches. > > Then, if anyone gets the lock, and commits a new version

Re: [fossil-users] Veracity

On Thu, Oct 20, 2011 at 10:07 AM, Mike Meyer wrote: > On Thu, Oct 20, 2011 at 3:46 AM, Martin Gagnon wrote: > >> On 2011-10-20, at 01:13, Jeff Slutter wrote: >> >> > A couple weeks ago I posted about the possibility of a new configuration >> setting called something like "allow-binmerge" (defau

Re: [fossil-users] Creating new branch/repository problems

Lets go though it step by step to ensure we aren't making wrong assumptions about what you are doing. I'm not trying to be condescending, I know you probably already know all this but from the error message it is very unclear what is going on. It looks to me like you are on Linux, is that correct?

Re: [fossil-users] Creating new branch/repository problems

On Sun, Oct 23, 2011 at 12:17 PM, Jared Harder wrote: > @Matt: I followed the directions and eventually started up a second server. > I needed to use fossil server instead because I couldn't access the fossil > ui interface from external machines. The README file I edited showed up in > the new

Re: [fossil-users] Fossil Repository Does Not Exist Error

I usually open the _FOSSIL_ file with sqlite3 and update the pointer to the repo db. A "repodb reset" command or some such would be nice to have. matt@hermes> sqlite3 _FOSSIL_ ~/data/opensrc SQLite version 3.7.5 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> upda

[fossil-users] Cloning, syncing via ssh appears to hang...

I'm on Linux and commands such as the following appear to hang: fossil clone ssh://u...@host.domain.tld/path/repo.fossil repo.fossil I have ssh with keys (passwordless login) working fine. How to debug this? fossil version This is fossil version 1.19 [6517b5c857] 2011-09-01 18:25:19 UTC ___

Re: [fossil-users] Cloning, syncing via ssh appears to hang...

On Mon, Nov 7, 2011 at 9:21 PM, Eduardo Tongson wrote: > On Tue, Nov 8, 2011 at 4:00 AM, Matt Welland wrote: > > I'm on Linux and commands such as the following appear to hang: > > > > fossil clone ssh://u...@host.domain.tld/path/repo.fossil repo.fossil &g

[fossil-users] Quickref available for fossil

I'm teaching a class on using fossil next week and put together a quick ref sheet to help folks get going. I haven't seen any other quick ref sheets for fossil so maybe this will be of use to others. PDF: http://www.kiatoa.com/cgi-bin/fossils/opensrc/doc/tip/docs/fossil-quickref.pdf Opendoc: http:

Re: [fossil-users] Quickref available for fossil

24, 2011 at 10:54 PM, Richard Hipp wrote: > > > On Fri, Nov 25, 2011 at 5:43 AM, Matt Welland wrote: > >> I'm teaching a class on using fossil next week and put together a quick >> ref sheet to help folks get going. I haven't seen any other quick ref >&

Re: [fossil-users] Quickref available for fossil

a transport mechanism is working for them and provide me with an example URL I'd appreciate it. Thanks, Matt -=- On Fri, Nov 25, 2011 at 1:50 AM, Richard Hipp wrote: > On Fri, Nov 25, 2011 at 6:21 AM, Matt Welland wrote: > >> >> I don't have -y documented in my curre

[fossil-users] A couple thoughts/suggested future enhancements for fossil, ui security, move and ssh access

fossil ui == problem: on a shared machine it is possible to accidentally browse someones already-running ui session possible solutions 1. only the first "login" is passwordless, subsequent logins require a password 2. a random key is passed to the browser in the URL, only with that key is the

Re: [fossil-users] A couple thoughts/suggested future enhancements for fossil, ui security, move and ssh access

in 0.3 seconds Bytes per second: sent 7697.3, received 6667.9 debug1: Exit status 0 end transcript=== On Fri, Nov 25, 2011 at 11:44 AM, Joerg Sonnenberger < jo...@britannica.bec.de> wrote: > On Fri, Nov 25, 2011 at 11:17:20AM -0700, Matt Welland wrote: > > s

Re: [fossil-users] hidden files on linux support?

Perhaps you want: fossil add --dotfiles . On Fri, Dec 2, 2011 at 11:41 AM, Stephan Beal wrote: > On Fri, Dec 2, 2011 at 7:36 PM, Oliver Friedrich wrote: > >> i'm testing out fossil for my source, found an interesting issue. >> >> Checking in files and folders leaves out hidden files, on linux

Re: [fossil-users] hidden files on linux support?

On Fri, Dec 2, 2011 at 4:03 PM, Eric wrote: > On Fri, December 2, 2011 7:26 pm, Stephan Beal wrote: > > On Fri, Dec 2, 2011 at 8:17 PM, Eric wrote: > > > >> Why on earth would you want to? > >> > >> I know others have offered suggestions and explanations for how to do > >> it, > >> but I would n

Re: [fossil-users] hidden files on linux support?

On Sat, Dec 3, 2011 at 4:16 AM, Eric wrote: > On Fri, December 2, 2011 11:39 pm, Matt Welland wrote: > > On Fri, Dec 2, 2011 at 4:03 PM, Eric wrote: > > > >> On Fri, December 2, 2011 7:26 pm, Stephan Beal wrote: > >> > On Fri, Dec 2, 2011 at 8:17 PM, Eric

[fossil-users] FYI - fossil on n900 works great. Using as sync for zim

Just in case it piques anyones interest, I'm using fossil on my n900 phone to sync zim data to from my desktop and netbook. I like the fit between zim and the "Getting Things Done" methodology ( http://zim-wiki.org/manual/Usage/Getting_Things_Done.html). I just installed scratchbox (aprox 1/2 hr)

[fossil-users] It would be nice if sync collisions failed more gracefully

This is on NFS and with a large check in so it is worst case scenario but still I'm seeing this error when people simultaneously do certain heavy weight actions. Are there any settings that would help here? I've dug though the docs and not seen anything yet. I'll dig though the code tonight but p

Re: [fossil-users] It would be nice if sync collisions failed more gracefully

x27;t clear in my message, these are being served directly by file access, not http and via NFS from multiple hosts. I don't think wal is a safe option. > On 12/07/2011 07:48 PM, Richard Hipp wrote: > > > > On Wed, Dec 7, 2011 at 7:15 PM, Matt Welland wrote: > >> Thi

Re: [fossil-users] Fossil version 1.21

The changes include: "Stop showing the server-code in status outputs - it is no longer used for anything." I've been using the server code extracted with "fossil info" to uniquely identify repos. Is there a new way? I assume that the server code itself continues to exist? On Tue, Dec 13, 2011 at

Re: [fossil-users] Fossil version 1.21

On Tue, Dec 13, 2011 at 10:43 AM, Richard Hipp wrote: > > > On Tue, Dec 13, 2011 at 12:33 PM, Matt Welland wrote: > >> The changes include: "Stop showing the server-code in status outputs - it >> is no longer used for anything." >> >> I've bee

[fossil-users] fossil timeline after/before date interpretation

I'm not getting what I would expect from running fossil timeline commands. The example command below should have suppressed the 2011-12-01 entry should it not? chlr11723> fossil timeline after '2011-12-06 00:09:08' -R fossil.fossil === 2011-12-13 === 14:05:36 [489c67ae46] Update the release date o

[fossil-users] bug in user handling

Based on what I've tried so far fossil ui will *always* choose the first user listed in the user table. None of $USER, --user, -U, default-user in global-config or in config will override fossil ui using the first user listed. This is a problem because cloning from a file will preserve the users a

Re: [fossil-users] Behavior of rm, mv, and changes/extra

A "-f" option on rm and mv might do the trick. Default behavior doesn't change. Add two characters to force the filesystem action. On Wed, Dec 21, 2011 at 3:07 PM, Dmitry Chestnykh wrote: > On Wed, 21 Dec 2011 16:52:54 -0500 Jeremy Cowgar wrote: > > > fossil rm should not remove a file it doesn't

Re: [fossil-users] fossil not tracking directories / dir artifacts after switching branches

I think a good algorithm would be quite simple: If a file being removed as part of a checkout to a different branch is the last file in a directory and the directory is not listed in the empty-dirs entry then remove the directory. This should have zero negative impact on anyone and during the ea

Re: [fossil-users] fossil not tracking directories / dir artifacts after switching branches

On Thu, Dec 22, 2011 at 6:15 PM, Richard Hipp wrote: > The rmdir(2) system call on Posix is a no-op if the directory is not > empty. So I was thinking that we could just invoke rmdir() (or _rmdir() on > windows) on the directory of a file every time a file is deleted, and let > the OS worry abou

Re: [fossil-users] PDF as embedded documentation

I have been doing exactly the same thing. A LaTeX (lyx) document plus a make file that writes out html and a pdf and it seems to work great. I suppose it may depend on just how much in the way of hard to compress pictures comprise your document. I do wish there was a way with the embedded document

Re: [fossil-users] Work from Windows and Linux simultaneously.

Essentially the request here is to support a relative path to the .fossil file in the _FOSSIL_ file. This would be very useful for me and as far as I can tell there is no good technical reason why it would not work just fine. John's desired work strategy can easily be supported with the relative p

Re: [fossil-users] Work from Windows and Linux simultaneously.

could well end up on the wish list as a low priority but I don't see any compelling technical reasons why relative paths wouldn't work fine. On Sat, Jan 28, 2012 at 2:00 PM, Stephan Beal wrote: > On Sat, Jan 28, 2012 at 9:58 PM, Matt Welland wrote: > >> John's de

Re: [fossil-users] Work from Windows and Linux simultaneously.

On Sat, Jan 28, 2012 at 2:54 PM, Richard Hipp wrote: > > > On Sat, Jan 28, 2012 at 3:58 PM, Matt Welland wrote: > >> Essentially the request here is to support a relative path to the .fossil >> file in the _FOSSIL_ file. >> > > >> i. Use the path to the

Re: [fossil-users] PDF as embedded documentation

lyx in this case) the fossil heading, menu etc. goes away. I may not have it set up optimally however. > Thanks, > > Tomek > > On Fri, Jan 20, 2012 at 7:28 PM, Matt Welland wrote: > >> I have been doing exactly the same thing. A LaTeX (lyx) document plus a >> make

Re: [fossil-users] How to limit "fossil diff" output to just names of the changed files?

On Tue, Jan 31, 2012 at 11:41 AM, Leo Razoumov wrote: > Hi All, > I am a new Fossil SCM user and it is my first posting to this mailing > list. Please, forgive me if what I am asking has been discussed and > answered here before. > > When I do > sh$ fossil diff --from ver1 --to ver2 > I get t

Re: [fossil-users] How to limit "fossil diff" output to just names of the changed files?

On Thu, Feb 2, 2012 at 1:32 PM, Heinrich Huss < heinrich.h...@psh-consulting.de> wrote: > Why not using 'fossil change'? > Or am I missing the point? > As far as I can tell fossil changes doesn't take --to and --from > Regards > Hein > > Am 02.02.2012 18:35, schrieb Leo Razoumov: > > 2012/2/2

Re: [fossil-users] Retro side-by-side diffs

On Fri, Feb 3, 2012 at 8:25 AM, Richard Hipp wrote: > For some time now, the SQLite and Fossil websites have been running on the > "retro-sbsdiff" branch of Fossil. The retro-sbsdiff branch uses a vastly > simplified format for the side-by-side diffs that omits all of the colors > and decoration

[fossil-users] fossil rm followed by unix rm followed by update and files come back, is this desirable?

If I do: fossil rm some/file.txt rm some/file.txt ...do stuff... fossil update then some/file.txt is resurrected which is really really annoying when you just got your build to work and then because files that shouldn't be there suddenly reappear and things break. I can see where might be some c

Re: [fossil-users] fossil rm followed by unix rm followed by update and files come back, is this desirable?

On Fri, Feb 3, 2012 at 9:46 AM, Dmitry Chestnykh wrote: > On Fri, 3 Feb 2012 09:18:32 -0700 Matt Welland wrote: > > > If I do: > > > > fossil rm some/file.txt > > rm some/file.txt > > fossil commit > People often prefer to commit when their work has reache

Re: [fossil-users] Retro side-by-side diffs

Seconded. The hidden lines receive more emphasis than the change. Do a tkdiff on the same change and it is immediately obvious what the change is. I checked meld, tkdiff and xxdiff and in all of them the actual character that was removed is also highlighted making it immediately obvious what change

Re: [fossil-users] zip/tar patch

On Sat, Feb 11, 2012 at 7:55 AM, frantisek holop wrote: > > any interest in this simple patch? > I think the proposed behavior is a good way to go. > hmm, on Tue, Feb 07, 2012 at 07:48:30PM +0100, frantisek holop said that > > hi there, > > > > the motivation for this patch was that the zip an

[fossil-users] With jimtcl available can we have hooks that trigger tcl scripts stored in the db?

I think it may be very useful if it was possible to call tcl scripts stored in the repo db (revision controlled files or wiki pages?) at pre/post commit and other interesting times. I know hooks were previously not accepted since making things consistent between Windows and Linux was difficult. Bu

Re: [fossil-users] With jimtcl available can we have hooks that trigger tcl scripts stored in the db?

On Mon, Feb 13, 2012 at 1:43 PM, Steve Bennett wrote: > > On 14/02/2012, at 4:22 AM, Matt Welland wrote: > > I think it may be very useful if it was possible to call tcl scripts > stored in the repo db (revision controlled files or wiki pages?) at > pre/post commit and other in

Re: [fossil-users] With jimtcl available can we have hooks that trigger tcl scripts stored in the db?

On Mon, Feb 13, 2012 at 7:26 PM, Leo Razoumov wrote: > On Mon, Feb 13, 2012 at 18:30, Gé Weijers wrote: > > On Mon, Feb 13, 2012 at 1:49 PM, Steve Bennett > > wrote: > >> > >> Joe Mistachkin has recently added support for calling TH1 scripts on > >> certain actions. > >> See http://www.fossil-s

[fossil-users] fsl wrapper script, might be of use to others ...

I have written a wrapper script for fossil that makes some minor adaptions to accommodate a somewhat more Unix centric use model and where a large number of repos must be dealt with. In the off chance that others may find it useful I'm making it available at: http://chiselapp.com/user/kiatoa/reposi

Re: [fossil-users] Behavior of rm, mv, and changes/extra

On Tue, Feb 28, 2012 at 5:28 AM, Richard Hipp wrote: > > > On Tue, Feb 28, 2012 at 2:06 AM, Gour wrote: > >> On Wed, 21 Dec 2011 12:25:19 -0500 >> Richard Hipp wrote: >> >> > I fear to change it now, though, since it might really mess up people >> > who are used to the older style. >> >> What a

Re: [fossil-users] Overwriting binary files on 'update'

On Thu, Mar 1, 2012 at 8:03 AM, Leo Razoumov wrote: > 2012/3/1 Lluís Batlle i Rossell : > > Hello, > > > > in fossil 1.21, I've a modified openoffice file. Then I run "fossil > update", and > > it tells me there is a merge conflict with a binary file, that it cannot > merge. > > > > What I'm surp

  1   2   3   4   >