Hello,
on Monday 30 July 2012 at 18:53, Stephan Beal wrote:
On Mon, Jul 30, 2012 at 10:41 AM, Natacha Porté nata...@instinctive.euwrote:
What remains to do:
+ review my code to ensure it meets fossil level of quality,
+ format it using fossil code style if needed,
+ any other
hello,
while the wiki has its entry in the fossil menu and is easy to find
the in-project documentation is not so obvious.
As a fossil user I have to read the manual to find the docs at all so
I would know. The manual is even quite well explained and almost
exhaustive.
However, if I were to
On 3 August 2012 11:23, Remigiusz Modrzejewski l...@maxnet.org.pl wrote:
On Jul 30, 2012, at 19:43 , Gautier DI FOLCO wrote:
2012/7/30 Bill Burdick bill.burd...@gmail.com
I'd like to see it included, as well!
I'd like it too, it will be easier for beginnes (like me!).
+1
Why markdown
On Aug 3, 2012, at 11:53 , Michal Suchanek wrote:
On 3 August 2012 11:23, Remigiusz Modrzejewski l...@maxnet.org.pl wrote:
+1
Why markdown and not one of the dozens of other wiki syntaxes?
Because markdown is a very popular one, used by github, and we have on board
the creator of a major
On 3 August 2012 12:07, Remigiusz Modrzejewski l...@maxnet.org.pl wrote:
On Aug 3, 2012, at 11:53 , Michal Suchanek wrote:
On 3 August 2012 11:23, Remigiusz Modrzejewski l...@maxnet.org.pl wrote:
+1
Why markdown and not one of the dozens of other wiki syntaxes?
Because markdown is a very
On Aug 3, 2012, at 12:19 , Michal Suchanek wrote:
Why markdown and not one of the dozens of other wiki syntaxes?
Because markdown is a very popular one, used by github, and we have on board
the creator of a major implementation (the one used by github, iirc).
Github has a cute logo but I
On 3 August 2012 12:26, Remigiusz Modrzejewski l...@maxnet.org.pl wrote:
Note there are JavaScript hacks for interpreting random wiki syntax so
you can have markdown interpreted without any direct support in
fossil.
Note there are good wiki engines out there, so no need for one in Fossil
Hello,
On Aug 3, 2012, at 11:53 , Michal Suchanek wrote:
Why markdown and not one of the dozens of other wiki syntaxes?
If I understand correctly this question wasn't addressed to me (as a
developer of the markdown-in-fossil code) but I'll try to contribute as
objectively as I can.
As a
On 3 August 2012 13:04, Natacha Porté nata...@instinctive.eu wrote:
Hello,
On Aug 3, 2012, at 11:53 , Michal Suchanek wrote:
Why markdown and not one of the dozens of other wiki syntaxes?
If I understand correctly this question wasn't addressed to me (as a
developer of the
Hello,
on Friday 03 August 2012 at 13:41, Michal Suchanek wrote:
On 3 August 2012 13:04, Natacha Porté nata...@instinctive.eu wrote:
As a user, the killer feature I see for markdown is that the
implementation exists (assuming my code is considered worthy, which is
quite a strong
On Fri, 3 Aug 2012 12:19:01 +0200
Michal Suchanek hramr...@gmail.com wrote:
Why markdown and not one of the dozens of other wiki syntaxes?
Because markdown is a very popular one, used by github, and we have
on board the creator of a major implementation (the one used by
github, iirc).
On Fri, Aug 3, 2012 at 11:48 AM, Michal Suchanek hramr...@gmail.com wrote:
huge snip
I also notice that while the CSS is customizable the HTML templates
are not. While this is not much of a problem for many projects in some
cases you would want to reorganize the page layout and/or add
On Fri, Aug 3, 2012 at 10:39 AM, Natacha Porté nata...@instinctive.euwrote:
No problem at all, I'm genuinely that patient. You could tell me nobody
would have time to look at it in 2012, and that would be fine with me
and I wouldn't send any other reminder before end of Januray 2013.
No, no,
On 3 August 2012 14:02, Natacha Porté nata...@instinctive.eu wrote:
Hello,
on Friday 03 August 2012 at 13:41, Michal Suchanek wrote:
I have strong objections about all such makups, none is perfect, all
have some annoyances, and they are all mutually incompatible.
Changing from one to
On Fri, Aug 3, 2012 at 12:19 PM, Michal Suchanek
...not to decide that but I have to agree. Once you let in markdown
people used to some other wiki syntax would argue they have needlessly
hard time and there would be no end to the stream of requests to
include yet another.
Hi Michal,
For
On Fri, Aug 3, 2012 at 2:56 PM, Michal Suchanek hramr...@gmail.com wrote:
And given somebody wrote a bbcode parser implementation, moin moin
parser implementation, and a half dozen others which will be allowed
in the fossil proper? Or is parser for any random format to be added?
And now i
On 3 August 2012 14:40, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
On Fri, 3 Aug 2012 12:19:01 +0200
Michal Suchanek hramr...@gmail.com wrote:
Why markdown and not one of the dozens of other wiki syntaxes?
Because markdown is a very popular one, used by github, and we have
On 3 August 2012 15:14, Remigiusz Modrzejewski l...@maxnet.org.pl wrote:
On Aug 3, 2012, at 14:57 , Stephan Beal wrote:
That said: in several of my fossil wikis i store Google Code format in the
wiki and render it client-side. My only point there is that it _is_
currently possible to
On Fri, 3 Aug 2012 15:06:45 +0200
Michal Suchanek hramr...@gmail.com wrote:
[...]
Stackoverflow and all the sites under its umbrella, and all the
sites using this engine, use (modified) markdown syntax [1], [2].
So again a somewhat slightly incompatible variation.
Correct, but I hardly
On Fri, 3 Aug 2012 14:02:38 +0200
Natacha Porté nata...@instinctive.eu wrote:
[...]
As I have said elsewhere, I'm not clever enough to imagine a solution
to introduce markdown into fossil's internal wiki. So I don't propose
it. I propose the extra embedded doc rendering, and the tools to
On 2012-08-03 11:53, Michal Suchanek wrote:
On 3 August 2012 11:23, Remigiusz Modrzejewski l...@maxnet.org.pl
wrote:
On Jul 30, 2012, at 19:43 , Gautier DI FOLCO wrote:
2012/7/30 Bill Burdick bill.burd...@gmail.com
I'd like to see it included, as well!
I'd like it too, it will be easier
On Fri, Aug 3, 2012 at 3:31 PM, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
I do understand the rationale for this approach; if I were the author
of Fossil (I'm incapable for this, but let's pretend I am, for the
moment) I'd probably pick the same approach during an early phase
On 3 August 2012 14:45, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Aug 3, 2012 at 11:48 AM, Michal Suchanek
I am not opposed to writing patches, and all these issues are quite
trivial but I am also aware that some patches are rotting in the
fossil tickets for years so I guess patches
On Fri, Aug 3, 2012 at 3:37 PM, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
Supposedly, Fossil's wiki page editor could provide the same pick list
the first time a page is created and then persist the chosen markup
syntax with the page entry itself in an appropriate table.
On Fri, Aug 3, 2012 at 3:47 PM, Stephan Beal sgb...@googlemail.com wrote:
These pages show 3 page-specified renderers in action (it uses a
name-extension mapper):
That's a lie - each page has a client-specified mime-type string. Click on
the editor button on these pages to see that.
On 3 August 2012 15:39, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Aug 3, 2012 at 3:22 PM, Michal Suchanek hramr...@gmail.com wrote:
When user HTML templates are implemented it will be possible to store
in the HTML template, presumably as part of configuration that can be
replicated
I'm having a weird problem serving up files in my /doc/tip/*. Some of the
files I access through that tree are source files. If the source files are
foo.m (Mercury source), fossil serves them up as MIME type text/html and it
gets displayed nicely in my browser (Firefox 14). If, however, the
On Fri, Aug 3, 2012 at 3:49 PM, Michal Suchanek hramr...@gmail.com wrote:
And how do you prevent malicious code import through synchronization?
The same way Windows does, of course: This app comes from god-only-knows
where. Do you want to run it?
;)
i have absolutely no idea, to be honest.
On 3 August 2012 15:54, Michael Richter ttmrich...@gmail.com wrote:
I'm having a weird problem serving up files in my /doc/tip/*. Some of the
files I access through that tree are source files. If the source files are
foo.m (Mercury source), fossil serves them up as MIME type text/html and it
On Fri, Aug 3, 2012 at 4:09 PM, Michal Suchanek hramr...@gmail.com wrote:
Because it does not know about .sno files.
Even reporting .m as text/html is bogus, obviously. The built-in table
shows it should be assigned text/plain, however.
At one point we tossed around the idea of adding a
On Fri, 3 Aug 2012 15:42:05 +0200
Stephan Beal sgb...@googlemail.com wrote:
I do understand the rationale for this approach; if I were the
author of Fossil (I'm incapable for this, but let's pretend I am,
for the moment) I'd probably pick the same approach during an early
phase of
On 3 August 2012 16:03, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Aug 3, 2012 at 3:49 PM, Michal Suchanek hramr...@gmail.com wrote:
And how do you prevent malicious code import through synchronization?
The same way Windows does, of course: This app comes from god-only-knows
where.
On Fri, Aug 3, 2012 at 4:30 PM, Michal Suchanek hramr...@gmail.com wrote:
I don't think that doing this is desirable. fossil status should be
fossil status.
And i agree entirely, i just posted the idea as a possible extension of the
custom commands (since this is an evolutionary process, and
On 3 August 2012 16:43, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Aug 3, 2012 at 4:30 PM, Michal Suchanek hramr...@gmail.com wrote:
I don't think that doing this is desirable. fossil status should be
fossil status.
And i agree entirely, i just posted the idea as a possible extension
On 2012-08-03 11:48, Michal Suchanek wrote:
hello,
while the wiki has its entry in the fossil menu and is easy to find
the in-project documentation is not so obvious.
As a fossil user I have to read the manual to find the docs at all so
I would know. The manual is even quite well explained and
On Fri, Aug 3, 2012 at 6:06 PM, Rene renew...@xs4all.nl wrote:
I'm not sure I follow you. again fossil has evolved this way.
You have a wonderful opportunity to take fossil system and build ...you
can set the the first page to anything you want. including index.html
He was referring to
Hi,
I have a private branch in my Tcl repository, and I wantto turn it into
a public branch that I can push to other repos (without pushing all my
private branches).
I've tried cancelling the 'private' tag (fossil tag cancel --raw) on the
first checkin of the branch, and on the latest, and
Michal Suchanek escribió:
Note there are JavaScript hacks for interpreting random wiki syntax so
you can have markdown interpreted without any direct support in
fossil.
Note there are good wiki engines out there, so no need for one in Fossil
too. But once we set the scope to include
Remigiusz Modrzejewski decía, en el mensaje Re: [fossil-users] The future of
markdown-in-fossil del Viernes, 03 de Agosto de 2012 07:26:27:
I've read the we'll have requests for all the markups in the world
argument many times. I can't remember anyone actually coming and asking for
*anything*
On Mon, Jul 30, 2012 at 10:41 AM, Natacha Porté nata...@instinctive.euwrote:
Currently the code is in a new branch off a clone of the official fossil
repository, available at
http://fossil.instinctive.eu/fossil-scm/timeline?r=markdown
Can you please update your fossil binary so that:
Hello,
on Friday 03 August 2012 at 19:11, Stephan Beal wrote:
On Mon, Jul 30, 2012 at 10:41 AM, Natacha Porté nata...@instinctive.euwrote:
Currently the code is in a new branch off a clone of the official fossil
repository, available at
On 2012-08-03 18:15, Stephan Beal wrote:
On Fri, Aug 3, 2012 at 6:06 PM, Rene renew...@xs4all.nl [1] wrote:
I'm not sure I follow you. again fossil has evolved this way. You
have a wonderful opportunity to take fossil system and build ...you
can set the the first page to anything you want.
42 matches
Mail list logo
