Re: [fossil-users] Who runs Fossil servers on Windows?

[The Tick]

On 8/7/2018 11:55 AM, Richard Hipp wrote:

If you are running a Fossil server on Windows, please share with me
how you set it up.  You can respond via private email directly to me
if you like.

  (1)  Run using "fossil server"
  (2)  Run using "fossil winsrv"
  (3)  Using Apache with CGI
  (4)  Using Apache with SCGI
  (5)  Using Nginx with SCGI
  (6)  Via SSH using some kind of SSHD for Windows
  (7)  Some other webserver (please specify)
  (8)  Other (please specify)

I have the impression that most if not all Fossil servers on Windows
are run using either (1) or (2).  If you are using any of the other
approaches, then I especially want to hear from you.

Thanks.



I played with fossil under windows and, as far as I know, got it to 
work. I used the Abyss Web Server. At one time I set up port forwarding 
on my router for another little project and friends were able to connect 
successfully although they did not access the fossil stuff.


A link in a web page:
Tcl CWind extension

cgi-bin/fossil:
#!C:/bin/fossil.exe
directory: C:/Progra~1/AbyssW~1/htdocs/FossilRepositories
notfound: /badfossil.php

.../htdocs/Fossil/Repositories contains hardlinks to the actual fossil 
repositories:
htdocs/Fossil/Repositories/CWind.fossil  
C:/Users//Downloads/MyTclStuff/CWind.fossil


badfossil.php:

  
Fossil Repository Not Found
  
  
Fossil Repository Not Found

  





I asked some time ago if there was a way to pass more specific 
information to the "badfossil.php" page but, since I got no response, I 
assume the answer is "no".


___
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] email testing - no subscriber table?

[The Tick]

On 6/24/2018 2:04 PM, Richard Hipp wrote:


I do not (yet) have the bounce-processing logic working in the new
email notification system working, and so Fossil was not able to
detect that your confirmation request had bounced.




Thought I'd mention this. My ISP implements an anti-spam technique that 
saves the sender's hostname and/or IP and bounces the first email from 
that sender as temporarily unavailable (or something like that). 
Subsequent emails are accepted. The idea being that a spammer's email 
software won't bother dealing with temporary failures. It seems to work 
pretty well.


___
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 cgi: provide more info to notfound url?

[The Tick]

I was toying with fossil as cgi on win7. I installed the Abyss server 
and setup a cgi-bin/fossil:


#!C:/bin/fossil.exe
directory: C:/Progra~1/AbyssW~1/htdocs/FossilRepositories
notfound: /badfossil.php

with badfossil.php being:


  
Fossil Repository Not Found
  
  



When I used a URL to a non-existent repository:

http:://localhost/cgi-bin/fossil/bogus

It does run /badfossil.php -- but there seems to be no way to issue an 
error message referring to "bogus". I can find nothing in the server 
supplied environment that lets me identify a more specific error than a 
generic "fossil repository not found".


I am just wondering if there would be some way to be more specific. 
Maybe have the "badfossil.php" be run with some arguments? Maybe the 
original URL?


I tried this naive patch:


--- main.c.orig 2018-03-17 14:22:53.994344800 -0500
+++ main.c  2018-03-22 15:08:22.098101700 -0500
@@ -1539,7 +1539,14 @@
   && repo_list_page() ){
   /* Will return a list of repositories */
 }else if( zNotFound ){
+#if 1
+char t[1000];
+strcpy( t, zNotFound );
+strcat( t, "?repo=missing.fossil" );
+cgi_redirect(t);
+#else
   cgi_redirect(zNotFound);
+#endif
 }else{
 #ifdef FOSSIL_ENABLE_JSON
   if(g.json.isJsonMode){


This does work. PHP tells me:

$_REQUEST['repo']   missing.fossil
$_GET['repo']   missing.fossil
$_SERVER['QUERY_STRING']repo=missing.fossil
$_SERVER['SCRIPT_URL']  /badfossil.php?repo=missing.fossil
$_SERVER['SCRIPT_URI']  http://localhost/badfossil.php?repo=missing.fossil
$_SERVER['REQUEST_URI'] /badfossil.php?repo=missing.fossil

It looks to me that it is feasible to provide more information on the 
notfound url. I do not know if my patch above is the right place to 
start or whether it might mess something else up.

___
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] Any way to cleanup global _fossil or .fossil?

[The Tick]

On 3/19/2018 3:45 PM, Richard Hipp wrote:

But it seems like a relatively harmless issue.  How bit is your _fossil file?


It's only 50K so yes, it's harmless. I was just wondering if there was 
an easy way to clean it up.

___
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] Any way to cleanup global _fossil or .fossil?

[The Tick]

On 3/19/2018 3:29 PM, Richard Hipp wrote:

On 3/19/18, The Tick <the.t...@gmx.com> wrote:


I noticed that my AppData/Local/_fossil file is growing. Using sqlite3
on that file shows a bunch of items that are no longer valid.


I think the "fossil all list" command will automatically remove
entries that are no longer valid.



That did not seem to do much (if anything). There are still records for 
repositories that no longer exist. In addition -- this is windows: 
fossil is recording repository path names where only the alphabetic case 
differs (my lazy typing) but, of course, they all refer to the same file.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Any way to cleanup global _fossil or .fossil?

[The Tick]

I noticed that my AppData/Local/_fossil file is growing. Using sqlite3 
on that file shows a bunch of items that are no longer valid.


I assume this is because I've deleted a lot of temp repository checkouts 
without remembering to do a 'fossil close'.


The sqlite3 'select * from global_config' list also shows what appear to 
be a bunch of duplicates.


It also shows the certificate from chiselapp.com which I guess I want to 
keep.


So is there a way to cleanup obsolete entries but leave valid ones?
___
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] Web interface: "ls -l" list of files?

[The Tick]

On 3/19/2018 2:44 PM, Stephan Beal wrote:

On Mon, Mar 19, 2018 at 7:30 PM, The Tick <the.t...@gmx.com
<mailto:the.t...@gmx.com>> wrote:

Is there a was to get a "ls -l" style list of the files in a
repository from the web interface? I see "Tree-View" or "File Ages"
but the listing of "ages" seems to be relative to the last commit time.


A related sidebar: fossil doesn't actually store the creation- or
modification times of files. The only timestamps it remembers are when
changes are made to the repository (a checkin, wiki/ticket edit, new tag
applied to a commit, etc.). When fossil tells you the age of a file,
it's really showing you the timestamp of the commit which most recently
modified that file.



I see. I was mistakenly under the impression that fossil would preserve 
the timestamps on a checkout so that 'make' would work correctly. I 
didn't think about the fact that one does not store the intermediate or 
targets of a build in the repository -- one builds from scratch and when 
a product is shelved for a while, one just does a final commit, closes 
the repository and deletes the checkout.


That clears things up. Thanks.


___
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] Web interface: "ls -l" list of files?

[The Tick]

On 3/19/2018 1:33 PM, Richard Hipp wrote:

On 3/19/18, The Tick <the.t...@gmx.com> wrote:

Is there a was to get a "ls -l" style list of the files in a repository
from the web interface? I see "Tree-View" or "File Ages" but the listing
of "ages" seems to be relative to the last commit time. For instance, a
"Tree-View" on a repository that I have not touched for several months
shows file ages in minutes rather than months.


Not at the moment.  Easy enough to add, though.  Do you have a patch?  ;-)

I took a look and it is far beyond my ability to add. Thanks for your 
answer though.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Web interface: "ls -l" list of files?

[The Tick]

Is there a was to get a "ls -l" style list of the files in a repository 
from the web interface? I see "Tree-View" or "File Ages" but the listing 
of "ages" seems to be relative to the last commit time. For instance, a 
"Tree-View" on a repository that I have not touched for several months 
shows file ages in minutes rather than months.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Turning off GCC's "helpful" ansi color escape sequences in error/warning messages

[The Tick]

Seems to me that most people will either use script or redirect the make 
output to a file. Computers are simply too fast and the output too 
voluminous to catch warnings and errors as they scroll by. If you use 
GCC you will probably have noticed that it inserts ansi color escape 
sequences in an attempt to highlight portions of the messages. If you 
peruse the typescript file or log file of your build then these escape 
sequences are very distracting and make it more difficult than necessary 
to read the message. GCC does have an option to turn them off.


For fossil builds on windows, create a file "config.w32" in the fossil 
root directory with the contents:


CFLAGS=-fno-diagnostics-color

For unix (which I have not used for a while) I suspect you could just 
invoke configure with:


env CFLAGS=-fno-diagnostics-color ./configure ...
___
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] Errors in current trunk (24c2b99d) related to TIMESPEC

[The Tick]

On 1/9/2018 2:35 PM, Stephan Beal wrote:


On Tue, Jan 9, 2018 at 9:09 PM, The Tick <the.t...@gmx.com
<mailto:the.t...@gmx.com>> wrote:

  src/cson_amalgamation.c: In function 'cson_str_to_json':
  src/cson_amalgamation.c:3888:51: warning: '%04x' directive writing
