On 13/03/2017 15:50, Warren Young wrote:
A related wish that comes up here now and then is some kind of pretty-printer
support, so that common programming languages are colored nicely. Google’s
code-prettify JS library would work for this:
https://github.com/google/code-prettify
The comment style problem in attach.c is my fault - I'll provide a fix
(I'm far too used to the // style of comment :)
Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
You may need to extend the list of file extensions in ext/syn.js, for example to support js as an
extension for javascript I added
case "js":
t = "javascript";
break;
Dave
On 24/04/2016 18:04, Marko Käning wrote:
Hi Svyatoslav,
On 24.04.2016 14:31,
On 22/02/2016 06:28, jungle Boogie wrote:
Question: Would one expect server A to pick up the amended timeline
entry with the process above, or have I made a mistake with my
amending?
With autosync enabled, a synchronization happens prior to 'commit' and
'update' operations and after
On 05/01/2016 18:53, bch wrote:
How did we end up w/ dave.vines' completely untagged (no branch)
commits in the repository (or am I misreading what these are?) ?
ref:
/info/b208bf75777604dc
/timeline?u=dave.vines=2016-01-05+10%3A12%3A56=200
If I've messed this up, I do most humbly
On 05/01/2016 19:53, Richard Hipp wrote:
On 1/5/16, bch wrote:
What's incorrect, the documentation, or the implementation ?
Both, IIRC. I think you can convert a private branch to public by
cancelling the "private" tag. But I don't think that feature is
completely
On 04/01/2016 12:21, Stephan Beal wrote:
fossil att[achment] add ...
If it's a subcommand of "wiki" then the ability to use any unique short
form of it doesn't come for free (that only works for top-level commands).
:-?
I was unaware of this capability, and it makes sense to me. The
On 04/01/2016 14:07, John P. Rouillard wrote:
In message <568a7b26.7020...@zombi.eclipse.co.uk>,
David Vines writes:
On 04/01/2016 12:21, Stephan Beal wrote:
fossil att[achment] add ...
If it's a subcommand of "wiki" then the ability to use any unique short
form of it doesn
I now have a prototype for command line access to add attachments to
wiki pages and tech notes. I'd like to ask for any feedback on the
command itself before I polish my changes and put the changes up for review:
fossil wiki attachment add ?PAGENAME? FILENAME [-t|--technote DATETIME ]
On 16/12/2015 15:50, Ron W wrote:
Minor issue: While Fossil is inconsistent with this, the common
convention for "long options" is
--option
with 2 dashes. I haven't used the "-mimetype" option so I don't know if
it's a documentation error
or implementation oversight. In other Fossil
On 15/12/2015 09:55, Stephan Beal wrote:
Here's an encouraging anecdote for you: my first C work after 1995[1]
was implementing the wiki CLI commands Richard mentioned :). i concur
that the wiki commands would be the best starting point for adding Tech
Note (formerly "event") CLI support.
On 14/12/2015 15:20, Richard Hipp wrote:
I don't recall anybody ever writing such commands. There is nothing
technically difficult about doing so - I just don't think the need has
come up before.
The technote code is in the event.c source file. You can use the
"wiki" command implement in
something obvious?
David Vines
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
13 matches
Mail list logo