Re: [fossil-users] Suggestion: WIKI command EXPORT clean of tags

On Jun 28, 2017, at 7:57 AM, Tony Papadimitriou wrote: > > However, these formatting tags are displayed cluttering the display (for some > heavily formatted pages to the point of being unreadable). Why not use Markdown formatting then? The same source file that produces pretty

Re: [fossil-users] Suggestion: WIKI command EXPORT clean of tags

On Thu, Jun 29, 2017 at 8:00 AM, wrote: > > Date: Wed, 28 Jun 2017 16:57:29 +0300 > From: "Tony Papadimitriou" > Subject: [fossil-users] Suggestion: WIKI command EXPORT clean of tags > > I use Wiki a lot for keeping short notes/memos

Re: [fossil-users] Suggestion for MERGE default comment

From: Stephan Beal Sent: Sunday, January 17, 2016 3:11 AM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Suggestion for MERGE default comment On Sun, Jan 17, 2016 at 1:53 AM, <to...@acm.org> wrote: important. This is less work than trying to (remember and) type all d

Re: [fossil-users] Suggestion for local/global settings enhancement

This would be a very helpful enhancement. On Sat, Dec 5, 2015 at 1:05 PM, wrote: > > My suggestion is this: > > Have some form of shorthand notation – a text replacement macro, if you > like – (like the string “~global~”, for example – or some other that is > very unlikely to be

Re: [fossil-users] Suggestion for local/global settings enhancement

On 12/5/2015 10:05 AM, to...@acm.org wrote: Certain settings, like ignore-glob or binary-glob can have a really long list of items, which may be edited from time to time. This was the motivation for the invention of "versionable" settings, allowing the list to be maintained in a multi-line

Re: [fossil-users] Suggestion for command-line timeline display

On Oct 1, 2015, at 3:46 PM, Barry Arthur wrote: > > My favourite tool for this sort of thing is supercat: > http://supercat.nosredna.net/ > I don't know if it compiles on Windows. Not unless you build it under Cygwin. A quick scan of the source turns up a number of

Re: [fossil-users] Suggestion for command-line timeline display

Thus said "Tony Papadimitriou" on Thu, 01 Oct 2015 15:29:05 +0300: > I was wondering if the same idea could be used to highlight the > *CURRENT* entry in the timeline (with some soft color---a shade of > blue or green would be nice). You mean like this: fossil time | sed -e

Re: [fossil-users] Suggestion for command-line timeline display

Thus said "Tony Papadimitriou" on Thu, 01 Oct 2015 19:19:55 +0300: > 1. highlight the whole entry, not just the word *CURRENT*, and fossil time | sed -e '/\*CURRENT\*/ { s/.*/^[[1;32m&^[[0;m/ }' I don't know how to detect the current foreground color so if you can figure that out, you can

Re: [fossil-users] Suggestion for command-line timeline display

the rest. -Original Message- From: Andy Bradford Sent: Thursday, October 01, 2015 5:20 PM To: Tony Papadimitriou Cc: Fossil SCM user's discussion Subject: Re: [fossil-users] Suggestion for command-line timeline display Thus said "Tony Papadimitriou" on Thu, 01 Oct 2015 15:2

Re: [fossil-users] Suggestion for command-line timeline display

My favourite tool for this sort of thing is supercat: http://supercat.nosredna.net/ I don't know if it compiles on Windows. On 2 October 2015 at 01:08, Andy Bradford wrote: > Thus said "Tony Papadimitriou" on Thu, 01 Oct 2015 19:19:55 +0300: > > > 1. highlight the

Re: [fossil-users] Suggestion: new TH1 command 'dir' similar to cli 'ls'

On Mon, Aug 10, 2015 at 6:05 PM, Chris ckolum...@ac-drexler.de wrote: I had the need for a very simple blog-like page within the embedded doc functionality where a th1 page (with enabled th1-doc feature) displays a list with links to all documents within a specific folder. Whenever a new

Re: [fossil-users] Suggestion: new TH1 command 'dir' similar to cli 'ls'

Hi Stephan, thanks for the Feedback :-) On Tue, 11 Aug 2015 08:43:28 +0200 Stephan Beal sgb...@googlemail.com wrote: On Mon, Aug 10, 2015 at 6:05 PM, Chris ckolum...@ac-drexler.de wrote: I had the need for a very simple blog-like page within the embedded [...] Who can complain

