Re: [fossil-users] Couple of beginner questions
Warren, > Someone brought up TECO. I don’t expect anyone’s TECO implementation > to handle UTF-8, Hmm... I was going to say in jest that the DECUS swap tapes have a version written in C, were anyone nuts enough to take a crack at it. However Google reveals that it is closer at hand than I thought - someone has already ported it to Windows, Mac and Linux: https://github.com/blakemcbride/TECOC As someone who once wrote ad-hoc utilities as TECO macros, all I can say is: No. Shal -- Shal Farley Cheshire Engineering Corporation +1 626 303 1602 http://www.CheshireEng.com ___ 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] Couple of beginner questions
On Mar 31, 2017, at 1:42 PM, Andy Bradford wrote: > > You could have continued on the way you were > doing things. No need to change anything except tell your browser that > the content is not Unicode, but is instead ``Western'' or ISO-8895-1 or > something else. That only fixes one browser on one machine. The browser is just obeying what Fossil tells it in the Content Type header. The minimal fix, if someone wants their Fossil instance to serve ISO-8859 or similar over HTTP would be to modify the hard-coded “utf-8” declaration in src/cgi.c. Then browsers would understand how to render the content given. I don’t think that would let you have non-ASCII or non-UTF-8 characters in, say, checkin comments, though. To fix that, you’d probably have to make a whole lot in invasive changes to all the code that selects either UTF-8 or UTF-16 depending on the platform. Messy. The main thrust of my prior replies to this thread isn’t that people should throw away working and preferred tools, it’s that UTF-8 is a solved problem now, and has been solved for a long time. Someone brought up TECO. I don’t expect anyone’s TECO implementation to handle UTF-8, but that doesn’t count as “in 2017,” any more than watching Casablanca in 2017 would cause the movie to be set “in 2017.” But if you’re using a 20-year-old version of nvi, *that* problem has a solution. ___ 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] Couple of beginner questions
Thus said The Tick on Thu, 30 Mar 2017 14:35:22 -0500: > Goodness! All I wanted was to have a comment contain a copyright > character. Did you see my response? You could have continued on the way you were doing things. No need to change anything except tell your browser that the content is not Unicode, but is instead ``Western'' or ISO-8895-1 or something else. Andy -- TAI64 timestamp: 400058deb146 ___ 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] Unfortunately I still see blobs of text for commit messages
On Mar 30, 2017, at 9:32 PM, The Tick wrote: > > I don't know a lot about css but with the raw fossil html: > > that the CSS you gave refers to. ___ 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] Quick Q on valid markup for commit msgs
On Mar 30, 2017, at 11:34 PM, The Tick wrote: > > I went to admin->timeline and checked "allow block markup" > > I went to wiki->Formatting rules->Markdown wiki. According to an earlier post, it uses some variant on Fossil Wiki markup, not Markdown. It doesn’t seem to be complete. Attempts to get bullets here don’t work, for example. I suppose that’s what it means by “block markup.” That is, it is a subset of Fossil Wiki, not complete markup support. The more typical way to get paragraph breaks and such in timeline comments is to simply write your checkin comments with hard line breaks, then with this setting enabled, you can adjust your CSS to use style whitespace handling: https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg14620.html > I've used RCS in the past for my personal projects. I'm used to making a > simple list of the changes for a particular file and then doing a 'ci' for > that file. If you’re saying that you want to do ASCII-style formatting of comments, then I think the above solution will work for you. > When I reached a point where I considered the project "done" for the time > being, I tagged all the files with an ID. I have rarely found myself wanting when it comes to Fossil’s support for tagging. You can tag on commit with “fossil ci --tag”, or you can apply tags after the fact with either Fossil UI or “fossil tag”. > Perhaps my "rcs" thinking is obsolete. I never used RCS, but I did use CVS exclusively for years, which is built on the same concepts, and I’ve found the changes in each step from CVS -> Subversion -> Fossil to be quite sensible. You might have a harder time than I did with the transition, because you’re jumping so many steps. If you don’t see that that is a logical progression, Subversion was designed to replace CVS, fixing its faults while retaining its simplicity of use, and I find that Fossil shares most of Subversion’s usability sensibility while fixing Subversion’s weaknesses in the same way. About the only advantage Subversion holds over Fossil is the same one any centralized VCS has over a DVCS: sometimes you don’t want to clone the entire repository just to check out the code. For small repositories, it’s a difference without a distinction in practice, except that the clone-and-checkout process takes a few more steps. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Submit web forms by hitting enter
I noticed it's no longer possible to submit the form on top of the
timeline web view by hitting enter if one of the text input elements
("Max" or "Tag Filter") is focused in IE.
It seems that (all?) web browsers disable this logic for forms with
multiple text input elements lacking a "submit" element. The fix was
to add an "onchange" handler [0], but unfortunately this handler is
only triggered if the text input element lost focus, and not by
hitting enter in IE.
[0] http://www.fossil-scm.org/index.html/info/2929d5fced0909b5
Adding a hidden "submit" element would work, but might raise security
warnings in some web browsers. Conditional comments to make a hidden
"submit" element only visible for IE are no longer supported [1].
[1] https://msdn.microsoft.com/en-us/library/hh801214.aspx
I would like to suggest adding a new "onkeyup" handler to the text
input elements on the timeline web view to submit the form if enter is
pressed.
I'm sending a patch (as a Fossil bundle) directly to Mr. Hipp.
--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] "CGI" command and argc
> Therefore, I would expect: > env "-S perl -e 'print qq([$_] ) for (@ARGV)' a b c" > to output: > [a] [b] [c] Your example works on my FreeBSD server if the double quotes are omitted, and the command is run from a shell: env -S perl -e 'print qq([$_] ) for (@ARGV)' a b c ==> [a] [b] [c] But for a CGI script (named ./sample.cgi), it looks like this: #!/usr/bin/env -S perl -e 'print qq([$_] ) for (@ARGV)' a b c ==> [a] [b] [c] [./sample.cgi] The CGI script name is appended as an extra command line argument. So for the Fossil CGI command, it looks like this: #!/usr/bin/env -S ./fossil cgi fossil.config ==> no such file: cgi > If you have access to a compiler (gcc, clang) on your shared host, > I would recommend that solution. Unfortunately I don't, but for a short moment I was considering to use the custom libraries trick with clang or gcc ... ;-) --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] "CGI" command and argc
My two cents: Here are a few more examples for portable shebang expressions: http://perfec.to/shebang/ Not directly related to your problem, but the following shebang is usefule to detect and use different versions of awk (GNU or BSD): http://perfec.to/shebang/shebang.nawk.txt Another doubt about your linking to libs when installing fossil: I also have a shared hosting account (Linux, shell access). I simply downloaded the fossil source tarball, and compiled it from the command line. If you have access to a compiler (gcc, clang) on your shared host, I would recommend that solution. BR, Johan On Fri, Mar 31, 2017 at 5:32 AM, Ron W wrote: > On Thu, Mar 30, 2017 at 7:32 AM, fossil-scm.org> wrote: >> >> Date: Thu, 30 Mar 2017 11:15:37 +0200 >> From: Florian Balmer >> To: fossil-users@lists.fossil-scm.org >> Subject: Re: [fossil-users] "CGI" command and argc >> >> > So, I would expect both of the following to work: >> > #!/usr/bin/env -S fossil2/fossil cgi fossil.config >> > #!/user/bin/env -S fossil1/fossil cgi fossil.config >> >> No, they don't, as the CGI script name is appended as an extra >> argument to the shebang command line, causing Fossil to leave the path >> with the explicit "CGI" command. I was suggesting that Fossil keep >> going the explicit "CGI" command path even if there's more than three >> command line arguments. >> > > Unfortunately, I don't have a BSD box to test with. > > The BSD man page for env claims that the -S option tells env to split the > string following it by white space. > > Therefore, I would expect: > > env "-S perl -e 'print qq([$_] ) for (@ARGV)' a b c" > > to output: > > [a] [b] [c] > > There are examples of this behavior in the env man page (for BSD systems). > > But, as I said, I don't have a BSD box to test this on, > > Also, as best I can tell, only BSD's env has the -S option, so it is not a > portable solution. > > However, the following should be portable to most Unix/POSIX type systems: > > #!/bin/sh -c fossil cgi fossil.config > > > ___ > 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