4 bytes into a region of size between 3 and 5 [-Wformat-overflow=]
   rc = sprintf(ubuf, "\\u%04x\\u%04x",
 ^~~~
  src/cson_amalgamation.c:3888:40: note: directive argument in the
range [56320, 57343]
   rc = sprintf(ubuf, "\\u%04x\\u%04x",
  ^~~~
  src/cson_amalgamation.c:3888:24: note: 'sprintf' output between 13
and 15 bytes into a destination of size 13
   rc = sprintf(ubuf, "\\u%04x\\u%04x",
   ~~~^
(0xd800 | (ch>>10)),

(0xdc00 | (ch & 0x3ff)));



That buffer has been increased to 20 bytes. Please try with the latest
trunk. Thank you for your persistence!

http://fossil-scm.org/fossil/info/e508424e7d7863e1



Zero errors or warnings. Very nice. Thank you.

___
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] Errors in current trunk (24c2b99d) related to TIMESPEC

[The Tick]

On 1/9/2018 1:50 PM, Richard Hipp wrote:

On 1/9/18, The Tick <the.t...@gmx.com> wrote:


Fossil 666fc089b8 compiles successfully although there are still a few
warnings for shell.c. Thank you.



What about the later 9a33a240 check-in.  Does it fix all the warnings for you?



Fossil 9a33a240 compiles >much< cleaner -- there are no warnings for shell.c

$ Fossil-9a33a240/fossil.exe version -v
  This is fossil version 2.5 [9a33a240a2] 2018-01-09 14:29:29 UTC
  Compiled on Jan  9 2018 13:44:57 using mingw32 (64-bit)
  Schema version 2015-01-24
  zlib 1.2.11, loaded 1.2.11
  hardened-SHA1 by Marc Stevens and Dan Shumow
  SSL (OpenSSL 1.1.0f  25 May 2017)
  FOSSIL_ENABLE_LEGACY_MV_RM
  FOSSIL_ENABLE_EXEC_REL_PATHS
  FOSSIL_ENABLE_TH1_DOCS
  FOSSIL_ENABLE_TH1_HOOKS
  TCL (Tcl 8.6.6, loaded TH_OK: 8.6.8)
  USE_TCL_STUBS
  FOSSIL_TCL_STUBS
  FOSSIL_ENABLE_TCL_PRIVATE_STUBS
  JSON (API 20120713)
  MBCS_COMMAND_LINE
  FOSSIL_STATIC_BUILD
  SQLite 3.22.0 2018-01-09 14:27:58 a7446d3217
  SQLITE_DEFAULT_FILE_FORMAT=4
  SQLITE_DEFAULT_WAL_SYNCHRONOUS=1
  SQLITE_ENABLE_DBSTAT_VTAB
  SQLITE_ENABLE_FTS3_PARENTHESIS
  SQLITE_ENABLE_FTS4
  SQLITE_ENABLE_FTS5
  SQLITE_ENABLE_JSON1
  SQLITE_ENABLE_LOCKING_STYLE=0
  SQLITE_ENABLE_STMTVTAB
  SQLITE_LIKE_DOESNT_MATCH_BLOBS
  SQLITE_MAX_EXPR_DEPTH=0
  SQLITE_OMIT_DECLTYPE
  SQLITE_OMIT_DEPRECATED
  SQLITE_OMIT_GET_TABLE
  SQLITE_OMIT_LOAD_EXTENSION
  SQLITE_OMIT_PROGRESS_CALLBACK
  SQLITE_OMIT_SHARED_CACHE
  SQLITE_THREADSAFE=0
  SQLITE_USE_ALLOCA

The only warnings I get are:

  gcc -Wall -Wdeclaration-after-statement -Os -Lsrc/../compat/zlib 
-Isrc/../compat/zlib -Lsrc/../compat/openssl-1.1.0f 
-Isrc/../compat/openssl-1.1.0f/include 
-Lsrc/../compat/Tcl8.6.6srcdir/win 
-Isrc/../compat/Tcl8.6.6srcdir/generic 
-Isrc/../compat/Tcl8.6.6srcdir/win -DBROKEN_MINGW_CMDLINE=1 
-DFOSSIL_ENABLE_SSL=1 -DFOSSIL_ENABLE_EXEC_REL_PATHS=1 
-DFOSSIL_ENABLE_LEGACY_MV_RM=1 -DFOSSIL_ENABLE_TH1_DOCS=1 
-DFOSSIL_ENABLE_TH1_HOOKS=1 -DFOSSIL_ENABLE_TCL=1 
-DFOSSIL_ENABLE_TCL_STUBS=1 -DUSE_TCL_STUBS 
-DFOSSIL_ENABLE_TCL_PRIVATE_STUBS=1 -DFOSSIL_ENABLE_JSON=1  -I. -Isrc -c 
src/cson_amalgamation.c -o wbld/cson_amalgamation.o

  src/cson_amalgamation.c: In function 'cson_str_to_json':
  src/cson_amalgamation.c:3888:51: warning: '%04x' directive writing 4 
bytes into a region of size between 3 and 5 [-Wformat-overflow=]

   rc = sprintf(ubuf, "\\u%04x\\u%04x",
 ^~~~
  src/cson_amalgamation.c:3888:40: note: directive argument in the 
range [56320, 57343]

   rc = sprintf(ubuf, "\\u%04x\\u%04x",
  ^~~~
  src/cson_amalgamation.c:3888:24: note: 'sprintf' output between 13 
and 15 bytes into a destination of size 13

   rc = sprintf(ubuf, "\\u%04x\\u%04x",
   ~~~^
(0xd800 | (ch>>10)),

(0xdc00 | (ch & 0x3ff)));



GCC has the following that can remove "bogus" warnings:

#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wformat-overflow"

  :
  :

#pragma GCC diagnostic pop


I have no idea if other compilers have a method to avoid warning 
messages in particular circumstances.

___
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] Errors in current trunk (24c2b99d) related to TIMESPEC

[The Tick]

On 1/8/2018 6:57 PM, Richard Hipp wrote:

On 1/8/18, The Tick <the.t...@gmx.com> wrote:


Curious about the new skins, I attempted to compile Fossil-24c2b99d on
win7x64 with a current (as of today) MSYS2 using



There are changes on trunk that might fix these build problem.  But,
as nobody here has been able to reproduce them, we cannot be sure.
Therefore, please try the latest trunk check-in and see if it is
working better for you and report back.  Thanks.



Fossil 666fc089b8 compiles successfully although there are still a few 
warnings for shell.c. Thank you.


$ Fossil-666fc089/fossil version -v
  This is fossil version 2.5 [666fc089b8] 2018-01-09 02:28:19 UTC
  Compiled on Jan  9 2018 02:10:43 using mingw32 (64-bit)
  Schema version 2015-01-24
  zlib 1.2.11, loaded 1.2.11
  hardened-SHA1 by Marc Stevens and Dan Shumow
  SSL (OpenSSL 1.1.0f  25 May 2017)
  FOSSIL_ENABLE_LEGACY_MV_RM
  FOSSIL_ENABLE_EXEC_REL_PATHS
  FOSSIL_ENABLE_TH1_DOCS
  FOSSIL_ENABLE_TH1_HOOKS
  TCL (Tcl 8.6.6, loaded TH_OK: 8.6.8)
  USE_TCL_STUBS
  FOSSIL_TCL_STUBS
  FOSSIL_ENABLE_TCL_PRIVATE_STUBS
  JSON (API 20120713)
  MBCS_COMMAND_LINE
  FOSSIL_STATIC_BUILD
  SQLite 3.22.0 2018-01-09 02:27:13 cba0206a15
  SQLITE_DEFAULT_FILE_FORMAT=4
  SQLITE_DEFAULT_WAL_SYNCHRONOUS=1
  SQLITE_ENABLE_DBSTAT_VTAB
  SQLITE_ENABLE_FTS3_PARENTHESIS
  SQLITE_ENABLE_FTS4
  SQLITE_ENABLE_FTS5
  SQLITE_ENABLE_JSON1
  SQLITE_ENABLE_LOCKING_STYLE=0
  SQLITE_ENABLE_STMTVTAB
  SQLITE_LIKE_DOESNT_MATCH_BLOBS
  SQLITE_MAX_EXPR_DEPTH=0
  SQLITE_OMIT_DECLTYPE
  SQLITE_OMIT_DEPRECATED
  SQLITE_OMIT_GET_TABLE
  SQLITE_OMIT_LOAD_EXTENSION
  SQLITE_OMIT_PROGRESS_CALLBACK
  SQLITE_OMIT_SHARED_CACHE
  SQLITE_THREADSAFE=0
  SQLITE_USE_ALLOCA


FYI, here are the warnings:

  gcc -Wall -Wdeclaration-after-statement -Os -Lsrc/../compat/zlib 
-Isrc/../compat/zlib -Lsrc/../compat/openssl-1.1.0f 
-Isrc/../compat/openssl-1.1.0f/include 
-Lsrc/../compat/Tcl8.6.6srcdir/win 
-Isrc/../compat/Tcl8.6.6srcdir/generic 
-Isrc/../compat/Tcl8.6.6srcdir/win -DBROKEN_MINGW_CMDLINE=1 
-DFOSSIL_ENABLE_SSL=1 -DFOSSIL_ENABLE_EXEC_REL_PATHS=1 
-DFOSSIL_ENABLE_LEGACY_MV_RM=1 -DFOSSIL_ENABLE_TH1_DOCS=1 
-DFOSSIL_ENABLE_TH1_HOOKS=1 -DFOSSIL_ENABLE_TCL=1 
-DFOSSIL_ENABLE_TCL_STUBS=1 -DUSE_TCL_STUBS 
-DFOSSIL_ENABLE_TCL_PRIVATE_STUBS=1 -DFOSSIL_ENABLE_JSON=1  -I. -Isrc 
-Dmain=sqlite3_shell -DSQLITE_SHELL_IS_UTF8=1 
-DSQLITE_OMIT_LOAD_EXTENSION=1 -DUSE_SYSTEM_SQLITE= 
-DSQLITE_SHELL_DBNAME_PROC=fossil_open -Daccess=file_access 
-Dsystem=fossil_system -Dgetenv=fossil_getenv -Dfopen=fossil_fopen   -c 
src/shell.c -o wbld/shell.o

  src/shell.c: In function 'fsdirNext':
  src/shell.c:2505:30: warning: passing argument 2 of '_stat64i32' from 
incompatible pointer type [-Wincompatible-pointer-types]

 if( lstat(pCur->zPath, >sStat) ){
^
  src/shell.c:2079:38: note: in definition of macro 'lstat'
   #  define lstat(path,buf) _stat(path,buf)
^~~
  In file included from src/shell.c:108:0:
  D:/msys64/mingw64/x86_64-w64-mingw32/include/sys/stat.h:101:28: note: 
expected 'struct _stat64i32 *' but argument is of type 'struct _stat64 *'
 __CRT_INLINE int __cdecl _stat64i32(const char *_Name,struct 
_stat64i32 *_Stat)

  ^~
  src/shell.c: In function 'fsdirFilter':
  src/shell.c:2639:26: warning: passing argument 2 of '_stat64i32' from 
incompatible pointer type [-Wincompatible-pointer-types]

 if( lstat(pCur->zPath, >sStat) ){
^
  src/shell.c:2079:38: note: in definition of macro 'lstat'
   #  define lstat(path,buf) _stat(path,buf)
^~~
  In file included from src/shell.c:108:0:
  D:/msys64/mingw64/x86_64-w64-mingw32/include/sys/stat.h:101:28: note: 
expected 'struct _stat64i32 *' but argument is of type 'struct _stat64 *'
 __CRT_INLINE int __cdecl _stat64i32(const char *_Name,struct 
_stat64i32 *_Stat)

  ^~


And for completeness, here is the 'make' command I've been using:

$ make \
-f win/Makefile.mingw \
X64=1 \
FOSSIL_TCL_SOURCE=0 \
FOSSIL_ENABLE_JSON=1 \
FOSSIL_ENABLE_SSL=1 \
FOSSIL_BUILD_SSL=1 \
FOSSIL_ENABLE_EXEC_REL_PATHS=1 \
FOSSIL_ENABLE_LEGACY_MV_RM=1 \
FOSSIL_ENABLE_TH1_DOCS=1 \
FOSSIL_ENABLE_TH1_HOOKS=1 \
FOSSIL_ENABLE_TCL=1 \
FOSSIL_ENABLE_TCL_STUBS=1 \
FOSSIL_ENABLE_TCL_PRIVATE_STUBS=1 \
OPENSSLDIR='$(SRCDIR)/../compat/'$OPENSSLDIR \
TCLDIR='$(SRCDIR)/../compat/'$TCLDIR \
TCLSRCDIR='$(SRCDIR)/../compat/'$TCLSRCDIR



___
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] Errors in current trunk (24c2b99d) related to TIMESPEC

[The Tick]

On 1/8/2018 4:40 PM, Richard Hipp wrote:

On 1/8/18, Richie Adler  wrote:


AFAIK MSYS has a version number in the directory.
At the very list you should probably check the gcc version with "gcc -v"



It works for me on Win7 running gcc 4.5.0 and on Win10 running gcc 5.3.0.



Curious about the new skins, I attempted to compile Fossil-24c2b99d on 
win7x64 with a current (as of today) MSYS2 using


$ gcc -v
  Using built-in specs.
  COLLECT_GCC=D:\msys64\mingw64\bin\gcc.exe

COLLECT_LTO_WRAPPER=D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/7.2.0/lto-wrapper.exe
  Target: x86_64-w64-mingw32
  Configured with: ../gcc-7.2.0/configure --prefix=/mingw64 
--with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 
--host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 
--with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include 
--libexecdir=/mingw64/lib --enable-bootstrap --with-arch=x86-64 
--with-tune=generic 
--enable-languages=c,lto,c++,objc,obj-c++,fortran,ada --enable-shared 
--enable-static --enable-libatomic --enable-threads=posix 
--enable-graphite --enable-fully-dynamic-string 
--enable-libstdcxx-time=yes --disable-libstdcxx-pch 
--disable-libstdcxx-debug --disable-isl-version-check --enable-lto 
--enable-libgomp --disable-multilib --enable-checking=release 
--disable-rpath --disable-win32-registry --disable-nls --disable-werror 
--disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 
--with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 
--with-pkgversion='Rev1, Built by MSYS2 project' 
--with-bugurl=https://sourceforge.net/projects/msys2 --with-gnu-as 
--with-gnu-ld

  Thread model: posix
  gcc version 7.2.0 (Rev1, Built by MSYS2 project)


I get a slew of errors for src/shell.c

Using the same setup, fossil-2.4 compiles successfully.

$ f version -v
  This is fossil version 2.4 [a0001dcf57] 2017-11-03 09:29:29 UTC
  Compiled on Nov 11 2017 20:48:11 using mingw32 (64-bit)
  Schema version 2015-01-24
  zlib 1.2.11, loaded 1.2.11
  hardened-SHA1 by Marc Stevens and Dan Shumow
  SSL (OpenSSL 1.1.0f  25 May 2017)
  FOSSIL_ENABLE_LEGACY_MV_RM
  FOSSIL_ENABLE_EXEC_REL_PATHS
  FOSSIL_ENABLE_TH1_DOCS
  FOSSIL_ENABLE_TH1_HOOKS
  TCL (Tcl 8.6.6, loaded TH_OK: 8.6.7)
  USE_TCL_STUBS
  FOSSIL_TCL_STUBS
  FOSSIL_ENABLE_TCL_PRIVATE_STUBS
  JSON (API 20120713)
  MBCS_COMMAND_LINE
  FOSSIL_STATIC_BUILD
  SQLite 3.21.0 2017-10-24 18:55:49 1a584e4999
  SQLITE_DEFAULT_FILE_FORMAT=4
  SQLITE_DEFAULT_WAL_SYNCHRONOUS=1
  SQLITE_ENABLE_DBSTAT_VTAB
  SQLITE_ENABLE_FTS3_PARENTHESIS
  SQLITE_ENABLE_FTS4
  SQLITE_ENABLE_FTS5
  SQLITE_ENABLE_JSON1
  SQLITE_ENABLE_LOCKING_STYLE=0
  SQLITE_ENABLE_STMTVTAB
  SQLITE_LIKE_DOESNT_MATCH_BLOBS
  SQLITE_MAX_EXPR_DEPTH=0
  SQLITE_OMIT_DECLTYPE
  SQLITE_OMIT_DEPRECATED
  SQLITE_OMIT_GET_TABLE
  SQLITE_OMIT_LOAD_EXTENSION
  SQLITE_OMIT_PROGRESS_CALLBACK
  SQLITE_OMIT_SHARED_CACHE
  SQLITE_THREADSAFE=0
  SQLITE_USE_ALLOCA


There are a ton of diffs for shell.c. The first that caught my eye was:

92a96,97
> #endif
> #if (!defined(_WIN32) && !defined(WIN32)) || defined(__MINGW_H)

FYI, for this setup the following are #defined by gcc referenced above
  _WIN32 => 1
  WIN32  => 1
  __MINGW_H  not #defined

I have attached the gcc output for shell.c -- I wish I knew how to 
eliminate gcc's "helpful" insertion of ascii escape codes into its error 
messages. It makes them almost unreadable when reading the typescript 
file. I've run it thru 'col' in an attempt to clean it up a bit but the 
vestiges remain. It should clean enough for you to decipher it though.


gcc -Wall -Wdeclaration-after-statement -Os -Lsrc/../compat/zlib 
-Isrc/../compat/zlib -Lsrc/../compat/openssl-1.1.0f 
-Isrc/../compat/openssl-1.1.0f/include -Lsrc/../compat/Tcl8.6.6srcdir/win 
-Isrc/../compat/Tcl8.6.6srcdir/generic -Isrc/../compat/Tcl8.6.6srcdir/win 
-DBROKEN_MINGW_CMDLINE=1 -DFOSSIL_ENABLE_SSL=1 -DFOSSIL_ENABLE_EXEC_REL_PATHS=1 
-DFOSSIL_ENABLE_LEGACY_MV_RM=1 -DFOSSIL_ENABLE_TH1_DOCS=1 
-DFOSSIL_ENABLE_TH1_HOOKS=1 -DFOSSIL_ENABLE_TCL=1 -DFOSSIL_ENABLE_TCL_STUBS=1 
-DUSE_TCL_STUBS -DFOSSIL_ENABLE_TCL_PRIVATE_STUBS=1 -DFOSSIL_ENABLE_JSON=1  -I. 
-Isrc -Dmain=sqlite3_shell -DSQLITE_SHELL_IS_UTF8=1 
-DSQLITE_OMIT_LOAD_EXTENSION=1 -DUSE_SYSTEM_SQLITE= 
-DSQLITE_SHELL_DBNAME_PROC=fossil_open -Daccess=file_access 
-Dsystem=fossil_system -Dgetenv=fossil_getenv -Dfopen=fossil_fopen   -c 
src/shell.c -o wbld/shell.o
01mKsrc/shell.c:2074:0:mK 01;35mKwarning: mK"stat" redefined
 #  define stat _stat

In file included from 01mKsrc/shell.c:108:0mK:
01mKD:/msys64/mingw64/x86_64-w64-mingw32/include/sys/stat.h:279:0:mK 
01;36mKnote: mKthis is the location of the previous definition
 #define stat _stat64

01mKsrc/shell.c:2073:20:mK 01;35mKwarning: mK'01mKstruct TIMESPECmK' declared 
inside parameter list will not be visible outside of this definition or 
declaration
 #  define timespec 01;35mKTmKIMESPEC
01;35mK^mK

Re: [fossil-users] _WIN32 IPv6/IPv4 fossil server / ui support

[The Tick]

On 12/31/2017 6:57 PM, Olivier Mascia wrote:

Le 1 janv. 2018 à 01:20, The Tick <the.t...@gmx.com> a écrit :


Could you lend me pointers on which MinGW version to get (and from where) so I 
can have a similar setup as yours?
I didn't used MinGW these last years (though did in the past).
Just visited www.mingw.org, but it looks like the pointers to download there 
are severely outdated (2013?).
Is this the right current MinGW project?


Don't know if this would be helpful but I've been using MSYS2 -- that project 
is kept up-to-date with their pacman tool and they have both a 32- and 64-bit 
gcc. There is also a mingw flavored gcc but I am not sure how it differs from 
the msys2 flavored gcc.


Thanks.  Got msys2 configured for now.
I guess what I'll need is simply the recipe from Fossil developers on what 
'MingGW' setup they use and how they trigger the build using those tools, so I 
can reproduce building Fossil correctly with that configuration and give a hand 
to complete the win-server-ipv6 branch, using those tools.

Attached is what I use on win7x64. The resulting fossil.exe seems to 
work fine.
#
# Usage: bash BUILD.sh [clean] [fossil-directory]
#
# Build [or clean after a build] fossil
#
# Prerequisites for a build
#
# Msys2: make symlinks or place here (see Msys2 build section below):
#   fossil-2.1/compat/openssl-1.0.2k -> ../../openssl-1.0.2k
#   fossil-2.1/compat/Tcl-x64-8.6.6 -> ../../../Tcl/PREFIX-x64-8.6.6
#   fossil-2.1/compat/tcl8.6.6srcdir -> ../../../Tcl/tcl8.6.6
#

clean=false
FOSSIL=
while [ $# -gt 0 ]
do
  if [ -d "$1" ] && [ -f "$1/fossil.1" ]
  then
FOSSIL="$1"
  elif [ "$1" = "clean" ]
  then
clean=true
  else
echo >&2 Usage: $0 [fossil-directory] [clean]
exit 2
  fi
  shift
done

if uname -o | fgrep -iq linux
then
  unix=true
else
  unix=false
fi

if [ "$FOSSIL" != "" ]
then
  targetFossil="$FOSSIL"
  echo Using Fossil source directory $targetFossil
else
  fossil=($(ls -d fossil-[0-9].[0-9]*))
  if [ ${#fossil[*]} -eq 0 ]
  then
echo Fossil source directory not found
exit 1
  fi
  if [ ${#fossil[*]} -eq 1 ]
  then
targetFossil=${fossil[0]}
echo Fossil source directory $targetFossil found
  else
PS3="Select the Fossil directory to build (or 'q' to quit): "
select targetFossil in ${fossil[@]}
do
  if [ -n "$targetFossil" ]
  then
break
  fi
  if [ "$REPLY" = "q" -o "$REPLY" = "Q" ]
  then
exit 1
  fi
  echo "Response \"$REPLY\" unrecognized"
done
  fi
fi

cd "$targetFossil"

if $unix
then
  # Tested so far on Ubuntu

  if $clean
  then
test -f Makefile && make clean
rm -f Makefile config.log
exit 0
  fi

  TCL=$(ls -d /opt/ActiveTcl*)

  if [ ! -d $TCL ]
  then
echo >&2
echo >&2 TCL installation not found in /opt
exit 1
  fi

  ./configure \
--with-openssl=auto \
--with-zlib=auto \
--with-legacy-mv-rm \
--with-th1-docs  \
--with-th1-hooks \
--with-tcl=$TCL \
--with-tcl-stubs \
--json

  make -j3

else
  # Assume windows Msys2

  if $clean
  then
make \
  -f win/Makefile.mingw \
  clean
exit 0
  fi

  # Make symlinks or whatever in the compat/ directory as appropriate
  #OPENSSLDIR=openssl-1.0.2k
  OPENSSLDIR=openssl-1.1.0f
  TCLDIR=Tcl-x64-8.6.6
  TCLSRCDIR=Tcl8.6.6srcdir

  testdir() {
if ! eval test -d compat/\$$1
then
  if ! $fail
  then
fail=true
  fi
  eval echo >&2 $1 directory not found: compat/\$$1
fi
  }

  fail=false
  testdir OPENSSLDIR
  testdir TCLDIR
  testdir TCLSRCDIR
  if $fail
  then
echo >&2
echo >&2 Required prerequisite directory\(s\) not found
exit 1
  fi

  set -x 

  make \
-f win/Makefile.mingw \
X64=1 \
FOSSIL_TCL_SOURCE=0 \
FOSSIL_ENABLE_JSON=1 \
FOSSIL_ENABLE_SSL=1 \
FOSSIL_BUILD_SSL=1 \
FOSSIL_ENABLE_EXEC_REL_PATHS=1 \
FOSSIL_ENABLE_LEGACY_MV_RM=1 \
FOSSIL_ENABLE_TH1_DOCS=1 \
FOSSIL_ENABLE_TH1_HOOKS=1 \
FOSSIL_ENABLE_TCL=1 \
FOSSIL_ENABLE_TCL_STUBS=1 \
FOSSIL_ENABLE_TCL_PRIVATE_STUBS=1 \
OPENSSLDIR='$(SRCDIR)/../compat/'$OPENSSLDIR \
TCLDIR='$(SRCDIR)/../compat/'$TCLDIR \
TCLSRCDIR='$(SRCDIR)/../compat/'$TCLSRCDIR

 Load Tcl using the private stubs mechanism
# FOSSIL_ENABLE_TCL_PRIVATE_STUBS = 1
fi
___
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] _WIN32 IPv6/IPv4 fossil server / ui support

[The Tick]

On 12/31/2017 6:11 PM, Olivier Mascia wrote:

Le 31 déc. 2017 à 21:03, Richard Hipp  a écrit :

Your changes (with some minor alterations by me) are now on a branch.


Good.  Found it.  Thanks for the C89 fix.


They do not build using MinGW, sadly.  I don't know how to fix it.
Maybe somebody else on the mailing list can accomplish that?


Surely.  [I'm posting this to the list.]

Could you lend me pointers on which MinGW version to get (and from where) so I 
can have a similar setup as yours?
I didn't used MinGW these last years (though did in the past).
Just visited www.mingw.org, but it looks like the pointers to download there 
are severely outdated (2013?).
Is this the right current MinGW project?

Don't know if this would be helpful but I've been using MSYS2 -- that 
project is kept up-to-date with their pacman tool and they have both a 
32- and 64-bit gcc. There is also a mingw flavored gcc but I am not sure 
how it differs from the msys2 flavored gcc.

___
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] Lots of web interface changes

[The Tick]

On 12/6/2017 1:22 PM, Richard Hipp wrote:

There have been lots of changes (hopefully, "improvements") to the web
interface of Fossil over the past few days.  If you have not be
following the developments, I encourage you to visit a few of the main
sites running the latest code and let me know what you think.  Your
suggestions and comments are very important.


I have been reading the posts concerning the proposed CSS changes. I 
also am not by any means a CSS guru -- I have only a rudimentary 
knowledge of CSS.


I like to use longer commit comments and so I have used (which I found 
via this mailing list):


  span.timelineComment {
font-family: Consolas; /* optional */
white-space: pre;
  }

for my timeline. One thing I noticed is that other pages that display 
the commit comments (such as the overview on the info/ page for a 
particular commit) do not use the same (or any unique class or id that I 
could easily reference -- perhaps my CSS knowledge is just not 
sufficient) for the comment.


I would suggest that the html generated by fossil be consistent and use 
the same id= or class= tags for the elements on each page. This would 
allow one to more consistently change the look of specific elements 
displayed by fossil.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Curiosity question: is there a recap of add/change/remove on a per-file report

[The Tick]

Just wondering if this exists or if it would have to be scripted -- a 
way to get a per-file recap of added/changed/removed lines for the files 
in a commit. It would be a way to quickly gauge the amount of changes 
that had occurred.

___
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] What is the best way to update to a new upstream version

[The Tick]

On 6/13/2017 3:05 PM, Joerg Sonnenberger wrote:

On Tue, Jun 13, 2017 at 02:44:31PM -0500, The Tick wrote:

Thanks, that is what I was looking for. I've set up a test respository and
things look good until I get to the final "merge" step:

$ f init F.fossil
$ f open F.fossil
$ f add project
$ f commit --tag 1.5 --branch Official
$ f tag add --propagate Official 0dd97cd973

$ f co trunk
$ f add project
$ f commit


This part is the problem. You are missing the merge of 1.5 unto trunk.



That did it -- very cool. Thanks.

$ f init F.fossil
$ f open F.fossil
$ f add project/
$ f commit --tag 1.5 --branch Official
$ f tag add --propagate Official 1.5

$ f co trunk
$ f merge 1.5
$ f commit
# Make some local changes
$ f commit

$ f co Official
# Remove all files and unpack latest version
$ f addremove
$ f commit --tag 1.6

$ f co trunk
$ f merge 1.6
$ f commit

___
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] What is the best way to update to a new upstream version

[The Tick]

On 6/13/2017 12:52 PM, Joerg Sonnenberger wrote:

On Tue, Jun 13, 2017 at 12:17:46PM -0500, The Tick wrote:

Given a repository based on a previously fetched version of some software
package and having been modified with local changes, what is the best way to
update to a more recent version of the upstream package?


The best approach is still to kind of emulate what CVS is doing with
vendor branches. It works best if you start from scratch, but with some
work it can be fixed up later:

- Create a branch off the initial empty commit for this package.
- Put the sources into the correct subdirectory, addremove.
- Commit, possibly with a tag including the package name and version.
- Now merge that branch into trunk.
- Commit local changes on top.

If you want to update:

- Checkout the branch.
- Remove all files, put the sources into the correct subdirectory,
  addremove.
- Commit.
- Merge the branch into trunk.
- Fix any conflicts.



Thanks, that is what I was looking for. I've set up a test respository 
and things look good until I get to the final "merge" step:


$ f init F.fossil
$ f open F.fossil
$ f add project
$ f commit --tag 1.5 --branch Official
$ f tag add --propagate Official 0dd97cd973

$ f co trunk
$ f add project
$ f commit

#Make some local changes

$ f commit

At this point things look pretty good. I've got a branch "Official" and 
my "trunk" has my local changes. Now I download the latest official version.


$ f co Official
# Remove all files and unpack newest upstream version
# I guess I do an "addremove" here.
$ f commit --tag 1.6

Again, things are looking good. I've got the latest upstream version 
into branch "Official"


$ f co trunk

Now, how do I "merge"?

$ f merge -n Official
WARNING: no common ancestor for project/graph1.tcl
WARNING: no common ancestor for project/graph2.tcl
REMINDER: this was a dry run - no files were actually changed.
$ f merge -n 1.6
WARNING: no common ancestor for project/graph1.tcl
WARNING: no common ancestor for project/graph2.tcl
REMINDER: this was a dry run - no files were actually changed.
MSYS2 /tmp/f
$ f merge -n a85895dba5
WARNING: no common ancestor for project/graph1.tcl
WARNING: no common ancestor for project/graph2.tcl
REMINDER: this was a dry run - no files were actually changed.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] What is the best way to update to a new upstream version

[The Tick]

Given a repository based on a previously fetched version of some 
software package and having been modified with local changes, what is 
the best way to update to a more recent version of the upstream package?


A "f addremove" would import the new version but would lose all local 
changes.


What I've done so far is to "f diff --unified -r X" where X is 
the commit of the last upstream version. I can now apply my patches to 
the new version before I do an "addremove". Once the "addremove" is 
done, I would make further changes if necessary.


In the above scenario, how many and when would one commit? After the 
unpack of the latest version? After applying my local patches? After 
getting the whole thing to work again? Maybe a combination of the above?


Is there a way to get fossil to carry forward the local changes for me 
somehow? Is there a better way than what I've outlined?


With RCS I used to file any local changes into a new branch: for version 
X.Y of a package, I would checkin my changes as X.Y.1.0, etc. When there 
was a new version X.Z, I could checkin as version X.Z and then do a 
"rcsdiff -u -r X.Y -r X.Y.1.n" which I could apply to the new version 
X.Z and when all is working again, checkin the new branch X.Z.1.


Maybe there's a way to do the same with fossil (and I did not because I 
don't know how).



___
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 do I get a notification that a ticket has been created?

[The Tick]

On 6/2/2017 9:34 PM, Stephan Beal wrote:

On Sat, Jun 3, 2017 at 4:23 AM, The Tick <the.t...@gmx.com
<mailto:the.t...@gmx.com>> wrote:

Looking at that URL you provided, I went and tried 'f help cmds'. I
did not know that existed since neither 'f help' nor 'f help -a'
listed 'cmds' as something to ask for.

Are there other (for want of a better term) magic topics? Are some
only available via the web interface or would 'f help ...' be able
to retrieve the help?


Which commands appear using which help options has changed a few times
over the years. Try:

f help help

for the options needed to list various categories of commands. Note that
the CLI _can_ show help for web pages, but (to avoid any naming
ambiguities) you have to prefix the page name with a slash, e.g.:

f help timeline
vs
f help /timeline

both of those are valid but will show completely different things.


Wow! Those are all new.

I did a 'f help help'.

I tried 'f help -w'. Then, I accidentally typed 'f help www' and got a 
different list. I can't find 'www' as an option in either list.


There seems to be a lot of the help that is only available if one is "in 
the know" so to speak.


I will save this email so I won't forget. Thanks.

PS. Seems to me that a 'f help -a' should mention 'f help help', and 'f 
help help' should mention these other options. Maybe I missed it.


___
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 do I get a notification that a ticket has been created?

[The Tick]

On 6/2/2017 8:50 PM, Stephan Beal wrote:

On Sat, Jun 3, 2017 at 3:46 AM, The Tick <the.t...@gmx.com
<mailto:the.t...@gmx.com>> wrote:

I guess I'm blind. I can't find any RSS feed button on the tickets
page or the settings->tickets. Is it something I have to enable?
...in the repository? ...on chiselapp.com <http://chiselapp.com>?

At one time I remember investigating how to do rss and I think it
involved something called an aggregator? At that point I lost interest.


See:

http://fossil-scm.org/index.html/help?cmd=/timeline.rss



Thank you. I pointed thunderbird at a url for my repository based on 
that help page and it told me there was a ticket.


Looking at that URL you provided, I went and tried 'f help cmds'. I did 
not know that existed since neither 'f help' nor 'f help -a' listed 
'cmds' as something to ask for.


Are there other (for want of a better term) magic topics? Are some only 
available via the web interface or would 'f help ...' be able to 
retrieve the help?



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How do I get a notification that a ticket has been created?

[The Tick]

I've got one repository on chiselapp.com. Suppose someone creates a 
ticket. How do I -- as the administrator -- get notified? I've got no 
reason to login and even if I do it once a week, it's a waste of time if 
there are no tickets.


To see what happens when a ticket is created, I made a "test" ticket 
myself using the anonymous login to my repository on chiselapp.com. I 
expected that I'd get some sort of email... but nothing. Of course, I 
also find nothing under "settings" that allows me to set an email 
address. My email only exists for the chiselapp.com account.


So, what (if any) features exist for notification when a ticket is 
created/changed/etc.? I could not find anything in the fossilbook.pdf 
about the ticketing system.

___
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] Is it possible to merge repository's?

[The Tick]

On 5/31/2017 10:57 AM, Ron W wrote:

On Tue, May 30, 2017 at 8:00 AM,
<fossil-users-requ...@lists.fossil-scm.org
<mailto:fossil-users-requ...@lists.fossil-scm.org>> wrote:

Date: Mon, 29 May 2017 22:35:31 -0500
    From: The Tick <the.t...@gmx.com <mailto:the.t...@gmx.com>>
Subject: Re: [fossil-users] Is it possible to merge repository's?

On 5/29/2017 10:30 PM, Andy Bradford wrote:
> Thus said Stephan Beal on Tue, 30 May 2017 02:57:38 +0200:
>
>> However, there is  _hypothetically_ a way to completely  merge 2
repos
>> into one while keeping all commits, but i'm not at all certain if
this
>> would work...
>
> I think it actually will work for some definition of ``work''.
I've done
> it before.
>
> But... it depends on what one expects out of it.
>
> There will  be 2 separate  and independent timelines  once
reconstructed
> and there  will not be a  relationship between artifacts except
for the
> fact that they all live in the same Fossil file.
>

 From this I gather that there would be no way to connect the imported
repository onto the main trunk. That was not what I was hoping for.


What is your objective?

Once you have both time lines in one repository, you can then fetch
files from both into a single checkout and start making checkins  that
affect both timelines, therefore, effectively merging the timelines at
that checkin.

To get the "combined" checkout, I think you would have to "fossil
checkout uuidLatestA", then make a trivial change to all the files, then
"fossil update uuidLatestB".

At this point a commit would affect both timelines.

Though, as Stephan mentioned, you might need to do a reparent command to
insure that both uuidLatestA and uuidLatestB are parents of this new commit.



Thanks for the suggestions.

The reason I had is because I started a subproject and, after a couple 
weeks, realized that it would be more convenient to have its repository 
merged into my main project as a sub-directory. I thought this might be 
an existing feature somehow.


As I have just begun using fossil in the past month or so, the 
suggestions here are pretty much over my head and I don't feel 
comfortable enough with fossil to begin experimenting at this depth.



___
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] Is it possible to merge repository's?

[The Tick]

On 5/29/2017 10:30 PM, Andy Bradford wrote:

Thus said Stephan Beal on Tue, 30 May 2017 02:57:38 +0200:


However, there is  _hypothetically_ a way to completely  merge 2 repos
into one while keeping all commits, but i'm not at all certain if this
would work...


I think it actually will work for some definition of ``work''. I've done
it before.

But... it depends on what one expects out of it.

There will  be 2 separate  and independent timelines  once reconstructed
and there  will not be a  relationship between artifacts except  for the
fact that they all live in the same Fossil file.



From this I gather that there would be no way to connect the imported 
repository onto the main trunk. That was not what I was hoping for.


If I decide to do it, I'll probably look into a shell script to checkout 
each commit, then add and commit to the target repository.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Is it possible to merge repository's?

[The Tick]

Probably a quick question: is it possible to merge one repository into 
another and retain all the commit messages? There are no common files. 
It would be really great if I could specify the root within repository 
#1 at which to merge repository #2


From what I've googled, I think the answer is "no".
___
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 transfer/move/upload local repository to chiselapp.com

[The Tick]

On 5/15/2017 9:21 AM, Roy Keene wrote:

There is a way to upload the repository -- what you are probably doing
now is creating a new repo with the same project code then pushing to
that, which won't work out great.

When you go to "Create Repository" there are 3 options: 1. Create a new
repository; 2. Pull a repository from somewhere; 3. Upload a repository
file -- pick the last one.



That was exactly what I was doing -- after clicking 'Create Repository' 
my focus was on the form and I was totally oblivious to the additional 
options that had appeared.


It is now uploaded and is working fine. Thank you.
___
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 transfer/move/upload local repository to chiselapp.com

[The Tick]

Sorry for all these questions.

I ran across an exchange from 2013 (I think) that talked about 
chiselapp.com shutting down. Obviously it has not done so.


What is the status of chiselapp.com and is it a viable place to put an 
open source repository as of 2017?

___
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 transfer/move/upload local repository to chiselapp.com

[The Tick]

Hmmm. I now see on the timeline that there are two users and the last 
leaf is unconnected to the timeline entries from my local repository. 
There are two users: my windows user name (which I guess I now want to 
get rid of) and the username that I use on chiselapp.com


The chiselapp.com username is the one with the "empty" checkin
My windows username is now there on chiselapp.com after my 'push'

47 timeline items

2017-05-14
21:03   
[7a7ff8235f] Leaf: initial empty check-in (user: iamdave, tags: trunk)
20:59   • Deleted wiki page CWind 1.4 (user: imdave) [details]
20:57   • Changes to wiki page CWind (user: imdave) [details]
20:56   • Changes to wiki page CWind (user: imdave) [details]
20:35   • Changes to wiki page CWind 1.4 (user: imdave) [details]
20:31   • Changes to wiki page manpage (user: imdave) [details]
20:20   • Changes to wiki page manpage (user: imdave) [details]
20:04   • Changes to wiki page CWind 1.4 (user: imdave) [details]
19:56   
[0d276cd236] Leaf: Rename all files from .cpp to .c -- there is no 
reason to use C++ (user: imdave, tags: trunk)

19:28   • Changes to wiki page CWind 1.4 (user: imdave) [details]
05:39   • Changes to wiki page CWind 1.4 (user: imdave) [details]

The 21:03 and the 19:56 leaf's are not connected with the little arrow 
lines.


I'm probably really messing this up.

Is there a way to upload my local repository (created on windows and 
which is using my windows user name) to chiselapp.com and somehow create 
an equivalence to the username on chiselapp and my windows username?



___
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 transfer/move/upload local repository to chiselapp.com

[The Tick]

So, how can I upload/transfer/move my local repository to chiselapp.com?


I spoke too soon. I did the 'f push https://@chiselapp.com/...' 
and it did >something< -- stuff was uploaded. Now I see the most recent 
timeline:



[7a7ff8235f] Leaf: initial empty check-in (user: iamdave, tags: trunk)

This is followed by the timeline entries from my local repository.

So now there's nothing there?

Should I delete the chiselapp repository and start over?

___
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 transfer/move/upload local repository to chiselapp.com

[The Tick]

So, how can I upload/transfer/move my local repository to chiselapp.com?


Never mind, I finally found it: f push https://@chiselapp.com...

That came from a google search.

I did not find it from a "f help" -- I looked for "login" or something 
similar. It would be nice if a "f help" would have helped me but I admit 
I don't know where to show that info. Maybe when the 'f help push' 
mentions remote-url there could be some reference to the syntax that 
fossil understands.


Now, how do I delete the user that I created named as my windows user name?



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to transfer/move/upload local repository to chiselapp.com

[The Tick]

I've got a local repository that I'm ready to put on chiselapp.com

I created a new project, gave it the same name, and provided the same 
project-code.


It tells me it is created. I add my password and log in.

Now I want to somehow transfer my local repository to chiselapp.com

I tried (on windows)

f push https://chiselapp.com/user/iamdave/repository/CWind

I get an error Error: not authorized to write

It never prompts me for a user id/password

So, I tried using http://chiselapp.com

It would not even let me log in -- it kept saying "insecure". I don't 
care, I want to log in!


What is the user that fossil is using when attempting the 'push'? It 
never tells me. I tried turning on access log but no entries were made.


I then added my windows user name guessing that maybe fossil is using 
that. I gave that user every single permission on the create user page. 
I still get the 'not authorized to write'. Perhaps that is not 
surprising since fossil never prompted me for the password and I can see 
no where to put it.


So, how can I upload/transfer/move my local repository to chiselapp.com?
___
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] Suggested patch for src/user.c (password prompt)

[The Tick]

On 5/3/2017 1:05 PM, Richard Hipp wrote:

On 5/3/17, The Tick <the.t...@gmx.com> wrote:

On 5/3/2017 12:41 PM, Richard Hipp wrote:

On 5/3/17, The Tick <the.t...@gmx.com> wrote:


the current code
does not work when using mintty.


Have you tried the latest trunk version of Fossil?



I used fossil-src-2.2.tar.gz that I downloaded in the morning on 4/29


Not new enough.  https://www.fossil-scm.org/fossil/tarball/fossil.tar.gz


Yes, that works. It is essentially my "suggested" patch however the 
above version outputs an extra newline when using mintty.

___
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] Suggested patch for src/user.c (password prompt)

