Re: default & double terminal options

[Ethan M. <merritt@u.washington.edu>]

On Thursday 24 August 2006 12:01 pm, Petr Mikulik wrote:
> > I have no idea what "unset termoptions" is supposed to mean.
> > Could you please explain?
>
> Here is the previous email (corrected):
>
> As I remember, the need for an 'unset termoptions' or 'set
> termoptions reset' or 'set termoptions default' 

"set term default"   is 100% better than "unset termoptions".

If nothing else, it will work automatically if the terminal
in fact supports "set term <foo> default"


<begin rant>
  When/why was there a change to the syntax "unset <foo> <baz>"?   

  It is IMHO much uglier and harder to work with than
  "set <foo> no<baz>".
  The latter makes it clear that you are toggling option <baz>.
  Besides which, there is no verb "unset" in the English language.
  The usual antonym of 'set' is either 'clear' or 'reset'.
<end rant>




> command emerged some 
> years ago for the first time. It came from the octave community: how
> to reset terminal options to the default status after a script has
> changed them on its own.
>
> Shouldn't we provide a "dummy" command 'unset termoptions' (named
> under any of the above synonyms) right now, with a proper
> implementation for postscript only (if possible), and with
> implementation for other terminals after 4.2?
>
> ---
> PM

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle WA