Re: guile gnome-terminal macros take 1

gnome_util_home_file prepends ~/.gnome/ onto the filename, not just ~/.

You may want a default script file if the module won't work without a
script (most programs come with defaults that can be changed by the user
-- it is much easier to change an existing file than to create a new
config file in many cases).

James Henstridge.


On Sun, 28 Feb 1999, Maciej Stachowiak wrote:

> James Henstridge wrote:
> > 
> > First, you probably want to check if the user has a customised script in
> > place.  You should be able to get the filename with:
> >   fname = gnome_util_home_file("gnome-terminal.scm");
> > 
> Presumably you'd want a personal config file of this sort to start with
> a dot, i.e. ".gnome-terminal.scm" or something.
> > Then if it doesn't exist get the system wide config file:
> >   if (!g_file_exists(fname)) {
> >     g_free(fname);
> >     fname = gnome_datadir_file("gnome-terminal/script.scm");
> >   }
> It's also a good idea, I think, to make a system-wide config file
> have a name resembling that of an intended user config file, e.g.
> gnome-terminal/gnome-terminal.scm or 
> gnome-terminal/system.gnome-terminal.scm or something like that.
> I have to admit also that I am confused why a default config file
> is necessary in this case - you only need one if you want to use
> the gnome-terminal scripting extension, which you presumably want
> to do only if you want to customize your terminal. The idea of
> "default customizations" seems specious.
>  - Maciej
> -- 
> To unsubscribe: mail with "unsubscribe"
> as the Subject.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]