Re: [fossil-users] fossil CLI tricks: interrupting a commit message
On Mon, Jun 16, 2014 at 11:49 PM, B Harder wrote: > Remember that the buffer is only one level deep, though. A subsequent ^W, ^K > , etc will clobber the previous contents. > > Along lines of Stephan Beals method, I use ":" preceding the fossil command. > So: > > $ : fossil ci -m 'some msg' > > ("$" is shell prompt). While we're on stupid shell tricks... If you setup your $PS1 and PS2 just so you can make your commands safe to cut-n-pase. Set $PS1 to something that starts with ":" and ends with ";", and set $PS2 to just whitespace. I do something similar with the sqlite3 shell... Nico -- ___ 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] fossil CLI tricks: interrupting a commit message
Remember that the buffer is only one level deep, though. A subsequent ^W, ^K , etc will clobber the previous contents. Along lines of Stephan Beals method, I use ":" preceding the fossil command. So: $ : fossil ci -m 'some msg' ("$" is shell prompt). ":" is a command that consumes it's arguments and returns true. On Jun 16, 2014 3:34 PM, "Matt Welland" wrote: > Under bash another way to achieve the goal of temporarily putting your > partially written commit command aside is to do: ^a ^k > This puts your command in the cut buffer. To retrieve it (after having run > fossil gdiff to figure out what you did!) just do: ^y > > > > > On Mon, Jun 16, 2014 at 1:24 PM, Stephan Beal > wrote: > >> Hi, all, >> >> This is for Unix-shell users only (including workalikes on Windows)... >> >> Here's a time-saving tip which i use very often myself, but most CLI >> users i know don't seem to know about: >> >> It often happens that i'm typing a commit message when i decide i need to >> stop and go check if what i'm typing in really reflects reality (or needs >> to be tested). So: >> >> fossil commit -m ". >> >> You can stick that line in your command history without executing it by >> doing the following: >> >> 1) Move your cursor to the beginning of the line. In Bash-like shells >> that's normally Ctrl-A, but many terminals support the Home key as well. >> >> 2) Type the '#' character (shift-3 on a US keyboard). That's the shell's >> comment-to-end-of-line marker. >> >> 3) Tap ENTER >> >> Or, in the Bash shell, simply: >> >> 1) Tap Escape, then type the # character. That does all 3 of the above at >> once. >> >> >> Happy Fossiling! >> >> -- >> - stephan beal >> http://wanderinghorse.net/home/stephan/ >> http://gplus.to/sgbeal >> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of >> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > Matt > -=- > 90% of the nations wealth is held by 2% of the people. Bummer to be in the > majority... > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > ___ 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] fossil CLI tricks: interrupting a commit message
Under bash another way to achieve the goal of temporarily putting your partially written commit command aside is to do: ^a ^k This puts your command in the cut buffer. To retrieve it (after having run fossil gdiff to figure out what you did!) just do: ^y On Mon, Jun 16, 2014 at 1:24 PM, Stephan Beal wrote: > Hi, all, > > This is for Unix-shell users only (including workalikes on Windows)... > > Here's a time-saving tip which i use very often myself, but most CLI users > i know don't seem to know about: > > It often happens that i'm typing a commit message when i decide i need to > stop and go check if what i'm typing in really reflects reality (or needs > to be tested). So: > > fossil commit -m ". > > You can stick that line in your command history without executing it by > doing the following: > > 1) Move your cursor to the beginning of the line. In Bash-like shells > that's normally Ctrl-A, but many terminals support the Home key as well. > > 2) Type the '#' character (shift-3 on a US keyboard). That's the shell's > comment-to-end-of-line marker. > > 3) Tap ENTER > > Or, in the Bash shell, simply: > > 1) Tap Escape, then type the # character. That does all 3 of the above at > once. > > > Happy Fossiling! > > -- > - stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of > those who insist on a perfect world, freedom will have to do." -- Bigby Wolf > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority... ___ 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] fossil CLI tricks: interrupting a commit message
On Mon, Jun 16, 2014 at 2:24 PM, Stephan Beal wrote: > Hi, all, > > This is for Unix-shell users only (including workalikes on Windows)... > > Here's a time-saving tip which i use very often myself, but most CLI users > i know don't seem to know about: > > It often happens that i'm typing a commit message when i decide i need to > stop and go check if what i'm typing in really reflects reality (or needs > to be tested). So: > > fossil commit -m ". > > You can stick that line in your command history without executing it by > doing the following: > > 1) Move your cursor to the beginning of the line. In Bash-like shells > that's normally Ctrl-A, but many terminals support the Home key as well. > > 2) Type the '#' character (shift-3 on a US keyboard). That's the shell's > comment-to-end-of-line marker. > > 3) Tap ENTER > > Or, in the Bash shell, simply: > > 1) Tap Escape, then type the # character. That does all 3 of the above at > once. > On Windows when using cmd.exe, you can do something very similar. Hit home and type "rem" to remark (comment) out the line. The "" part is a literal space character (ascii 32), not the characters '<', 's', etc. Then hit enter. Now you can scroll back up to it later. "rem" is a legacy of command.com. :) SDR ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Working with large repository
Hi, I just want to share some feedback, for fun I tried to convert some of the FreeBSD repositories to fossil to see how it performs I first tried the FreeBSD Documentation repository, to go the easy way I took the FreeBSD git mirror (https://github.com/freebsd/freebsd-doc and run git fast-export --full-tree --all | fossil import --git ../doc.fossil The worked pretty well, and I manage to convert in a few hour the repo, the result it very usable (that wasn't the case a few years ago, some operations where slow) Result is available here: https://fossil.etoilebsd.net/doc if some want to play. At the same time I decided to try with ports and base repository which I would have expected to be a bit more complicated I cloned: https://github.com/freebsd/freebsd and https://github.com/freebsd/freebsd-ports I run the same command for the conversion git fast-export --full-tree --all | fossil import --git ../ports.fossil both are now running for more than 70H and still not finished!!! consuming 100% CPU This is running on pretty descent hardware. hw.model: Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz I guess I would have to run a svndump imported manually if I want a slightly faster conversion to happen, and given how the incremental import works with fossil import --git I cannot imagine running a fossil mirror using that tool. If anyone has ideas on how I can maintain a mirror more easily, tips welcome Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil CLI tricks: interrupting a commit message
Hi, all, This is for Unix-shell users only (including workalikes on Windows)... Here's a time-saving tip which i use very often myself, but most CLI users i know don't seem to know about: It often happens that i'm typing a commit message when i decide i need to stop and go check if what i'm typing in really reflects reality (or needs to be tested). So: fossil commit -m ". You can stick that line in your command history without executing it by doing the following: 1) Move your cursor to the beginning of the line. In Bash-like shells that's normally Ctrl-A, but many terminals support the Home key as well. 2) Type the '#' character (shift-3 on a US keyboard). That's the shell's comment-to-end-of-line marker. 3) Tap ENTER Or, in the Bash shell, simply: 1) Tap Escape, then type the # character. That does all 3 of the above at once. Happy Fossiling! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf ___ 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] How to deal with incomplete code?
On Sat, Jun 14, 2014 at 4:02 PM, wrote: > 2. Can a branch contain only the single incomplete file I'm working on, > but somehow to 'load' this branch together with the 'trunk'? I.e., I want > to have all the files of the current trunk plus the single (or few) file(s) > of my special WIP branch. Is this possible? If yes, how? Merging only merges in to your working space, so if you fetch a commit from your branch, then merge from Trunk, your working space will contain what you are requesting. Usually, after resoling any conflicts, the result would be committed to the branch, but that is not actually required. If you don't, then any fetch from your branch will result in a working space containing out of date files. That is, those files you haven't made changes to will be as they were when the branch was created. Usually this is not desirable as you would then always have to merge in from Trunk. Where as if you committed the result of your merge, you only have to merge when Trunk actually changed. There is only a very tiny cost to committing merged-in files not changed by a branch. The resulting delta will effectively be a pointer to a commit in Trunk (or other branch). Also, any record keeping advantages to not committing the merge is significantly outweighed by the cost of forgetting to merge in changes when checking out your branch. With an up to date branch, the -n option for a merge from your branch will give you a list of the changed files. Also, in the time line, it is easy to distinguish changes from merge-commits, so you can still easily see what files you've been working on. ___ 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] Fossil for Android?
Hi Urmil, actually there is an apk for fossil, though it only supports serving repos AFAIR. https://play.google.com/store/apps/details?id=es.dadbiz.fossil I used it often to backup my repos to my phones sd-card and it worked out quite well. Am 16.06.2014 12:02, schrieb Urmil Parikh: There was some discussion in past about compiling fossil for Android. Is it still alive? Is there any .apk available? ___ 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] 'all changes' missing some name
On 16 June 2014 13:29, Richard Hipp wrote: > > On Mon, Jun 16, 2014 at 7:21 AM, Michai Ramakers > wrote: >> >> $ fossil all changes >> Changes for ??? at /home/michai/proj/046/: >> EDITED db/parts.txt >> EDITED db/supplieritems.txt >> >> What was supposed to be in place of the '???' ? > > The "Project Name" that you set on the top line of the Admin/Configuration > page of the UI. d'oh, I should have known that - thx, and sorry for the noise. Michai ___ 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] 'all changes' missing some name
On Mon, Jun 16, 2014 at 7:21 AM, Michai Ramakers wrote: > Hello, > > $ fossil all changes > Changes for ??? at /home/michai/proj/046/: > EDITED db/parts.txt > EDITED db/supplieritems.txt > > What was supposed to be in place of the '???' ? > The "Project Name" that you set on the top line of the Admin/Configuration page of the UI. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] 'all changes' missing some name
Hello, $ fossil all changes Changes for ??? at /home/michai/proj/046/: EDITED db/parts.txt EDITED db/supplieritems.txt What was supposed to be in place of the '???' ? Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil for Android?
There was some discussion in past about compiling fossil for Android. Is it still alive? Is there any .apk available? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users