Thanks for the page, Gilles. But the formatting doesn't work so well. And I don't know how you want it to look so I can't fix it.
Do you know that you can view the formatting of these kinds of pages without checking them in? Just put the file (with a ".wiki" suffix) somewhere in an open checkout, then run "fossil ui". Enter " http://localhost:8080/doc/ckout/..."; as the URL where "..." is replaced by the filename. The key component in the URL is the "ckout" term which tells Fossil to render the files as they appear in the check-out on disk, not as they appear in the repository. The markdown language is also now supported. Just use the suffix ".md" instead of ".wiki". On Thu, May 23, 2013 at 4:15 PM, Gilles <gilles.gana...@free.fr> wrote: > On Thu, 23 May 2013 13:34:17 -0400, Richard Hipp > <d...@sqlite.org> wrote: > >Copy/pasting the text to this mailing list is one way. Or email the > >contribution to one of the many Fossil committers is another approach. > > Here it is. It's a way to access Fossil from Microsoft's Express IDE, > at least to use common commands: > > ------------------------------ > Integrating Fossil in the Microsoft Express 2010 IDE > > The Express version of Visual Studio doesn't support add-in's and > plug-in's, but it's not an issue since it's still possible to use > Fossil through the External Tools menu and Fossil is a CLI application > anyway: > > 1. Tools > Settings > Expert Settings > > 2. Tools > External Tools, where the items in this list map to > "External Tool X" that we'll add to our own Fossil menu later: > 1. Rename the default "[New Tool 1]" to eg. "Commit" > 2. Change Command to where Fossil is located eg. "c:\fossil.exe" > 3. Change Arguments to the required command, eg. "commit -m". The > user will be prompted to type the comment that Commit expects > 4. Set "Initial Directory" to point it to the work directory where > the source files are currently checked out by Fossil (eg. > c:\Workspace). It's also possible to use system variables such as > "$(ProjectDir)" instead of hard-coding the path > 5. Check "Prompt for arguments", since Commit requires typing a > comment. Useless for commands like Changes that don't require > arguments > 6. Uncheck "Close on Exit", so we can see what Fossil says before > closing the DOS box. Note that "Use Output Window" will display the > output in a child window within the IDE instead of opening a DOS box > 7. Click on OK > > 3. Tools > Customize > Commands > 1. With "Menu bar = Menu Bar" selected, click on "Add New Menu". A > new "Fossil" menu is displayed in the IDE's menu bar > 2. Click on "Modify Selection" to rename it "Fossil", and > 3. Use the "Move Down" button to move it lower in the list > > 4. Still in Customize dialog: In the "Menu bar" combo, select the new > Fossil menu you just created, and Click on "Add Command...": From > Categories, select Tools, and select "External Command 1". Click on > Close. It's unfortunate that the IDE doesn't say which command maps to > "External Command X". > ------------------------------ > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp 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
