Re: [fossil-users] Unfortunately I still see blobs of text for commit messages

[The Tick]

Never mind. I think I was going down the wrong path with this approach. 
I still have problems with using markup in the commit msgs tho. I asked 
about that in another thread.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Quick Q on valid markup for commit msgs

[The Tick]

On 3/29/2017 2:36 PM, Richard Hipp wrote:


The default formatting for comments is Wiki markup.  You can change
this for each repo using the Admin/Timeline menu.



I ran a "fossil ui"

First I went to admin->timeline and checked "allow block markup"

I went to wiki->Formatting rules->Markdown wiki.

Using that info, I created a commit msg for a dummy file. When I go to 
the timeline and files views, the only formatting I see is for 
paragraphs. There is no bold, italic, bullet lists. No indented 
paragraphs. It did honor  tho.


Where are the rules and syntax for this "block markup"?

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. When I reached a point where I considered the project 
"done" for the time being, I tagged all the files with an ID. Or, if I 
did not care, I'd just leave the ,v files as is and do a 'co *,v' when I 
wanted to do a build. Actually, gmake did that for me.


I've not used another scm (not quite true, I'm sure I used one when I 
was still working but I couldn't tell which one; git, cvs, etc. were not 
invented yet I think). Perhaps my "rcs" thinking is obsolete.


___
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

[Ron W]

On Thu, Mar 30, 2017 at 7:32 AM, 
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] Unfortunately I still see blobs of text for commit messages

[The Tick]

I thought my problem with the commit messages looking like a big blob of 
text was fixed by adding:


/* THIS WORKS - Enable timeline comments to respect linefeeds. */
span.timelineComment {
  font-family: Consolas;
  white-space: pre;
}

to the css here: http://localhost:8080/setup_skinedit

Now I was poking around and looked at an individual file. The commit 
messages are again a blob. I don't know a lot about css but with the raw 
fossil html:



[3a33db7b7c]
part of check-in
[76d36a9fdd]
Support a fixed-width font in addition to the default proportional font
  Use Option.mono in Options.txt to specify a specific fixed-width font
  Add tags F,FB and FI
 (user:


I've googled to see if I could go back and edit the commit messages but 
the answers I saw were a definite "no".


Before I just throw the whole thing away and start over using that 
markup language, is there any way to salvage this?


PS. This is not years of work. I've just started learning to use fossil 
so there are only a few commits so far. In the past I had used RCS for 
my projects but fossil looked like it would be a good replacement.

___
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

[Stephan Beal]

On Fri, Mar 31, 2017 at 12:14 AM, Scott Robison 
wrote:

> "Okay, so 640K of RAM isn't enough memory, but 64K code points will
> definitely encode more characters than we'll ever possibly need. You
> have my word on it!"
>
> True story. ;)


He apparently didn't foresee 0x1F4A9 - the "pile of poo" glyph:

http://www.fileformat.info/info/unicode/char/1f4a9/index.htm

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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

[Scott Robison]

On Thu, Mar 30, 2017 at 3:17 PM, Ross Berteig  wrote:
> The large part of the world stuck with MS products can and should exert some
> pressure to get better compliance from MS with many standards, not just
> Unicode. They change at glacial speeds, but they do change. A good first
> step would be for them to develop and support a "proper" Unicode Locale and
> code page for their console window. Doing that right likely means following
> the examples and lessons learned from the Linux community which has been
> blazing that trail and found (and escaped) most of the dead ends. I think it
> has become clear that Unicode is here to stay, and UTF-8 is the best
> representation of it both at rest in files and on the wire in protocols.

I agree completely about MS doing things Better(TM), but when it comes
to complaints or observations about their Unicode compliance, I laugh.
Not because they shouldn't change ... they should. But because they
were one of the *first* to support Unicode as designed and
standardized. UTF-8 was people blazing new trails because they didn't
want to do it in the blessed manner of the day. :) Unicode was a
simple straightforward two byte encoding back then. As Bill Gates
(then CEO of MS, MS being one of the earliest members of the Unicode
Consortium) said in 1991:

"Okay, so 640K of RAM isn't enough memory, but 64K code points will
definitely encode more characters than we'll ever possibly need. You
have my word on it!"

True story. ;)

-- 
Scott Robison
___
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

[Ross Berteig]

On 3/30/2017 12:35 PM, The Tick wrote:
Goodness! All I wanted was to have a comment contain a copyright 
character. Thanks to the people who were kind enough to take the time 
to respond to my questions. Now my commit messages are no longer a big 
blob of text, my .vimrc is modified, I've gotten fossil to stop 
complaining about my file, and I've learned some more about the 
intricacies of language support.


