Re: [fossil-users] Markdown wiki relative links

Sure, a name like /wiki/a/b could be interpreted as /wiki?name=a/b, but it would still break relative paths. It's not enough for Fossil to understand that the / in a/b isn't a path separator; the browser would need to understand that as well. Linking to (c) would either go to /wiki/a/c or /c, but

Re: [fossil-users] Markdown wiki relative links

On Wed, Jul 4, 2018 at 11:37 PM Stephan Beal wrote: > i don't _think_ that you can use %2f in a path component and have it apply > different semantics than a slash. How would software know to differentiate > between the two? That would be similar to expecting a local file name of > a\/b to work.

Re: [fossil-users] Markdown wiki relative links

On 07/04/18 16:37, Stephan Beal wrote: i don't _think_ that you can use %2f in a path component and have it apply different semantics than a slash. How would software know to differentiate between the two? That would be similar to expecting a local file name of a\/b to work. (If it did work,

Re: [fossil-users] Markdown wiki relative links

i don't _think_ that you can use %2f in a path component and have it apply different semantics than a slash. How would software know to differentiate between the two? That would be similar to expecting a local file name of a\/b to work. (If it did work, it would cause no end of confusion.) -

Re: [fossil-users] Markdown wiki relative links

On 07/04/18 16:01, Stephan Beal wrote: Fwiw, a few years back i created a patch which caused generated wiki links to always emit wiki/x rather than name=x, but it was pointed out to me that wiki/x doesn't work when x contains a slash, which is a valid wiki page name character. Thus the

Re: [fossil-users] Markdown wiki relative links

Fwiw, a few years back i created a patch which caused generated wiki links to always emit wiki/x rather than name=x, but it was pointed out to me that wiki/x doesn't work when x contains a slash, which is a valid wiki page name character. Thus the portable approach is to use name=x. :/ -

[fossil-users] Markdown wiki relative links

To create a link in the Markdown wiki, the syntax is [like this](url). That's all well and good, but what precisely does url need to be for one page to link to another? In writing embedded documentation, I've gotten used to relative paths, so in order to link /doc/trunk/doc/foo.md to

Re: [fossil-users] Markdown in tickets

On 26-6-2018 22:05, Richard Hipp wrote: > On 6/26/18, Chad Perrin wrote: >> I see no Markdown formatting option for tickets when visiting the web UI >> via `fossil serve`: > > Go to /Admin/Tickets and edit the scripts you find there to provide > support for markdown. As the scripts already

Re: [fossil-users] Markdown in tickets

On 6/26/18, Chad Perrin wrote: > > I am running Fossil v2.5 here: > > $ fossil version > This is fossil version 2.5 [188a0e2904] 2018-02-07 18:48:14 UTC > > I see no Markdown formatting option for tickets when visiting the web UI > via `fossil serve`: Go to /Admin/Tickets and edit the

Re: [fossil-users] Markdown in tickets

On Tue, Jun 26, 2018 at 12:05:51PM -0400, Richard Hipp wrote: > On 6/26/18, Andy Goth wrote: > > Is there a reason why Fossil tickets don't allow markdown? The format > > options are wiki, HTML, plain text, and [links only]. > > Markdown as a formatting option can be added by configuration. >

Re: [fossil-users] Markdown in tickets

On 06/26/18 11:05, Richard Hipp wrote: On 6/26/18, Andy Goth wrote: Is there a reason why Fossil tickets don't allow markdown? The format options are wiki, HTML, plain text, and [links only]. Markdown as a formatting option can be added by configuration. I apologize, I was unclear. When

Re: [fossil-users] Markdown in tickets

On 6/26/18, Andy Goth wrote: > Is there a reason why Fossil tickets don't allow markdown? The format > options are wiki, HTML, plain text, and [links only]. Markdown as a formatting option can be added by configuration. Perhaps you are asking for Markdown support to be added to the default

[fossil-users] Markdown in tickets

