On Mon, 18 Apr 2011 15:59:41 +0200 Arjen Markus <arjen.mar...@deltares.nl> wrote:
> On 2011-04-18 15:23, Konstantin Khomoutov wrote: > > On Mon, 18 Apr 2011 09:11:04 -0400 > > Martin Gagnon <eme...@gmail.com> wrote: > > > >>> I have a few comments (and not realy much more than that) on the > >>> way Fossil implements the editing of commit messages: > >>> > >>> - I noticed that the choice of editor seems to be a global setting > >>> in the repository. At least, that is the behaviour I observe > >>> with one repository (but that may be peculiar to that particular > >>> project). As editors are a highly personal choice, I would > >>> expect this to be a user-defined setting. > >> if you call fossil settings from outside a checkouted repository, > >> or if you specify "-global" to the settings subcommand, it will be > >> saved globally for the current user.. > >> > >> it is saved on a $HOME/.fossil on unix sytem and on > >> %HOME%\AppData\_fossil on windows (or something like that) > > Heh, exactly what I discovered right now looking at the contents of > > that _fossil config file and was about to post. ;-) > > Thanks for correcting. > > > > To be more precise, on Windows it's "%appdata%\_fossil". > like I said it may be the way I use this one repository in cooperation > with one other developer. It is no problem for me at the moment, I can > work my way around it ;). > > As for environment variables, I have no trouble setting them, but I do > forget them from time to time. Again not something that deeply > troubles me. Sorry, but I'm somewhat lost now. I interpreted your original question as that you were asking if it would be feasible to implement per-user settings in fossil to set the commit message editor. We then figured out that what are called "global" settings in fossil are, in fact, per-user settings so you could set your preferred editor using C:\> fossil set editor notepad.exe -global This setting would update your personal %appdata%\_fossil file which does not affect other developers and it is global in the sense that it applies to all your fossil repositories. What do you need to work around then? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