This list is one of the good ones, in my experience at least. You may 
not expect the thread you get, but usually you learn something about 
some fragment of reality you didn't expect to come up. And actual 
trolling is quite rare.


I never meant to start another editor war -- I thought that was over 
when the vi vs. emacs debate finally died years ago.


I didn't see a war here, just a bunch of people happy with the tools 
they use. Somehow I don't expect that to change soon.


I started using vi back when it was still named "vi" on early BSD 
systems, I'm happy to see it live on. I've used a commercial emacs 
inspired editor on the PC since DOS 3.1 (Lugaru Epsilon, and yes it is 
still supported by the same people). I've used DEC's TECO on a PDP-11, 
and ed on System III. (And punched cards and tape too, but I'm not that 
old, really!) I've survived IDEs too, and generally avoid them in favor 
of one or the other editor when I can. I may be unusual in not being 
willing to enlist in the editor wars. But I've found being willing to 
learn to use the tool that gets the job done is more likely to get the 
bills paid


Now its been suggested that I not only change my editor, but my 
keyboard, my programming language, my OS, and even to buy a new 
computer from a different manufacturer. While I suppose that might 
move the world closer to perfection, but I've been around long enough 
to know that will never happen.


Only in jest mixed with at least a little of platform bragging where 
some platforms make it easier to get things right.


The large part of the world stuck with MS products can and should exert 
some pressure to get better compliance from MS with many standards, not 
just Unicode. They change at glacial speeds, but they do change. A good 
first step would be for them to develop and support a "proper" Unicode 
Locale and code page for their console window. Doing that right likely 
means following the examples and lessons learned from the Linux 
community which has been blazing that trail and found (and escaped) most 
of the dead ends. I think it has become clear that Unicode is here to 
stay, and UTF-8 is the best representation of it both at rest in files 
and on the wire in protocols.


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/
+1 626 303 1602

___
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

[bch]

On Mar 30, 2017 12:35, "The Tick"  wrote:

Goodness! All I wanted was to have a comment contain a copyright character.
Thanks to the people who were kind enough to take the time to respond to my
questions. Now my commit messages are no longer a big blob of text, my
.vimrc is modified, I've gotten fossil to stop complaining about my file,
and I've learned some more about the intricacies of language support.

I never meant to start another editor war -- I thought that was over when
the vi vs. emacs debate finally died years ago.

Now its been suggested that I not only change my editor, but my keyboard,
my programming language, my OS, and even to buy a new computer from a
different manufacturer. While I suppose that might move the world closer to
perfection, but I've been around long enough to know that will never happen.

If I knew Mr. Sonnenberger personally, I might, out of consideration for an
acquaintance, reach out and ask how I might be able to spell his name
correctly. I would hope that his response would not be to insist that I
change editors, keyboard, etc. I also strongly suspect that he would feel
the same were the situation reversed.

Anyway, thanks again to those people who helped me. At this point I don't
find this thread going anywhere productive and I'm sort of sorry for
starting it.


It's interesting, and that's reason enough for it.


___
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

Re: [fossil-users] Couple of beginner questions

[The Tick]

Goodness! All I wanted was to have a comment contain a copyright 
character. Thanks to the people who were kind enough to take the time to 
respond to my questions. Now my commit messages are no longer a big blob 
of text, my .vimrc is modified, I've gotten fossil to stop complaining 
about my file, and I've learned some more about the intricacies of 
language support.


I never meant to start another editor war -- I thought that was over 
when the vi vs. emacs debate finally died years ago.


Now its been suggested that I not only change my editor, but my 
keyboard, my programming language, my OS, and even to buy a new computer 
from a different manufacturer. While I suppose that might move the world 
closer to perfection, but I've been around long enough to know that will 
never happen.


If I knew Mr. Sonnenberger personally, I might, out of consideration for 
an acquaintance, reach out and ask how I might be able to spell his name 
correctly. I would hope that his response would not be to insist that I 
change editors, keyboard, etc. I also strongly suspect that he would 
feel the same were the situation reversed.


Anyway, thanks again to those people who helped me. At this point I 
don't find this thread going anywhere productive and I'm sort of sorry 
for starting it.

___
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

[Joerg Sonnenberger]

