Re: [fossil-users] Web interface timeline rail colors

[Florian Balmer]

Noticing the recent Fossil commit to show real branch colors in the
branch list, I have been reminded of my suggestion [0] from September
2015 to change the `bg_to_fg()' function from src/timeline.c that
derives the timeline rail colors from the branch colors. The modified
version supports color values in shorthand hex triplet notation
(#HHH), ensures no invalid colors with any of the RGB components
beyond 0 and 255 are generated, and a reasonable default color (black
or white depending on the "white-foreground" skin setting) is returned
for all color values not in standard or shorthand hex triplet
notation.

[0] 
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg21416.html

The discussion ended with Rich Neswold submitting a patch to support
shorthand hex triplet color values, and me cross-posting basically the
same patch with the additional features mentioned above. I hope I have
not been offending, and have not violated the Fossil contributor or
coding style guidelines.

Is there any chance that my suggestion will be considered for
incorporation? Merging the `bg_to_fg()' function body from [1] into
src/timeline.c should do, but I could also submit a patch in a
different format if required, or a Fossil bundle (as a new
"pending-review" branch) with an additional step to remove my
philosophical comments and clear the implementation choices left in
the code. Of course I'm willing to submit a Contributor Agreement, if
necessary.

[1] http://pastebin.com/Z8SwJNHZ

--Florian
___
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] Using fossil just for the wiki. Images and tables?

[Tino Lange]

>> [...] Fossil's Markdown support is via libdiscount [...]
> [...] Oh, Fossil uses Discount. Thanks, [...]

libdiscount? Sure? Isn't that a special version of libsoldout?

___
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 LS does not honor -R option

[Tony Papadimitriou]

I needed to see the file contents of a repo without opening it.

So, I tried the ls command with the –R repo option but I got an error message: 
current directory is not within an open checkout
But, the –R option is listed in the help for the ls command.

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] FOSSIL LS does not honor -R option

[Richard Hipp]

On 1/26/16, Tony Papadimitriou  wrote:
> I needed to see the file contents of a repo without opening it.
>
> So, I tried the ls command with the –R repo option but I got an error
> message: current directory is not within an open checkout
> But, the –R option is listed in the help for the ls command.
>

The -R options does not work unless you also include the -r option to
specify a specific version for which you want the directory listing.

-- 
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] FOSSIL LS does not honor -R option

[Tony Papadimitriou]

OK, thanks.  Rereading the help it is now 'obvious' :)

-Original Message- 
From: Richard Hipp

Sent: Tuesday, January 26, 2016 5:39 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL LS does not honor -R option

On 1/26/16, Tony Papadimitriou  wrote:

I needed to see the file contents of a repo without opening it.

So, I tried the ls command with the –R repo option but I got an error
message: current directory is not within an open checkout
But, the –R option is listed in the help for the ls command.



The -R options does not work unless you also include the -r option to
specify a specific version for which you want the directory listing.

--
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 


___
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] Using fossil just for the wiki. Images and tables?

[Ross Berteig]

On 1/26/2016 6:41 AM, Tino Lange wrote:

[...] Fossil's Markdown support is via libdiscount [...]

[...] Oh, Fossil uses Discount. Thanks, [...]

libdiscount? Sure? Isn't that a special version of libsoldout?


Actually, it was derived from libsoldout by its author, Natacha Porté, 
and heavily tuned for fossil's internals. She said at the time that it 
essentially followed libsoldout, except for the deep changes need to 
replace her original buffer implementation with fossil's.


There's an extensive (internal) API for extension and customization, but 
that hasn't been exercised other than to add support for 
PHP-markdown-extra style tables, and to tweak link handling.


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/
+1 626 303 1602
___
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 link to other pages in the wiki, wiki-link syntax

[John Gabriele]