Re: [fossil-users] [Suggestion] Branch descriptions

On Tue, Jan 6, 2015 at 6:41 AM, Matt Welland estifo...@gmail.com wrote: +1 IMHO this is a good idea. How technically feasible it is I have no idea. agreed. AFAIK, branches currently do not use the VALUE part of the tag. Perhaps such a description could be set there when making a branch, e.g.:

Re: [fossil-users] [Suggestion] Branch descriptions

On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal sgb...@googlemail.com wrote: agreed. AFAIK, branches currently do not use the VALUE part of the tag. Perhaps such a description could be set there when making a branch, e.g.: fossil commit -b new-branch -d branch description -m commit message

Re: [fossil-users] [Suggestion] Branch descriptions

On 1/6/15, Ron W ronw.m...@gmail.com wrote: On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal sgb...@googlemail.com wrote: agreed. AFAIK, branches currently do not use the VALUE part of the tag. Perhaps such a description could be set there when making a branch, e.g.: fossil commit -b

Re: [fossil-users] [Suggestion] Branch descriptions

On Tue, Jan 6, 2015 at 11:50 AM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Jan 6, 2015 at 5:12 PM, Ron W ronw.m...@gmail.com wrote: The sym- one not having a value. Strange to me that 2 tags would be used (I would have thought only the branch tag), but looks like the sym- tag could

Re: [fossil-users] [Suggestion] Branch descriptions

On Tue, Jan 6, 2015 at 5:12 PM, Ron W ronw.m...@gmail.com wrote: The sym- one not having a value. Strange to me that 2 tags would be used (I would have thought only the branch tag), but looks like the sym- tag could be used to hold a branch description. One downside: this precludes modifying

Re: [fossil-users] [Suggestion] Branch descriptions

On Jan 4, 2015, at 10:55 AM, Philip Bennefall phi...@blastbay.com wrote: I don't know what a lot of the branches are and I have no obvious way of finding out. If it’s a temporary branch, e.g. to develop a risky feature before it gets into good enough shape that it can be committed to the

Re: [fossil-users] [Suggestion] Branch descriptions

+1 IMHO this is a good idea. How technically feasible it is I have no idea. On Jan 4, 2015 10:59 AM, Philip Bennefall phi...@blastbay.com wrote: Hi all, I have a quick suggestion to present. While browsing the SqLite timeline, it struck me that I don't know what a lot of the branches are and

Re: [fossil-users] Suggestion for cloning

On Tue, Jul 29, 2014 at 5:10 AM, Andy Bradford amb-fos...@bradfords.org wrote: When cloning a repository, if I don't have write privileges, can autosync by default be set to pullonly in the clone, to prevent annoying pull only - not authorized to push? Are you suggesting that

Re: [fossil-users] Suggestion for cloning

On Mon, Jul 28, 2014 at 10:10 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Baruch Burstein on Sun, 27 Jul 2014 23:31:17 +0300: Maybe this should be the default always, even if I have write permission, in order to prevent accidental pushes? I believe changing the

Re: [fossil-users] Suggestion for cloning

Thus said Ron W on Tue, 29 Jul 2014 12:25:08 -0400: Making autosync default to pull-only would not impact minimize unintentional forks. Actually, it would. Consider this scenario. Tizio clones and uses default autosync. Caglio clones and enabled pull-only. Tizio commits something.

Re: [fossil-users] Suggestion for cloning