On Thu, Mar 30, 2017 at 04:34:57PM +0200, Stephan Beal wrote:
> On Thu, Mar 30, 2017 at 4:30 PM, Warren Young  wrote:
> 
> > I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger
> > that we misspell their names simply because we refuse to give up
> > ASCII-centrism.
> >
> 
> OTOH, Joerg can't (IMO!) expect the majority to change keyboard mappings or
> use app/OS-specific voodoo to type his name.

It's more that I prefer a decent transliteration of my name over the
dumb approach used for most French names :)

Joerg
___
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

[Stephan Beal]

On Thu, Mar 30, 2017 at 5:00 PM, Warren Young  wrote:

> happens when you try to “cd ~/foo”.  I have to fix that every time I
> re-flash my Raspberry Pi with Raspbian, which defaults to expect a British
> English keyboard.  I suppose they think that’s fair revenge for the decades
> of  software from US developers that blindly assumes US-English keyboards.
> :)
>

a related funny anecdote: Suse Linux's primary admin tool front-end is
called "yast" (yet another setup tool). Every Suse system i've used
symlinks /usr/bin/zast to /usr/bin/yast because a primary difference
between German and US keyboards, aside from the addition of umlauted
characters on the right, is that 'z' and 'y' are swapped (Suse originated
in Germany).

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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

[Warren Young]

On Mar 29, 2017, at 2:47 PM, The Tick  wrote:
> 
> I also understand that a program script or, say, C source file can use the 
> utf-8 escape sequence to generate these characters when the program is run. 
> That is not possible in comments tho.

I put © in C++ comments all the time.  Every time I touch an old file that 
still uses (c), I update it.  All of the C++ compilers I use cope with this 
just fine.

UTF-8 isn’t an “escape sequence” system, by the way.  It’s interpreted by the 
terminal, but it isn’t part of the terminal protocol.  You tell your local 
terminal what character encoding you want it to use as part of the locale 
setting.

UTF-8 is no more an “escape sequence” than would be setting your terminal into 
EBCDIC mode or changing it from US-English to UK-English.

And if you think that latter has no effect on the keyboard input 
interpretation, try it, then see what happens when you try to “cd ~/foo”.  I 
have to fix that every time I re-flash my Raspberry Pi with Raspbian, which 
defaults to expect a British English keyboard.  I suppose they think that’s 
fair revenge for the decades of  software from US developers that blindly 
assumes US-English keyboards. :)
___
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

[Warren Young]

On Mar 30, 2017, at 8:38 AM, Warren Young  wrote:
> 
> On Mar 29, 2017, at 2:48 PM, The Tick  wrote:
>> 
>> I've been using vi for 40 years so that's not going to change.
> 
> I’ve “only” been using vi for about 37 years

Ooops, I can’t math, apparently.  “Only” 27-28 years.  I first used vi in 1989 
or 1990.
___
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

[Warren Young]

On Mar 30, 2017, at 8:34 AM, Stephan Beal  wrote:
> 
> On Thu, Mar 30, 2017 at 4:30 PM, Warren Young  wrote:
> I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger that 
> we misspell their names simply because we refuse to give up ASCII-centrism.
> 
> OTOH, Joerg can't (IMO!) expect the majority to change keyboard mappings or 
> use app/OS-specific voodoo to type his name.

That’s an OS usability issue, not a Unicode issue.

OS X solved this problem beautifully about the same time nvi and Vim were 
getting proper Unicode support.  From my US-English keyboard, I can type most 
common Western language accents and special characters — including £ — with 
some simple, easy to learn shortcuts.

(£ is Opt-3, and the em dashes are Shift-Opt-Hyphen.  Much nicer than Windows’ 
Alt-CODE scheme or Ubuntu’s even worse Ctrl-Shift-U-CODE scheme.)

For the less common characters, recent versions of OS X let you hold down the 
character nearest in form to what you mean to type (e.g. ‘o’ to get ó, ø, ö, 
etc.) to get a palette of variants on that character.  (If you have an iOS 
device, you may have seen this; OS X got it later.)

And if all else is lost, Cmd-Ctrl-Space brings up a palette with the same 
effect as Windows’ separate Character Map tool, but much easier to use.

Solutions are available, if you go looking.

(And I don’t mean “switch to macOS” here.  But you’d be welcome if you did.)
___
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

[Warren Young]

On Mar 29, 2017, at 2:48 PM, The Tick  wrote:
> 
> On 3/29/2017 3:25 PM, Warren Young wrote:
>> 
>> Any text editor or compiler that can’t cope with UTF-8 in 2017 is broken or 
>> can be ignored.
> 
> I've been using vi for 40 years so that's not going to change.