[The Tick]

On 5/3/2017 12:41 PM, Richard Hipp wrote:

On 5/3/17, The Tick <the.t...@gmx.com> wrote:


the current code
does not work when using mintty.


Have you tried the latest trunk version of Fossil?



I used fossil-src-2.2.tar.gz that I downloaded in the morning on 4/29
___
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] Suggested patch for src/user.c (password prompt)

[The Tick]

On 5/3/2017 4:26 AM, Florian Balmer wrote:

Just because I have done some research about this topic recently, and
find it interesting, please allow me to ask why you can make any
assumptions regarding STDIN, after only testing STDERR? Couldn't each
of the standard handles be redirected individually, as in "COMMAND
nul 2>errors.log"?

To distinguish console handles from files, pipes and other redirected
devices on Windows, MSDN recommends using GetConsoleMode(), as for
example mentioned in the documentation for WriteConsole():

https://msdn.microsoft.com/en-us/library/windows/desktop/ms687401.aspx

"... determine whether the output handle is a console handle (one
method is to call the GetConsoleMode function and check whether it
succeeds) ..."

A more detailed test from Michael Kaplan, similar to earlier versions
of MSVCRT (current UCRT seems to rely on a combined test of isatty(),
GetFileType() and GetConsoleMode(), now):

http://archives.miloush.net/michkap/archive/2008/03/18/8306597.html

