[fossil-users] Issue in adding files
Hello, I ran into a small issue while adding two files to my repository, using a somewhat old version of fossil, so it may be that the problem has already been solved. Anyway, here is the scenario: fossil add filea fileb where filea is the name of an existing file and fileb contains a typo, so fossil is quite right in complaining about that one. However, the message is something like: ADDED: filea fileb not found ... This looks as if filea was added and fileb was not. So, subsequently I did: fossil add fileb_correct And then I did: fossil commit The list of files that were modified or added did NOT include filea! The fact that fileb was an invalid name nullified the addition of filea to the repository despite the message on the screen. As there was no indication at all of this, I thought filea was in fact added. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. ___ 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] Line numbers in file view (being greedy)
On Mon, 2 May 2011 13:42:46 -0400, Tomek Kott wrote:
Hi folks,
It seems that there is a capability to put in line numbers in file
view (using ln as part of the query string), and have them be
highlighted if specified in the url params (ln=10) or even a range
(ln=10-11). (see src/info.c [1])
Additionally, there [2] are [3] various [4] libraries [5] that can
highlight code, and there is even a helpful tutorial [6]on the
fossil
wiki to get those working. Great!
I want to put those two together so that if you click on the line
number, you automatically highlight that line, either using the
imported library or fossil. Has anyone attempted or succeeded at
this?
Tomek
Links:
--
[1]
http://fossil-scm.org/index.html/artifact?name=acda9c4b5b73eecddd8b14607f9d0a58d3793c68
[2] http://code.google.com/p/google-code-prettify/
[3] http://softwaremaniacs.org/soft/highlight/en/
[4] http://balupton.com/sandbox/jquery-syntaxhighlighter/demo/
[5] http://alexgorbatchev.com/SyntaxHighlighter/
[6]
http://www.fossil-scm.org/fossil/info/bde8ce985d52d3d76efafa37d8670a32fe16f79c#source-hilight
most simple is to adjust src/info.c to generate
pre tittle='win/version.c' alt='c' class='fossilcat'
span class='line' onclick='highlightline(this)'1 /*/span
span class='line' onclick='highlightline(this)'2 ** This C
program exists to do the job that AWK would do for the unix/span
/pre
Ttitle would help you to identify the file (but could be inferred by
get the contents of a
href=/index.html/finfo?name=win/version.cwin/version.c/a)
Alt would hint a the type of file (but could be inferred by get the
contents of a
href=/index.html/finfo?name=win/version.cwin/version.c/a)
class fossilcat to do CSS styling
off course this would require fossil to have a javascript function
highlightline which is unacceptable
but if this was changed to
span class='line'1 /*/span
you could do some dom magic and add the function to every span.line
element when the page loads.
if on page artiface then
for every span in blockquote.pre.span do
span.onclick=highlight(this)
However you could go the hard way :-)
if page is artifact
var el = document.getElementsByTagName('pre')
s = el.innerHTML
n = ''
for every line in s do
n += 'span onclick=highlight(this) '+line+'/span'
el.innerHTML = n
--
Rene
___
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] Line numbers in file view (being greedy)
On Tue, May 3, 2011 at 10:57 AM, Rene renew...@xs4all.nl wrote: Maybe I'm comming on to strong with unacceptable. I think it is a lot of work to support javascript. There are so many libraries each with good and bad. Which would you choose (jquary, yul, google). And you create a dependency. And what really is a lot of work to maintain the html pages in c-src. adding javascript complicates that even more. One src file can contain C-preprocessor, C language, HTML, TH1 and javascript Backward compatability (not breaking any code) is high on the list. I could see that going wrong with javascript. Couldn't agree more: dependencies are bad. Just wanted to get an idea of Fossil coding philosophy. I do think that namming your classes unique is a sensible thing. I have been mucking around with documentation and have generated documentation with docbook and lyx. for an docbook example see http://chiselapp.com/user/renez/repository/cvs2scm/doc/tip/doc/wiki/index.wiki You stand a risk that docbook generated class names confilct with fossil classnames. So generating a name space by prefixing classnames with fsl_ or fossil_ seems prudent. I also think that generating good class names for every output type e.g. fsl_wiki fsl_wikiedit fsl_artifact fsl_artifact_content fsl_artifact_type, is a good thing. I like the idea of prefixing 'documentation' class names with fsl_ thought I think the current batch of class names is fine (they're all fairly general). Tomek ___ 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] Line numbers in file view (being greedy)
On Tue, May 3, 2011 at 4:22 PM, Tomek Kott tkott.s...@gmail.com wrote: If HTML + CSS is ok, would there be much opposition if I were to (eventually) go through and add some classes to every html output I could find? What I'm shooting towards is something like WordPress, which puts a class for every imaginable parameter in the source code. Personally i would be all for that. It would make custom JS scripting of the repo simpler. Not that there would be that many classes for a fossil archive, but especially for the html we can't change (i.e., not the main menu) it would be nice to have more descriptors (say timeline, tickets, etc.). Amen. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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] Line numbers in file view (being greedy)
On Tue, May 3, 2011 at 7:07 PM, Tomek Kott tkott.s...@gmail.com wrote: with the cart getting ahead of the horse then, when and if I get around to doing these upgrades, what's the best way to submit them as patches, not having push capabilities on the fossil-scm site. First you need to fill out and mail in the disclaimer: http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.pdf http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html and then Richard will review/accept/deny it. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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] Line numbers in file view (being greedy)
On May 3, 2011, at 19:07 , Tomek Kott wrote: with the cart getting ahead of the horse then, when and if I get around to doing these upgrades, what's the best way to submit them as patches, not having push capabilities on the fossil-scm site. You give a link here to your personal copy, it's easier to cope with than patches. If people seem to like it, you put it as a branch on the official repo. Once all issues with it are resolved, DRH merges your stuff into trunk. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