I’ve “only” been using vi for about 37 years, and I can type UTF-8 in my vi 
variant of choice just fine.  (Vim, which got Unicode support in 2001.)

> I certainly won't revert to something as horrendous as notepad or similar.

Ironically, Notepad does support Unicode, completely, even UTF-8:

https://imgur.com/a/AIFZA

You know it’s time to update when your text editor of choice is outdone by 
Notepad. :)

And no, I’m not endorsing Notepad.  One of the things on my long to-do list is 
a comparison of Windows 10 Notepad vs 1980 vi.  Even the Unicode issue aside, I 
think vi still wins, which is very sad.

>> It may be that your particular Tcl implementation is blindly assuming UTF-16 
>> because you’re running it on Windows.
> 
> Active State Tcl 8.6.4.

So bug ActiveState.  Stock Tcl does the right thing.

> As much as I wish unix had supplanted windows, it's an unfortunate de facto 
> standard for probably most people using desktop computers.

…or use WSL, or Cygwin.

___
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

[Stephan Beal]

On Thu, Mar 30, 2017 at 4:30 PM, Warren Young  wrote:

> I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger
> that we misspell their names simply because we refuse to give up
> ASCII-centrism.
>

OTOH, Joerg can't (IMO!) expect the majority to change keyboard mappings or
use app/OS-specific voodoo to type his name. When writing about British
currency i'll type "quid" before i'll spend the effort to go find a
copy/pasteable "pound" currency symbol.

(No offense intended to Joerg or any Brits in the group. ;)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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

[Warren Young]

On Mar 29, 2017, at 8:54 PM, Andy Bradford 
 wrote:
> 
> Thus said Warren Young on Wed, 29 Mar 2017 14:25:34 -0600:
> 
>> Any text  editor or  compiler that  can't cope with  UTF-8 in  2017 is
>> broken or can be ignored.
> 
> I rarely use any editor but nvi.  It doesn't support UTF-8.

According to Wikipedia, nvi got Unicode support in 2000.

Here on my Mac, “brew install nvi” gets me an nvi that does preserve UTF-8 
non-ASCII characters in files, and does let me insert them.  It claims to be 
version 1.81.6_3.

I did see one bobble in its handling of UTF-8, namely that I had to say ‘x’ 
twice to get it to delete a character that’s expressed as 2 bytes in UTF-8.

> Here is what
> utf16le.txt (from Fossil test directory) looks like to me:

That’s UTF-16, of course, so no surprise that nvi doesn’t do the right thing on 
a machine that is likely using either a UTF-8 or ISO-8859 locale setting.

A more useful test would be the W3C’s UTF-8 test file:

https://www.w3.org/2001/06/utf-8-test/UTF-8-demo.html

And if that fails, what is your LANG/LC_* variable set to?

> Do I need UTF-8?  Not really.

I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger that we 
misspell their names simply because we refuse to give up ASCII-centrism.

That was fine 15-20 years ago, when Unicode support on *ix platforms was still 
weak, but the first Bubble exposed most of these problems to the Many Eyeballs.

> I don't  even have  a keyboard  that can
> produce any UTF-8 characters

That’s purely a local issue.  Many people do have such keyboards, as I’ve 
demonstrated above.  And I’m not German.  Or Swedish.  Or Dutch.

And that’s just the consequences of missing out on one single accent.

> except those which overlap with ASCII, and
> even then, they are only 1 byte characters anyway.

You must mean ISO-8859 or or one of the Windows code pages, not ASCII.  
X3.4-1968 (the last version) is a 7-bit character set.  When expressed with 
8-bit code points, the meaning of values > 127 is not defined by ASCII.

And since ISO-8859 and the Windows code pages are all mutually incompatible 
except for their shared ASCII subset, we need Unicode.  We have lots of 
solutions to parts of the problem, but only Unicode solves the whole problem.
___
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] Fossil as an app server?

[Stephan Beal]

On Thu, Mar 30, 2017 at 12:23 PM, Paul Hammant  wrote:

> Nice achievement and great document on the JSON-api usage (and challenges
> you faced).  should be in markdown under source-control of course
> .
>

i agree, it "should" be in source control somewhere, but at the time it was
written (hand-in-hand with the code) that was deemed impractical - i needed
something i could edit live from non-development machines, as i often
edited it from machines other than my development box. Also, how best to
structure it in a wiki wasn't (and still isn't) clear (i wouldn't want it
packed up in a single long wiki page). At that time (late 2011), the only
wiki format fossil supported was its own, so markdown was not an option.


