In article <[EMAIL PROTECTED]> you write:
>> "jw" == joost witteveen <[EMAIL PROTECTED]> wrote:
>
>jw> do you want me to
>jw> 1 move xosview to 'contrib', and stop maintaining it
>jw> 2 just go on maintaining a broken xosview?
>
>IMHO, you should stick with 1. There are other things that m
> "jw" == joost witteveen <[EMAIL PROTECTED]> wrote:
jw> do you want me to
jw> 1 move xosview to 'contrib', and stop maintaining it
jw> 2 just go on maintaining a broken xosview?
IMHO, you should stick with 1. There are other things that may do the
same thing xosview is supposed to do.
On Mon, 26 Aug 1996, joost witteveen wrote:
> > Xosview only reads the file XOSView (and ~/.Xdefaults) when evaluating
> > its X resources. It does this by doing all the reading by foot (calling
> > XrmGetFileDatabase() etc.).
> > This is IMO the wrong way to do it; the application should use
>
>> Xosview only reads the file XOSView (and ~/.Xdefaults) when evaluating
>> its X resources. It does this by doing all the reading by foot (calling
>> XrmGetFileDatabase() etc.).
>> This is IMO the wrong way to do it; the application should use
>> XtGetApplicationResources() (as xsysinfo does i
>
> Package: xosview
> Version: 1.3.2-6
>
> Xosview only reads the file XOSView (and ~/.Xdefaults) when evaluating
> its X resources. It does this by doing all the reading by foot (calling
> XrmGetFileDatabase() etc.).
> This is IMO the wrong way to do it; the application should use
> XtGetApp
Package: xosview
Version: 1.3.2-6
Xosview only reads the file XOSView (and ~/.Xdefaults) when evaluating
its X resources. It does this by doing all the reading by foot (calling
XrmGetFileDatabase() etc.).
This is IMO the wrong way to do it; the application should use
XtGetApplicationResources()
6 matches
Mail list logo