Re: [fossil-users] Patch: Enables integration of syntax highlighting systems

2018-06-29 Thread Sam Putman
On Thu, Jun 28, 2018 at 12:14 PM, Chad Perrin wrote: > On Thu, Jun 28, 2018 at 11:40:01AM -0700, Sam Putman wrote: > > > > As a target, I would suggest the emitted html look as much like this > > as possible: > > > > view-source:https://github.com/jvirkki/libbloo

Re: [fossil-users] Patch: Enables integration of syntax highlighting systems

2018-06-28 Thread Sam Putman
On Thu, Jun 28, 2018 at 9:07 AM, Chad Perrin wrote: > See if this makes sense: > > Apply syntax highlighting to a block of code. Organize the code in > second column TD elements of a table. Organize line numbers in first > column TD elements of a table. > > Thus, you would have HTML for a line

Re: [fossil-users] email testing - no subscriber table?

2018-06-26 Thread Sam Putman
On Mon, Jun 25, 2018 at 2:51 PM, Richard Hipp wrote: > On 6/25/18, jungle Boogie wrote: > > If I inadvertently forward my email along > > to someone/group without modifying the footer, the person/group would > > be able to alter my subscription. > > How can I fix that? > > -- > D. Richard Hipp >

Re: [fossil-users] A fossil library

2018-06-19 Thread Sam Putman
On Tue, Jun 19, 2018 at 11:28 AM, Stephan Beal wrote: > On Tue, Jun 19, 2018 at 8:13 PM Sam Putman wrote: > >> >>> >>>> I got the sense from the docs that the hash is using the SQLite style >>>> versioned API, so it follows that >&g

Re: [fossil-users] A fossil library

2018-06-19 Thread Sam Putman
On Tue, Jun 19, 2018 at 10:20 AM, Stephan Beal wrote: > On Mon, Jun 18, 2018 at 7:18 PM Sam Putman wrote: > >> A Capitalized pure-C struct being referred to as an object is not unheard >> of! But it did lead me down >> the wrong path. >> > > Here's my

Re: [fossil-users] A fossil library

2018-06-18 Thread Sam Putman
On Mon, Jun 18, 2018 at 4:54 AM, Stephan Beal wrote: > On Sun, Jun 17, 2018 at 11:11 PM Sam Putman wrote: > >> On Sun, Jun 17, 2018 at 6:39 AM, David Mason wrote: >> >>> Just had a quick thought that might make the conversion to library much >>> easier. &g

Re: [fossil-users] A fossil library

2018-06-18 Thread Sam Putman
On Mon, Jun 18, 2018 at 4:43 AM, Stephan Beal wrote: > On Sun, Jun 17, 2018 at 11:07 PM Sam Putman wrote: > >> About those objects... >> >> What your docs call fossil(1) is written in plain C. Or rather C, Tcl, >> SQL and TH1, if you prefer. >> In any cas

Re: [fossil-users] A fossil library

2018-06-17 Thread Sam Putman
On Sun, Jun 17, 2018 at 6:39 AM, David Mason wrote: > Just had a quick thought that might make the conversion to library much > easier. > > If you have a relatively small API interface, each of the API functions > could do a setjmp https://en.wikipedia.org/wiki/Setjmp.h and then the > fatal error

Re: [fossil-users] A fossil library

2018-06-17 Thread Sam Putman
On Sun, Jun 17, 2018 at 4:50 AM, Stephan Beal wrote: > On Sat, Jun 16, 2018 at 11:44 PM Sam Putman wrote: > >> >> An incremental refactoring of this into something more modular would >> be a boon to maintenance and testing. Seems like a sleeping dog we can >>

Re: [fossil-users] A fossil library

2018-06-16 Thread Sam Putman
On Sat, Jun 16, 2018 at 3:07 AM, Stephan Beal wrote: > On Sat, Jun 16, 2018 at 12:46 AM Stephan Beal > wrote: > >> i will write a longer response when i'm back on the PC, but short version: >> >> - refactoring to a lib is a huge effort. >> ... >> More details upcoming about that first point in t

[fossil-users] A fossil library

2018-06-15 Thread Sam Putman
ys feel some trepidation towards what amounts to asking other people for free work. I feel this refactoring could benefit fossil as well as my own software. I'd be a part of such an effort as soon as anything halfway plausible was compiling, if invited. Sincerely, -Sam Putman -- Special Circumst