What was the name of your GoogleCode application?  They all got auto-moved
> to Github at some point.  I'm example orientated and can only really make
> leaps in understanding after looking a tight solutions :)
>

The gcode project was called 'wikiwym', a JS implementation of the gcode
wiki renderer (and i was one of the devs, so i "should" (might) still have
access to export it). However, i'm currently on long-term medical leave for
a back/nerve problem which partially disables my hands, and programming (or
any significant amount of typing, for that matter) is off-limits for me.
"One of these days," when i'm finally off medical leave, i'll get around to
fixing the links which import the external code. (i didn't even notice the
problem until yesterday.)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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] Fossil as an app server?

[ng0]

Paul Hammant transcribed 7.9K bytes:
> Are you sure there's not some no-frills way of getting at what used to be
> on Google code - e.g.
> https://code.google.com/archive/p/majesticuo/source/default/source ?

Well, it's still there on google.com. Surprisingly, as I thought they'd
just cut off connections at the date they targeted to shut down the
hosting. So you can still get the master, export to github, export to a
real git hosting, etc.
So
https://storage.googleapis.com/google-code-archive-source/v2/code.google.com/majesticuo/source-archive.zip
works and
https://code.google.com/export-to-github/export?project=majesticuo will
do the export to GitHub.
I just wanted to express under the assumption that it was already
offline, that sometime it can be difficult to find the "real" developers
repository with all these exports.
 
> On Thu, Mar 30, 2017 at 7:01 AM, ng0  wrote:
> 
> > Paul Hammant transcribed 4.8K bytes:
> > > Thanks Joe, thanks Stephen.
> > >
> > > Joe,
> > >
> > > Here's a "seatmap" app I made using CouchDB -
> > > http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
> > > with CORS enabled.  In the new Serverless era (
> > > https://martinfowler.com/articles/serverless.html - Mike is a buddy and
> > > former colleague of mine) things like CouchDB make perfectly usable
> > > "backend as a service" (BaaS) technologies. CouchDB allows anon access as
> > > well as logged in users (if so configured). In a sophisticated BaaS
> > > solution you'll probably want both and something fine grained to support
> > > that in the BaaS platform . which probably means some TH1 fu on the
> > > server side.
> > >
> > > Stephen,
> > >
> > > Nice achievement and great document on the JSON-api usage (and challenges
> > > you faced).  should be in markdown under source-control of course
> > > . What was the name of your GoogleCode application?  They all got
> > > auto-moved to Github at some point.  I'm example orientated and can only
> >
> > If only.. You had the option to export them at free will. That sadly
> > also means that in the cases where upstream developers went on hiatus
> > long enough to miss the shutdown we now have to search for the correct
> > upstream. libmp4v2 is one of the packages which makes our job as package
> > maintainers harder than it has to be.
> >
> > > really make leaps in understanding after looking a tight solutions :)
> > >
> > > - Paul
> > >
> > > On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
> > > wrote:
> > >
> > > >
> > > > If you compile Fossil with TH1 docs & hooks support and with Tcl
> > > > integration
> > > > enabled (like I compile it), it makes quite a reasonable server for
> > running
> > > > server-side scripts written in TH1/Tcl.
> > > >
> > > > --
> > > > Joe Mistachkin @ https://urn.to/r/mistachkin
> > > >
> > > > ___
> > > > 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
> >
> > ___
> > 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

___
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] Fossil as an app server?

[Paul Hammant]

Are you sure there's not some no-frills way of getting at what used to be
on Google code - e.g.
https://code.google.com/archive/p/majesticuo/source/default/source ?

On Thu, Mar 30, 2017 at 7:01 AM, ng0  wrote:

