Re: [fossil-users] Markdown in tickets
On 26-6-2018 22:05, Richard Hipp wrote:
> On 6/26/18, Chad Perrin wrote:
>> I see no Markdown formatting option for tickets when visiting the web UI
>> via `fossil serve`:
>
> Go to /Admin/Tickets and edit the scripts you find there to provide
> support for markdown. As the scripts already provide support for
> text/plain, text/html, and text/x-fossil-wiki, it should be apparent
> how to enhance them with an extra case for text/markdown.
Rendering the markdown is not quite that easy: all the existing options
use the "wiki" command, supplied with various incantations of the
tag. This doesn't appear to work for markdown.
Browsing the source code suggests there is a separate "markdown"
command, but that returns a list instead of actually rendering HTML,
like the wiki command does.
> Once you get this working, submit your changes for inclusion in the
> SQLite source tree.
After some spelunking in th_language.c, here’s what I got working to
render the markdown. Setting the proper mimetype and including it as an
option is left as an exercise for the reader.
(...)
if {$mutype eq "Markdown"} {
set md [string trimright $icomment]
set md [markdown $md]
set title [lindex $md 0]
set body [lindex $md 1]
html ""
html $title
html ""
html $body
} elseif {$mutype eq "Wiki"} {
(...)
I’d never written TH1 (or Tcl) before, so it can probably be improved
upon — most notably skipping the if the title is empty, which will
usually be the case in a ticket — but it seems to work OK.
--
Martijn Coppoolse
___
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] Joke about Spın̈al Tap
On 1-7-2015 3:40, Andy Goth wrote: However, Firefox's View Page Source feature does not. I have reported the bug here https://bugzilla.mozilla.org/show_bug.cgi?id=1179073 if anyone cares. So my little joke bore some fruit. Expect the bug to be closed: it's a font problem, not a Firefox one. Attached is a screenshot of the bug page's title in Google Chrome, after changing the title's font to 'Courier New'. Also, I've set the font for Firefox's Source view to 'Consolas', and that renders just fine. I haven’t tried Courier New on Mac or Linux, so I don't know if the issue is actually with the font, or with that font's rendering on Windows. -- Martijn Coppoolse ___ 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] Tab stop width
Stephan Beal schreef op 1-10-2014 19:48: More info, for those interested: http://www.w3schools.com/cssref/css3_pr_tab-size.asp apparently MSIE doesn't support it, but that table might simply be out of date. http://caniuse.com/#feat=css3-tabsize (CanIUse.com is usually better up to date than w3schools). -- Martijn Coppoolse ___ 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 DIFF --TK improvement
On 9-9-2014 8:28, Stephan Beal wrote: On Tue, Sep 9, 2014 at 8:25 AM, Tony Papadimitriou to...@acm.org mailto:to...@acm.org wrote: So, I would like to see this improvement, if possible: Once launched, the window to come in front of other windows, and its position to be always centered. FWIW: if this change is made, i'd request that it only be made on Windows. Unix WM's, with smart window placement, have always done the right thing for me in this regard. I actually have the same gripe (or the first half of it, anyway) on Mac OS X: the diff window always appears in the background. It would be really nice it that could be changed to foreground. The position is OK, however (though I always maximize it). -- Martijn Coppoolse ___ 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] how to push to chiselapp
On 7-8-2014 21:47, Will Parsons wrote: Andy Bradford wrote: Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -: Since I wasn't transmitting any sensitive data anyway, I answered yes, and then got: Error: not authorized to write Is there something wrong with the way I'm trying to authenticate? I see you used -B for HTTP_AUTH. I don't know, but does chiselap actually require HTTP_AUTH? At any rate, it won't be used unless required, however, I suspect you are missing the actual Fossil username somewhere and this is why Fossil is telling you that you are not authorized to write. Without a Fossil username, you get the default set of permissions which does not include the permission to write to the repository. I don't understand - what I represented by uname in the command *is* my chiselapp user name. To be clear, in my original local repository, I had a superuser name1. I created the chiselapp user as name2. Looking at the repository on chiselapp, I see two superusers, name1 and name2. name2 is what I represented by uname in the command I indicated. I assume I would have to supply my chiselapp name and password in the command line somehow, and if not by the -B option, then how? If both name1 and name2 are a superuser in the remote repo, then either of the following should work: fossil push https://na...@chiselapp.com/user/name2/repository/repo fossil push https://na...@chiselapp.com/user/name2/repository/repo (it does when I try it using my own hosted repo). You need to use the repository's user name and passwords, but Chisel adds your chisel user name and password as superuser to each and every repo you host with them anyway. Each repo can be accessed completely independently from your chiselapp username (except that it's part of the URL). When syncing with that repo, all the handling is done by Fossil, without intervention from Chisel. And Fossil will only look at the table of users present in the repo. HTH, -- Martijn Coppoolse ___ 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 vs git-based arrangements. code review and ticket export
On 5-8-2014 23:16, Warren Young wrote: On 7/26/2014 08:53, Eric Rubin-Smith wrote: * Code review! Fossil already provides all the code review I think any nimble team should need: RSS. 1. Set Fossil up as a server. [1] It's not even necessary to set Fossil up as a server; you can also run `fossil rss` (with relevant options) as a cron job (or a Scheduled Task :-P) and redirect the output to a file, or FTP it to some server. Your RSS reader can then read that file. [2] A quick glance at src/rss.c in the Fossil sources says this is a one-off oddball feature. It doesn't look like there are any other Fossil UI pages you can monitor via RSS. It would be handy to monitor wiki pages and tickets via RSS, for example. Tickets and wiki are supported, but via the same rss page, not by adding .rss to their respective pages: timeline.rss?y=ttkt=tkt_uuid timeline.rss?y=wwiki=name AFAIK, the page's parameters are identical to the CLI command's options: http://fossil-scm.org/fossil/help/rss HTH, -- Martijn Coppoolse ___ 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] G+ Fossil page?
On 19-3-2014 18:28, Ron Wilson wrote: Does fossil need a G+ page (or FB page, or AOL page, for that matter) where that type of thing can be posted? i, for one, wouldn't mind manning a G+ community. I don't think Fossil *needs* a Google+ page; but it's always an extra channel for Fossil users. (Or is there perhaps one i've missed so far? A cursory search revealed none.) There is also freecode.com http://freecode.com. Fossil has a listing there, but it is out of date. (http://freecode.com/projects/fossil) Does anybody know who the maintainer is? Freecode seems to have an API, and so do Google+ and Facebook. It should be feasible to write a script that parses the downloads page for new versions, and publish the new version (including what's new) to those pages, no? IMHO, it would be sufficient if such a script were to run once a day. That could make it easier to avoid forgetting a new release. -- Martijn Coppoolse ___ 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] ticket editing
On 15-3-2014 17:08, j. van den hoff wrote: Does not work for me. Clicking Edit in the ticket shows the Edit Ticket page where edit every ticket field (title, status, etc.) and also append a new comment/remark, but there seems to be no user interface for editing previous comments even if I submitted the ticket and I am the repo admin. This was possible some time ago IIRC. yes, same for me here: no way to edit previous comments, irrespective of privileges. This was changed when the `ticketchng` table was added. That table enables tracking all comments added to a ticket separately. Before, a ticket only had a single 'comments' field, and each new comment was appended to that field. Editing the comments was therefore easy; just a question of replacing the entire field, instead of appending to it. Now, it's become much more complex, because you'd need to replace a specific row in the ticketchng table. In itself, this wouldn't be that hard to do, but I've no idea how to process such an edit as a ticket-change artifact, which is what ultimately determines what ends up in the ticket and ticketchng tables. My guess is that the current default ticket-edit page doesn't allow editing separate comments either because it's impossible in this setup, or because it was too hard to do. (I've tried adjusting the ticket-edit page to allow this, because I wanted to restore the change preview possibility I had built in the old ticket-edit page, but gave up because it was taking too much time to solve). -- Martijn Coppoolse ___ 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] looking for interesting new fossil skins
Remigiusz Modrzejewski schreef op 11-2-2014 15:54: On 11 Feb 2014, at 15:42, Stephan Beal sgb...@googlemail.com wrote: i'm looking to clone someone's interesting fossil skin to snazz up my fossil repos a bit. Can any suggest a fossil repo with a nice skin? I once stole a skin I like, see here: http://dev.lrem.net/p2pvsim2/timeline I stole a similar one too; it was originally less 'advanced' (e.g. no blue background on mouseover of the menu items), which leads me to think that was the original. It was located at codingrobots.com, but that site no longer sports anything recognizable as fossil, though. And codingrobots.org redirects to a GitHub repo, so it looks as they've switched SCM. Another one I liked is this one: http://projects.depar.is/divers/ It's based on GitHub's style, as the one above is based on Google Code's style. :-) -- Martijn Coppoolse ___ 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] JS errors in IE8 on www.fossil-scm.org/fossil and www.sqlite.org/src
If you're changing that code anyway, could you please also take care of
the following change:
setTimeout(updateClock();,(60-d.getUTCSeconds())*1000);
to
setTimeout(updateClock,(60-d.getUTCSeconds())*1000);
(i.e. pass the function itself to setTimeout, instead of passing a
string to be evaluated).
Personally, I don't see the need for a clock on a web page, in general.
Most screens have a clock in a corner somewhere anyway.
On 01/21/2014 02:59 PM, Jan Nijtmans wrote:
The fossil web-sites mentioned have a little running clock
just below the Not logged in string (or the username for
people who are logged in). In IE8, this clock doesn't
work, and (when opening the debugger) gives javascript
errors. The reason is that Date.toISOString() is not
supported in IE8. Coolpit is the function updateClock():
function updateClock(){
var e = document.getElementById(clock);
if(e){
var d = new Date();
e.innerHTML=d.toISOString().replace(T, ).replace(/:\d\d\.\d+Z/,);
setTimeout(updateClock();,(60-d.getSeconds())*1000);
}
}
Here is a version of the same function which works
with IE8 and gives exactly the same output:
function updateClock(){
var e = document.getElementById(clock);
if(e){
var d = new Date();
function f(n) {
return n 10 ? '0' + n : n;
}
e.innerHTML = d.getUTCFullYear()+ '-' +
f(d.getUTCMonth() + 1) + '-' +
f(d.getUTCDate()) + ' ' +
f(d.getUTCHours()) + ':' +
f(d.getUTCMinutes());
setTimeout(updateClock();,(60-d.getUTCSeconds())*1000);
}
}
The standard styles included in Fossil don't have such a clock
(but it would be a nice addition... hint .)
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Martijn Coppoolse
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] CSS classes in tree-view?
Hi all, I really like the new tree-view feature. I set out to apply the same CSS tricks to differentiate files and directories, but it turns out that unlike the 'flat view', no CSS classes are included. Would it be possible to add those to each a link? -- Martijn Coppoolse ___ 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] ui cosmetics
j. van den hoff schreef op 30-10-2013 20:38:
on the other hand, I still believe that the average not-so-experienced
user will not want to dive into these sort of do-it-yourself
configuration and that a basic built-in solution would be good to have.
I agree that one of these options should be incorporated in the default
skin -- personally, I’d vote for adding the slash after the link:
li.dir:after {
content: '/';
}
Virtually every file manager I know somehow differentiates between files
and folders, by default. Appending a slash seems like a very simple way
to do so. Those who don’t want that distinction made, can easily choose
a different skin that doesn’t have it.
--
Martijn Coppoolse
___
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] ui cosmetics
Joel Bruick schreef op 30-10-2013 18:49: I'm stoked that someone else uses (or at least is aware of) this. I added it a few months back for my own selfish purposes. And, yeah, replacing the standard bullets with icons is exactly what I do. You can even add icons based on a file's extension (files with no extension get the class file, *.c files get file-c, *.txt files get file-txt, etc.). Yes, I noticed that. It does make it a tad more complex to add a generic icon for ‘files’: you have to specify a default icon for the list items, then override it for directories (and/or specific file types). Also, an alternative to adding the icons to your repository is to embed them in your stylesheet as data URIs. You can use a site like this to convert images: http://dataurl.net/#dataurlmaker Very good point, I’d forgotten about those. Icons usually aren’t too large, so they would likely fit in a data URI without it becoming prohibitively large. That’s why I prefer the current CSS class-based method to hard-coded inclusion of the trailing slash: it enables fairly extensive customization. :-) Agreed, that's why I added it! Although I suppose we can always argue on what the default style should be (at least until Richard says that the bike shed will be yellow and that's that). True. Does anybody know what the arguments were in favour of dropping the trailing slash? (Or roughly when the subject was discussed? I can't seem to find the right keywords). -- Martijn Coppoolse ___ 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] ui cosmetics
On 30-10-2013 12:15, j. van den hoff wrote:
On Wed, 30 Oct 2013 10:49:58 +0100, Richard Hipp d...@sqlite.org wrote:
== files ==
* it would be nice if directories where differentiated from files
(e.g. in
unix `ls -F' fashion) by trailing `/').
That can be done using CSS, nowadays. Since directories get a class of
dir, you can specify the following in the CSS to get a trailing slash:
li.dira:after {
content: '/';
}
Or, if you’d rather the slash not be part of the link:
li.dir:after {
content: '/';
}
It’s also possible to change the bullet into a circle, for example:
li.dir {
list-style-type: circle;
}
or even into a folder icon:
li.dir {
list-style-image:
url('http://icons.iconarchive.com/icons/deleket/sleek-xp-basic/16/Folder-icon.png');
}
(Of course, deeplinking like this is not recommended, so it would be
preferable to store the icon image in the repository, and refer to that).
That’s why I prefer the current CSS class-based method to hard-coded
inclusion of the trailing slash: it enables fairly extensive
customization. :-)
--
Martijn Coppoolse
___
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] Question about Source forge Fossil hosting
On 04/05/2013 09:12 AM, Jan Nijtmans wrote: Jeff, this is a very useful recipe that should be documented in the fossil documentation somewhere! Tried it, and only found one obvious minor typo: ssh -t myproject,myu...@shell.sourceforge.net create This should be: ssh -t myuser,myproj...@shell.sourceforge.net create A new fosclipse project is registered now, the related chiselapp repositories moved there and all other steps followed. So, I would expect the following url to lead to the core repository: http://fosclipse.sourceforge.net/projects/fosclipse/cgi-bin/repos/fosclipse-core I tried all kinds of variations for this URL as well, but I don't see anything. Any ideas how I can debug that? What did I do wrong? I haven't really looked into it, but http://fosclipse.sourceforge.net/cgi-bin/ returns a 403 error (Forbidden), which suggests that there _is_ a cgi-bin directory there all right, but that there's a permissions problem. (I suspect the /projects/fosclipse/ part of your URL are just server-side mapping for the 'fosclipse' subdomain). -- Martijn Coppoolse ___ 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] Chiselapp.com shutting down
On 03/29/2013 03:34 PM, Richard Hipp wrote: What if we were to extend Fossil itself so that it was capable of hosting multiple projects after the fashion of chiselapp? Fossil already has the feature of being able to host multiple projects using a single CGI script or single stand-alone server instance. (...) I currently have this set up on a server (http://fossil.2of4.net): one directory full of fossil repositories, and a (hand-crafted) index page listing all the repositories starting with a lowercase letter (as a poor man's version of public repositories). A script, running every 15 minutes, updates the index page if the max(mtime) of all the repository files is more recent than last time it ran. This works fine for hosting my own repositories, but not for providing a hosting platform for other people's repositories. I'm wondering if this capability can be extended in modest ways to provide a full-blown chiselapp replacement. The idea is that anybody who wants to host something like chiselapp simply has to obtain a low-cost internet host, copy the fossil executable into /usr/bin, create a single CGI script that is less than 10 lines long, and they are up and running. I'm still a little fuzzy on the details of how this would all work, though. Feature suggestions from readers and chiselapp users are appreciated. Chisel is set up so that your Chisel username becomes the admin-username for each of your hosted repositories. After logging in on Chisel, your personal dashboard page provides the following options: * a list of _your_ repositories (both public and private); * option to create a new repository, by either - creating a new repo, or - cloning an existing repo; * manually sync an existing repository; * remove a repository. * for each repository, you can edit the following properties: - your password - the remote URL for the repo - whether or not to periodically sync the repo - make the repo public or private Apart from changing your password and the remote URL, none of this is possible through Fossil's current web interface, AFAIK. One thing you could do, is add a CGI parameter to indicate one repository to rule them all, I mean a repo to provide the skin and store the users' information for the 'hosting' website. That way, perhaps you could re-use the current functionality for logging in, and generating skinned webpages. You'd still need a web interface listing all public repos; and also a list of public and private personal repos once a user has logged in. For that, you'd need a way to keep track of which repo belongs to which user, and whether it's public or private; then provide a web interface for editing these properties. You'd also need webpages for adding and removing repos from the server, and manually syncing a repo. -- Martijn Coppoolse ___ 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] Chiselapp.com shutting down
Op 29-3-2013 1:52, James Turner schreef: After a couple weeks of debate, I've decided to shut down Chiselapp.com. As the message on the homepage states, new account and repository creation has been disabled. Access to the website and repositories will remain open until May 1st 2013. Sad to see it go, I really liked its simplicity (both in usage and looks). If someone wanted to carry on the initiative, could you tell us approximately what the load would be, both in terms of bandwidth and storage space? A big thanks for everyone who's used the service, sadly I just don't have the time to maintain it and hosting it has started to become a burden. A big thank you for having hosted it all these years! The Chisel codebase, Flint, is available under the AGPLv3 license so if your interested now is probably the time to grab it. I’d already done that. :-) -- Martijn Coppoolse ___ 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] source viewing code
On 21-3-2013 19:48, Stephan Beal wrote: On Thu, Mar 21, 2013 at 7:18 PM, C. Thomas Stover wrote: i know that some users are using JavaScript to do diff highlighting, and don't see why the same couldn't be done for source code highlighting. There’s a description of how to implement client-side source code highlighting via the skin on the Cookbook page: http://www.fossil-scm.org/fossil/wiki?name=Cookbook#source-hilight It works really well; I’m using it in (almost) all my repositories (after tweaking the JS code a bit for optimization). One disadvantage is that you have to either include Alex’s syntax highlighter in your repository, or refer to the online version (which means you don’t get syntax highlighting when offline). Another is that you have to re-incorporate it every time you change skins. (Lastly as a side note, my apologies if this reply comes in crazy. (...) Seems perfectly normal to me - no craziness is evident. Same here. -- Martijn Coppoolse ___ 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] Whether or not this function examines the entire contents of the blob is officially unspecified.
On 20-3-2013 9:33, Jan Nijtmans wrote: 2013/3/20 Joe Mistachkin sql...@mistachkin.com: Actually, given the variety of possible text encodings, we know very little with absolute certainty. That's true. The fact that NUL is no valid character in any text encoding is an absolute certainty, but other assumptions cannot be made. Hm... NUL as a *character* might be invalid, NUL as a *byte* is perfectly valid, in UTF-16 at the least. Not certain which one you meant there. -- Martijn Coppoolse ___ 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] Side-by-side diff and non-English text
On 28-2-2013 9:33, Sergei Gavrikov wrote: For example http://chiselapp.com/user/sg/repository/pangrams/fdiff?v1=edab872a806e8d4cv2=6936fca46ff9d180 Left-side hunk: 30 Right-side hunks: 29, 81, 126, 137 Of course, unified diff has no such quirks. It looks like the side-by-side diff algorithm isn't UTF-8-aware, and looks at the text byte-for-byte. Consequently, it may detect a difference in the second byte of a multi-byte character, and start marking a difference right in the middle of that character. The result is an invalid single-byte character, followed by an HTML tag, followed by another (possibly also invalid) single-byte character. The same could happen at the end of a different sequence, of course, if the first byte is different but the second identical. If fossil knows that a text is UTF-8-encoded, the diff algorithm should ideally compare characters (which may span multiple bytes), and not bytes. Adding a setting indicating a default diff would perhaps be easier, in the short term. :-) -- Martijn Coppoolse ___ 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] RSS feeds
On 20-2-2013 19:53, Stephan Beal wrote: No objections were given, so here it is: http://fossil-scm.org/index.html/info/dbaf520910 Thanks again to David Given (he did the majority of the work). While writing a script that checks periodically if there's any new tickets, and sends out an e-mail to me by generating the relevant 'View Ticket' page; I happened to be poring over the config table of a fossil repository, and in there, I noticed the config item 'ticket-title-expr'. That is probably what should be used to get the ticket title in the info page: http://fossil-scm.org/index.html/artifact/9825d0cfe7?ln=1699-1701 I’d totally forgotten such a setting existed, but it can be configured on the tktsetup_timeline page. Note that this is *not* a priority issue, though! I’m happy with the functionality as it currently is -- so far, I haven’t seen a ticket configuration that had a different ticket-title-expr, nor can I really see the need to change it from the default, 'title'. :-) -- Martijn Coppoolse ___ 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 error when pushing
On 20-2-2013 22:59, Stephan Beal wrote: On Wed, Feb 20, 2013 at 10:44 PM, Arnel Legaspi wrote: Error: not authorized to writet: 0 received: 0 The not authorized to writet does not come from fossil: stephan@tiny:~/cvs/fossil/fossil/src$ grep writet *.c It looks like the 't' at the end of 'writet' stems from the word 'sent' that went with the 'received' that follows. It would appear that the 'sent: 0 received: 0' was written, followed by a carriage return WITHOUT linefeed, and then the error message was printed, overwriting the prior message (partially, in this case). Which is why grepping for 'writet' will not find anything. :-) (This is something I've seen happen several times already: error messages overwriting existing 'regular' output; perhaps it’s a Windows console issue). -- Martijn Coppoolse ___ 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 svn conversion gets confused if last svn checkin is on a branch
On 20-2-2013 22:34, Warren Young wrote: But before looking at it, I want to stress that I don't believe Fossil has lost any data, it's just that the default Files view shows the last branch I worked on, rather than the trunk as I expected. This sounds as if the 'Files' tab of your repository links to http://server/repo/dir?ci=tip whereas you expected it to link to http://server/repo/dir?ci=trunk 'tip' is an alias for the most recent check-in. If your most recent check-in was not in trunk, you won’t see trunk on that page. You can easily adjust that in the Admin/Header section of the web interface. -- Martijn Coppoolse ___ 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] Feature requests: fossil ui and server improvements
Op 20-2-2013 15:51, j. van den hoff schreef: On Wed, 20 Feb 2013 15:40:27 +0100, Richard Hipp d...@sqlite.org wrote: Interesting. I never thought to try that, but it does work. I did this: sudo apt-get install lynx fossil setting web-browser lynx fossil ui ... and it works! You don't see the timeline graph (of course) and the side-by-side diff display doesn't work, but a lot of things do work. ELinks actually has no problems with the side-by-side diff; even the colouring works (if you set $TERM=xterm-256colors before you launch elinks, that is). The CAPTCHA is perfectly readable, as well. well not quite, not for me: the timeline links are not recognized (neither by lynx, nor by links, nor by w3m, nor by elinks I have to login first, but after that ELinks shows all the links properly -- and they all work, too. Check-ins, tickets, branches, everything shows up as expected. (Haven't tried lynx or links as yet). Perhaps Fossil doesn't recognize ELink's user-agent string, and that's why you need to log in first? The only thing elinks doesn't show properly on my machine, is the timeline graph. Of course, if you're using a different skin, that relies heavily on javascript and CSS, the chance of problems will rise accordingly. (I've included a syntax highlighter for my code on the artifact pages, but sadly, that doesn't seem to work in elinks). -- Martijn Coppoolse ___ 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] RSS feeds
Op 18-2-2013 16:12, Stephan Beal schreef: i'll give them another once-over (i only briefly glanced over your merge) and try to get that done in the next day or two. If there are any objections, please voice them soon! Unfortunately, I haven't had time to check (busy with other stuff), but how does the info page react to a ticket table which doesn't have a title field -- or do we assume that's one field which won't be removed or renamed? That's the only potential issue I can see ATM. I agree that other improvements can be made later on. TODOs which come to mind: - add a hyperlink to the RSS on the ticket view page. - add the (whatever it's called) embedded RSS hint in the header. This probably requires adding the current ticket ID to the TH1 engine, and i can't say off-hand whether that requires any re-wiring or not. The ticket ID is known to the TH1 engine already, when rendering the pages for viewing or editing a ticket: $tkt_uuid You might have to move the initialization of those variables to a point before the header gets written; but I have no idea whether there's any dependencies between writing (or having written) the header and initializing the ticket variables. -- Martijn Coppoolse ___ 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] Poll: which markdown extensions in fossil?
Op 18-2-2013 13:48, Natacha Porté schreef: Hello, a while back it has been brought to my attention that markdown-in-fossil behaves differently than fossil wiki when an absolute path is entered as a URI. Fossil wiki prepends it with the repository path, making absolute relative to repository root. On the other hand, current markdown-in-fossil follows the original markdown in that whatever is provided as a link is dumped directly into the href attribute, making it absolute in the usual HTML meaning. A reasonable case can be made for fossil wiki behavior, since the repository root is a more meaningful reference for anything inside the repository than the HTML root. However porting such behavior to markdown-in-fossil would deviate from original markdown. This is not a bag thing in itself, but this is a really called an extension to markdown. My vote goes to Markdown-in-fossil treating rooted paths as Fossil itself does (i.e. prefixing the base path and repo to any 'rooted' link). It means that the same 'rooted' links can be used for Fossil serving only that repository, as well as Fossil serving a directory full of repositories. I currently have several projects where both need to work: the 'master' repository on the server (which is served as part of a directory), and the 'local' repository fired up with fossil ui. But then again, this is not the only link processing performed by fossil wiki. So if a case can be made for mangling absolute links, couldn't one be made for easier linking of artifacts or wiki pages? It could, but this would be less of a priority for me. I don't really mind having to write out the actual links — but then, I'm only using fossil with people that are familiar with URLs and their intricacies and idiosyncracies. This raises an even wider question: what set of extensions should be included in markdown-in-fossil? Apart from tables, which is already included, I've never really immersed myself in the difference between markdown dialects. The version I most often use is the variant encountered on stackoverflow.com and its sister sites, as described here: http://stackoverflow.com/editing-help Thanks again for implementing this! -- Martijn Coppoolse ___ 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] RSS feeds
On 11-2-2013 20:11, Stephan Beal wrote: If the RSS entry links back to the ticket instead of the change record then all entries in the feed will point to the same thing. That seems much less helpful than linking to the change record, IMO. Eh... yes, you’re right, of course. Hadn’t thought of that. X-D So, _if_ we want to make this more user-friendly, wouldn’t it suffice to add the ticket title (linking to the 'view ticket' page for that ticket) to the info page for a ticket change artifact? I note that the info page for a ticket changes already has a link to the view ticket page, but the link text is the ticket's full UUID, labeled 'UUID' — which will sound rather obscure to the average user, and perhaps a tad threatening to some... Again, I have no idea if it’s that simple -- where would you get the ticket title from, if that is not part of the changes? -- Martijn Coppoolse ___ 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] RSS feeds
On 12-2-2013 11:17, Stephan Beal wrote: http://fossil-scm.org/index.html/timeline?r=timeline-rss-ticket that branch contains David's patch, plus i've added the ticket's title to the linked-to change details page to address your last comment. Thanks a lot, Stephan! One question: as the 'title' field doesn’t start with 'tkt_', it *could* be removed from the ticket table. Does the `db_text` function handle SQL errors by returning its first parameter? If not, this code could be problematic in the case of an altered ticket table that does not have a 'ticket' field. (Personally, I don’t see why anyone would want to remove that field, but... it is possible.) In such a case, it would make the info page unusable for ticket change records. I can’t seem to find the definition of `db_text` (I haven’t got a clone of the Fossil repo here at work.) :-? -- Martijn Coppoolse ___ 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] RSS feeds
On 9-2-2013 10:58, Stephan Beal wrote: Thanks to the rss reader tip from Martin i can finally try this out. i like it :). The Firefox extension that does the same thing is here: https://addons.mozilla.org/en-us/firefox/addon/rss-icon-in-awesombar/ In IE, the feed icon sitting in the Command Bar (which is off by default). In Opera, it’s visible by default (IIRC). What parts (if any) are still missing? i still can't believe nobody proposed this feature a long time ago. Well, I was expecting the timeline.rss to accept the same (basic) options as the timeline page, but I noticed that the ?y=e parameter (the list of events) isn’t recognized, as yet. Since I haven’t really used events so far, I’m not too bothered. But it might come in handy some day... (I’m still trying to come up with an easy way to combine tags and the RSS feed to provide an easy-to-maintain auto-update mechanism for [some of] my projects). -- Martijn Coppoolse ___ 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] RSS feeds
On 11-2-2013 18:00, David Given wrote: It doesn't show up at all in Chrome. I went into my skin to add RSS links to the head elements, and then discovered they were already there... No, in Chrome you need an extension too, like I wrote earlier: You can install the RSS Subscription Extension (by Google) https://chrome.google.com/webstore/detail/rss-subscription-extensio/nlbjncdgjeocebhnmkbbbdekmmmcbfjd (or at http://goo.gl/XeLSB for short) Customising the head link will probably require some clever TH1 scripting to figure out what kind of page the user is looking at, and then generate the appropriate RSS feed URL, since the header is common for all pages. Yes, well, figuring out what kind of page we're on is not all that difficult; the default header already does that a lot (I don't really know how easy it is to match the start of a string in TH1, though). I was rather wondering how to get the ticket UUID for the current page... Is it worth having more obvious links in the main body text for the appropriate pages? I should think so, since none of the major browsers show a feed icon by default anymore (except Opera). But that's something that can already be included in the customizable pages for editing and viewing tickets. It might be nice to include them in the default templates, though. What parts (if any) are still missing? i still can't believe nobody proposed this feature a long time ago. Hm. A feed for a specific ticket report activity? Unfortunately I have no idea how to implement it. Well, I was expecting the timeline.rss to accept the same (basic) options as the timeline page, but I noticed that the ?y=e parameter (the list of events) isn’t recognized, as yet. I can't seem to make this work --- it just returns the same timeline view (the same as y=all). I see some code but don't follow how it works. Can you give me a sample URL? http://fossil-scm.org/index.html/timeline?y=e Seeing as this results in 4 entries, events aren't used very extensively by the Fossil team themselves, it seems... :-) But I can't figure out why the rss code doesn't isolate the events with event.type='e', either. Also: I notice that the RSS feeds link to the change description page (e.g. https://cowlark.com/calculon/info/75c4948da0fe0e5a970148e44870b4be3940922a). This is useful from a technical perspective, but not necessarily user friendly, at least for tickets, where linking directly to the ticket itself would be more appropriate. Any thoughts on this? That is true. I do like seeing what the specific changes were; it’s just that from a UX viewpoint it would be nice to have a link to the ticket itself feature more prominently; for example the ticket title linking to the 'view ticket' page. But that would require changing the 'info' page's output for ticket changes. -- Martijn Coppoolse ___ 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] RSS feeds
On 6-2-2013 1:03, David Given wrote: It lives! https://cowlark.com/calculon/tktview?name=9e114e9de0 https://cowlark.com/calculon/timeline.rss?tkt=9e114e9de0 Thanks a lot! I’d forgotten that the UUID is not the original ticket ID. http://www.fossil-scm.org/xfer/info/3f43ab397e Am I right when reading the following lines as erroring out when no ticket with that ID was found, then writing the HTML footer? http://www.fossil-scm.org/xfer/artifact/f7ea590658?ln=97-100 If so, wouldn’t it be better to return an empty (but valid) RSS feed? The error message could be included in the feed title or description. Or, provide a single entry in the RSS feed, which merely mentions the error message. If the error message is to be returned as-is, perhaps a different HTTP status could be issued, like 500 (instead of 200). Though I seem to remember that Fossil had trouble returning other status codes, or that the authors didn’t want to use HTTP status codes when the problem was not on the HTTP layer, but application-related (which this is, strictly speaking). It probably also wants changes to the view ticket code to add [RSS feed] to the menu, but that can wait until I see if anyone likes it. (The link on the Calculon site above is part of the skin.) Very nice! The (default) skin is probably where you’d want to include the link anyway. It might be nice to include an autodiscovery link for that specific ticket on the page as well: link rel=alternate type=application/rss+xml title=Ticket changes feed href=timeline.rss?tkt=9e114e9de0 / The Firefox extension appears to pick it up wherever the link is on the page; I don’t know about other browser( extension)s and feed readers. Officially[1], the link is supposed to go in the head/ section: does anybody know if the current ticket ID is available from TH1 when processing the header? [1] http://www.rssboard.org/rss-autodiscovery Of course, if the feed is about a specific ticket, then that could be reflected in the feed's title and description as well, like putting the ticket title in the feed's title, and the original ticket description in the feed's description. (I’m freewheeling a bit here: this would probably mean a lot more ticket-specific code). Thanks again, -- Martijn Coppoolse ___ 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] RSS feeds
Op 6-2-2013 19:53, Stephan Beal schreef: Normally i love Google Chrome but right now it tells me oops, there is no service available for this file type and refuses to do anything useful with the RSS feed. Aarrgghh. i don't have another browser on this machine and am too tired to fight with it. i'll check it out tomorrow from my dev machine. You can install the RSS Subscription Extension (by Google) https://chrome.google.com/webstore/detail/rss-subscription-extensio/nlbjncdgjeocebhnmkbbbdekmmmcbfjd (or at http://goo.gl/XeLSB for short) -- Martijn Coppoolse ___ 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] RSS feeds
Op 6-2-2013 18:46, David Given schreef: Checkin: http://fossil-scm.org/index.html/vinfo/d244452bda?sbs=1 I haven't figured out how to get the web interface to give me a diff of just one file against trunk, though. If you go to the file's timeline at http://fossil-scm.org/index.html/finfo?name=src/rss.c then, click the timeline box next to the last 'trunk' version of the file, and finally click on the timeline box next to your most recent version, you will be redirected to the following diff: http://fossil-scm.org/index.html/fdiff?v1=db44782246b1cv2=01e85ec41a53a Is that what you were looking for? It's also live on https://cowlark.com/calculon if you want to play with it. Looking good! Thanks a lot, David! -- Martijn Coppoolse ___ 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] RSS feeds
On Tue, Feb 5, 2013 at 11:29 AM, David Given d...@cowlark.com wrote: The code doesn't look too complicated. I presume I'd just need to add an extra URL parameter for the ticket id and then add another condition to the SELECT statement. I'll have a look. On 2013-02-05 11:37, Stephan Beal wrote: For tickets it's (unfortunately) more complicated than that because tickets can have custom fields, custom stati, etc. They are, in essence, completely configurable by the client, Not *completely*. The fields starting with `tkt_` are mandatory, and can’t be removed. The ticket-ID being one of them, adding it as a filtering parameter to the timeline.rss feed shouldn’t be problematic. Filtering on the non-mandatory fields would probably be a lot more problematic, indeed. -- Martijn Coppoolse ___ 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] Improvements to side-by-side diff
On 17-12-2012 8:33, Baruch Burstein wrote: Another suggestion: Since visual diffs are always for text files (I think), it doesn't make much sense to mark partial words as changed. If the whole word is not unchanged, then the whole word is changed. I am referring to things like line 73817 on the left in the fourth link below. Respectfully disagree. The line you refer to works perfectly fine; I see no reason to reduce granularity to word level, and every reason to keep it the way it works now: if a word is partially changed, I like to see _what_ part was changed. IMO, diff highlighting should highlight changes, not words. I can recognize words by myself just fine; seeing what exactly changed is what I need the highlighting for. Also, in my case (at least), visual diffs are usually for text files representing source code. In code, especially for a case-sensitive language, a change to a single character can be crucial. Reducing highlighting to only indicate changes per word makes it more difficult to see this. On Sat, Dec 15, 2012 at 4:16 AM, Richard Hipp d...@sqlite.org mailto:d...@sqlite.org wrote: Reposted from fossil-dev: OLD: http://www2.sqlite.org/src/ci/52e755943f?sbs=1#chunk1 NEW: http://www.sqlite.org/src/ci/52e755943f?sbs=1#chunk1 OLD: http://www2.fossil-scm.org/fossil/fdiff?v1=955cc67ace8fb622v2=e2e1c87b86664b45#chunk24 NEW: http://www.fossil-scm.org/fossil/fdiff?v1=955cc67ace8fb622v2=e2e1c87b86664b45#chunk24 -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎɟı ˙pɐǝɥ ʎɯ uo buıʇʇıs uǝɥʍ ǝuıɟ ʇsnظ uʍop ǝpısdn pɐǝɹ uɐɔ ı ¡ʎןןıs ǝq ʇ’uop -- Martijn Coppoolse ___ 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] Improvements to side-by-side diff
On 17-12-2012 10:27, Paolo Bolzoni wrote: Maybe joining both ideas? Like coloring the whole word of a more neutral color and the difference with the usual bright color? I think it would be the best as I agree with both point of views. That would work for me. :-) -- Martijn Coppoolse ___ 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] Problem on website with non-root repository
Hello Gautier,
I have multiple repositories on a server which hosts other things (like
internal tools accessible via a web browser, etc.), so I setup nginx with
the reverse proxy module, my fossil server is accessible via /fossil/, but
all media, css, etc. are seeked at /, they are not found, is there a place
to set the root of the server, or is this a lack/bug?
The HTML links generated by fossil always assume it's sitting in the
root path of the web server. AFAIK, there's no way to tell Fossil to
prefix an extra path to the root.
Perhaps that could be added as an extra option for the fossil http
command, I don’t know. (I have no idea what big an impact it would have
-- though seeing as 'fossil http' with a folder already prefixes the
folder name to the path, perhaps it wouldn’t be such a humongous change).
In the meantime, I see two possible workarounds.
1. Personally, I’ve created a separate subdomain which points to the
same server, and set up nginx to proxy_pass all requests for the fossil
subdomain to fossil (which runs on a different port number).
2. You could also try to get nginx to rewrite the HTML that's returned
to the client using HttpSubModule[1] or even NginxHttpSubsModule[2], and
prefix your extra root path to any link in your URL starting with
double-quote and slash (/).
[1] http://wiki.nginx.org/HttpSubModule
[2] http://wiki.nginx.org/NginxHttpSubsModule
For example:
location / {
sub_filter '/' '/fossil/';
sub_filter_once off;
}
Of course, this assumes that links will always be in the form a
href=/..., or img src=/..., or script src=/...; this example
doesn't handle a href='/...', which is just as valid HTML.
Also, I noticed that Chisel[3] does manage to host repositories on a
longer path, without breaking the HTML generated by fossil, so I’m
assuming he does some HTML rewriting as well. You could check out the
source code[4] to see how he does that (though I do note that he’s using
Apache, and not nginx).
[3] http://chiselapp.com
[4] http://chiselapp.com/user/james/repository/chisel/
HTH,
--
Martijn Coppoolse
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Config pull ticket doesn't apply table definition changes?
Hi all, Yesterday I stumbled on what I think is a bug (albeit a minor one, since there's a fairly easy workaround). It would seem that config pull ticket doesn't apply the changes in the definition of the ticket table. Steps to reproduce -- On a remote repository, I changed the definition of the ticket table using the web interface: - added a field, and applied the changes. - changed the ticket view and edit pages to include the new field. - altered an existing report to include the new field. - Tested by creating a new ticket, and editing an existing one. In both cases, it shows up fine in the report. Then, on my local repo: - (cli) fossil config pull ticket - (web) tried to edit a ticket = error: 'unknown field' - (web) tried to view the list of tickets = error: 'unknown field' Workaround -- - (web) admin/ticket/table page - click on 'Apply Changes' - then editing a ticket or viewing a report works From what I can see, clicking 'Apply Changes'[1] on the ticket table page, causes fossil to call [ticket_schema_check] and then [ticket_rebuild]. configuration pull/sync ticket should probably do that as well, if a ticket-table has been received. [1]: http://fossil-scm.org/index.html/artifact/a63d053af5cc76ef22b8f8018a36dcef35033420?ln=169-170 [ticket_schema_check]: http://fossil-scm.org/index.html/artifact/583b882efd0979b42e0bd73de3f9aa19e1851677?ln=627 [ticket_rebuild]: http://fossil-scm.org/index.html/artifact/583b882efd0979b42e0bd73de3f9aa19e1851677?ln=276 Unfortunately, my C skills aren't quite sufficient to provide a patch. :-\ -- Martijn Coppoolse ___ 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] Ticket contact info garbled
I’ve created a ticket on a publicly served repository, and entered a contact e-mail address for the ticket. When I edit the ticket, I can see the e-mail address fine. After synchronizing my local repository, viewing the ticket using `fossil ui` locally, the ticket shows up identically, except that the contact is now a seemingly random hexadecimal string, and not the e-mail I entered. How is the contact info garbled? I assume it’s being encrypted using some other ticket-related info, but I can't figure out why it would decrypt to something else here... Op 29-8-2012 11:57, Richard Hipp schreef: This is a feature, not a bug. Information which some people consider to be sensitive (such as the contact-information) is not stored in the database directly. Instead, a SHA1 hash of the information is stored. There is a separate table in the repository database, the CONCEALED table, that stores a mapping from these hashes back to the original text. That confirms my suspicion. Kudos for not storing sensitive info as-is, by the way! Hardly a month goes by these days that there’s no news about some website that’s been hacked where usernames and passwords were stored as-is. Only authorized users are allowed to clone or sync the CONCEALED table, and hence only authorized users are able to see the sensitive information. Thanks for the explanation! So what determines who is authorized? My remote-url includes a username and password with developer permissions for the remote repository, so I would have expected the concealed info to come along when syncing. This doesn’t seem to have happened, however. I’ve now manually copied the relevant record from the remote server’s repository, which fixed the immediate problem. I’ll try to see if I can replicate the issue. -- Martijn Coppoolse ___ 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] Ticket contact info garbled
Richard Hipp drh@... writes: RH Only authorized users are RH allowed to clone or sync the CONCEALED table, and hence only authorized RH users are able to see the sensitive information. MC So what determines who is authorized? RH The user doing the syncing needs to have e permissions in their login. RH Also, the CONCEALED table is not automatically synced - you have to run RH fossil config pull email. Ah, that’s the final piece of the puzzle I was missing. I now removed the manually inserted record from the concealed table, did a fossil config pull email, and the contact info showed up fine. Thanks a lot! -- Martijn Coppoolse ___ 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] Is there a way to make the web server follow symlinks?
Stuart Rackham srackham@... writes: I'm displaying documentation using the Embedded Documentation feature, the web server returns the contents of symlinks, is there a way to make the web server follow symlinks? What is the value of the allow-symlinks setting? From the help: allow-symlinks If enabled, don't follow symlinks, and instead treat (versionable) them as symlinks on Unix. Has no effect on Windows (existing links in repository created on Unix become plain-text files with link destination path inside). Default: off IIRC, this would suggest that allow-symlinks is ON in your repository. This means that the target of the symlink won't present in the repository. And since —AFAIK— Fossil's web server only serves files from inside the repository, it won't serve files behind a symlink. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Ticket contact info garbled
Hello all, I’ve created a ticket on a publicly served repository, and entered a contact e-mail address for the ticket. When I edit the ticket, I can see the e-mail address fine. After synchronizing my local repository, viewing the ticket using `fossil ui` locally, the ticket shows up identically, except that the contact is now a seemingly random hexadecimal string, and not the e-mail I entered. How is the contact info garbled? I assume it’s being encrypted using some other ticket-related info, but I can't figure out why it would decrypt to something else here... -- Martijn Coppoolse ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Sync using proxy: unknown repository?
Hi all, I’ve got Fossil listening to a non-standard port on a server somewhere (http://domain.com:8080/repo). From within our office’s network, I can’t directly connect to outside URLs on nonstandard ports (i.e. other than 80 for http, or 443 for https). Fortunately, we do have a proxy server, which does allow this. When I tried syncing the repository using a direct connection, fossil times out and fails (as expected). Server:http://u...@domain.com:8080/repo Bytes Cards Artifacts Deltas Sent:5385115 0 0 C:\MC\Run\Util\Console\fossil.exe: cannot connect to host domain.com:8080 Total network traffic: 0 bytes sent, 0 bytes received Then I did fossil set proxy fwdh2:8080 (since fwdh2:8080 is our network's proxy server), but now `fossil sync` gives the following error: Server:http://u...@domain.com:8080/repo C:\MC\Run\Util\Console\fossil.exe: unknown repository: fwdh2:8080 Am I doing something wrong? If so, what should I do instead? Or is Fossil somehow interpreting my proxy as a repository name? (Note that I’m running this command from the checkout directory; with `fossil set proxy off`, it tries to connect to the correct remote-url). Or is Fossil running into some other problem, and somehow displaying the wrong error message? FYI: I’m using the official Windows release: This is fossil version 1.23 [957b17af58] 2012-08-08 11:25:57 UTC Thanks for any info, hints or pointers! -- Martijn Coppoolse ___ 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] Sync using proxy: unknown repository?
Thank you for your reply. On 13-8-2012 13:13, Richard Hipp wrote: Have you read about accessing Fossil through a proxy? http://www.fossil-scm.org/fossil/doc/trunk/www/quickstart.wiki#proxy Yes, that's where I read about the proxy settings. It’s specifically when I try to _use_ a proxy that I get this unexpected error: unknown repository: C:\Proj32\Vragenlijst\srcfossil sync --proxy fwdh2:8080 returns the following: Server:http://u...@domain.com:8080/repo C:\MC\Run\Util\Console\fossil.exe: unknown repository: fwdh2:8080 This error suggests that Fossil is somehow interpreting the proxy-url as a repository. Or is there something obvious I’m missing? Thanks in advance, -- Martijn Coppoolse Then I did fossil set proxy fwdh2:8080 (since fwdh2:8080 is our network's proxy server), but now `fossil sync` gives the following error: Server: http://u...@domain.com:8080/repo C:\MC\Run\Util\Console\fossil.exe: unknown repository: fwdh2:8080 Am I doing something wrong? If so, what should I do instead? Or is Fossil somehow interpreting my proxy as a repository name? (Note that I’m running this command from the checkout directory; with `fossil set proxy off`, it tries to connect to the correct remote-url). Or is Fossil running into some other problem, and somehow displaying the wrong error message? FYI: I’m using the official Windows release: This is fossil version 1.23 [957b17af58] 2012-08-08 11:25:57 UTC Thanks for any info, hints or pointers! -- Martijn Coppoolse _ fossil-users mailing list fossil-users@lists.fossil-scm.__org mailto:fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:__8080/cgi-bin/mailman/listinfo/__fossil-users http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org mailto:d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Martijn Coppoolse ___ 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] Sync using proxy: unknown repository?
Lluís Batlle i Rossell viric@... writes: I once had problems because the proxy URL I used didn't contain http://;. Bingo, that’s it! Something simple after all... Though Fossil does report the wrong error message: it says unknown repository, whereas wrong proxy protocol would be nearer the mark... Thanks a bunch, Lluís! I was using the http_proxy envvar though. I expect the result will be the same whether you use the envvar, the repository’s setting or the command-line parameter. :-) Thanks again, -- Martijn Coppoolse ___ 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] problem with illegal characters
Matt Wellandestifo...@gmail.com wrote: IMHO a more viable philosophy is to use documentation and methodology to make seamless interoperability between Windows and Unix/Linux possible for teams that need it. Otherwise where possible and where the code cost is not too high, independently make fossil work perfectly on Unix and perfectly on Windows. Agree. Out of curiosity, is there someone that's already followed Richard's advice and created their own branch of fossil, disabling just those three lines? If so, do they often run into trouble with the mentioned files? I keep reading about potential issues if [ and ] were to be allowed, but the only *actual* issues I’m seeing are due to the fact that [ and ] are _not_ allowed. It would be nice to have that balanced by someone who's already tried it. (I may try it at some point in the future, but haven’t got too much time for it atm). Fossil does work perfectly both on Unix Windows, but having those funky characters (space included) in a filenames which are meant to be kept under DVCS is *bad practice* both on Unix Windows. Why is that a bad practice? Because there's programs (like Fossil) that won't let you work with them? As I wrote earlier, not being able to have space in a tag name is much severe limitation, but I do not hear many people complain about (g)it. I reckon you don't hear so much people complain about spaces in tags because it *isn't* a more severe limitation than disallowing (otherwise perfectly valid) characters in file names. Tags are something you add once you're using your SCM; also, you're free to decide what kind of tag you want to use. Programmers have been circumventing lack of spaces in identifiers for ages, by using underscores, dashes, or by playing on capitalization. Filenames, on the other hand, are often pre-existing, and you don't always have the luxury of picking and choosing, since they are not always created by you; worse, sometimes you don't even have the possibility of imposing limitations on the characters used. We've already seen that someone who wants to store OOXML files in a 'diff'-able way, will have to jump through extra hoops to get the [Content-Types].xml file into fossil. I also run into this issue every now and then, because someone in our office once long ago decided to timestamp historical versions with the time and dates between square brackets. Our office's current VCS (PVCS/Serena ChangeMan) has no trouble at all with [ and ], but then we routinely use the GUI interface. I haven't used their command line interface extensively, so I don't know how it fares then. Then again, it's on Windows, and AFAIK [ and ] have no special meaning for cmd.exe -- certainly not if you quote the file names (which is a good idea anyway, since spaces do occur from time to time). Yours, -- Martijn Coppoolse ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