A comment by Raymond Chen why GetFileType() alone (as used by some
isatty() CRT implementations) is not sufficient to detect a console
handle:

https://blogs.msdn.microsoft.com/junfeng/2005/07/08/how-do-i-know-if-console-handle-is-redirected/

My investigations were about output handles, but GetConsoleMode() can
also be used with input handles.



...which is why I labelled it a "suggested" patch. :)

I know next to nothing about windows api's, however the current code 
does not work when using mintty. It was extremely frustrating trying to 
enter a password and finding that it did not read what I had typed. 
Ultimately I had to refer to the source code to figure it out.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Suggested patch for src/user.c (password prompt)

[The Tick]

Here's a prototype patch for getpass() in src/user.c

This was very frustrating because, while I thought I entered a password, 
I actually was not when I did "f user password username".


The issue is entering a password when using mintty on MSYS2. From some 
prior research, mintty does not use the windows console interface. 
Instead it uses pipes for some sort of emulation. Therefore, the 
_getch() function in mintty does not return anything (maybe an error?).


Running fossil in a tcc.exe or cmd.exe window works since those two use 
the windows console interface.


I don't have any other "consoles" to test this with, but what this patch 
is attempting to do is determine if stderr is a "console" under windows 
-- this is true if _isatty(fileno(stderr)) is true. Otherwise, it falls 
back to getc().