> Paul Hammant transcribed 4.8K bytes:
> > Thanks Joe, thanks Stephen.
> >
> > Joe,
> >
> > Here's a "seatmap" app I made using CouchDB -
> > http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
> > with CORS enabled.  In the new Serverless era (
> > https://martinfowler.com/articles/serverless.html - Mike is a buddy and
> > former colleague of mine) things like CouchDB make perfectly usable
> > "backend as a service" (BaaS) technologies. CouchDB allows anon access as
> > well as logged in users (if so configured). In a sophisticated BaaS
> > solution you'll probably want both and something fine grained to support
> > that in the BaaS platform . which probably means some TH1 fu on the
> > server side.
> >
> > Stephen,
> >
> > Nice achievement and great document on the JSON-api usage (and challenges
> > you faced).  should be in markdown under source-control of course
> > . What was the name of your GoogleCode application?  They all got
> > auto-moved to Github at some point.  I'm example orientated and can only
>
> If only.. You had the option to export them at free will. That sadly
> also means that in the cases where upstream developers went on hiatus
> long enough to miss the shutdown we now have to search for the correct
> upstream. libmp4v2 is one of the packages which makes our job as package
> maintainers harder than it has to be.
>
> > really make leaps in understanding after looking a tight solutions :)
> >
> > - Paul
> >
> > On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
> > wrote:
> >
> > >
> > > If you compile Fossil with TH1 docs & hooks support and with Tcl
> > > integration
> > > enabled (like I compile it), it makes quite a reasonable server for
> running
> > > server-side scripts written in TH1/Tcl.
> > >
> > > --
> > > Joe Mistachkin @ https://urn.to/r/mistachkin
> > >
> > > ___
> > > 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
>
> ___
> 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

Re: [fossil-users] Fossil as an app server?

[ng0]

Paul Hammant transcribed 4.8K bytes:
> Thanks Joe, thanks Stephen.
> 
> Joe,
> 
> Here's a "seatmap" app I made using CouchDB -
> http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
> with CORS enabled.  In the new Serverless era (
> https://martinfowler.com/articles/serverless.html - Mike is a buddy and
> former colleague of mine) things like CouchDB make perfectly usable
> "backend as a service" (BaaS) technologies. CouchDB allows anon access as
> well as logged in users (if so configured). In a sophisticated BaaS
> solution you'll probably want both and something fine grained to support
> that in the BaaS platform . which probably means some TH1 fu on the
> server side.
> 
> Stephen,
> 
> Nice achievement and great document on the JSON-api usage (and challenges
> you faced).  should be in markdown under source-control of course
> . What was the name of your GoogleCode application?  They all got
> auto-moved to Github at some point.  I'm example orientated and can only

If only.. You had the option to export them at free will. That sadly
also means that in the cases where upstream developers went on hiatus
long enough to miss the shutdown we now have to search for the correct
upstream. libmp4v2 is one of the packages which makes our job as package
maintainers harder than it has to be.

> really make leaps in understanding after looking a tight solutions :)
> 
> - Paul
> 
> On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
> wrote:
> 
> >
> > If you compile Fossil with TH1 docs & hooks support and with Tcl
> > integration
> > enabled (like I compile it), it makes quite a reasonable server for running
> > server-side scripts written in TH1/Tcl.
> >
> > --
> > Joe Mistachkin @ https://urn.to/r/mistachkin
> >
> > ___
> > 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

___
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] Fossil as an app server?

[Paul Hammant]

Thanks Joe, thanks Stephen.

Joe,

Here's a "seatmap" app I made using CouchDB -
http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works
with CORS enabled.  In the new Serverless era (
https://martinfowler.com/articles/serverless.html - Mike is a buddy and
former colleague of mine) things like CouchDB make perfectly usable
"backend as a service" (BaaS) technologies. CouchDB allows anon access as
well as logged in users (if so configured). In a sophisticated BaaS
solution you'll probably want both and something fine grained to support
that in the BaaS platform . which probably means some TH1 fu on the
server side.

Stephen,

Nice achievement and great document on the JSON-api usage (and challenges
you faced).  should be in markdown under source-control of course
. What was the name of your GoogleCode application?  They all got
auto-moved to Github at some point.  I'm example orientated and can only
really make leaps in understanding after looking a tight solutions :)

- Paul

On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin 
wrote:

>
> If you compile Fossil with TH1 docs & hooks support and with Tcl
> integration
> enabled (like I compile it), it makes quite a reasonable server for running
> server-side scripts written in TH1/Tcl.
>
> --
> Joe Mistachkin @ https://urn.to/r/mistachkin
>
> ___
> 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

Re: [fossil-users] "CGI" command and argc

[Florian Balmer]

Thanks for the link and the additional information. I have stumbled
upon a website with meticulous research about the unspecified shebang
behavior across a wide range of systems:

https://www.in-ulm.de/~mascheck/various/shebang/

There's indeed so many variants that it may not be a good idea to do
any modifications, here.

Of course the portable solution you mentioned is also fine
(performance is no issue on my stone-age shared host with just a
handful of personal repositories).

> 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.

http://fossil-scm.org/index.html/artifact/5105d4bc1b?ln=1834

--Florian
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users