On May 27, 2014, at 7:55 PM, Joel Bruick j...@joelface.com wrote:
Richard Hipp wrote:
I think that's an HTTP thing. In a URL, spaces are encoded as +.
It's really an HTML form thing [1] that only applies to the query portion of
the URL. In the path component, we technically should be
On Tue, May 27, 2014 at 03:46:30PM -0400, Richard Hipp wrote:
On Tue, May 27, 2014 at 3:43 PM, Warren Young war...@etr-usa.com wrote:
Hi there,
I had a file called README-Visual-C++.txt in one of my repositories and
wanted to link to the tip version of it from an outside web page. I
On Wed, May 28, 2014 at 01:08:26AM +, Joe Prostko wrote:
On Tue, May 27, 2014 at 11:31 PM, Warren Young war...@etr-usa.com wrote:
Hi there,
1. You don't need to do regex matching on the URL here. This does the same
thing more efficiently and more clearly:
location
On Tue, May 27, 2014 at 02:19:09PM -0600, Andy Bradford wrote:
Thus said Richard Hipp on Tue, 27 May 2014 15:46:30 -0400:
Hi there,
Perhaps this should really be something like the following?
th1
html base href='$baseurl/[httpize $current_page]' /
/th1
This results in the following
Hello,
in fossil version 1.29 [87130593e4], '-R' switch is not mentioned in
'fossil help timeline' (but works fine).
If any more of this kind of issues come up, where shall I report them?
(I guess right here on the list.)
Michai
___
fossil-users
On Wed, May 28, 2014 at 5:37 PM, Michai Ramakers m.ramak...@gmail.comwrote:
in fossil version 1.29 [87130593e4], '-R' switch is not mentioned in
'fossil help timeline' (but works fine).
IIRC only a relative minority of commands don't support -R. As a rule of
thumb, anything which can work
On 28 May 2014 18:02, Stephan Beal sgb...@googlemail.com wrote:
On Wed, May 28, 2014 at 5:37 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
in fossil version 1.29 [87130593e4], '-R' switch is not mentioned in
'fossil help timeline' (but works fine).
IIRC only a relative minority of
On Wed, May 28, 2014 at 9:28 AM, Francis Daly fran...@daoine.org wrote:
Strictly, space is only encoded as + in the QUERY_STRING part of a URL.
So fossil is incorrect to convert + to space if it is before the first
? in the URL.
Interesting question, especially in the face of this case:
On 5/28/2014 10:14, Stephan Beal wrote:
So fossil is incorrect to convert + to space if it is before the first
? in the URL.
Interesting question, especially in the face of this case:
/wiki/foo
equivalent to ===
/wiki?name=foo
the first one has no QUERY_STRING but is, internally,
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]:
On Wed, May 28, 2014 at 7:51 PM, Warren Young war...@etr-usa.com wrote:
I don't see that there is ambiguity here at all. Doesn't your case happen
after URL parsing? URL escape decoding should happen *before* the URL is
parsed.
...If I have a wiki article called foo++ and want to access it
On Tue, May 27, 2014 at 8:34 AM, Abilio Marques amarq...@smartappsla.comwrote:
I was looking for an easier path. My set of tests can be run from command
line, and I really like shell scripting, so I was wondering, does fossil
has a trigger mechanism (on commit / push) run this command?
Do
On 5/28/2014 11:58, Stephan Beal wrote:
On Wed, May 28, 2014 at 7:51 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
I don't see that there is ambiguity here at all.
Ah, correct. The onus is on the one creating the link to do the escaping.
...which does mean it is
On Tue, May 27, 2014 at 5:00 PM, Petrica Clement Chiriac (Tica2)
petrica_chir...@fluxinternet.ro wrote:
Hi fossil-users,
I have simple JS app (build with GWT) and
these static files are in one folder ./jsout
You can get the raw content of any file stored in Fossil. For example:
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
On Wed, May 28, 2014 at 2:23 PM, Ron Wilson ronw.m...@gmail.com wrote:
On Tue, May 27, 2014 at 5:00 PM, Petrica Clement Chiriac (Tica2)
petrica_chir...@fluxinternet.ro wrote:
Hi fossil-users,
I have simple JS app (build with GWT) and
these static files are in one folder ./jsout
You
Thanks Ron,
Now I use nginx with conf like this:
server {
listen 8081;
server_name localhost;
location ~ ^/(gwt)/ {
rootC:/static/gwt;
expires 30d;
}
location / {
proxy_pass http://localhost:8080;
}
}
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
Warren Young wrote:
On May 27, 2014, at 7:55 PM, Joel Bruickj...@joelface.com wrote:
Richard Hipp wrote:
I think that's an HTTP thing. In a URL, spaces are encoded as +.
It's really an HTML form thing [1] that only applies to the query portion of the URL. In
the path component, we
19 matches
Mail list logo