Is there a reason why Fossil tickets don't allow markdown? The format options are wiki, HTML, plain text, and [links only]. -- Andy Goth | ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] markdown option missing in dropdown of tickets

On Dec 15, 2016, at 9:18 AM, Aldo Nicolas Bruno wrote: > > I see only: Wiki, HTML, plain-text and [links-only] That is a known-missing feature. I and others have wished for it here on the mailing list. All that’s needed is for someone to want it badly enough to write

[fossil-users] markdown option missing in dropdown of tickets

Hi, from the fossil web interface... if I try to create a new ticket from /tknew From the list of format options markdown is missing... not that I use markdown too much... ;) I see only: Wiki, HTML, plain-text and [links-only] Thank you -- Aldo Nicolas Bruno

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 30, 2015, at 2:27 AM, Stephan Beal wrote: > > On Sun, Aug 30, 2015 at 10:15 AM, Baptiste Daroussin > wrote: > > Number #1 is the inhability to run "external" hooks easily > > it's difficult to do portably system() is ANSI C. There

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 6:40 PM, Warren Young wrote: > On Aug 30, 2015, at 2:27 AM, Stephan Beal wrote: > > it opens up many more potential failure cases > > I don’t see what’s difficult about failing a transaction if a hook is > defined and the external

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

There are docs on --with-tcl and the commands it provides (see th1.md in the source tree). Also, with Tcl enabled the hooks work perfectly for sending mail and I've personally been doing so for several years on a repository of mine. Sent from my iPhone > On Aug 31, 2015, at 9:40 AM, Warren

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 10:46 AM, Stephan Beal wrote: > > The push fails because a remote hook disallows it. What then? The same thing that happens when you try to push to a read-only repo, or push while the Internet connection is down, or push to a repo you accidentally

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 10:59 AM, Joe Mistachkin wrote: > > > There are docs on --with-tcl and the commands it provides (see th1.md in the > source tree). Yes, I already saw that, via the web: http://fossil-scm.org/index.html/doc/tip/www/th1.md You have to admit, it’s

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 7:27 PM, Warren Young wrote: > > That becomes fossil's problem > > No, it’s the hook-writer’s problem. > > The hook-writer solves that in the normal way: log the problem so that a > human can figure out how to solve it, then retry the commit. > Hooks

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 11:39 AM, Stephan Beal wrote: > > Hooks are not just about emails, but about policy decisions. "Does this file > conform to XYZ." A failure at that level is unrecoverable without changing > the policy. I think we can agree that using hooks to

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 1:56 PM, Warren Young wrote: > On Aug 31, 2015, at 11:46 AM, Warren Young wrote: > > I think we can agree that using hooks to enforce, say, code formatting > rules is a bad idea. > > I did a bit of Googling, and this blog article

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

2015-08-30 4:35 GMT+02:00 Stephan Beal sgb...@googlemail.com: On Sun, Aug 30, 2015 at 4:27 AM, Warren Young w...@etr-usa.com wrote: On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: the number 2 major complaints I heard from user Really? What’s #1 and

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Sun, Aug 30, 2015 at 10:15 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Number #1 is the inhability to run external hooks easily, like execute this script each time a sync is done, for before checking in, run this scripts. (personnally I can live with that) Management

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

Good support for sending email would be wonderful. We are getting along by running rss2email, far from ideal but adequate. On Sun, Aug 30, 2015, 1:55 AM Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2015-08-30 10:27 GMT+02:00 Stephan Beal sgb...@googlemail.com: On Sun, Aug 30, 2015

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Sun, Aug 30, 2015 at 4:27 AM, Warren Young w...@etr-usa.com wrote: On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: the number 2 major complaints I heard from user Really? What’s #1 and #3? :) +1 In some 20 years (as of this coming winter) of

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 29, 2015, at 8:35 PM, Stephan Beal sgb...@googlemail.com wrote: i can count on one hand the number of times i've seen commit messages (in project i work on/contribute to) which span more than two sentences. Well, you may have noticed that I can be verbose. :) Also, I think the

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 29, 2015, at 8:58 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: the number 2 major complaints I heard from user Really? What’s #1 and #3? :) I find that setting the “block formatting” option in Admin/Settings/Timeline solves most of my problems in this area. I don’t