The patch was tested using MSYS2's mintty, and cmd.exe & tcc.exe on win7x64.

--- fossil-2.2/src/user.c.orig  2017-04-11 15:54:55.0 -0500
+++ fossil-2.2/src/user.c   2017-05-01 15:22:30.217545000 -0500
@@ -55,6 +55,9 @@
   char *zPwd;
   size_t nPwd;
   size_t i;
+#if defined(_WIN32)
+  int use_getch = _isatty( _fileno(stderr) );
+#endif

   if( zPwdBuffer==0 ){
 zPwdBuffer = fossil_secure_alloc_page();
@@ -70,7 +73,10 @@
   assert( nPwd>0 );
   for(i=0; i

Re: [fossil-users] A tutorial about "branches", "trunks", "leafs", etc.?

[The Tick]

OK, I think I've figured it out!

You're supposed to do a fossil >open< with a version name being "trunk" 
(default) or "branch name". When finished, do a fossil close.


It appears that I can even do this in separate directories at the same 
time -- one instance open with the default "trunk" and another instance 
with "branch name". A commit in one of the directories will apply those 
changes against the branch that was opened in that directory.


Wow! I kept thinking that one would somehow specify the branch against 
which the changes were to apply when one did a commit.


Am I right or at least not too far off?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] A tutorial about "branches", "trunks", "leafs", etc.?

[The Tick]

Is there any page that describes "branch", "trunk", "leaf", etc.?

I created a dummy repository to experiment with.

I made several commit's and then another using -branch

The timeline shows what I would call a "fork" in the tree.

When I made further commits, the changes were applied to this new branch.

I would assume that I should be able to make changes with respect to the 
point at which I created the fork. I tried "f commit -branch " where 
 was the artifact (?) number shown on the timeline. It worked and 
the timeline graph shows a jog back to the "main" line... but from the 
graph it looks to me as though the changes are with respect to the most 
recent leaf on the branch I created.


I would like to understand these terms, how to interpret the timeline 
graph, and how to do commits against specific versions.

___
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] Incomplete patch with idea for enhancement

