[Top][All Lists]

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

Re: [PATCH 2/2] "auto" keyword in gfxmode and gfxpayload specification

From: Robert Millan
Subject: Re: [PATCH 2/2] "auto" keyword in gfxmode and gfxpayload specification
Date: Mon, 24 Aug 2009 00:42:23 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Aug 23, 2009 at 01:01:16PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >
> > Ah, I see.  Yeah, we really should contemplate into detecting native
> > resolutions.
> >
> > But is there any reason we don't want this behaviour when gfxmode was
> > not set?  If we can avoid an additional keyword, what we do fits better
> > with what the user would expect.
> When gfxmode wasn't set it's treated like if it was set to "auto".I
> feel like having keyword "auto" can be handy in situations like
> gfxpayload=keep,auto
> Which with payloads needing working graphics would mean "use current
> graphics mode if we're already in one, otherwise autodetect"

I would interpret "keep" as "keep what we have now".  If we're in text mode,
then "keep text mode".

I think native resolution detection is an opportunity for us to simplify the
user interface, rather than add more options to it.

Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]