Re: [fossil-users] Markdown

On 5/27/2014 22:58, Scott Robison wrote: The best I can come up with for a link to a wiki page (from another wiki page) is something like [Page](wiki?name=Page) which really seems kinda ugly You probably want this syntax: [Page][1] later, typically at end of doc... [1]:

Re: [fossil-users] Markdown

On Wed, May 28, 2014 at 12:05 PM, Warren Young war...@etr-usa.com wrote: On 5/27/2014 22:58, Scott Robison wrote: The best I can come up with for a link to a wiki page (from another wiki page) is something like [Page](wiki?name=Page) which really seems kinda ugly You probably want this

Re: [fossil-users] Markdown

On May 28, 2014 2:31 PM, Warren Young war...@etr-usa.com wrote: {deleted stuff} The attached Fossil repo also contains a copy of the official Markdown documentation. It was included in the test suite, so I linked to it from the repo's wiki, rather than remove it. Thanks very much for the

Re: [fossil-users] Markdown rules for Fossil Wiki

On Tue, 13 May 2014 11:49:32 -0700 Gerald Gutierrez gerald.gutier...@gmail.com wrote: I can use the [thename](target_link) markdown style, but that is a generic link and I seem to have to specify the full link and not just the wiki page name. I use [Page name](wiki?name=Page name) to

[fossil-users] Markdown rules for Fossil Wiki

I understand from the wiki formatting rules page that links can be created via [mylink], but this doesn't work if I use markdown. I can use the [thename](target_link) markdown style, but that is a generic link and I seem to have to specify the full link and not just the wiki page name. Is there a

[fossil-users] markdown embedded docs

Hello, no question, just the urge to vent my enthousiasm (about 1/2 year too late perhaps): this weekend was the 1st time I looked at Markdown in generel as a quick markup-language, and I like it very much. Fossil integration works very nicely - thank you for the effort, all involved. Michai

Re: [fossil-users] Markdown

On Sun, 5 Jan 2014 01:05:57 -0600 Jonathan Otsuka djg...@gmail.com wrote: You can use the as a starting guide: http://daringfireball.net/projects/markdown/ Thanks. I know about that but wonder about fossil's implementation. Some more details? Sincerely, Gour -- The humble sages, by

Re: [fossil-users] Markdown

Hello, on Sunday 05 January 2014 at 13:06, Gour wrote: On Sun, 5 Jan 2014 01:05:57 -0600 Jonathan Otsuka djg...@gmail.com wrote: You can use the as a starting guide: http://daringfireball.net/projects/markdown/ Thanks. I know about that but wonder about fossil's implementation. Some

Re: [fossil-users] Markdown

On Sun, 5 Jan 2014 14:23:34 +0100 Natacha Porté nata...@instinctive.eu wrote: Hiya Natacha, I'm the one to blame for fossil's implementation, and what ended up in trunk implements only official markdown, with PHP-markdown-extra-styled tables as only extension. Why blame? You have to be

Re: [fossil-users] Markdown

On Wed, 24 Jul 2013 10:46:01 -0500 djg...@gmail.com wrote: Didn't read the change notes for 1.26 until a couple days ago. I just noticed that markdown is now turned on by default this is awesome! I'ts beginning of New Year and another opportunity to re-evaluate Fossil...having Markdown I very

Re: [fossil-users] Markdown

I was caught off guard since I saw my email your reply. You can use the as a starting guide: http://daringfireball.net/projects/markdown/ Jonathan Otsuka On Jan 4, 2014, at 11:10 PM, Gour g...@atmarama.net wrote: On Wed, 24 Jul 2013 10:46:01 -0500 djg...@gmail.com wrote: Didn't read

Re: [fossil-users] Markdown

