[sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

Dear all, Could it be that something is broken with fossil 2.4 windows binary (as available from fossil-scm.org)? When attempting fossil ui the pages served seem to be missing things right after opening resulting in rendering missing styling. For instance: FossilBranches Olivier —

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

On Dec 26, 2017, at 3:35 PM, Olivier Mascia wrote: > > Could it be that something is broken with fossil 2.4 windows binary (as > available from fossil-scm.org)? It works for me. Here’s my test: c:\tmp> fossil new ..\x.fossil c:\tmp> fossil open ..\x.fossil

Re: [sqlite] Move to Github!!?

On Mon, Dec 25, 2017 at 8:24 PM, Jay Kreibich wrote: > > > On Dec 25, 2017, at 12:24 PM, J. King wrote: > > > > SQLite source is managed in a Fossil (not Git) repository, which is > software itself designed by Dr. Hipp and based on SQLite. GitHub would be >

[sqlite] disk io error in vxworks

sqlite bugs in vxworks in function unixTempFileDir, static const char *unixTempFileDir(void){ static const char *azDirs[] = { 0, 0, "/var/tmp", "/usr/tmp", "/tmp", "." }; unsigned int i = 0; struct stat buf; const char *zDir = sqlite3_temp_directory;

Re: [sqlite] LSM extension lsm_work

On 12/25/2017 11:17 PM, Josu Diaz de Arcaya wrote: Hi all, I am very happy with the inclusion of LSM extension in sqlite3's code base. I have a question regarding the merging of segments within the database. I noticed that autowork enabled was not enough for keeping disk consumption at bay,

Re: [sqlite] Move to Github!!?

On Tue, 26 Dec 2017 10:27:39 -0500 "J. King" escribió: > I use Git, but I'm not attached to it. I run my own publicly-accessible > remote (using Gitea), but that would be completely replaceable with Fossil > (which I am very impressed by). > > What's not so easy to replace

Re: [sqlite] SQLite 3.21 on IBM Mainframe - z/OS

Quick update: The -qdll compiler option, needed to enable dynamic extensions, causes problems with some SQLite commands. Removing it fixes those problems. For the time being I've removed the option and I will continue to test. Thank you, mario On 12/25/2017 10:08 PM, Mario Bezzi wrote:

Re: [sqlite] Move to Github!!?

> What's not so easy to replace is the Git integration in my editor (Visual Studio Code) Same here, but I use JetBrains products. I put a bug in the ear of JetBrains. At least its something. Have a good one, all On Tue, Dec 26, 2017 at 9:27 AM, J. King wrote: > I use Git,

Re: [sqlite] Move to Github!!?

On 12/25/17, Shekhar Reddy wrote: > > Is there any particular reason that the source is not moved to GitHub? I > think that would reach more number of people there. > There is a mirror of the SQLite repository on GitHub at https://github.com/mackyle/sqlite

Re: [sqlite] FTS5 crash with NULL in snippet() function's 5th parameter

On 12/26/2017 03:16 AM, Tony Papadimitriou wrote: (SQLite v3.21.0 with FTS5 enabled) If instead of ‘’ (empty string) one uses NULL for the 5th parameter in the snippet() function it consistently crashes. Thanks for reporting this. Now fixed (so that NULL is equivalent to an empty string)

Re: [sqlite] Move to Github!!?

Hi, This is a question I have asked myself many times (I.E. Git projects moving to Fossil). GitHub is well known and boasts over 74 million repositories, yet Fossil, which both hosts and utilises one of the most well-known database systems in the world, I doubt can count a thousand. Even the

Re: [sqlite] Move to Github!!?

I use Git, but I'm not attached to it. I run my own publicly-accessible remote (using Gitea), but that would be completely replaceable with Fossil (which I am very impressed by). What's not so easy to replace is the Git integration in my editor (Visual Studio Code) which allows me to easily

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 9:45 AM, Don V Nielsen wrote: > > What's not so easy to replace is the Git integration in my editor (Visual > Studio Code) > > Same here, but I use JetBrains products. I put a bug in the ear of > JetBrains. At least its something. > > Have a good

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 5:10 AM, Richard Hipp wrote: > On 12/25/17, Shekhar Reddy wrote: > > > > Is there any particular reason that the source is not moved to GitHub? I > > think that would reach more number of people there. > > > > There is a

Re: [sqlite] Move to Github!!?

On Tue, 26 Dec 2017, J Decker wrote: Why aren't you moving all of your GitHub projects over to Fossil! Because Pull Requests, and a larger variety of tools to deal with Git repositories. It is good that such tools are available to help surmount Git's extreme complexity. Are there such

Re: [sqlite] Move to Github!!?

On Tuesday, 26 December, 2017 13:28, J Decker wrote: >On Tue, Dec 26, 2017 at 12:25 PM, Keith Medcalf >wrote: >> Isn't GitHub a place for Gits to hang out, sort of like Twitter is >> a place for Twits to hang out? >Nope that's gitter.im (related, and

Re: [sqlite] Move to Github!!?

On 26 Dec 2017, at 7:07pm, Bob Friesenhahn wrote: > On Tue, 26 Dec 2017, J Decker wrote: > >>> Why aren't you moving all of your GitHub projects over to Fossil! >> >> Because Pull Requests, and a larger variety of tools to deal with Git >> repositories. > > It is

Re: [sqlite] Move to Github!!?

On Dec 26, 2017, at 2:47 AM, J Decker wrote: > > doesn't require a fee unless they want to amke it private. You’re speaking of today’s benevolent policies. Let’s review: 1. SourceForge: Once the largest host of FOSS software, eventually became “evil” in the eyes of many of

Re: [sqlite] Move to Github!!?

On Dec 26, 2017, at 12:07 PM, Bob Friesenhahn wrote: > > On Tue, 26 Dec 2017, J Decker wrote: >>> Why aren't you moving all of your GitHub projects over to Fossil! >>> >> Because Pull Requests, and a larger variety of tools to deal with Git >> repositories. > >

Re: [sqlite] Move to Github!!?

On Tue 26 Dec 2017 3:08 PM, Damien Sykes wrote: > Hi, > This is a question I have asked myself many times (I.E. Git projects moving > to Fossil). > GitHub is well known and boasts over 74 million repositories, yet Fossil, > which both hosts and utilises one of the most well-known database systems

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

> Le 26 déc. 2017 à 23:35, Olivier Mascia a écrit : > > Dear all, > > Could it be that something is broken with fossil 2.4 windows binary (as > available from fossil-scm.org)? > When attempting fossil ui the pages served seem to be missing things right > after opening

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

> Le 27 déc. 2017 à 00:13, Warren Young a écrit : > > On Dec 26, 2017, at 3:35 PM, Olivier Mascia wrote: >> >> Could it be that something is broken with fossil 2.4 windows binary (as >> available from fossil-scm.org)? > > It works for me. > > Here’s my

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

On Dec 26, 2017, at 4:22 PM, Olivier Mascia wrote: > > I have no issues or difficulties with fossil commands themselves and know how > to, for instance, clone and properly open sqlite repository Oh, I thought you were seeing this with your own new repository. Now that I

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 3:31 PM, Keith Medcalf wrote: > > Heavens forbid! > > How is it possible to work if not from a Command-Line window? That is, > YUCK. > Seriously how can anyone get any work done at all without having a command > prompt at which one, how to put this,

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 5:10 AM, Richard Hipp wrote: > > Finally, the use of GitHub would create a reliance on an outside > company over which we have no influence. The people who run GitHub > today seem like great folks. But the company might be sold or fall > under new

Re: [sqlite] Move to Github!!?

Heavens forbid! How is it possible to work if not from a Command-Line window? That is, YUCK. Seriously how can anyone get any work done at all without having a command prompt at which one, how to put this, types commands? I happen to be one of those that holds Ashton-Tate's dBase II (or was

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

> Le 26 déc. 2017 à 23:46, Olivier Mascia a écrit : > >> >> Le 26 déc. 2017 à 23:35, Olivier Mascia a écrit : >> >> Dear all, >> >> Could it be that something is broken with fossil 2.4 windows binary (as >> available from fossil-scm.org)? >> When

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 12:25 PM, Keith Medcalf wrote: > > Isn't GitHub a place for Gits to hang out, sort of like Twitter is a place > for Twits to hang out? > Nope that's gitter.im (related, and integrates well with github for talking about issues and pull requests. Will

Re: [sqlite] Move to Github!!?

What fossil needs is for the UI to perform ALL normal common functions (new, commit, clone,...) WITHOUT having to open a command line window. That is imo the main limitation. - Scott Doctor sc...@scottdoctor.com -

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

On Dec 26, 2017, at 4:45 PM, Olivier Mascia wrote: > >> Le 27 déc. 2017 à 00:39, Warren Young a écrit : >> >> Until drh ships Fossil 2.5, you’ll have to either stick with that workaround >> or build your own fossil.exe against the trunk code. > > Makes

Re: [sqlite] Move to Github!!?

Isn't GitHub a place for Gits to hang out, sort of like Twitter is a place for Twits to hang out? --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users [mailto:sqlite-users-

Re: [sqlite] Move to Github!!?

On Tue 26 Dec 2017 2:09 PM, Warren Young wrote: > On Dec 26, 2017, at 2:47 AM, J Decker wrote: > > > > doesn't require a fee unless they want to amke it private. > > You’re speaking of today’s benevolent policies. > Yes, I completely agree with everything you said. Nicely

Re: [sqlite] Off-topic: is fossil 2.4 (windows binary) broken in some way?

> Le 27 déc. 2017 à 00:39, Warren Young a écrit : > > Until drh ships Fossil 2.5, you’ll have to either stick with that workaround > or build your own fossil.exe against the trunk code. Makes it clear. Thanks. -- Best Regards, Meilleures salutations, Met vriendelijke