Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 30, 2015, at 2:27 AM, Stephan Beal wrote: > > On Sun, Aug 30, 2015 at 10:15 AM, Baptiste Daroussin > wrote: > > Number #1 is the inhability to run "external" hooks easily > > it's difficult to do portably system() is ANSI C. There

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 6:40 PM, Warren Young wrote: > On Aug 30, 2015, at 2:27 AM, Stephan Beal wrote: > > it opens up many more potential failure cases > > I don’t see what’s difficult about failing a transaction if a hook is > defined and the external

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

There are docs on --with-tcl and the commands it provides (see th1.md in the source tree). Also, with Tcl enabled the hooks work perfectly for sending mail and I've personally been doing so for several years on a repository of mine. Sent from my iPhone > On Aug 31, 2015, at 9:40 AM, Warren

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 10:46 AM, Stephan Beal wrote: > > The push fails because a remote hook disallows it. What then? The same thing that happens when you try to push to a read-only repo, or push while the Internet connection is down, or push to a repo you accidentally

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 10:59 AM, Joe Mistachkin wrote: > > > There are docs on --with-tcl and the commands it provides (see th1.md in the > source tree). Yes, I already saw that, via the web: http://fossil-scm.org/index.html/doc/tip/www/th1.md You have to admit, it’s

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 7:27 PM, Warren Young wrote: > > That becomes fossil's problem > > No, it’s the hook-writer’s problem. > > The hook-writer solves that in the normal way: log the problem so that a > human can figure out how to solve it, then retry the commit. > Hooks

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 11:39 AM, Stephan Beal wrote: > > Hooks are not just about emails, but about policy decisions. "Does this file > conform to XYZ." A failure at that level is unrecoverable without changing > the policy. I think we can agree that using hooks to

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 1:56 PM, Warren Young wrote: > On Aug 31, 2015, at 11:46 AM, Warren Young wrote: > > I think we can agree that using hooks to enforce, say, code formatting > rules is a bad idea. > > I did a bit of Googling, and this blog article

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

2015-08-30 4:35 GMT+02:00 Stephan Beal sgb...@googlemail.com: On Sun, Aug 30, 2015 at 4:27 AM, Warren Young w...@etr-usa.com wrote: On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: the number 2 major complaints I heard from user Really? What’s #1 and

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Sun, Aug 30, 2015 at 10:15 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Number #1 is the inhability to run external hooks easily, like execute this script each time a sync is done, for before checking in, run this scripts. (personnally I can live with that) Management

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

Good support for sending email would be wonderful. We are getting along by running rss2email, far from ideal but adequate. On Sun, Aug 30, 2015, 1:55 AM Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2015-08-30 10:27 GMT+02:00 Stephan Beal sgb...@googlemail.com: On Sun, Aug 30, 2015

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Sun, Aug 30, 2015 at 4:27 AM, Warren Young w...@etr-usa.com wrote: On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: the number 2 major complaints I heard from user Really? What’s #1 and #3? :) +1 In some 20 years (as of this coming winter) of

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 29, 2015, at 8:35 PM, Stephan Beal sgb...@googlemail.com wrote: i can count on one hand the number of times i've seen commit messages (in project i work on/contribute to) which span more than two sentences. Well, you may have noticed that I can be verbose. :) Also, I think the

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: the number 2 major complaints I heard from user Really? What’s #1 and #3? :) I find that setting the “block formatting” option in Admin/Settings/Timeline solves most of my problems in this area. I don’t