On Mon, Jan 25, 2016, at 04:49 PM, John Gabriele wrote:
> On Mon, Jan 25, 2016, at 04:40 PM, Richard Hipp wrote:
> > On 1/25/16, John Gabriele  wrote:
> > >>
> > >> It works on the Fossil self-hosting webpage:
> > >> https://www.fossil-scm.org/fossil/wiki?name=Sandbox
> > >
> > > No, the page that I'm trying to link to does already exist.
> > >
> > > I thought it might be because there were spaces in the name, but I tried
> > > it for a page with no spaces, and that doesn't work either. I also tried
> > > it with a [CamelCase] named page, but that doesn't work either.
> > >
> > 
> > And you are doing this using the Fossil wiki format?  Notice that it
> > does not work with Markdown, only with Fossil's native wiki format.
> 
> Ah. No, I was using markdown.
> 
> Ok. Thank you.


By the way, I think it would be very helpful if, when using Markdown,
the Fossil wiki had built-in syntax for linking to other pages in the
wiki. Many popular wikis (MediaWiki (Wikipedia), moinmoin, Usemod,
PmWiki, ikiwiki) use [[this style]] syntax.

-- John
___
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 link to other pages in the wiki, wiki-link syntax

[Warren Young]

On Jan 26, 2016, at 12:36 PM, John Gabriele  wrote:
> 
> I think it would be very helpful if, when using Markdown,
> the Fossil wiki had built-in syntax for linking to other pages in the
> wiki.

Agreed.

> Many popular wikis (MediaWiki (Wikipedia), moinmoin, Usemod,
> PmWiki, ikiwiki) use [[this style]] syntax.

I think you’re mixing two things that ought not be mixed.

Fossil Wiki syntax already supports this, as drh pointed out up-thread:

[Other Wiki Article|plus optional descriptive text]

When adding such a feature to the Fossil Markdown processor, it should be 
within the existing syntax, not by borrowing wiki syntax.

Currently, if you say something like this in Fossil Markdown:

[some descriptive text](Other Wiki Article)

you get broken HTML:

some descriptive text

The only trick required here is for Fossil’s Markdown formatter to realize that 
“Other Wiki Article” is an existing wiki article title and rewrite the URL 
appropriately.

There is an advantage to [[this syntax]] in wikis: it can point to articles 
that don’t exist yet, implicitly requesting someone to write that article.  I 
don’t see that Fossil should provide such a feature.  Fossil Wiki is intended 
for well-scoped wikis, not encyclopedia wikis, so there is no need for dangling 
links.
___
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 link to other pages in the wiki, wiki-link syntax

[John Gabriele]

On Tue, Jan 26, 2016, at 03:10 PM, Warren Young wrote:
> On Jan 26, 2016, at 12:36 PM, John Gabriele 
> wrote:
> > 
> > I think it would be very helpful if, when using Markdown,
> > the Fossil wiki had built-in syntax for linking to other pages in the
> > wiki.
> 
> Agreed.
> 
> > Many popular wikis (MediaWiki (Wikipedia), moinmoin, Usemod,
> > PmWiki, ikiwiki) use [[this style]] syntax.
> 
> I think you’re mixing two things that ought not be mixed.
> 
> Fossil Wiki syntax already supports this, as drh pointed out up-thread:
> 
> [Other Wiki Article|plus optional descriptive text]
> 
> When adding such a feature to the Fossil Markdown processor, it should be
> within the existing syntax, not by borrowing wiki syntax.

Ok. One (minor) drawback to [this style] is that it's something that
might come up in regular prose content, so you'd have to remember to
\[backslash escape] when you don't want it to form an intra-wiki link.

> Currently, if you say something like this in Fossil Markdown:
> 
> [some descriptive text](Other Wiki Article)
> 
> you get broken HTML:
> 
> some descriptive text
> 
> The only trick required here is for Fossil’s Markdown formatter to
> realize that “Other Wiki Article” is an existing wiki article title and
> rewrite the URL appropriately.

I see. You want to be able to have both of these link to the same wiki
page:

[fettuccine alfredo]
[you might like this](fettuccine alfredo)

That last line above doesn't look good to me; since this is markdown,
that thing in parens should be a url or path to an html file. I see this
as a drawback to re-using the [descriptive text](wiki page name) syntax
for intra-wiki-links.

Incidentally: Fossil's markdown --- and, I'm guessing, most markdowns
--- allow you to write [this] to indicate a link (rather thank having to
write `[this][]`), and it assumes that somewhere else you have a line
that looks like:

[this]: http://example.com
or
[this]: /wiki?name=mumble