El 29/05/2013 06:28, Jonathan Otsuka djg...@gmail.com escribió: Downloads are not compiled with --markdown (its still experimental) you will need to checkout and compile fossil with --markdown yourself. Beware that --mardown is not a configure option anymore, in trunk, so it will be enabled by

[fossil-users] Markdown

Do the default (downloadable) versions of Fossil not have Markdown support enabled, or am I doing something wrong? My browser keeps telling me open or save this unknown file type. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list

Re: [fossil-users] Markdown

Downloads are not compiled with --markdown (its still experimental) you will need to checkout and compile fossil with --markdown yourself. Jonathan Otsuka On May 28, 2013, at 10:29 PM, Doug Franklin nutdriverle...@comcast.net wrote: Do the default (downloadable) versions of Fossil not have

[fossil-users] Markdown question

So I converted all the embedded documentation to markdown and on a, cursory, inspection it looks the same. I found one peculiar thing which is reported to Natacha. I think I like it. There are extensions to markdown syntax. but I'm not sure how they can be used. example centertable border=1

Re: [fossil-users] Markdown engine integrated into fossil

On 2012-07-09 15:41, Richard Hipp wrote: On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com [6] wrote: 2012/6/7 Richard Hipp d...@sqlite.org [1]: My priority is to get WYSIWYG wiki editing going, at which point the underlying wiki formatting language becomes

Re: [fossil-users] Markdown engine integrated into fossil

2012/6/7 Richard Hipp d...@sqlite.org: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on

Re: [fossil-users] Markdown engine integrated into fossil

On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2012/6/7 Richard Hipp d...@sqlite.org: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ?

Re: [fossil-users] Markdown engine integrated into fossil

2012/7/9 Richard Hipp d...@sqlite.org: On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2012/6/7 Richard Hipp d...@sqlite.org: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on

Re: [fossil-users] Markdown engine integrated into fossil

On Mon, Jul 9, 2012 at 3:41 PM, Richard Hipp d...@sqlite.org wrote: Yeah. Unfortunately, no actual code writing took place at the code sprint. Though lots of cool ideas were exchanged and developed! i think this particular one probably got forgotten because none of those present are among

Re: [fossil-users] Markdown engine integrated into fossil

Hello, on Thursday 07 June 2012 at 12:14, Richard Hipp wrote: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil

Re: [fossil-users] Markdown engine integrated into fossil

On Fri, Jun 8, 2012 at 3:30 AM, Natacha Porté nata...@instinctive.euwrote: Hello, on Thursday 07 June 2012 at 12:14, Richard Hipp wrote: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review

Re: [fossil-users] Markdown engine integrated into fossil

Is there any status on this? rejected ? still under review ? regards, Bapt ___ 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] Markdown engine integrated into fossil

On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! regards, Bapt

Re: [fossil-users] Markdown engine integrated into fossil

On Thu, May 24, 2012 at 1:51 AM, Natacha Porté nata...@instinctive.eu wrote: If you don't mind, I'd rather have it not named at all. Due to how it's (still) heavily loaded with negative emotions, I would like not having to interact with the original project or its repository. And a name

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 30, 2012 at 1:24 PM, Ron Wilson ronw.m...@gmail.com wrote: On Thu, May 24, 2012 at 1:51 AM, Natacha Porté nata...@instinctive.eu wrote: If you don't mind, I'd rather have it not named at all. Due to how it's (still) heavily loaded with negative emotions, I would like not having

Re: [fossil-users] Markdown engine integrated into fossil

Hello, on Wednesday 23 May 2012 at 15:26, Richard Hipp wrote: Nevertheless, though attached by fraud, the name is still inappropriate, and must be changed before being added to Fossil. Thanks to some invaluable help, I finally managed to get it done (I think). My markdown C library shall

Re: [fossil-users] Markdown engine integrated into fossil

On 05/30/2012 02:28 PM, Natacha Porté wrote: Hello, on Wednesday 23 May 2012 at 15:26, Richard Hipp wrote: Nevertheless, though attached by fraud, the name is still inappropriate, and must be changed before being added to Fossil. Thanks to some invaluable help, I finally managed to get it

