On Wed, 05 May 2010 16:32:29 +0200
>> "renework" == renework wrote:
renework> You get into trouble if it is contained in two wiki pages.
renework> Basically your are better of to write two markdown files and
renework> a Makefile. Which you can do in Darcs anyway.
Well, the more I think about
On Wed, 05 May 2010 16:53:27 +0200
>> "Twylite" == Twylite wrote:
Twylite> Plugins are of limited value. The repository becomes
Twylite> non-portable except to other Fossil installations with the
Twylite> same plugins. The end of that road is that everyone has to
Twylite> have all the markup
On 05/05/2010 10:53 AM, Twylite wrote:
> That said, if you really want Markdown, why don't you use something like
> Attacklab's Showdown (http://attacklab.net/showdown/), which is a
> Markdown implementation in JavaScript. Write your Wiki pages in plain
> text, include Showdown in the site header,
Hi,
On 09:59 PM, Gour wrote:
> Richard> There is exists no wiki markup that will make everybody
> Richard> happy. Any choice of wiki markup will leave some users
> Richard> grumbling that a different choice should have been made.
>
> I'm very well aware of it...and not knowledgable enough to k
On Wed, 5 May 2010 14:48:33 +0200, Gour wrote:
> On Wed, 05 May 2010 13:09:34 +0200
>>> "renework" == wrote:
>
> renework> I'm not clear for what you are going to use this for.
>
> I'll try to explain...
>
> renework> If for writing documentation, say a user manual. Then You
> renework> do
On Wed, 05 May 2010 13:09:34 +0200
>> "renework" == wrote:
renework> I'm not clear for what you are going to use this for.
I'll try to explain...
renework> If for writing documentation, say a user manual. Then You
renework> don't want to use fossil markup.
I'd like to use it for user manua
On Tue, 4 May 2010 15:54:18 +0200, Gour wrote:
> On Sun, 29 Nov 2009 12:07:06 -0500
>>> "Joshua" == wrote:
>
> Hello list,
[snip]
> Sincerely,
> Gour
I'm not clear for what you are going to use this for.
If for writing documentation, say a user manual. Then You don't want to
use fossil ma
On Tue, 4 May 2010 11:28:03 -0400
>> "Richard" == Richard Hipp wrote:
Richard> There is exists no wiki markup that will make everybody
Richard> happy. Any choice of wiki markup will leave some users
Richard> grumbling that a different choice should have been made.
I'm very well aware of it..
There is exists no wiki markup that will make everybody happy. Any choice
of wiki markup will leave some users grumbling that a different choice
should have been made.
I am personally very happy with the current wiki markup in Fossil. It meets
my needs very well. And even if someone where able
On Tue, 04 May 2010 10:39:22 -0400
>> "Joshua" == "Joshua Paine"wrote:
Joshua> If it's safe for your use case to turn on 'allow all html
Joshua> tags' (it's not safe if you let the general public create or
Joshua> edit tickets or wiki pages), then it's possible to implement
Joshua> Markdown fo
On 05/04/2010 09:54 AM, Gour wrote:
> wonder if there is still some live in the dead-horse of
> Markdown-as-fossil-wiki-format?
If it's safe for your use case to turn on 'allow all html tags' (it's
not safe if you let the general public create or edit tickets or wiki
pages), then it's possible t
On Sun, 29 Nov 2009 12:07:06 -0500
>> "Joshua" == wrote:
Hello list,
I know I may be beating the dead horse, but...
Joshua> I recognize that the improvement I and others are asking for
Joshua> may be non-trivial to implement, so while I think markdown (the
Joshua> particular format, not the
This is kind of funny. We have been debating this and the end result was
something to the effect of:
Yeah, it may be good, but who will program it?
It's already done and has been by Robert...
http://fossil-scm.org/index.html/timeline?t=creole
So, no dependencies, the code is written and Cr
I'm done with Fossil. Dropping this email so people don't fruitlessly reply
with more silly things.
On Sun, Dec 6, 2009 at 10:42 AM, Twylite wrote:
> Hi,
> > Try closer to 40. It may be a small number compared to the amount of
> > people who download Fossil but I believe it to be a representativ
Hi,
> Try closer to 40. It may be a small number compared to the amount of
> people who download Fossil but I believe it to be a representative number.
Your lack of understanding of negative response bias doesn't make it go
away. The majority have been silent on this issue, which doesn't tell
u
. That will be well into the future, as the topic is low on my
priority list.
Paul
From: fossil-users-boun...@lists.fossil-scm.org on behalf of Kurtis
Rainbolt-Greene
Sent: Sun 12/6/2009 10:57 AM
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-user
Will Duquette wrote:
> On Dec 5, 2009, at 3:23 AM, Daniel Clark wrote:
>
>> Joshua Paine wrote:
>>> On Fri, 2009-12-04 at 16:21 -0500, Daniel Clark wrote:
I'm missing why you wouldn't want to just implement this as code
(in C
or Javascript) that can translate from fossil wiki mark
On Sun, December 6, 2009 at 9:57 am, "Kurtis Rainbolt-Greene"
wrote:
> Try closer to 40. It may be a small number compared to the amount of people
> who download Fossil but I believe it to be a representative number.
>
> So yes, I'm calling this an "overwhelming majority". You can stick your head
Try closer to 40. It may be a small number compared to the amount of people
who download Fossil but I believe it to be a representative number.
So yes, I'm calling this an "overwhelming majority". You can stick your head
in the sand if you want but this is a pretty clear cut case of: Software is
l
On Sat, Dec 05, 2009 at 03:26:20PM -0500, Joshua Paine wrote:
> On Sat, 2009-12-05 at 11:46 -0800, Kurtis Rainbolt-Greene wrote:
> > If the feature were put in wouldn't it just be "people with old fossil
> > needing to update"?
>
> Yes, but...
>
> > I'm not sure I get why there's talk of "custom
On Sat, 2009-12-05 at 11:46 -0800, Kurtis Rainbolt-Greene wrote:
> If the feature were put in wouldn't it just be "people with old fossil
> needing to update"?
Yes, but...
> I'm not sure I get why there's talk of "custom fossil". This is a
> feature that a overwhelming majority want.
But it's a
I'm not sure I get why there's talk of "custom fossil". This is a feature
that a overwhelming majority want. If the feature were put in wouldn't it
just be "people with old fossil needing to update"?
On Sat, Dec 5, 2009 at 8:29 AM, Will Duquette wrote:
> On Dec 5, 2009, at 3:23 AM, Daniel Clark
On Dec 5, 2009, at 3:23 AM, Daniel Clark wrote:
> Joshua Paine wrote:
>> On Fri, 2009-12-04 at 16:21 -0500, Daniel Clark wrote:
>>> I'm missing why you wouldn't want to just implement this as code
>>> (in C
>>> or Javascript) that can translate from fossil wiki markup to
>>> markdown
>>> marku
Joshua Paine wrote:
> On Fri, 2009-12-04 at 16:21 -0500, Daniel Clark wrote:
>> I'm missing why you wouldn't want to just implement this as code (in C
>> or Javascript) that can translate from fossil wiki markup to markdown
>> markup (or whatever) and back.
>
> Doing it in C, if it's not integrate
On Fri, 2009-12-04 at 16:21 -0500, Daniel Clark wrote:
> I'm missing why you wouldn't want to just implement this as code (in C
> or Javascript) that can translate from fossil wiki markup to markdown
> markup (or whatever) and back.
Doing it in C, if it's not integrated into fossil core, means to
Hello Daniel,
> I'm missing why you wouldn't want to just implement this as code (in C
> or Javascript) that can translate from fossil wiki markup to markdown
> markup (or whatever) and back.
I think everyone here is interested in any markup implementation.
However, there's only one implementati
only those who dislike a format
> making assumptions as to what will happen.
>
> Jeremy
>
>
> From: Michael Richter
> Sent: Sunday, November 29, 2009 9:36 AM
> To: fossil-users@lists.fossil-scm.org
> Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
>
> I'm not going to bother stopping it, nor did I plan to. I was only
> showing
> you what the first 10m showed. Now?
>
> YES: 13
> NO: 3
>
> Any: 13
> Markdown: 3
> Creole: 1
Don't forget to add in the "Apathetic" or "Not sure"s. I'm so unsure
and apathetic, I don't remember which one I picked
I'm not going to bother stopping it, nor did I plan to. I was only showing
you what the first 10m showed. Now?
YES: 13
NO: 3
Any: 13
Markdown: 3
Creole: 1
On Sun, Nov 29, 2009 at 7:26 PM, Zed A. Shaw wrote:
> On Sun, Nov 29, 2009 at 04:19:02PM -0800, Kurtis Rainbolt-Greene wrote:
> > Q1: 4 YES
On Sun, Nov 29, 2009 at 04:19:02PM -0800, Kurtis Rainbolt-Greene wrote:
> Q1: 4 YES | 1 APATHETIC | 2 NO
> Q2: 4 WHATEVER WORKS | 2 HTML | 1 MARKDOWN
>
> PS I said this was specifically for my own curiosity, nothing more. Nice
> try, Zed.
Now now, you can't stop it when you want. To keep you hon
uitable library but the idea of a
> dependency
> scares everyone off so maybe we need a C source file that does the
> formatting and can be added too slowly, etc...
>
> Jeremy
>
> ------------------
> From: "Will Duquette"
> Sen
file that does the
formatting and can be added too slowly, etc...
Jeremy
--
From: "Will Duquette"
Sent: Sunday, November 29, 2009 9:15 PM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> Purely out of curiousit
Purely out of curiousity, I've glanced at Markdown and Creole, neither
of which I've used.
The problem with Markdown is that the format as defined simply isn't a
Wiki format. It's Wiki-like, but doesn't include the markup for links
to wiki pages. (There's some kind of linking, but it isn't
Just to be clear here since there has been some distracting arguments made:
There is no bikeshedding being done in this thread. As proof of point a
clear major majority do not care what color the bikeshed is (AKA, what
format to use) according to my poll.
I see two (major) sides of this conversati
Q1: 4 YES | 1 APATHETIC | 2 NO
Q2: 4 WHATEVER WORKS | 2 HTML | 1 MARKDOWN
PS I said this was specifically for my own curiosity, nothing more. Nice
try, Zed.
On Sun, Nov 29, 2009 at 3:51 PM, Zed A. Shaw wrote:
> On Sun, Nov 29, 2009 at 05:05:52PM -0600, Kurtis Rainbolt-Greene wrote:
>
> > Also,
On Sun, Nov 29, 2009 at 05:05:52PM -0600, Kurtis Rainbolt-Greene wrote:
> Also, Zed challenged me to prove that more people want any kind of (better)
> formatting than not:
>
> http://spreadsheets.google.com/viewform?formkey=dDBVZS1CM0M0akFiSlRtUE5CdUdKa2c6MA
>
> There's the form link. I am in n
gt; Fossil half the networking didn't even work on Windows.
>
> Jeremy
>
> --
> From: "Eric"
> Sent: Sunday, November 29, 2009 1:53 PM
> To:
> Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
>
> > From: "Jeremy Cowgar"
> > D
on Windows.
Jeremy
--
From: "Eric"
Sent: Sunday, November 29, 2009 1:53 PM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> From: "Jeremy Cowgar"
> Date: Sun, November 29, 2009 2:33 pm
>
>> For those that
From: "Jeremy Cowgar"
Date: Sun, November 29, 2009 2:33 pm
> For those that would like a real human formatting language it would be
worth
> a dependency.
Let's hear it for emotion and subjectivity!
More reasonably, what about this scenario:
You use Fossil to host a product
From: "Jeremy Cowgar"
Date: Sun, November 29, 2009 6:14 pm
> Did you read the follow ups?
>
> Jeremy
>
Yes, I did. And thanks for the clarifications. But I still don't want an
outside markup format grafted in to Fossil.
Eric
___
Did you read the follow ups?
Jeremy
--
From: "Eric"
Sent: Sunday, November 29, 2009 1:06 PM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> From: "Will Duquette"
> Date: Sun, November 29,
From: "Will Duquette"
Date: Sun, November 29, 2009 3:36 pm
> My two cents on all of this: regardless of what wiki syntax is used,
> the Fossil Wiki is a lousy way to do your software documentation. You
> write your software. Ultimately, you deliver your software. Then you
On Sun, 2009-11-29 at 08:51 -0800, Kurtis Rainbolt-Greene wrote:
> There is a divide on which markdown to use.
That's just it: there isn't! There are people who say we don't need a
markdown-esque formatting (or the minimal one already in fossil is
enough), and there are people who want a more comp
One thought that I had was to enable feeding wiki pages through a TCP
pipe so that they could be post-processed. That would enable storing
the pages in the wiki and rendering the wiki pages completely could be
done on any platform that supports a web server. Any wiki markup can be
supported a
The current way to format text blows.
There is a divide on which markdown to use.
Formatting makes reading text much much better.
Solution: Put the "top" three markdowns in a list. Use a random number
generator to pick the markdown language.
These large email conversations about markdown* are n
the
> development process for me. That's what I use the Fossil wiki for.
>
> Jeremy
>
> --
> From: "Will Duquette"
> Sent: Sunday, November 29, 2009 10:36 AM
> To:
> Subject: Re: [fossil-users] The case fo
From: "Jeremy Cowgar"
Sent: Sunday, November 29, 2009 11:01 AM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> I think you are misunderstanding what one should document in the fossil
> wiki.
I should have said what I put in the wiki. The wiki can be used
Duquette"
Sent: Sunday, November 29, 2009 10:36 AM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> My two cents on all of this: regardless of what wiki syntax is used,
> the Fossil Wiki is a lousy way to do your software documentation. You
> write your softw
d that there will be complaining and arguing to
> what format to choose and yet there has been none, only those who
> dislike a format making assumptions as to what will happen.
>
> Jeremy
>
> From: Michael Richter
> Sent: Sunday, November 29, 2009 9:36 AM
> To: fossil-user
started this thread.
Jeremy
--
From: "Zed A. Shaw"
Sent: Sunday, November 29, 2009 3:18 AM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> On Sat, Nov 28, 2009 at 11:34:09PM -0500, Joshua Paine wrote:
>&g
2009/11/29 Jeremy Cowgar
> It has been mentioned that there will be complaining and arguing to what
> format to choose and yet there has been none, only those who dislike a
> format *making assumptions* as to what will happen.
>
In other news, irony is my very favourite thing in the whole world.
nt: Sunday, November 29, 2009 9:36 AM
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
And with this you lose the interoperability of Fossil repositories.
Go team.
2009/11/29 Jeremy Cowgar
For those that would like a real human formatting l
I'm new to fossil, but if you need a different markup notation you can
check it in, along with the tool you need to process it.
Stephen
On Sunday, November 29, 2009, Kurtis Rainbolt-Greene
wrote:
> What about just having a few small plugins based on the markdown you want?
> Separate from the so
my
>
> --
> From: "Eric"
> Sent: Sunday, November 29, 2009 6:44 AM
> To:
> Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
>
> > The number of mails about this just proves that there is no right ch
fossil
Pretty easy, eh? Now, that's an over simplification but not by much.
Jeremy
--
From: "Eric"
Sent: Sunday, November 29, 2009 6:44 AM
To:
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
> The number of mai
emy
From: Michael Richter
Sent: Sunday, November 29, 2009 12:53 AM
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] The case for Markdown (yes, I rtfm)
Now to refute this. Keep in mind that if I had my 'druthers I'd have Markdown
as well while you read this.
Markd
The number of mails about this just proves that there is no right choice
for a new wiki markup. There are plenty of lightweight markup formats out
there (with their own enthusiastic followers) that haven't even been
mentioned here yet. If you want to do your project documentation a
particular way,
On Sun, Nov 29, 2009 at 5:34 AM, Joshua Paine wrote:
> There are only a small handful of popular wiki languages. Some
> implementations may have more or less features
+1 for google code wiki. :)
> Fossil itself is an example of looking at an already-crowded field and
> deciding to start over a
What about just having a few small plugins based on the markdown you want?
Separate from the source, not required, 1 plugin per formatting.
I don't care what's used, as long as it's not plain HTML. HTML is
mental-process retardant.
___
fossil-users maili
On Sat, Nov 28, 2009 at 11:34:09PM -0500, Joshua Paine wrote:
> On Sat, 2009-11-28 at 09:10 -0500, D. Richard Hipp wrote:
> > http://www.fossil-scm.org/fossil/wiki_rules
>
> I re-read this and noticed again the rationale for using the simple wiki
> rules included instead of an existing wiki langua
Now to refute this. Keep in mind that if I had my 'druthers I'd have
Markdown as well while you read this.
Markdown is a non-trivial format to parse and implement. The resulting code
is non-trivial in size as well. Not everybody universally accepts Markdown
as the format they want. Others want
On Sat, 2009-11-28 at 09:10 -0500, D. Richard Hipp wrote:
> http://www.fossil-scm.org/fossil/wiki_rules
I re-read this and noticed again the rationale for using the simple wiki
rules included instead of an existing wiki language. Given the
rationale, I think Markdown would be a better choice.
> 1
62 matches
Mail list logo