On Tue, Jul 29, 2014 at 6:25 PM, Ron W ronw.m...@gmail.com wrote: the push (assuming autosunc isn't pull-only AND the local repo is not no-push). i didn't know about that option (it's called dont-push, though) dont-pushPrevent this repository from pushing from client to

Re: [fossil-users] Suggestion for cloning

On Tue, Jul 29, 2014 at 12:46 PM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Jul 29, 2014 at 6:25 PM, Ron W ronw.m...@gmail.com wrote: the push (assuming autosunc isn't pull-only AND the local repo is not no-push). i didn't know about that option (it's called dont-push, though)

Re: [fossil-users] Suggestion for cloning

Thus said Baruch Burstein on Sun, 27 Jul 2014 23:31:17 +0300: When cloning a repository, if I don't have write privileges, can autosync by default be set to pullonly in the clone, to prevent annoying pull only - not authorized to push? Are you suggesting that the clone detect

Re: [fossil-users] Suggestion about fossil commit

On Mon, Apr 14, 2014 at 12:47:11PM -0400, Martin Gagnon wrote: Le 14 avr. 2014 11:48, Stephan Beal sgb...@googlemail.com a écrit : But, in my defense, (and I just re-read it to be sure I didn't miss it) nowhere in the help documentation (FOSSIL HELP COMMIT) or the comment in the editor (#

Re: [fossil-users] Suggestion about fossil commit

That sounds like a bad idea to me. IMO, this is a case of good enough getting in the way of good as far as solutions to your annoyance. Off the top of my head, I can think of two workflow habits that may help you: 1) set up/turn on gpg signing, so you'll be required to sign commits before

Re: [fossil-users] Suggestion about fossil commit

I often have the same problem for a different reason. I type “f cha” and “f com” so often that sometime instead of “f cha” I accidentally type “f com”. What I would like to have is an extra prompt, “Are you sure (y/N)?” with No default for commits. Since commits are irreversible, I think the

Re: [fossil-users] Suggestion about fossil commit

with # are ignored.) does it say, or even imply, that an empty comment is one of the reasons that will 'abort' the commit. LOL!!! Thanks. -Original Message- From: Martin Gagnon Sent: Monday, April 14, 2014 3:24 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Suggestion about fossil

Re: [fossil-users] Suggestion about fossil commit

On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou to...@acm.org wrote: But, in my defense, (and I just re-read it to be sure I didn't miss it) nowhere in the help documentation (FOSSIL HELP COMMIT) or the comment in the editor (# Enter commit message for this check-in. Lines beginning with

Re: [fossil-users] Suggestion about fossil commit

Le 14 avr. 2014 11:48, Stephan Beal sgb...@googlemail.com a écrit : On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou to...@acm.org wrote: But, in my defense, (and I just re-read it to be sure I didn't miss it) nowhere in the help documentation (FOSSIL HELP COMMIT) or the comment in the

Re: [fossil-users] Suggestion about fossil commit

On 4/14/14, Martin Gagnon eme...@gmail.com wrote: Le 14 avr. 2014 11:48, Stephan Beal sgb...@googlemail.com a écrit : On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou to...@acm.org wrote: But, in my defense, (and I just re-read it to be sure I didn't miss it) nowhere in the help

Re: [fossil-users] Suggestion about fossil commit

On 4/14/14, 9:31 PM, B Harder wrote: [...] Our users shouldn't need CVS, SVN, etc experience to know this. I added documentation to clarify. It might also be useful to add: # (To abort the commit, leave this file unchanged) ...to the commit message, too. -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─

Re: [fossil-users] Suggestion about fossil commit

On 4/14/14, David Given d...@cowlark.com wrote: On 4/14/14, 9:31 PM, B Harder wrote: [...] Our users shouldn't need CVS, SVN, etc experience to know this. I added documentation to clarify. It might also be useful to add: # (To abort the commit, leave this file unchanged) ...to the commit

Re: [fossil-users] Suggestion about fossil commit

Thus said David Given on Mon, 14 Apr 2014 22:28:07 +0100: It might also be useful to add: # (To abort the commit, leave this file unchanged) I was about to point out that this wouldn't be a good idea when using merge --cherrypick because it actually automatically includes the

Re: [fossil-users] Suggestion about fossil commit

Thus said Andy Bradford on Mon, 14 Apr 2014 21:40:00 -0600: ... but apparently Fossil is smart enough to figure out that even with an uncommented line in the commit message, it still treats it as an empty message unless you alter it! Correction, unchanged, not empty. Andy -- TAI64

Re: [fossil-users] Suggestion about fossil commit

This might better be handled with an alias or wrapper script. #!/bin/bash read -p You just ran fossil $@ ; are you sure? yn case $yn in [Yy]* ) /usr/bin/fossil $@ ;; [Nn]* ) echo Whew! Dodged a bullet there! ;; esac Elaborated to suit. - JK On Sun, Apr 13, 2014 at 5:41 PM, Stanislav

Re: [fossil-users] suggestion

* Richard Hipp d...@sqlite.org [20121120 01:13]: On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: -- fossil timeline: I find this really hard to read and use for at least two reasons: I seldom use fossil timeline, preferring instead to run fossil ui and

Re: [fossil-users] suggestion

Le 2012-11-20 à 04:58, Joan Picanyol i Puig lists-fos...@biaix.org a écrit : * Richard Hipp d...@sqlite.org [20121120 01:13]: On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: -- fossil timeline: I find this really hard to read and use for at least two

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 6:13 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff veedeeh...@googlemail.com mostly I would like to get information here whether there are changes (edits, adds, removals...) or not and what files are not tracked. `hg stat' does

Re: [fossil-users] suggestion

On Tue, 20 Nov 2012 00:53:04 +0100, Themba Fletcher themba.fletc...@gmail.com wrote: On Mon, Nov 19, 2012 at 3:46 PM, Themba Fletcher themba.fletc...@gmail.com wrote: On Mon, Nov 19, 2012 at 3:12 PM, j. v. d. hoff veedeeh...@googlemail.com wrote: On Mon, 19 Nov 2012 22:49:22 +0100, Richard

Re: [fossil-users] suggestion

On Tue, 20 Nov 2012 01:13:51 +0100, Richard Hipp d...@sqlite.org wrote: On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: some more remarks from a new user: I've been trying out fossil only for the last two weeks or so. and coming from `mercurial' (and

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 4:30 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: hi there, a modest suggestion: I would prefer (and I believe it actually would be more correct, thought what's correct is always arguable) if `fossil set' would explicitly report not only explicitly set (local)

Re: [fossil-users] suggestion

On Mon, 19 Nov 2012 22:49:22 +0100, Richard Hipp d...@sqlite.org wrote: On Mon, Nov 19, 2012 at 4:30 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: hi there, a modest suggestion: I would prefer (and I believe it actually would be more correct, thought what's correct is always arguable)

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 3:12 PM, j. v. d. hoff veedeeh...@googlemail.com wrote: On Mon, 19 Nov 2012 22:49:22 +0100, Richard Hipp d...@sqlite.org wrote: On Mon, Nov 19, 2012 at 4:30 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: hi there, a modest suggestion: snip -- there seems no

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 3:46 PM, Themba Fletcher themba.fletc...@gmail.com wrote: On Mon, Nov 19, 2012 at 3:12 PM, j. v. d. hoff veedeeh...@googlemail.com wrote: On Mon, 19 Nov 2012 22:49:22 +0100, Richard Hipp d...@sqlite.org wrote: On Mon, Nov 19, 2012 at 4:30 PM, j. v. d. hoff

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: some more remarks from a new user: I've been trying out fossil only for the last two weeks or so. and coming from `mercurial' (and knowing `subversion' to some extent) I find the user interface quite

Re: [fossil-users] suggestion

Le 2012-11-19 à 19:13, Richard Hipp d...@sqlite.org a écrit : On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff veedeeh...@googlemail.com wrote: snip -- the transfer statistics stuff reported at every checkin. usually I don't want to see this. maybe this should be made configurable (or is

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 6:30 PM, Martin Gagnon eme...@gmail.com wrote: Or I suggest a version that refresh always the same line showing a kind of incrementing counter of 'cards' or bytes, so we can see there's activity without being too verbose. ... or something that doesn't start showing the

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 7:36 PM, Dirk Reiners dirk.rein...@gmail.comwrote: On Mon, Nov 19, 2012 at 6:30 PM, Martin Gagnon eme...@gmail.com wrote: Or I suggest a version that refresh always the same line showing a kind of incrementing counter of 'cards' or bytes, so we can see there's

Re: [fossil-users] suggestion

On Mon, Nov 19, 2012 at 9:06 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Nov 19, 2012 at 7:36 PM, Dirk Reiners dirk.rein...@gmail.comwrote: On Mon, Nov 19, 2012 at 6:30 PM, Martin Gagnon eme...@gmail.com wrote: Or I suggest a version that refresh always the same line showing a kind

Re: [fossil-users] Suggestion for the 'ticket' command

Ron Aaron r...@... writes: Is there a reason why it has to be in a valid fossil checkout? It would be convenient if it were possible to specify -R my.fossil, as can be done with a number of other commands. I added the -R option to the ticket command. Wolfgang