[fossil-users] Cannot set remote-url password when running Fossil non-interactively
Hi, In my application (Fuel) users can set the default remote url for their repositories. The application spawns Fossil with the "remote-url " parameters. It appears however that when urls contain passwords, Fossil does not store the provided password. I think that the problem lies with the way that Fossil handles urls when spawned non-interactively, specifically all password saving is prevented in Fossil's url.c since "isatty(fileno(stdin))" is false when spawned via another application. Perhaps passwords could be explicitly stored when run non-interactively, or some other mechanism could be introduced. Thanks Kostas ___ 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.exe: Catching errors?
Hi, When I was implementing Fuel (my take on a Fossil GUI), one of the problems I was facing was not so much catching the success or failure of a command but rather capturing and handling the interactive queries that fossil asks while performing an action (eg. inconsistent EOLs, empty commit messages etc.) occasionally hindered by the fact the query format was not always consistent. Essentially this means that while Fossil is spawned executing a command, you need to keep parsing the text output in order to detect and handle these cases and, for example, present a dialog box to the user or whatnot. If not fossil will hang in the background waiting for a reply. Another issue the use of stdin/out/err. On Windows since all i/o goes via the console, all text goes through the encoding conversion via codepages. In many cases the fossil output parsing would fail due to incorrect conversion of filenames with international characters, which were not in the current codepage. Another extra problem with spawning a process is that each OS has different limits for command-line arguments. This was a problem for the initial check-in where the user wants to add a lot of new files to a repository but would hit that limit on Windows. Perhaps some kind of method could be added to fossil for driving it non-interactively. Ideally it would bypass stdio/err and allow talking to a fossil process via a socket or something similar, using a protocol (JSON?) that also supports the interactive queries that fossil occasionally requires. Filenames should be expressed in a single consistent encoding (say utf-8). Cheers On 8 June 2013 00:17, tpero...@compumation.com tpero...@compumation.com wrote: I wrote a simple GUI for Fossil using .NET for myself. After reviewing the source code for the commands I used, I concluded that all errors were written to stderr. By redirecting and displaying stdout / stderr I was able to provide feedback as to the success or failure of a command. Also, fossil.exe exits with zero if all is well, otherwise non-zero: fossil_exit(0); or fossil_exit(1); Tony Perovic Compumation, Inc. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Gilles Sent: Friday, June 07, 2013 6:00 AM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Fossil.exe: Catching errors? Hello I'd like to write a GUI front-end for fossil.exe to avoid having to open a DOS box and type Fossil commands. Does someone know of a way to catch errors, if any, instead of parsing the output returned by the application to figure it out? Thank you. ___ 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 on Android or compiling with tcc?
I'm running an Arch linux chroot on my tablet. Compiling fossil from source on the tablet worked fine for me. No patching necessary. ___ 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] Status of GUI for Windows?
Yes, that is what they mean. The file status essentially matches the output of the the fossil ls -l command (similar to the status command for those coming from subversion) Ignored files, are files that you have told fossil to explicitly ignore, for example temporary files or binaries you would never want to add to source control. On 20 April 2012 23:35, Gilles gilles.gana...@free.fr wrote: On Fri, 20 Apr 2012 22:51:45 +0900, Kostas Karanikolas karaniko...@gmail.com wrote: A reason why files are not being displayed could be that a view filter for some kind of file is active (Unknown files for example). Check the View menu. I have a new version coming up soon, so this a good time for bug reports or even feature requests. If you are still having problems, feel free to contact me directly. Thanks Kostas, that was the problem. Could you confirm/explain the options in the View menu? Modified: Files monitored by Fossil (ie. that have been added and committed to the Fossil repo) that have been modified since the repo was opened Unchanged: Files that live in the repo, ie. not modified since opening the repo Unknow: Will scan the whole filesystem starting at the root of where the repo file lives. This is what you should choose if you want to adding and committing folders/files to the repository. If there are lot of folders and files, it could take a long time and freeze the UI in the meantime. Also, since the four options in the View menu are cumulative (ie. you can have all of them checked simultaneously) the scan will occur every time if you leave that option checked Ignored: Don't know what this does. ___ 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] Status of GUI for Windows?
On 20 April 2012 23:55, Matt Welland estifo...@gmail.com wrote: On Fri, Apr 20, 2012 at 6:51 AM, Kostas Karanikolas karaniko...@gmail.com wrote: Hi, I'm the developer of Fuel. A reason why files are not being displayed could be that a view filter for some kind of file is active (Unknown files for example). Check the View menu. I have a new version coming up soon, so this a good time for bug reports or even feature requests. If you are still having problems, feel free to contact me directly. I just tried Fuel and it looks like it could be very useful. The first problem I ran into is that I can't seem to open up an already opened repo via samba. Does Fuel recognize the _FOSSIL_ file? I don't think it is related to samba. I was able to open a repo where the .fossil file was in the top directory. I think two ways of opening are needed: 1. Open an already 'opened' area, Fuel should be able to find the .fossil file by inspecting the _FOSSIL_ file. The .fossil file may be outside the opened repo area. This will be addressed in the next release. 2. Open a .fossil file and create an open area but give the user an opportunity to browse to and or create the area to be used. Do you mean allow creating a workspace in a folder different than the one that holds the fossil file? Also, you may be amused to know that I went to check my laptop power cable and spent a few seconds trying to figure out a) why I wasn't plugged in and b) what had changed on my system to give me the new battery icon until I moused over the icon and realized it was Fuel. I guess I'd prefer something other than a battery as the default icon. How about a fuel canister with a fossil, you know fossil fuel, was that your original intent with the name? :) I agree, the icon is a bit misleading, but finding a good, consistent, high-res icon set that matches the semantics of source control is not easy! Truth be told this icon has grown on me, I tend to think of it as a fuel cell now. Yes Fuel is a lame pun on fossil fuel. On 19 April 2012 19:12, Gilles gilles.gana...@free.fr wrote: Hello I find typing commands in a DOS box not as convenient as right-clicking on a file/folder in Windows Explorer, to the point where I don't use Fossil as often as I'd like when working on scripts/programs and would like to keep tracks of things. So I wanted to check what the status is on the existing GUI projects. Googling for fossil gui returns the following projects: - (Java) http://code.google.com/p/jurassic-fossil/ - (.Net) http://repository.mobile-developers.de/cgi-bin/ikoch/sharpfossil/ - (Qt) http://code.google.com/p/fuel-scm/ Apparently, 1. SharpFossil is just a library, the application is WinFossil, but it doesn't seem to be under actual development 2. Fuel-SCM seems like the most advanced and (I don't like Java, and find .Net apps too slow to load; I'd rather use a native Win32 application, but Qt will have to do), but I can't figure out what to do once I hit File Open my.repo (right side is blank) Is this correct? Are there other tools I should know about? Thank you. ___ 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] Annoucement: Fuel GUI Client
Since there's been some interest lately in alternative GUI tools for Fossil I'd like to take this opportunity to announce Fuel a cross-platform GUI client for Fossil. Binaries for Windows and OSX are available at: http://code.google.com/p/fuel-scm/ Fuel itself does not embed any Fossil code, it just drives Fossil via the command line. As such, the above packages include a Fossil executable to allow users to start using Fossil quickly without having to download files from multiple sources. The OSX version includes the official V1.19 binary, but on Windows I've had to build Fossil from source in order to include support for SSL. If distributing custom binaries (especially those combining legally unclear encryption) is a problem, let me know and I will replace the binary with the official one. Unix users are encouraged to build from source. The code is available on Chisel at http://chiselapp.com/user/karanik/repository/fuel/ The only dependency for building is Qt. Please give it a try and let me know what you think (Apologies if you received this message more than once) ___ 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] Annoucement: Fuel GUI Client
On 8 October 2011 20:04, Gilles gilles.gana...@free.fr wrote: I unzipped and launched 0.9.4 on Windows, and it displays the familiar Fuel.exe has encountered a problem and needs to close. We are sorry for the inconvenience. [...] Please tell Microsoft about this problem.. Are there some additional files/steps I should install/perform before running Fuel? All the required files are included in the archive, and everything should just work. Has your machine been fully updated via WindowsUpdate? Especially any updates relating to the Microsoft Visual C Runtime library (MSVCRT.dll). Also can you try removing the included fossil.exe and see if the app starts? Any more information regarding the crash would really help me to track down any issues, for example any information displayed in the windows crash dialog. Feel free to contact me directly, to avoid flooding the mailing list. If this proves to be problem for other people as well, I could provide a statically-linked binary for Windows users. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
