On Tue, Jan 28, 2025 at 08:25:57AM -0500, Greg Wooledge wrote:
> On Tue, Jan 28, 2025 at 07:51:44 -0500, Haines Brown wrote:
> > On Sun, Jan 26, 2025 at 07:04:44PM +0000, Darac Marjal wrote:
> > > So, my reading of that could be that *.mlterm/main* should read:
> > >
> > > bg_color=FAF0E6
> > > geometry=128x30
> > >
> > > and *.mlterm/font* should read:
> > >
> > > DEFAULT=monospace-20
>
> > Yes, the problem is that the configuration has no effect. My .mlterm/main
> > file constains:
> >
> > geometry = 128x30
> > bg_color = #FAF0E6
> > bg_color = FAF0E6
> >
> > and my font file has:
> >
> > DEFAULT = monospace-20
>
> Do you see the difference between what you wrote, and what Darac wrote?
Yes retarding the spaces around the equal sign. Based on my limited
experiene I'm surprised it makes a difference.
But that is not the real problem. For example, Darac said that the
configuration for fonts is:
DEFAULT=*/font/
What is the asterisk there for? Is the forward slashes around the
workd "font " means to indicate it is variable? I had assumed so. In
any case in my font file I have the line
DEFAULT=monospace-20
This has no effect. My main file has the line bg_color=red and this has no
effect either.
My default mlterm window linen background, which is what I want. If I
use any command line options, the background turns white. This
suggests to me there is a configutatioan file somewhere that ddoes not
yield to what is in the files in ~/.mltemp
>
