On Thu, 30 Nov 2017 13:09:12 -0500
Richard Hipp wrote:
>
> Please download and compile the latest version of the symlink-refactor
> branch (https://www.fossil-scm.org/fossil/info/b2594738460036b9) and
> let me know whether or not it is working better for you.
>
> Thanks for the bug report, and
Looks like this resolves the issue.
On Thu, 30 Nov 2017 13:10:09 -0500
Richard Hipp wrote:
> Can you rebuild using the latest check-in on the symlink-refactor
> branch (https://www.fossil-scm.org/fossil/info/b2594738460036b9) and
> let me know whether or not this problem is resolved?
Thus said Paolo Bolzoni on Thu, 30 Nov 2017 12:40:17 +0100:
> It worked fairly well until I received an unexpected update of the
> original files. I unpacked the new files in dir1 and fossil detected
> hundreds of changes; looking better however this changes are mostly
> just order change
On 30 November 2017 at 10:55, Warren Young wrote:
> On Nov 30, 2017, at 8:16 AM, jungle Boogie wrote:
>>
>>mkcss.exe ..\src\default_css.txt default_css.h
>> ..\src\default_css.txt:1: syntax error
>
> Has src/default_css.txt changed? Try reverting it.
>
Thanks for the pointer! There as a
On Nov 30, 2017, at 9:07 AM, Marc Simpson wrote:
>
> Re: CSS issues: I think the default skin would be a bit more readable
> with 1 or 2 pixels of space between these newly added commit
> bubbles/boxes.
>
> (Adjacency currently yields a doubly thick shared line.)
My original design had about 2
On Nov 30, 2017, at 8:16 AM, jungle Boogie wrote:
>
>mkcss.exe ..\src\default_css.txt default_css.h
> ..\src\default_css.txt:1: syntax error
Has src/default_css.txt changed? Try reverting it.
The fact that you have an evolving stream of different errors is a big concern.
Why isn’t th
On 30 November 2017 at 08:07, Marc Simpson wrote:
> Re: CSS issues: I think the default skin would be a bit more readable
> with 1 or 2 pixels of space between these newly added commit
> bubbles/boxes.
>
> (Adjacency currently yields a doubly thick shared line.)
Comparing to the sqlite skin, I ag
On 11/25/17, bytevolc...@safe-mail.net wrote:
> On OpenBSD 6.1, running "fossil uv edit" will result in the
> following error:
>
> unable to create directory /var/tmp
Can you rebuild using the latest check-in on the symlink-refactor
branch (https://www.fossil-scm.org/fossil/info/b2594738460036b9
On 11/29/17, James B wrote:
> Hi all,
>
> I'm a long-time users of fossil.
> Recently I upgraded from fossil 1.35 to fossil 2.4, and found the following
> problem about symlinks. It seems that the allow-symlinks settings doesn't
> work properly.
Please download and compile the latest version of t
On 11/30/17, jungle Boogie wrote:
>
> Visual Studio 2017 Developer Command Prompt v15.0.26730.16
>
So, it works with Microsoft Visual Studio v14.0.
Please suggest a fix to get it working with v15.0.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users
On 30 November 2017 at 08:43, Richard Hipp wrote:
> On 11/30/17, jungle Boogie wrote:
>> On 30 November 2017 at 07:46, Richard Hipp wrote:
>>> On 11/30/17, jungle Boogie wrote:
Still failing with latest changes and nmake /f Makefile.msc and with
buildmsvc.bat:
>>>
>>> Sorry
On 11/30/17, jungle Boogie wrote:
> On 30 November 2017 at 07:46, Richard Hipp wrote:
>> On 11/30/17, jungle Boogie wrote:
>>>
>>> Still failing with latest changes and nmake /f Makefile.msc and with
>>> buildmsvc.bat:
>>>
>>
>> Sorry you are having trouble. It works for me. Please suggest a f
On 30 November 2017 at 07:46, Richard Hipp wrote:
> On 11/30/17, jungle Boogie wrote:
>>
>> Still failing with latest changes and nmake /f Makefile.msc and with
>> buildmsvc.bat:
>>
>
> Sorry you are having trouble. It works for me. Please suggest a fix...
Are you using Microsoft Visual Studio
Re: CSS issues: I think the default skin would be a bit more readable
with 1 or 2 pixels of space between these newly added commit
bubbles/boxes.
(Adjacency currently yields a doubly thick shared line.)
On Thu, Nov 30, 2017 at 7:16 AM, jungle Boogie wrote:
> On 30 November 2017 at 06:36, Martin
On 11/30/17, jungle Boogie wrote:
>
> Still failing with latest changes and nmake /f Makefile.msc and with
> buildmsvc.bat:
>
Sorry you are having trouble. It works for me. Please suggest a fix...
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users m
Thanks for the bisect.
I am refactoring the misdesigned symbolic link support in Fossil now.
It will be a few days before I have a fix for you.
This is not a simple patch. This is a complete redesign of the
symbolic link handling logic, and so will take a little time to get
right. Your patience
On 30 November 2017 at 06:36, Martin Gagnon wrote:
> Do ctrl-f5 to force a full refresh. CSS is cached.
>
Yes, now it back!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-
On 29 November 2017 at 15:35, jungle Boogie wrote:
> On 29 November 2017 at 15:06, jungle Boogie wrote:
>> Hi All,
>>
>> First time to compile Fossil on Windows in awhile, so this might me a
>> fault of my own doing.
>>
>> ..\src\../skins/original/header.txt
>> ..\src\../skins/plain_gray/css.txt
On Thu, 30 Nov 2017 13:45:44 +1000
James B wrote:
> Hi all,
>
> I'm a long-time users of fossil.
> Recently I upgraded from fossil 1.35 to fossil 2.4, and found the following
> problem about symlinks. It seems that the allow-symlinks settings doesn't
> work properly.
>
> Steps to reproduce:
Do ctrl-f5 to force a full refresh. CSS is cached.
Le jeu. 30 nov. 2017 à 09:31, jungle Boogie a
écrit :
> On Nov 30, 2017 3:35 AM, "Richard Hipp" wrote:
> >
> > On 11/30/17, jungle Boogie wrote:
> > >>
> > >> In previous builds, this commit would certainly have a number of green
> > >> lines,
On Nov 30, 2017 3:35 AM, "Richard Hipp" wrote:
>
> On 11/30/17, jungle Boogie wrote:
> >>
> >> In previous builds, this commit would certainly have a number of green
> >> lines, but that's not the case anymore.
> >
> > bisect complete
> > 4 BAD 2017-11-29 19:18:45 5c9c51be5f033de2 CURRENT
>
On Thu, 30 Nov 2017 13:19:38 +0100
Jan Nijtmans wrote:
> This patch has no relation to fossil's symlink support, it's just part
> of the code to find a suitable temporary directory to write some
> intermediate file. It's unfortunate it's that complicated, but useful
> because sometimes the workin
On Thu, Nov 30, 2017 at 1:19 PM, Jan Nijtmans
wrote:
> 2017-11-28 0:20 GMT+01:00 :
> > On Mon, 27 Nov 2017 09:52:19 -0500
> > Richard Hipp wrote:
> >> I am very sorry that I allowed symbolic link support into Fossil in
> >> the first place. (Symbolic link support was neither designed nor
> >>
2017-11-28 0:20 GMT+01:00 :
> On Mon, 27 Nov 2017 09:52:19 -0500
> Richard Hipp wrote:
>> I am very sorry that I allowed symbolic link support into Fossil in
>> the first place. (Symbolic link support was neither designed nor
>> written by me - it is contributed code.) I would really like to g
Dear list,
I have a fairly large set of files, (a bit fewer than 60,000)
containing a simple key-value store in text format.
Being it so huge, and since I need to do edit only few files
(besides the customer needs only the changed ones) i organized my
project in this way:
dir1/ original files
di
On 11/30/17, jungle Boogie wrote:
>>
>> In previous builds, this commit would certainly have a number of green
>> lines, but that's not the case anymore.
>
> bisect complete
> 4 BAD 2017-11-29 19:18:45 5c9c51be5f033de2 CURRENT
> 3 GOOD2017-11-29 16:20:29 f9fc914eaef2c9e7
> 2 GOOD
On 30 November 2017 at 02:21, Jungle Boogie wrote:
> It's possible to highlight lines (or multiple lines) in fossil, but you
> need to manually edit the URL:
> https://www.fossil-scm.org/index.html/artifact?ln=45-52&name=24bd6b806af1782c
this is great, wish i knew that before!
--
Javier
__
27 matches
Mail list logo