[The Tick]

On 4/19/2017 12:52 AM, Warren Young wrote:

I’d call your patch “close enough.”  It’s only got a 1 in 4 billion chance of 
matching something incorrectly for a uniform probability distribution, and a 
much smaller chance than that in practice given the bias towards text file 
types in Fossil repositories.


My idea was to have a way to specify the mime type on a per-file basis. Or 
maybe by file extension like the 'encoding-glob', etc. settings?

So far, the one-off policy works pretty well, since typical web browsers don’t 
add new internally-viewable file types that often.  With this move away from 
plugins, the list of viewable file types may be *shrinking* at the moment.

I’m not rejecting the idea, I’m just calling into question its ROI.


My thinking went like this:

+ showing a PNG is neat
+ why doesn't it show an ICO?
+ make a quick little patch so it does
+ the patch is not 100% certain to ID an ICO
+ how to make it 100%?
+ a) allow one to set mime on a per-file basis
-- advantage: 100% reliable
-- disadvantage: has to be done for each applicable file
+ b) use file suffix
-- advantage: applies gobaly
-- disadvantage: applies globally & is prob. a lot more work

Since I know nothing about the internal workings of fossil, I have no 
way to judge how much effort it would be.


The bottom line: this is just cosmetic so it's probably not worth 
spending much effort on it. Maybe, as you mentioned, the simple patch 
could be added since it would work most of the time. In addition, even 
if it erred, browsers just show a broken image for an file that fails to 
decode.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Incomplete patch with idea for enhancement

[The Tick]

I'm very new to fossil so maybe there's a way to do this already.