so it knows where the link should point to. I find it quite handy, and
better looking without the trailing `[]`.

The gitit wiki uses Pandoc under the hood, and Markdown for markup
syntax, and it uses [this style]() for intra-wiki links. I like that
pretty well, and it doesn't interfere with the above-mentioned
[shorthand].

What do you think of `[descriptive text|wiki page name]()`?

> There is an advantage to [[this syntax]] in wikis: it can point to
> articles that don’t exist yet, implicitly requesting someone to write
> that article.  I don’t see that Fossil should provide such a feature. 
> Fossil Wiki is intended for well-scoped wikis, not encyclopedia wikis, so
> there is no need for dangling links.

Actually, I see that if I include a link to a non-existent page using
Fossil markdown, ex. [Moose](/wiki?name=Moos),
then save the wiki page, it actually does make a link for me to follow,
and I can click that link and be taken to a page, the content of which
is "Empty Page" (in italics). And I can then click the "Edit" link and
start editing it. So, as-is, it seems to already provide that
"autovivification" feature.

-- John
___
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 link to other pages in the wiki, wiki-link syntax

[Warren Young]

On Jan 26, 2016, at 2:06 PM, John Gabriele  wrote:
> 
> On Tue, Jan 26, 2016, at 03:10 PM, Warren Young wrote:
>> The only trick required here is for Fossil’s Markdown formatter to
>> realize that “Other Wiki Article” is an existing wiki article title and
>> rewrite the URL appropriately.
> 
> I see. You want to be able to have both of these link to the same wiki
> page:
> 
>[fettuccine alfredo]
>[you might like this](fettuccine alfredo)

Yes.

> That last line above doesn't look good to me; since this is markdown,
> that thing in parens should be a url or path to an html file.

It would be straightforward for Fossil to test whether the link text is a 
Fossil wiki article text before writing it literally into the HTML.  If it 
isn’t, it can simply fall back to its current HTML generation logic.

The only risk is that there’s a wiki article with that title, but you *don’t* 
want Fossil to make the link.

Do you see that as a significant risk?

While I’m thinking about it, Fossil should also auto-link artifact IDs and tag 
names when used as link targets, for the same reason:

See the [original bug report](f86d58fe11).

Here, f86d58fe11 is explicitly the link text.  If it matches a Fossil artifact 
ID, Fossil should auto-link it.

This design error was fixed in [the v5 branch](v5.0.0).

Same thing, only with a tag name instead of an artifact ID.

This design extends a partial fix already committed. ([f86d58fe11])

There is a tiny risk of ambiguity here, since the descriptive text and the link 
target are the same thing.  But, all that’s needed to resolve it is a clear 
precedence hierarchy.  I propose:

1. Try to treat it as a link reference.  (e.g. [foo] in a document that also 
contains [foo]: target)

2. Try to find a tag or branch with the same name.

3. Try to find a wiki article with the same name.

4. If it’s hexadecimal, try to treat it as an artifact ID.

5. Failing all that, do what it does now.

Your challenge: find a sane use case where the precedence rules above give 
surprising results.

You will notice that I have ordered the rules to give a controlled expansion of 
the search scope.  Rules 2 and 3 could swap, but rule 4 must certainly follow 
the other three, and rule 1 must be first.

> Incidentally: Fossil's markdown --- and, I'm guessing, most markdowns
> --- allow you to write [this] to indicate a link (rather thank having to
> write `[this][]`), and it assumes that somewhere else you have a line
> that looks like:
> 
>[this]: http://example.com
> or
>[this]: /wiki?name=mumble
> 
> so it knows where the link should point to. I find it quite handy, and
> better looking without the trailing `[]`.

The only risk there I see is that you may use a link tag that happens to have 
the same text as an existing Fossil wiki document.

That sounds like a clear case of “so don’t do that, then.”

> [gitit] uses [this style]() for intra-wiki links

I can live with that.  I just don’t see it as necessary protection.  It sounds 
like a solution in search of a problem.

> What do you think of `[descriptive text|wiki page name]()`?

That’s again trying to mix Fossil Wiki with Fossil Markdown.  Let Markdown be 
Markdown.

> [Fossil] seems to already provide that
> "autovivification" feature.

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