On Aug 15, 2017, at 11:41 AM, Steve Schow wrote:
>
> Today I tried to check something in to the master repository, but even after
> going to one of the others and running fossil sync, the change doesn’t show
> up there…am I forgetting something?
What does “fossil set autosync” say?
___
On Aug 15, 2017, at 2:53 PM, Steve Schow wrote:
>
> well…its not for a website…javascript is used for a lot of stuff out there
> besides the web. Its not practical for the name of the file to have a
> version encoded into it.
Easily solved. During the “generate deployment package” step, crea
On Aug 15, 2017, at 3:07 PM, Steve Schow wrote:
>
> yea that’s way overkill.
The attached script creates versioned zip files given a Fossil-versioned file
name containing the file and a manifest file called VERSION. You can therefore
get the version number in the file name and in the VERSION
On Aug 15, 2017, at 3:50 PM, Steve Schow wrote:
>
> I will try to find a solution outside of fossil.
The ship script gets you 95% of the way there.
For example, if you absolutely positively had to have the version number
embedded into the deployed JS file, you could substitute it into the ship
On Aug 15, 2017, at 3:50 PM, Steve Schow wrote:
>
> its way overkill to have to follow any kind of build or deployment process
> whatsoever for these scripts.
One other thing: you had to have some kind of step to deploy these. If it’s
just a “cp” command, build that into a modified version
On Aug 15, 2017, at 3:55 PM, Steve Schow wrote:
>
> no matter what I have tried to add enumeration lists in my fossil tickets,
> the ticket comment is still coming up without any formatting.
There are two ways I can see that happening:
1. You didn’t select Wiki from the “Format” drop-down. The
On Aug 15, 2017, at 3:58 PM, Steve Schow wrote:
>
> if each script file has its own independent version, its not part of a
> greater whole per say…its just the version of that exact file..nothing
> more……appearing in the source comment.
My ship script doesn’t care about “greater wholes”. It e
On Aug 15, 2017, at 4:12 PM, Steve Schow wrote:
>
> yes the wiki menu item is selected
>
> yes no blank lines are present, still getting unformatted results. for
> example
>
> This is some paragraph
> # item one
> # item two
>
> this results in:
>
> This is some paragraph # item one #
On Aug 15, 2017, at 4:23 PM, Steve Schow wrote:
>
> I have tried with a blank line between the paragraph and the list also, same
> result. yes I am making sure always that the wiki menu item is selected
Here’s a freshly-created Fossil repository with one ticket, formatted as you
ask:
htt
On Aug 15, 2017, at 4:46 PM, Steve Schow wrote:
>
> i’m getting the same result with new tickets, or adding on to tickets, makes
> no difference.
Send back the changed repository so that I (or someone else) can examine it.
___
fossil-users mailing lis
On Aug 15, 2017, at 4:28 PM, Warren Young wrote:
>
> Here’s a freshly-created Fossil repository with one ticket, formatted as you
> ask:
>
>https://drive.google.com/open?id=0B6JrNPgaCV7RYldEc0d6MnpXTGc
I apologize to those who have tried the link since I created it: I f
On Aug 15, 2017, at 5:46 PM, Steve Schow wrote:
>
> well figured it out.. for some reason my main repository had the following
> is it possible to have a diagram on my wiki page without that HTML option
> checked?
Fossil Wiki syntax accepts HTML tags. See:
https://www.fossil-scm.org/in
On Aug 23, 2017, at 7:21 AM, Richard Hipp wrote:
>
> On 8/23/17, j. van den hoff wrote:
>> unable to create directory /var
>
> It is trying to create a temporary file in which to store the one of
> the two sides of the diff. Can you trace the problem by running in a
> debugger?
This sounds li
On Aug 24, 2017, at 6:21 AM, David Mason wrote:
>
> I want a symlink to behave in fossil like it does in the Unix find command -
> i.e. stop at a symlink without a --follow switch
+1: principle of least surprise. Fossil should not invent new semantics.
> like it does in the Unix tar command (
On Aug 29, 2017, at 10:59 PM, BohwaZ wrote:
>
> But if you don't sync between removal and add, the 0 bytes bug is happening.
I’ve seen this, too, but didn’t report it because there is the workaround
you’ve discovered.
___
fossil-users mailing list
fos
On Sep 7, 2017, at 4:21 PM, Richard Hipp wrote:
>
> https://www.fossil-scm.org/fossil/help?cmd=ignore-glob for the
> documentation on the ignore-glob setting. I confess that the
> documentation is a bit thin at the moment and needs enhancement, but
> it is what we have for now.
The globbing rul
> On Sep 14, 2017, at 11:12 PM, Johan Kuuse wrote:
>
> I would like to have a stronger argument against rebasing, preferrably with
> an example.
It’s been hashed over here on the mailing list many times before. Just search
the archives for “git rebase”.
The short argument I prefer to use is
On Sep 18, 2017, at 6:49 PM, BohwaZ wrote:
>
> I'm looking at ignoring some files when an archive (zip/tarball) is created
> by Fossil.
What’s a good example where you’d want to do that?
If anything, I find Fossil zip/tarball to produce *less* than I want in a
release tarball, lacking things
On Sep 19, 2017, at 3:22 PM, BohwaZ wrote:
>
> But I'm not sure if I want to implement that in Fossil just because another
> unrelated piece of software makes bad decisions…
I think you have *two* uses of zip/tarball here, not one: Fossil’s built-in
mechanism for providing checkouts to people
On Sep 19, 2017, at 9:32 PM, Richard Hipp wrote:
>
> /first-10-checkins /timeline?n=10&a=1970-01-01
You could also use this for Tickets reports:
/bugs /rptview?rn=3
/wishlist /rptview?rn=2
Those being the report IDs of my Feature_Requests a
On Sep 21, 2017, at 11:16 AM, Andy Goth wrote:
>
> xyzzy...Nothing happens.
You win 10 geek points today.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Sep 26, 2017, at 7:10 AM, Lonnie Abelbeck wrote:
>
> sqlite3 /mnt/kd/fossil/astlinux.fossil .dump >
> "$CUSTOM_BACKUP_DIR/astlinux.fossil.dump”
[snip]
> This seems to work well with limited testing ... Am I missing anything ?
That’s more or less what we do here for our off-site backups. T
On Sep 26, 2017, at 9:11 AM, Lonnie Abelbeck wrote:
>
> # fossil sqlite3 --version -R /mnt/kd/fossil/astlinux.fossil
> 3.17.0 2017-02-13 16:02:40 ada05cfa86ad7f5645450ac7a2a21c9aa6e57d2c
That would be Fossil 2.0, a transitional release meant to ease the move from
Fossil 1.x to 2.x. Why run th
On Oct 14, 2017, at 4:16 PM, Andy Goth wrote:
>
> Please review the enhanced-symlink branch.
Aside from a manifest.symlinks file appearing at the project root, what should
we see? How do we test it?
For example, if I declare a file to be a symlink in the repository by editing
that file, what
On Oct 16, 2017, at 4:44 PM, Arseniy Terekhin wrote:
>
> What should "ln" do on FAT16/32 and exFAT filesystems? Well, I'd just expect
> fossil to not bother creating any links and maybe give a warning.
Or, write two copies of the file, then on checkin either: a) take the later of
the two files
On Oct 16, 2017, at 7:28 PM, Andy Goth wrote:
>
> I don't have the luxury of Cygwin because my end users won't have it.
You can just distribute the DLL, then.
In cases where your users *may* have Cygwin installed, it is considered polite
to install the DLL only when it doesn’t already exist on
On Oct 17, 2017, at 7:12 PM, Andy Goth wrote:
>
> requiring JavaScript access has proven to be
> fatal for his project's usage of Fossil.
I noticed a complete lack of “me, too” in that thread. Usually when one of the
other VCSes does something different from Fossil, people are quick to jump on
On Oct 18, 2017, at 3:44 AM, Warren Young wrote:
>
> The more web apps that ship with stringent Content-Security-Policy headers,
> the fewer arguments we’ll have for allowing JS on web pages.
Wow…caffeine isn’t working yet, obviously.
What I meant to say is that the more web site
On Oct 18, 2017, at 7:04 AM, Richard Hipp wrote:
>
> On 10/18/17, Warren Young wrote:
>> On Oct 18, 2017, at 3:44 AM, Warren Young wrote:
>>>
>>> The more web apps that ship with stringent Content-Security-Policy
>>> headers, the fewer arguments
On Oct 18, 2017, at 8:27 AM, Warren Young wrote:
>
> On Oct 18, 2017, at 7:04 AM, Richard Hipp wrote:
>> I'll have to add a "/fossil.js” resource
While you’re about it, I’d suggest shipping /fossil-$hash.js instead and
setting a multi-year Expires header for the file so
On Oct 18, 2017, at 8:51 AM, Andy Goth wrote:
>
> style-$hash2.css where $hash2 is a hash (or prefix thereof)
> of the contents of style.css, possibly combined with the Fossil checkin
> prefix.
If style.css is stored as a Fossil artifact, we get that for free.
If it’s stored in SQL, Fossil coul
Someone wrote up a document laying out opinions about how “mature” a given
software project’s top-level README file is:
https://github.com/LappleApple/feedmereadmes/blob/master/README-maturity-model.md
It’s good food for thought, except insofar as it confuses “GitHub” with “the
way softwar
On Nov 3, 2017, at 12:08 PM, Richard Hipp wrote:
>
> On 11/3/17, Olivier R. wrote:
>>
>>
>> Sorry. My knowledge of the C toolchain is null.
>
> The next step will be to figure out
> how to attach the debugger to a hung process.
Problem #1 could be fixed (in principle) without any more help f
On Nov 8, 2017, at 8:24 AM, Pietro Cerutti wrote:
>
>> -with-tcl=path=> {Enable Tcl integration, with Tcl in the
>> specified path}
>> +with-tcl:path=> {Enable Tcl integration, with Tcl in the
>> specified path}
autosetup 0.6.8 changes this again, dropping “with/without
I add a line explaining the file’s provenance to
the module’s header comment:
Merged from foo.c and bar.c on 2017.11.14 by Warren Young
or
Extracted from foo.c on 2017.11.14 by Warren Young
Between that and the checkin comments near that date, I can backtrace merges
and splits manually.
On Nov 14, 2017, at 8:21 AM, Warren Young wrote:
>
> What Fossil could backtrace automatically, and still doesn’t, are renames.
> Change a file’s name and the “finfo” terminates at the rename point.
To clarify:
I realize that Fossil *remembers* each rename. What I’m wishing fo
On Nov 14, 2017, at 2:42 PM, Stephan Beal wrote:
>
> On Tue, Nov 14, 2017 at 4:26 PM, Warren Young wrote:
> https://tangentsoft.com/pidp8i/finfo?name=libexec/mkos8
>
> Don't take this the wrong way, but that is a mighty fine skin you have, sir.
Thank you. It’s large
On Nov 14, 2017, at 6:57 PM, Richard Hipp wrote:
>
> On 11/14/17, Warren Young wrote:
>>
>> If anyone wants it, they can consider it to be under the SIMH license:
>
> Can I make it would of the built-in skin options in Fossil?
Flattered but baffled, I says “Yes.”
I see a new wiki article:
https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG
I’m glad to see shallow and narrow clones being planned.
The section on narrow clones should specify whether these can take on a life
independent of the parent repository. That is, can they be used to shard
On Nov 20, 2017, at 1:33 PM, Warren Young wrote:
>
> I see a new wiki article:
>
>https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG
Shallow clones bear some thinking, too.
Let us posit that “fossil clone” takes a -shallow option with no argument,
telling it to fe
On Nov 20, 2017, at 2:55 PM, Offray Vladimir Luna Cárdenas
wrote:
>
> On 20/11/17 16:45, Carlo Miron wrote:
>> On Mon, Nov 20, 2017 at 9:33 PM, Warren Young wrote:
>>
>>> When the FILENAME parameter is not given, it produces a “Fossil”
>>> subdirectory con
On Nov 20, 2017, at 3:12 PM, Offray Vladimir Luna Cárdenas
wrote:
>
> I thought that was the extension
> the shallow cloned repository would get if no extension name was specified.
If you say
$ fossil clone https://fossil-scm.org fossil
You get a repository file called “fossil”, not “foss
On Nov 20, 2017, at 1:33 PM, Warren Young wrote:
>
> There is one more thing Git really gets right compared to Fossil: single-step
> clone-and-open. We should be able to do the same:
I’ve prototyped this as a simple shell script:
#!/bin/sh -e
url=$1
shift
tmprepo=`mktemp
On Nov 20, 2017, at 3:41 PM, Offray Vladimir Luna Cárdenas
wrote:
>
> On 20/11/17 17:22, Warren Young wrote:
>> On Nov 20, 2017, at 3:12 PM, Offray Vladimir Luna Cárdenas
>> wrote:
>>> I thought that was the extension
>>> the shallow cloned repositor
On Nov 20, 2017, at 4:04 PM, Warren Young wrote:
>
> Git allows you to do this in 2 steps: clone & cd. Fossil currently requires
> 5, as I showed up-thread.
4 steps. The fifth step in the post starting this thread is part of a sepa
On Nov 20, 2017, at 4:57 PM, bytevolc...@safe-mail.net wrote:
>
> Why add more complexity and bloat to the Fossil core?
Because interoperability. One of the major arguments against using Fossil is
that it’s largely a one-way transition today, which messes up muscle memory for
both Fossil parti
On Nov 21, 2017, at 1:24 PM, Ron W wrote:
>
> But, a "universal VCS adaptor" won't really be universal, so tool developers
> will still end up supporting git, Hg and maybe SVN, so why would a tool
> developer support Fossil-NG?
Tool developers will ignore Fossil-NG to the same extent that they
On Nov 21, 2017, at 2:09 PM, Ron W wrote:
>
> While I like the idea of a "smart default" for the file name, I'd rather have
> an "--open" (or "-o") option to trigger the automatic "fossil open”.
So…you want to remain more difficult to use than Git in this regard?
That’s not very Fossil.
(Yes,
On Nov 21, 2017, at 3:55 PM, bytevolc...@safe-mail.net wrote:
>
> On Mon, 20 Nov 2017 17:44:49 -0700
> Warren Young wrote:
>>
>> …muscle memory for both Fossil partisans and for partisans of other
>> VCSes.
>
> This seems more like a complaint about t
On Nov 21, 2017, at 4:44 PM, Zoltán Kócsi wrote:
>
> Adding unnecessary complexity to its innermost workings would open the
> door to a maintenance hell, I think.
If it were someone else proposing this feature as something for drh to do, then
I might well agree with you, but since it is drh pro
On Nov 21, 2017, at 5:21 PM, Zoltán Kócsi wrote:
>
> On Tue, 21 Nov 2017 16:42:56 -0700
> Warren Young wrote:
>
>> [...]
>>
>> There are some truly bletcherous C compilers in the embedded space.
>
> Well, I have some reservations about accepting that an
On Nov 21, 2017, at 5:22 PM, Offray Vladimir Luna Cárdenas
wrote:
>
> I don't see the point of raising this in the users list if
> any voice we raise as users is answered as dumb or rudely by more
> experienced users or devs.
Since you’re replying to me, I can only take that reply as saying tha
On Nov 22, 2017, at 7:43 AM, bytevolc...@safe-mail.net wrote:
>
> On Tue, 21 Nov 2017 16:42:56 -0700
> Warren Young wrote:
>
>>> This seems more like a complaint about the user interface.
>>
>> How does that observation get us to a different solution?
>
On Nov 22, 2017, at 9:56 PM, Richard Hipp wrote:
>
> On 11/22/17, Warren Young wrote:
>>
>> 1. Visit https://example.com
>> 2. Click Timeline (and how would my users know to do that?)
>> 3. Click checkin ID.
>> 4. Find and click Tarball link
>> 5. U
On Nov 23, 2017, at 5:19 AM, bytevolc...@safe-mail.net wrote:
>
> They want maximum results for minimum effort? That may be normal, but
> it's still whiney.
If “normal” is “whiney”, it ceases to be a useful disparagement unless you
intend to change society. This mailing list is not a good place
On Nov 24, 2017, at 7:35 AM, Richard Hipp wrote:
>
> Which is better?
>
> A: https://www.fossil-scm.org/a/timeline
> B: https://www.fossil-scm.org/b/timeline
I prefer A because I don’t like having to dig for details. Hiding details
isn’t the answer to clutter. Drawing the eye to key deta
On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>
> The big down-side is that less
> information is visible on a single screen now, so you have to scroll
> more. But that seems to be the trend with websites these days….
The design ideas I tapped into this were old when desktop publishing was t
On Nov 27, 2017, at 3:46 PM, Warren Young wrote:
>
> On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>>
>> The big down-side is that less
>> information is visible on a single screen now, so you have to scroll
>> more. But that seems to be the trend with website
On Nov 27, 2017, at 7:04 PM, Steve Landers wrote:
>
> Note that I would retain the rounded corners on Warren’s backgrounds, they
> make the visuals “softer”.
You can have that without the stroked borders:
td.timelineTableCell {
border-radius: 10px;
background-color: #f8f8f8;
}
That is, do
On Nov 28, 2017, at 3:12 AM, Johan Kuuse wrote:
>
> I think the one important thing is that all involved HTML elements have a
> 'class' or 'id' tag.
Yes. Several times in making my last custom Fossil skin, I’ve had to employ
some rather clever CSS selector trickery to target the elements I wa
On Nov 28, 2017, at 9:07 AM, Mike Burns wrote:
>
> > You won't get Fossil/SQLite running on a Commodore 64 without a lot of work.
>
> What are the chances someone will take up take up this challenge, and have a
> Commodore 64 or Apple II version of fossil up and running by the end of the
> yea
On Nov 29, 2017, at 7:53 AM, Martin Gagnon wrote:
>
> There's a small display glitch, the mouse cursor over the
> Basic/Advanced button is set to "text selection" mode instead of the
> usual "hand with the index finger up" for clickable links.
It can be fixed by adding href="#" into the element
On Nov 29, 2017, at 7:26 AM, Richard Hipp wrote:
>
> The "selected entry" highlighting, such as seen here:
>
>https://www.fossil-scm.org/fossil/timeline?c=trunk
>
> Still looks goofy in the Modern View, especially using Edge. Your
> help in fixing that problem will be much appreciated.
It
On Nov 29, 2017, at 8:16 AM, Warren Young wrote:
>
> [*] To be clear, that means the element ends up with two classes.
Even more clear:
...
td.timelineSelected {
border-width: 2px;
background-color: #ffc;
box-shadow: 4px 4px 2px rgba(0, 0,
On Nov 29, 2017, at 8:27 AM, Martin Gagnon wrote:
>
>> It can be fixed by adding href="#" into the elements
>
> Using "Inspect" on chrome, I found that adding:
>
> cursor: pointer;
>
> inside "element.style" fix the problem.
That feels more heavy-handed to me. My method works with the br
On Nov 29, 2017, at 8:26 AM, Richard Hipp wrote:
>
> On 11/29/17, Warren Young wrote:
>>
>>https://imgur.com/a/TEWjA
>
> I think we'd like the selection mechanism to somehow highlight the
> entire row
I don’t think it really helps, but thi
On Nov 29, 2017, at 8:50 AM, Richard Hipp wrote:
>
> Apparently what I would need to do is generate HTML without all of the
> onclick= and style= attributes
Yes.
> but make sure every element has an id= attribute.
Or at least a class attribute, when you want multiple elements to have the same
On Nov 29, 2017, at 3:10 PM, Joerg Sonnenberger wrote:
>
> On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote:
>> On 11/29/17, Jacob MacDonald wrote:
>>> Ah, I see. It seems strange to me that the policy didn't get set when I
>>> cloned. How can I avoid the same thing in the future and
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 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 Dec 2, 2017, at 5:00 AM, bytevolc...@safe-mail.net wrote:
>
> What's up with this comment in add.c starting at line 27:
It was written back when “Fossil 2.0” meant something different from what we
now call “Fossil 2.0”:
https://www.fossil-scm.org/index.html/wiki?name=Fossil+2.0
At minim
On Dec 5, 2017, at 8:47 AM, Roy Keene wrote:
>
> Version 2.2 is in Debian testing, has been for a while.
Thank you for chasing this on the back-channel, Roy. It’s good to know that
there is a binary version of Fossil 2.x in Debian current already, if you
absolutely cannot use one of the offic
On Dec 5, 2017, at 8:47 AM, Warren Young wrote:
>
> At minimum, that wiki article should be renamed
Never mind. I see now that the page is being maintained under its current name
to avoid breaking existing links on the web.
___
fossil-users m
On Dec 6, 2017, at 2:12 AM, Jan Nijtmans wrote:
>
> 2017-12-06 10:03 GMT+01:00 Scott Doctor:
>>
>> How can I permanently turn off the crlf warning that occurs when I do I do a
>> commit without having to use the crlf-glob command each time? I do not get
>> why that warning even exists.
>
> Jus
On Dec 6, 2017, at 2:03 AM, Scott Doctor wrote:
>
> I do not get why that warning even exists.
Because people working on cross-platform projects often have one user (there’s
always one) who opens a text file with Unix line endings on a Windows box and
commits it with DOS line endings, thus pot
On Dec 6, 2017, at 12:22 PM, Richard Hipp wrote:
>
> (6) CSP headers says: "default-src 'self' 'unsafe-inline’".
Don’t undersell the advantages. That’s a significant improvement already:
1. It disallows all eval() cases, which closes off a whole class of attacks.
2. It disallows active conte
On Dec 6, 2017, at 12:34 PM, Sean Woods wrote:
>
> https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki
>
> See that ugly "index.html" in the URL? Was that always there?
Yes, it was:
https://web.archive.org/web/20151225132659/http://www.fossil-scm.org/index.html/doc/trunk/www/i
On Dec 7, 2017, at 10:41 AM, Offray Vladimir Luna Cárdenas
wrote:
>
> I have been looking in the help on revert, but it seems related to files
> and I wonder which is the command to revert a wiki page from it
> particular version to some previous one.
>
> Now that web interface is changing, may
On Dec 10, 2017, at 2:40 PM, Thomas wrote:
>
> the reason why horizontal tabs in artifacts are 8 characters wide is because
> { tab-size: 4; } doesn't appear.
>
> Wouldn't it make sense to add this so that the /artifact, /fdiff etc pages
> fall back to 4 instead of 8?
Tabs at a multiple of 8
On Dec 10, 2017, at 7:40 PM, Andy Bradford wrote:
>
> Thus said Richard Hipp on Sun, 10 Dec 2017 19:20:59 -0500:
>
>> Minor correction: the hash algorithm changes was from SHA1 to
>> SHA3-256.
>
> I would call that a major correction! I knew something didn't seem right
> about what I s
On Dec 11, 2017, at 2:07 PM, Florian Balmer wrote:
>
> So my strategy here was to argue for a generally accepted default that
> would be built into Fossil ;-)
Switch to Modern view? :)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
htt
On Dec 11, 2017, at 3:09 PM, Rolf Ade wrote:
>
> Florian Balmer writes:
>> I didn't want to spend my hobby time with CSS
>> diffing.
>
> ...having own
> skins and CSS as branch of the main trunk(s) (the build-in skins) and to
> be able to merge the own skins/CSS from the build-in skins, as they
On Dec 11, 2017, at 3:26 PM, Thomas wrote:
>
> On 2017-12-11 21:47, Warren Young wrote:
>> Try this > echo -e "\tHi" | cat
>
> Tried it just now.
The leading $ means it’s intended to be understood as a Bourne shell command.
The point remains true in Windows, ho
On Dec 11, 2017, at 5:03 PM, Richard Hipp wrote:
>
> A new version of Fossil is up with some minor UI tweaks:
>
> (1) No more box around comments in the Modern and Columnar views.
> Instead, the background color is a light gray.
Works for me, though maybe a slightly lighter gray, barely percept
On Dec 11, 2017, at 9:01 PM, Steve Landers wrote:
>
> The slightly lighter gray has the downside of not being visible by many folk
> with diminished contrast perception.
I’d worry more about poor quality monitors that either have poor white clipping
behavior or off-axis brightness problems.
A
On Dec 13, 2017, at 6:21 AM, Tino Lange wrote:
>
> The directory/directories will keep existing!
Given that Fossil doesn’t know anything about directories, other than as
containers for the files it manages, I’m not sure that isn’t the right thing.
To have Fossil remove intermediate directories
On Dec 13, 2017, at 8:31 AM, Tony Papadimitriou wrote:
>
> * The first is the inclusion of un-versioned files which although inflate the
> total file size have no play in the versioning part, which is what I believe
> the compression ratio was meant to highlight.
If unversioned file data isn’t
I just tried to rebuild a Fossil repo that I’d lost permission to read due to
some sysadmin silliness, and got spammed by this in a rapid loop:
PRAGMA database_list
SQLITE_CANTOPEN: cannot open file at line 36229 of [1a584e4999]
SQLITE_CANTOPEN: os_unix.c:36229: (2) open(/nunya/binness.fossil-wal
On Dec 12, 2017, at 2:40 PM, Thomas wrote:
>
> On 2017-12-11 22:55, Warren Young wrote:
>> notepad.exe and Internet Explorer also obey the 8-character tab standard.
>> Go tell Microsoft it is wrong, too.
>
> I'm not sure how many people use notepad.exe to
On Dec 12, 2017, at 12:33 PM, Juan Francisco Cantero Hurtado
wrote:
>
> I want share a fossil repo using a static http server
Call something like this from a crontab:
$ wget -O /var/www/html/dl/my-project.zip http://localhost:8080/zip
Then in the HTML:
Download
> I want share only t
On Dec 13, 2017, at 9:55 AM, Richard Hipp wrote:
>
> Would Git or GitHub have told me about those prior tickets?
GitHub is pretty good about surfacing such information, as long as the ticket
references the checkin ID.
In fact, GitHub can be a bit overeager about cross-linking everything. Ju
On Dec 13, 2017, at 9:26 AM, Warren Young wrote:
>
> ...I’d lost permission to read...
>
> SQLITE_CANTOPEN: os_unix.c:36229: (2) open(/nunya/binness.fossil-wal) - No
> such file or directory
Actually, it looks like it’s opening the DB for reading but then fails to write
the W
On Dec 13, 2017, at 1:03 PM, jungle Boogie wrote:
>
> On 13 December 2017 at 07:58, Warren Young wrote:
>
>> I’d feel differently if Fossil owned the directories, but it doesn’t.
>> They’re mine; leave them alone!
>
> Yes, I agree. I think this topic has b
On Dec 13, 2017, at 1:37 PM, Richard Hipp wrote:
>
> On 12/13/17, Warren Young wrote:
>> I just tried to rebuild a Fossil repo that I’d lost permission to read due
>> to some sysadmin silliness, and got spammed by this in a rapid loop:
>>
>> PRAGMA database_list
&
On Dec 11, 2017, at 9:19 PM, Warren Young wrote:
>
> I’d go as far as #F8F8F8 myself.
One of my Fossil projects’ skins is based on Khaki, which hasn’t yet been
restyled to override the base styles for the timeline boxes, so I get light
gray on yellow, not terribly attractive. The fol
On Dec 13, 2017, at 2:21 PM, Zakero wrote:
>
> The "fossil clean" command has the "--emptydirs" option. That might be
> useful for the "rm" command as well.
If Fossil got that option, I’d probably forget that it existed a week after the
change went in. I’d end up saying something like
$
On Dec 14, 2017, at 10:19 AM, jungle Boogie wrote:
>
> So Warren edited a file at the same exact time as tangent?
Fossil arguably has a bug here, where if you check a change in as local user
name “tangent”, as I do here, then *later* do a “fossil sync” to a URL with a
user name, some bit of th
On Dec 17, 2017, at 1:44 PM, Kevin wrote:
>
> I believe deception and impersonation are important.
I agree. One of the core tenets of Fossil is durable accountability, and here
we have a case where it allows the who-did-what history to be muddied.
What Fossil allowed in the case that started
On Dec 18, 2017, at 6:52 AM, Olivier R. wrote:
>
> When gdb was active, Fossil didn’t answer when asking for a webpage. It
> seemed blocked.
That’s exactly what happens. If you want the process to run while GDB remains
attached, say “cont” after attaching.
> Here is what gdb said:
Did it sa
On Dec 18, 2017, at 7:04 PM, bch wrote:
>
> Does contemporary Linux not randomize its PIDs?
It may be an option, but it isn’t happening on a near-stock CentOS 7 box I have
near at hand here:
$ ls > /dev/null & echo $!
Run that repeatedly on a quiet system, and chances are, you’ll get ste
201 - 300 of 934 matches
Mail list logo