After I had committed a PNG to a fossil repository then fossil UI showed 
the PNG itself instead of just its name. Pretty nice! After adding an 
ICO, fossil just said it was XXX number of bytes. After looking at the 
source, I added this patch:


--- doc.c.orig  2017-03-10 11:07:08.0 -0600
+++ doc.c   2017-04-17 23:32:03.770418400 -0500
@@ -49,6 +49,7 @@
 { "\211PNG\r\n\032\n",   8, "image/png"  },
 { "\377\332\377",3, "image/jpeg" },
 { "\377\330\377",3, "image/jpeg" },
+{ "\0\0\1\0",4, "image/x-icon" },
   };

   if( !looks_like_binary(pBlob) ) {


Now >my< version of fossil show the ICO file also. (I say this patch is 
incomplete because definitively identifying an ICO file is more that 
just looking at the first 4 bytes).


My idea was to have a way to specify the mime type on a per-file basis. 
Or maybe by file extension like the 'encoding-glob', etc. settings?


Perhaps this is already possible?
___
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 obsolete stuff in a repository

[The Tick]

On 4/17/2017 9:11 PM, Ross Berteig wrote:

On 4/17/2017 6:50 PM, The Tick wrote:

I've put a project under fossil. Since it depends on a couple other
libraries, I've also put those into the repository so that I am not
dependent on being able to download those particular versions. Now,
when new versions of those dependent libraries become available, I
want to update my project. I could just add the new versions and
modify my makefile. The problem I see is that over time the fossil
repository is going to get >really< big as it will contain a bunch of
obsolete stuff.

Is there a way to handle this? I really want to keep the dependent
libraries in the repository since who knows what might happen to
someone else's open source project in the future, and in addition, it
makes my project "self contained".







Unzip the new library on top of the old in your workspace. Try to avoid
preserving a version number as part of the folder names in the workspace
even if your upstream does that to you. That will just confuse life.



So I've goofed up by putting freetype-2.7.1/ and others into the repository?

I guess I had assumed that I could just add, say, freetype-2.8 some day 
and change the master makefile as appropriate while making any other 
changes that might be necessary to accommodate the new library version. 
Then, I would do a commit after verifying everything still works.


If the library's name should not contain a version string, I guess I'd 
need a readme or something to tell what the current version is? I guess 
the commit message could mention that, but stuff gets lost in all the 
commit messages.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to deal with obsolete stuff in a repository

[The Tick]

I've put a project under fossil. Since it depends on a couple other 
libraries, I've also put those into the repository so that I am not 
dependent on being able to download those particular versions. Now, when 
new versions of those dependent libraries become available, I want to 
update my project. I could just add the new versions and modify my 
makefile. The problem I see is that over time the fossil repository is 
going to get >really< big as it will contain a bunch of obsolete stuff.


Is there a way to handle this? I really want to keep the dependent 
libraries in the repository since who knows what might happen to someone 
else's open source project in the future, and in addition, it makes my 
project "self contained".

___
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] Unfortunately I still see blobs of text for commit messages

[The Tick]

Never mind. I think I was going down the wrong path with this approach. 
I still have problems with using markup in the commit msgs tho. I asked 
about that in another thread.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Quick Q on valid markup for commit msgs

[The Tick]

On 3/29/2017 2:36 PM, Richard Hipp wrote:


The default formatting for comments is Wiki markup.  You can change
this for each repo using the Admin/Timeline menu.



I ran a "fossil ui"

First I went to admin->timeline and checked "allow block markup"

I went to wiki->Formatting rules->Markdown wiki.

Using that info, I created a commit msg for a dummy file. When I go to 
the timeline and files views, the only formatting I see is for 
paragraphs. There is no bold, italic, bullet lists. No indented 
paragraphs. It did honor  tho.


Where are the rules and syntax for this "block markup"?

I've used RCS in the past for my personal projects. I'm used to making a 
simple list of the changes for a particular file and then doing a 'ci' 
for that file. When I reached a point where I considered the project 
"done" for the time being, I tagged all the files with an ID. Or, if I 
did not care, I'd just leave the ,v files as is and do a 'co *,v' when I 
wanted to do a build. Actually, gmake did that for me.


I've not used another scm (not quite true, I'm sure I used one when I 
was still working but I couldn't tell which one; git, cvs, etc. were not 
invented yet I think). Perhaps my "rcs" thinking is obsolete.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Unfortunately I still see blobs of text for commit messages

[The Tick]

I thought my problem with the commit messages looking like a big blob of 
text was fixed by adding:


/* THIS WORKS - Enable timeline comments to respect linefeeds. */
span.timelineComment {
  font-family: Consolas;
  white-space: pre;
}

to the css here: http://localhost:8080/setup_skinedit

Now I was poking around and looked at an individual file. The commit 
messages are again a blob. I don't know a lot about css but with the raw 
fossil html:



[3a33db7b7c]
part of check-in
[76d36a9fdd]
Support a fixed-width font in addition to the default proportional font
  Use Option.mono in Options.txt to specify a specific fixed-width font
  Add tags F,FB and FI
 (user:


I've googled to see if I could go back and edit the commit messages but 
the answers I saw were a definite "no".


Before I just throw the whole thing away and start over using that 
markup language, is there any way to salvage this?


PS. This is not years of work. I've just started learning to use fossil 
so there are only a few commits so far. In the past I had used RCS for 
my projects but fossil looked like it would be a good replacement.

___
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] Couple of beginner questions

[The Tick]

Goodness! All I wanted was to have a comment contain a copyright 
character. Thanks to the people who were kind enough to take the time to 
respond to my questions. Now my commit messages are no longer a big blob 
of text, my .vimrc is modified, I've gotten fossil to stop complaining 
about my file, and I've learned some more about the intricacies of 
language support.


I never meant to start another editor war -- I thought that was over 
when the vi vs. emacs debate finally died years ago.


Now its been suggested that I not only change my editor, but my 
keyboard, my programming language, my OS, and even to buy a new computer 
from a different manufacturer. While I suppose that might move the world 
closer to perfection, but I've been around long enough to know that will 
never happen.


If I knew Mr. Sonnenberger personally, I might, out of consideration for 
an acquaintance, reach out and ask how I might be able to spell his name 
correctly. I would hope that his response would not be to insist that I 
change editors, keyboard, etc. I also strongly suspect that he would 
feel the same were the situation reversed.


Anyway, thanks again to those people who helped me. At this point I 
don't find this thread going anywhere productive and I'm sort of sorry 
for starting it.

___
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] Couple of beginner questions

[The Tick]

On 3/29/2017 4:21 PM, Martin Gagnon wrote:


About gvim and UTF-8 files without BOM, my vim is set with
  set encoding=utf-8
  set fileencoding=utf-8

and everything works like a charm.

Also, If I edit a ascii file that doesn't contain any special character,
it remain ascii.



I didn't know I could do that -- thank you! I will put that into my vimrc.
___
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] Couple of beginner questions

[The Tick]

On 3/29/2017 4:03 PM, sky5w...@gmail.com wrote:

Doh! It was my CSS. I was using a test repo without my modified CSS. Now
it works.
I think this is the 2nd time I tripped on this. :(

// from CSS //
/* THIS DOES NOT WORK - Enable Check-in comments to respect linefeeds. */
span.checkinComment {
  font-family: Consolas;
  white-space: pre;
}
/* THIS WORKS - Enable timeline comments to respect linefeeds. */
span.timelineComment {
  font-family: Consolas;
  white-space: pre;
}


Where and how would I use the above?



@the.tick - With UTF-8(±BOM) source files, I can't reproduce your
problem. Win10 x64, Fossil v2.1.


I'm on win7x64. Both Active State's Tcl 8.6.4 and a compiled 8.6.6 
(msys2's x64 gcc) barf on the 'bom' at the beginning of a .tcl source 
file. I compiled fossil from the 2.1 source I downloaded around 3/13. 
That version of fossil ignores newlines in my commit text -- I need to 
look into this markup thing.



On Wed, Mar 29, 2017 at 4:04 PM, Richard Hipp > wrote:

On 3/29/17, sky5w...@gmail.com 
> wrote:
>
> Side note:
> I have all Timeline Display Preferences unchecked and my v2.1 Timeline 
does
> not respect new lines in my check-in comment?
> v1.37 showed newlines in the Timeline for identical setup.
> Is this intentional change?
>

No.  Can you show us a test case?
--
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

Re: [fossil-users] Couple of beginner questions

[The Tick]

On 3/29/2017 3:25 PM, Warren Young wrote:

On Mar 29, 2017, at 2:05 PM, The Tick <the.t...@gmx.com> wrote:


On 3/29/2017 2:36 PM, Richard Hipp wrote:

Most of the world is using UTF-8 now.


I'm wondering how that can be for programming language source files.







Any text editor or compiler that can’t cope with UTF-8 in 2017 is broken or can 
be ignored.


I've been using vi for 40 years so that's not going to change. I 
certainly won't revert to something as horrendous as notepad or similar.





$ /c/Program\ Files/tcl/bin/tclsh u.tcl
invalid command name "puts"
   while executing
"puts "This is a copyright symbol: ©.""
   (file "k.tcl" line 1)


That sounds like an issue you should bring up with the providers of your Tcl 
implementation.  Tcl works just fine with UTF-8 on POSIX type platforms.

Second existence proof: https://tangentsoft.com/pidp8i/artifact/79fb335f12f1f6de

(auto.def is an autosetup script, which is based on Tcl.)

It may be that your particular Tcl implementation is blindly assuming UTF-16 
because you’re running it on Windows.


Active State Tcl 8.6.4.

As much as I wish unix had supplanted windows, it's an unfortunate de 
facto standard for probably most people using desktop computers.


___
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] Couple of beginner questions

[The Tick]

On 3/29/2017 2:36 PM, Richard Hipp wrote:

Most of the world is using UTF-8 now.


I'm wondering how that can be for programming language source files.

I managed to put the "bom" in front of a one-line tcl script:

puts "This is a copyright symbol: ©."

where the '©' was previously converted to utf-8 by fossil.

gvim now reads the file and renders the utf-8 '©' as a '©'
notepad displays the file and renders the utf-8 '©' as '©'

>but<

$ /c/Program\ Files/tcl/bin/tclsh u.tcl
invalid command name "puts"
while executing
"puts "This is a copyright symbol: ©.""
(file "k.tcl" line 1)

While adding the option "-encoding utf-8" to the tclsh command line 
makes it work, it does not work when I double-click on the .tcl file as 
I have no way to set any sort of encoding option -- unless I have to 
make a windows shortcut for each and every .tcl file that I want to run 
and put the -encoding there.


So, how can one use a program source file encoded in utf-8?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Couple of beginner questions

[The Tick]

1) When I did a commit, I formatted the commit message very nicely. 
After the commit, it's just a big blob of text. That certainly defeats 
the purpose of making a commit message of any detail.


