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
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
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
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 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
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 (
>
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
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”
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
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
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
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.
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
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
> >
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
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
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
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
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
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
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
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
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
23 matches
Mail list logo