[fossil-users] Markdown engine integrated into fossil

Hello, stuff happens, and it turns out that now I have finished integrating my markdown library (libupskirt) into fossil. And I really mean integrating, that is using struct Blob as dynamic buffers and other idioms. I used it to translate *.mkd and *.markdown embedded docs in a similar way as

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 5:53 PM, Natacha Porté nata...@instinctive.euwrote: I used it to translate *.mkd and *.markdown embedded docs in a similar way as *.wiki are currently translated. FWIW (not that my opinion really matters)... The addition of a more common wiki parser into fossil has

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 11:53 AM, Natacha Porté nata...@instinctive.euwrote: Hello, stuff happens, and it turns out that now I have finished integrating my markdown library (libupskirt) into fossil. We appreciate your efforts on behalf of Fossil. However, let me be very clear that any

Re: [fossil-users] Markdown engine integrated into fossil

on Wednesday 23 May 2012 at 12:18, Richard Hipp wrote: Note that after reading this far, and observing our choice of library names, I have chosen to read no further in your post. Oblivion was such a nice place for me to be... All by apologies for having dared creep out it. pgp2vbVQ9SlGI.pgp

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 06:28:59PM +0200, Natacha Porté wrote: on Wednesday 23 May 2012 at 12:18, Richard Hipp wrote: Note that after reading this far, and observing our choice of library names, I have chosen to read no further in your post. Oblivion was such a nice place for me to be...

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 12:25 PM, BohwaZ boh...@bohwaz.net wrote: Le Wed, 23 May 2012 12:18:52 -0400, Richard Hipp d...@sqlite.org a écrit : We appreciate your efforts on behalf of Fossil. However, let me be very clear that any library with the name libupskirt has *zero* chance of ever

Re: [fossil-users] Markdown engine integrated into fossil

On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote: Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Do you mind explaining this bit please, Richard? TIA, -Martin

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 12:36 PM, Weber, Martin S martin.we...@nist.govwrote: On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote: Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Do you

Re: [fossil-users] Markdown engine integrated into fossil

On 2012-05-23 12:39 , Richard Hipp d...@sqlite.org wrote: On Wed, May 23, 2012 at 12:36 PM, Weber, Martin S martin.we...@nist.gov wrote: On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote: Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 12:41 PM, Weber, Martin S martin.we...@nist.govwrote: Not that bit. The bit about even if you rename it to something that is completely inoffensive, it will be difficult to rehabilitate the code. Why is that? The choice of library name suggests that the author does

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 6:39 PM, Richard Hipp d...@sqlite.org wrote: https://www.google.com/search?q=upskirt http://en.wikipedia.org/wiki/Upskirt FWIW, and in Natacha's defense: i'm a native US-English speaker, but i've been away from the States long enough (going on 15 years) that the U word

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 1:00 PM, Stephan Beal sgb...@googlemail.com wrote: FWIW, and in Natacha's defense: i'm a native US-English speaker, but i've been away from the States long enough (going on 15 years) that the U word entered my vocabulary for the first time today. It cannot be expected

Re: [fossil-users] Markdown engine integrated into fossil

The choice of library name suggests that the author does not have a keen eye for beauty, in which case the code is unlikely to be something I would care to work with. Maybe the name of the library just don't represent the same for the author as for you, different culture, etc; but this really

Re: [fossil-users] Markdown engine integrated into fossil

On Wed, May 23, 2012 at 1:31 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: This is to bad that this great library is just pushed out because of an unfortunate name which was chosen for a joke (with references, that apparently noone from the native english speaking world get)

Re: [fossil-users] Markdown engine integrated into fossil

on Wednesday 23 May 2012 at 15:26, Richard Hipp wrote: Therefore, I hereby publicly apologize to Natasha for accusing her of generating code that is less than beautiful, based solely on the name of the code. The code is once again a candidate for incorporation into Fossil. Thanks. At this