What is the standard practice with this? Keeping a separate 
"changelog.txt" where the details are listed? Now I've got another file 
to keep accurate?


2) My source has a couple of characters like copyright and the 
multiplication 'x' and I get this message from fossil:


./Guide.tcl contains invalid UTF-8. Use --no-warnings or the 
"encoding-glob" setting to disable this warning.

Commit anyhow (a=all/c=convert/y/N)?

I set encoding-glob to *.tcl so now the message goes away.

I've read this: 
http://fossil-users.fossil-scm.narkive.com/6Ci1qs0J/file-contains-invalid-utf-8-but-is-not-utf-8


As that post mentioned, my © symbol remains but fossil shows the file 
with a black ? in place of the ©.


I use gvim and switching to a different editor is something that will 
never happen.


I tried saying 'c' for convert and fossil made a new file with "real 
utf-8" characters in the place of the originals.


The copyright symbol is something that I really want in the source file 
-- it's in a comment but that is beside the point. It needs to show as a 
real copyright symbol when the file is edited >and< viewed. As far as I 
know, gvim does not have a way to convert the goofy "real utf-8" 
sequence to a copyright symbol so I cannot see the © when I edit the 
file >nor can I insert a real utf-8 copyright symbol<. Also neither 
notepad nor another file viewer shows the "real utf-8" copyright symbol 
correctly in a "converted" file.


Is there any solution to this?

___
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 actually >use< TH1?

[The Tick]

On 4/12/2016 9:38 PM, Joe Mistachkin wrote:


The Tick wrote:


I spent an hour or so googling "how to use th1 in fossil". I got a ton
of links for the language spec but I could not find a single real, live
example of how to actually use it.



There are various ways to use it, depending on context:


   :
Six various ways
   :



Another thing to remember is that when Fossil is compiled with support
for "full Tcl" integration, you can use the TH1 commands "tclEval",
etc to interact with full Tcl scripts, in both directions.  Full details
are available here:

https://www.fossil-scm.org/index.html/doc/trunk/www/th1.md

Examples of all functionality described in this email are available in
the Fossil test suite.



Thanks.

I guess this answers the question that I did not know how to ask precisely:

Can TH1 be used on the wiki pages (such as the "home" page)? Answer: no

I wonder why TH1's use is excluded for all these pages.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to actually >use< TH1?

[The Tick]

I spent an hour or so googling "how to use th1 in fossil". I got a ton 
of links for the language spec but I could not find a single real, live 
example of how to actually use it.


(This is win7 x64)

I downloaded fossil-w32-1.34.zip. I created a project w/ fossil init, 
started the ui, set all three tcl options under "settings", and went to 
create the "home" wiki page. I tried the following (with all three of 
the markdown options on the edit page):



puts "Hello, world!\n"
puts [TclExpr date]


TH1: date
TH1: TclExpr date
TH1: [TclExpr date]

At this point I'm just trying random stuff.

I looked at http://localhost:8080/admin_th1
I tried "date" and it worked
I did a Ctrl-U to look at the source
It looks like the page just invokes itself but I don't see how the page 
is generated to actually run the TH1 statements that I provided.

___
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] Questions about wiki linking to non-branch artifact IDs/images

[The Tick]

On 10/19/2015 9:36 AM, Richard Hipp wrote:

On 10/19/15, Tony Papadimitriou  wrote:


My question is how can I add this image to the repo in a way that it is not
part of any branch or ticket (e.g., attachment to a ticket)?
I only need it for the purpose of being shown in the wiki page but I do not
want it to be part of any checkout or ticket.



Add the image as an attachment to the wiki page.  Then edit the wiki
page to reference the attachment.  (I remember adding that capability
way back when I was first designing Fossil, but I haven't actually
used it so I don't remember the exact syntax.)



This is similar to what I want to do so I gave it a try--I added an 
image to a wiki page as an attachment. It's not what I want. It adds 
text to the bottom of the page that says "Attachments".


How can I remove the attachment now?

Perhaps if I knew what "artifacts" or "artifact ids" were, I could 
figure it out. Are there any docs on all this terminology?

___
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 embed image in project home page or wiki pages?

[The Tick]

On 9/15/2015 6:09 PM, Ron W wrote:

On Tue, Sep 15, 2015 at 6:18 PM, The Tick <the.t...@gmx.com
<mailto:the.t...@gmx.com>> wrote:

However, if I do that, then the image would be included in the
project download, right? I guess one small image would not be that
big a deal, but it would be good to not foist unnecessary files on
users.


What about your project's "user manual"? Screenshots are often included,
so would be reasonable to include in the source "tarball".


First of all, thanks for your reply.

The app is a Tcl script and associated image files. There is no "User 
Manual". It also requires Tcl with the Tk Img package be installed. If 
someone does not know how to unpack a ZIP and double-click a file, 
well... Adding a windows installer (even NullSoft) would add more 
complexity than I am willing to handle, especially trying to determine 
if Tcl is already installed, downloading ActiveState's version if not, 
etc. I am also assuming Unix users know how to unpack a tarball.


There's an 'INSTALL.txt' that should provide enough information. After 
that I will assume that most people know how to click a mouse.


If the 'INSTALL.txt' is unclear or there are bugs, I'd like the bug 
tracking system to be easy to use. Since there's no "Users Manual", I do 
not need nor want a public "wiki".




FYI, Fossil can automatically create "tarballs" of the files in the
repository for a specified version, which defaults to the latest.


That is one of the features that I was looking for. How to get the URL 
for that to put on the 'home' page is one of my next tasks. I doubt that 
most windows users would explore fossil's interface (and understand it 
enough) to click 'files' then click the weird check-in id to get to the 
ZIP download button. At this point I'm assuming I can just copy that URL 
and duplicate it on my home page.




I suppose a work-around would be to add the image(s) to a specific
version of your project, commit that version, then remove (rm) the
image(s) from the next version and commit that. Then your pages can link
to the image(s) at that specific version of your project, while the
automatically made tarballs would not have it/them.


I'll have to explore that. It's just one image to get an idea of the 
app's GUI.




Also, besides Fossil created tarballs, your project's build procedure
can, possibly should, create release packages. Such packages would
contain only what you choose to put in them. (But, see below.) The
specific version "trick" I described would work for these, as well as
images.


Since there is no build procedure, I want whatever source control system 
or host to supply the simple download Zip/Tar button. Again, thanks for 
your help.

___
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] Admin->Configuration suggests '/home' as index page. How do I create '/home'?

[The Tick]

On 9/15/2015 4:00 PM, Ron W wrote:

On Tue, Sep 15, 2015 at 3:54 PM, The Tick <the.t...@gmx.com
<mailto:the.t...@gmx.com>> wrote:

After starting 'fossil ui', I go Admin->Configuration

The Index page value has the suggestion to use '/home'. I did that.
Now, how do I create this '/home' page?


 From the instructions on that set up page:

The default "/home" page displays a Wiki page with the same name as the
Project Name specified above. Some sites prefer to redirect to a
documentation page (ex: "/doc/tip/index.wiki") or to "/timeline".

So, if your project's name is "Fossil", then create a wiki page named
"Fossil".



Ah, so there's a mapping: /home ==> wiki page named 
Thank you
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to embed image in project home page or wiki pages?

[The Tick]

This is my first open source project... I think fossil is the easiest 
source control for me to use, but I've got a lot to learn.


I've not found a way to put an image in the home page for a project.

I did run across a way to embed an image that is checked in as part of a 
project: 
http://stackoverflow.com/questions/3982999/fossil-how-to-display-checked-in-image-files-on-wiki-pages


However, if I do that, then the image would be included in the project 
download, right? I guess one small image would not be that big a deal, 
but it would be good to not foist unnecessary files on users.


I'd like to put a small screenshot image to illustrate the project's 
GUI. Eventually, I will use Chisel to host this project, so perhaps 
there's a way to host an image file outside of a project's repository? 
(And, of course, to reference the image with an  tag.)



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Admin->Configuration suggests '/home' as index page. How do I create '/home'?

[The Tick]

Following a recommendation to use fossil and Chisel for my very first 
open source project, my impression of fossil is very favorable. I've 
downloaded fossil to my win7x64 PC, created a repository and am now 
trying to set it up as I eventually will on Chisel (I assume).


After starting 'fossil ui', I go Admin->Configuration

The Index page value has the suggestion to use '/home'. I did that. Now, 
how do I create this '/home' page?


I clicked on 'Wiki' and it let me create a 'new' page. I called it 
'home' and put some content there.


Where is it? Why does it not show up when I click 'Home'?

I found a discussion in the archives that had some suggestions as to 
various options. I don't yet understand what's being suggested. So, I 
just want to keep things really, really simple to start with.


How do I create this '/home' page so that I don't get 'Empty page' when 
I click on 'Home'?


[As an aside, when I click on 'Home' I see 'Project name / project name' 
as the heading. Is there any way to remove the redundancy?]


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users